Repository navigation
Count self-check catches apart; order worker finish as block, commit, selfcheck - #46
Merged
Merged
Conversation
…mit, selfcheck All 3 of live run 27's gate blocks were workers' own selfcheck runs (two scaffolders before committing), which never reach the supervisor. run-summary now reports them as selfcheck_blocks, and the RED/GREEN/SCAFFOLD prompts state the finish order in one sentence. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014j4wLin3oJTtnvjE9Lq2VV
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.
Requested by Adeel · project thread
Before:
run-summarycounted everyexit: 2line in gates.jsonl as a gate block. That included a worker's ownselfcheckrun, which never reaches the supervisor. Run 27 reported 3 blocks, but all 3 were self-check catches. Two of them came from scaffolders that ranselfcheckbefore committing, because the worker prompts put "commit" and "block first, then selfcheck" in two separate sentences.After:
summary.jsongainsselfcheck_blocks, and the summary prints "N blocks, M caught by the worker's own self-check". The ledger's gate-blocks column is unchanged, so rows stay comparable. The RED, GREEN and SCAFFOLD prompts now give the finish order in one sentence: append the block, commit, then run selfcheck.How:
run-summaryparses each verdict line as JSON. I also added a test inevidence.test.pyand a prompt-order check indispatch.test.py(14 checks). Re-runningrun-summaryon run 27's directory gives 3 blocks, all 3 self-check catches. Local checks pass: test-hosts, conformance 63/63, site, check-tracking and plugin validate --strict.Generated by Claude Code