Repository navigation
An unclear triage answer frees the agent that holds the item - #493
Merged
Merged
Conversation
el-bri-ga
enabled auto-merge (squash)
November 20, 2026 06:36
|
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.



Fixes #488.
A person can accept a root before its triage item finishes, and an agent can claim the fix. A later
triagedwithunclearthen setopen_questionon the held root, so it was held and waiting on a person at once. From format 27 the fold ends the holder's hold when the answer opens the question, aswork_askdoes: the claim is given back and the item waits in Needs you. The holder's next write is refused asnot_holder; its claim extension notices the hold is gone (the tracker already checks the log for that). Below 27 nothing changes, so no old log folds differently.Tests: fold unit tests (frees at 27, unchanged at 26, nothing to free), a format 27 log pinned in
wasm/golden, and the fault sweep now accepts roots before triage ends, which reproduces the issue (seed 74 failed with 'p1 is held with an open question' with the gate removed, passes with it; 200 seeds green locally). Docs: upgrades table, work tracker, fault sweep. NoUpgrade-Break: no new record, and a fresh log starts below 27.Review notes