Align recovery delivery with Codex 0.153.4 and preserve bounded qualification evidence - #32
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.
Completed scope
The interrupted upload was recovered from its Git objects, reviewed and completed. Final head:
1d5884f3bf89dfdeb1f113672f070ec0778ac714; verified local and remote tree:678b85380318f57e3458a4870e3daaae1753f208.Product and C10
Codex 0.153.4 PostCompact is stateless and accepts universal output fields; model-visible recovery is delivered by SessionStart(source=compact). The product now emits a target-free PostCompact readiness advisory and retains the actual recovery pointer in SessionStart. C10 tests independent startup and after-compaction fixtures, narrowing the second primary-checkout matcher to
^compact$before bootstrap. Real hook output, actual expected target, lifecycle order, exact model echo, checkpoint validity and source/planning immutability remain required. Value-flow diagnostics contain only comparisons/counts/classifications, never the opaque proof.The implementation specification, compliance record, baseline description and materialized C10 documentation are synchronized with the pinned source and official hooks reference. The two C10 acceptance assertion strings are unchanged. No new live capability result is asserted.
C09/C10 process observations
Only C09/C10 opt into bounded content-free process observations. On timeout the owned process group/tree is terminated and partial structural progress is retained. Reader/cleanup failures reject even positive output. Unexpected reader exceptions are flagged rather than disappearing in daemon threads. C09's 900-second timeout, compaction trigger, two-cycle/continuation/checkpoint requirements and rejection of incomplete output remain unchanged. This is not a claim that C09's live timeout cause is fixed.
Evidence packaging
Only a deterministic verified inner ZIP is uploaded. Every capability manifest is checked, including the three hidden fixture files. Missing/changed/unlisted files and symlinks are rejected. The temporary source-snapshot workflow has been removed. Extract the inner ZIP when reviewing the downloaded Actions artifact.
Verification
Boundaries and next run
C13 runtime is unchanged. Sandbox, approval policy, auth ownership, generator/executor separation and full C01-C16 release requirements are not relaxed. No self-hosted Codex workflow was dispatched.
After merge and post-merge CI: existing PlanAnvil Codex qualification workflow, branch main, mode=recovery (C09/C10/C13). Do not use full yet. C10 now tests the supported delivery channel; C09 may still report a timeout, but its remaining progress and cleanup will be observable.