fix: recover native App continuation receipts - #168
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
1 participant
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.
A native same-thread continuation is recorded as a codex_app/send_message_to_thread delegation. The read-only observation helper accepted only create_thread, so it returned zero matches even when the exact bound repair turn had completed and its raw final was present. Native read_thread can also expose a completed turn with no items, making this fallback necessary.
Recognize both native delegation methods while retaining the exact request marker, unique-match and bound-turn checks. Document the fallback in the installed controller runbook. No Codex state/transcript writes, resubmission or runtime restart is involved.
Validation: six Python tests pass after reproducing the failure; negative cases reject unrelated tool outputs, assistant markers, duplicate matches and the wrong bound turn. Live read-only recovery matched the already returned authority repair final byte-for-byte. Diff check passed.