fix: preserve hook evidence and report durable replay progress - #59
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.
Live OrgX health shows an active Codex 0.1.14 installation with a growing hook backlog and no observed replay. Before upgrading it to the newer automatic replay implementation, this fixes evidence-loss and reporting defects in that implementation.
Validation: npm run check passes; 29 focused replay/health tests pass locally, including partial writes, UTF-8 boundaries, upload-time appends, failure retention and cursor-based health. Full npm test runs in the added PR CI; local dependency installation was interrupted by the environment's network approval layer.
This release does not upgrade or sign in the user's running Darwin client. Live backlog drainage remains unverified until that client is updated and restarted. Delivery remains at least once across crashes; no exactly-once claim is made.