A valid native Codex completion review can be admitted and finish successfully, then lose its workflow completion because storing the bounded result pushes the request beyond the request-state limit.
Observed with the qualified ca-codex0.15.5 package at PR918 head73ebdbb28f18ddc01ff0a9d645b028ee2d9dd84a:
- A fresh default-role native V1 child was associated with the exact parent turn, call ID and child UUID.
- Its first final passed the installed closed decision parser, including the completion digest and all seven separate task obligations.
- The genuine immutable observation was written successfully; its bytes exactly match the closed observation derived from that first final.
- The completed request serialized to1,052,491 bytes, above MAX_STATE1,048,576.
_save raises INVALID_AUTHORITY_STATE: request state would exceed its bound before retaining the observation reference and payload.
- The outer native lifecycle handler reloads the last RUNNING state and records terminal
failed-native-review-lifecycle. Publication then reports AUTHORITY_NOT_COMPLETE: successful observation is absent, despite the retained immutable observation.
The frozen input manifest alone is approximately1,009,486 bytes. Trimming redundant supporting metadata leaves only259 bytes of headroom for this particular final, while the protocol permits a decision up to65,536 bytes. It is not a reliable correction.
Expected: preserve complete source/evidence checks and all current authority boundaries, but account for bounded completion growth before launching the reviewer. A request that passes admission should retain a valid first stop through publication, or be rejected before expensive review. Missing/tampered context, over-budget inputs, terminal rejections and legacy recovery restrictions must remain fail closed.
Add an isolated native lifecycle regression at the state boundary, plus admission and integrity negatives. Preserve the failed production attempt and original observation; do not synthesize a new receipt or replay the rejected first stop. Fix work is continuing in PR918; no merge or release is requested.
A valid native Codex completion review can be admitted and finish successfully, then lose its workflow completion because storing the bounded result pushes the request beyond the request-state limit.
Observed with the qualified ca-codex0.15.5 package at PR918 head73ebdbb28f18ddc01ff0a9d645b028ee2d9dd84a:
_saveraisesINVALID_AUTHORITY_STATE: request state would exceed its boundbefore retaining the observation reference and payload.failed-native-review-lifecycle. Publication then reportsAUTHORITY_NOT_COMPLETE: successful observation is absent, despite the retained immutable observation.The frozen input manifest alone is approximately1,009,486 bytes. Trimming redundant supporting metadata leaves only259 bytes of headroom for this particular final, while the protocol permits a decision up to65,536 bytes. It is not a reliable correction.
Expected: preserve complete source/evidence checks and all current authority boundaries, but account for bounded completion growth before launching the reviewer. A request that passes admission should retain a valid first stop through publication, or be rejected before expensive review. Missing/tampered context, over-budget inputs, terminal rejections and legacy recovery restrictions must remain fail closed.
Add an isolated native lifecycle regression at the state boundary, plus admission and integrity negatives. Preserve the failed production attempt and original observation; do not synthesize a new receipt or replay the rejected first stop. Fix work is continuing in PR918; no merge or release is requested.