fix: bound session marker fallback and require an owner - #74
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.
An old workspace marker could select the wrong session's jobs or authorize cleanup when SessionEnd omitted its owner.
Limit marker fallback to 24 hours and require an owner for new delegation and implicit result/cancel selection. Keep explicit references and
status --allavailable. Serialize marker writes and owner-checked clears, preserve marker age during same-owner delegation, and publish the SessionStart owner before cleanup consumes its budget.Validation:
npm run checkand coverage passed all 1,223 tests without skips. Independent CLI/hook E2E passed 20 scenarios on both current Node and Node 18. A real Fable 5.1 task preserved marker bytes through forwarded routing. Fresh Opus 5.5 review found no blocking defects. Mutation scores passed the 55% threshold: marker functions 88.16%, tracked-jobs 69.75%, job-control 70.52%, and render 58.14%.