[AUTOMATED] docs(re-needs): persist the three round-3 closes - #426
Merged
Conversation
The three needs that shipped in round 3 -- #417, #421, #422 -- had their acceptance probes flip from FAIL to PASS on a freshly built main at 80e965c, but the record on disk still said `status: open`. Anyone reading docs/re-needs/ (or any selector that reads it) would see three closed gaps as dispatchable work. This is the second time this edit has been applied: the first application was made in the main working tree and never committed, and it was lost when that tree was moved between branches. Committing it is the fix. Statuses, `closed_in_round` and `closing_pr` come from .kuna-repipe/rounds/3/acceptance-suite.json (sha 80e965c, 3 closed, 0 regressed) -- no verdict is re-derived here. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
The problem
Three needs shipped in round 3 and their acceptance probes now pass, but the record on disk still says they are open:
while the round's own acceptance run disagrees:
An open need is dispatchable, so the backlog offers three already-closed gaps as work.
The fix
status: closed,closed_in_round: 3andclosing_pr([AUTOMATED] fix(p2): a Windowsint 0x29(__fastfail) ends the flow instead of unbalancing the stack #417, [AUTOMATED] feat(console): --assert accepts the standard C scalar types #421, [AUTOMATED] fix(p2,cli): checker-exceeds-instruction-ceiling — a function past the instruction budget yields a truncated body, not nothing #422) on the three records, and append the acceptance line naming the sha the probe passed at.rounds/3/acceptance-suite.json; nothing is re-derived, and no probe is re-run or relaxed.The tests
Records only -- no code, no gate input.
docs/re-needs/feeds no gate; the acceptance probes themselves are unchanged.