fix(coding-agent): preserve SDK recovery event cursors - #63
Merged
Conversation
This was referenced Sep 12, 2026
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.
Pylon could finish a native conversation but reject its transcript after an idle restart: the public Prime SDK dropped the event cursor, leaving durable recovery progress behind the saved messages. Accepted session and prompt-lifecycle events now carry their original cursor through the existing validation path.
The regression covers message completion, lifecycle delivery, stale/duplicate/foreign events, retired generations, invalid attribution, and cursorless legacy events. All 226 focused tests and
npm run checkpass; the regression fails without the fix. No daemon wire, SDK feature token, artifact recipe, or publication policy changes. Publication must produce new immutable SDK bytes.Fixes #62. Part of pylon-code/pylon#114. Maintainer authorization to finish the necessary fixes, reviewed green merges, and managed publication is recorded in the owning Pylon task.
Independent adversarial checkpoint review passed at
5defac13059ba2707cf62c03f0108bfd8a88ca5f. The review confirmed that stale, foreign, retired-generation and invalid-attribution events remain excluded before cursor metadata reaches subscribers.Model: GPT-6. Harness: Codex.