bmottin/claude_mac
1
0
Fork 0
forked from bchanot/claude
Code Pull Requests Activity

fix(plan-challenger): ERROR verdict added to the load-bearing OUTPUT grammar (STEP 1 emitted it, parser enum omitted it)

Browse Source
This commit is contained in:
Bastien Chanot
2026-08-26 21:54:35 +02:00
parent ab75fc5e1f
commit 27f17939d7
1 changed files with 5 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents/plan-challenger.md
+5 -2
View File
@@ -63,7 +63,7 @@ Ground EVERY finding in the plan text (quote the section) or the real code
## OUTPUT (exact format — machine-parsed by the orchestrator) ## OUTPUT (exact format — machine-parsed by the orchestrator)
``` ```
CHALLENGE — LENS: <correctness|robustness|simplicity> — VERDICT: SOLID | CONCERNS(n) | FATAL(n) CHALLENGE — LENS: <correctness|robustness|simplicity> — VERDICT: SOLID | CONCERNS(n) | FATAL(n) | ERROR(<reason>)
PLAN: <path> PLAN: <path>
FINDINGS: FINDINGS:
1. [BLOCKER] <claim> — WHY: <why it fails — plan § or file:line> — FIX: <one line> 1. [BLOCKER] <claim> — WHY: <why it fails — plan § or file:line> — FIX: <one line>
@@ -86,7 +86,10 @@ PROOF: read <n> files, inspected <what>, checked plan §<…>
the orchestrator discards. the orchestrator discards.
- Stay in your lens. A finding outside it belongs to another challenger. - Stay in your lens. A finding outside it belongs to another challenger.
- The verdict grammar is load-bearing: exactly one - The verdict grammar is load-bearing: exactly one
`CHALLENGE — LENS: … — VERDICT:` line, spelled as above. `CHALLENGE — LENS: … — VERDICT:` line, spelled as above. `ERROR(<reason>)`
(STEP 1's missing/unreadable-plan verdict) is part of the grammar: it
carries only the `PLAN:` line — no FINDINGS, no PROOF — and the
orchestrator treats it as a dispatcher-side failure, not a challenge result.
## ORCHESTRATOR PROTOCOL (consumer contract — wiring reference) ## ORCHESTRATOR PROTOCOL (consumer contract — wiring reference)