Repository navigation
fix: expose an active native Codex configuration receipt - #203
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The native Codex configuration endpoint returned raw configuration without a receipt that diagnostic clients could bind to a running configuration epoch. Its getter could also return a cancelled snapshot.
The existing GET now returns four
X-Sub2API-Codex-*headers with native hosting mode, configuration version, the SHA-256 of the exact response bytes, and runtime generation. Raw JSON andCache-Control: no-storeare preserved. The lifecycle lock selects one snapshot, verifies its persisted metadata and byte hash, and rejects stopped, cancelled or inconsistent state with a fixed 503 response and no receipt or raw configuration. The read path does not rebuild settings, change generation or acquire a business lease; retired installations remain disabled.Validation: five direct service methods and two HTTP contract methods passed, covering exact bytes and copying, full int64 versions, shutdown and cancellation, persisted-fence changes, opaque errors and header removal. Independent review checked the lifecycle and multi-query fence boundary; formatting and documentation checks passed. Existing business-test results are reused locally, with normal required CI retained. No model calls or production changes.
This is the user-approved compatibility follow-up to #202. The published
v0.2.8-codexrip.5artifact remains unchanged; the receipt correction will ship in a new immutable version before the unified production deployment.