Repository navigation
bug(unic-archon-dlc): the pr-review summary states what the Box instructed, and attributes a check a sub-agent reports #660
Description
What to build
Implement the decision recorded in #487 (§ Decisions and § Acceptance criteria). The criteria live there and are not copied here, so they have one home. Read #487's body in full before you start.
In short, the pr-review summary's block "Checks this review did not run" no longer claims that nothing ran. It states what the Box instructed. review records in reported_checks the checks its sub-agents report, each named by need, and the block renders them as attributed claims. ADR-0037 §8 is amended in place.
Order
This ticket edits apps/claude-code/unic-archon-dlc/.archon/workflows/unic-dlc-pr-review.yaml after #482 has merged. #482 rewrites reconcile's summary frame and post. Every criterion in #487 that touches the summary frame is written against #482's criteria. Read the file on develop after #482 has merged, not as it stands today.
What the PR meets, and what it does not
The PR meets every criterion in #487 except the two under "Checked in run 4 (#502), not at merge". Those are checked when run 4 is scored, under #502, and the PR does not tick them. The criterion under "What a run here does not prove" is a merge criterion: the PR states that the change is unproven in the Consumer until a Consumer run reads it.
Release
unic-archon-dlc is on 0.x. This change adds a field to review.json and renames a summary heading, so it is a minor bump. If you find a reader outside this Box that parses the old heading, add a ### Breaking entry and say so in the PR.
Decision ticket: #487, closed when its criteria were approved. Parent map: #498.
Activity
reconcilemarks a finding fixed when the next review omits it, andpostresolves the thread #482orioltf commentedon Oct 28, 2026
Opener for #660
Written 2026-10-28 by the
/afk-loop 498orchestrator, at dispatch.What this session produces
One pull request to
developthat changesapps/claude-code/unic-archon-dlc/.archon/workflows/unic-dlc-pr-review.yamlso that the summary block on checks states what the Box instructed, and renders as attributed claims the checks a review sub-agent reports. It also revises ADR-0037 § Decision item 8, updates the Box doc and records the change in the changelog. The criteria are in #487's body, not in this ticket's body. Do not invoke/tddor/to-tickets: the Box is prose, and the bar is a run and a read (AGENTS.md§ Acceptance criteria are prose).Read in this order
unic-dlc-pr-review.yamlonorigin/develop. #482 merged on 2026-10-28 asunic-archon-dlc0.32.0, so the tree is already the one bug(unic-archon-dlc): the summary's § "Checks this review did not run" is false when a sub-agent ran a declared command #487's criteria are written against. Readbootstrap(its paragraph on checks),review(both sub-agent prompts and every path that writesSESSION/findings/review.json),synthesize, andreconcilestep 5b and its summary frame.apps/claude-code/unic-archon-dlc/docs/adr/0037-config-declares-sdlc-needs.md§ Decision item 8, anddocs/adr/README.mdfor the plugin's inline-revision convention.apps/claude-code/unic-archon-dlc/docs/boxes/unic-dlc-pr-review.md, where it describes the block.The trap that costs an hour
Naming a check by its command. Decision 5 and its criterion say
reviewassigns the need by judging what a command does, from thesdlc_needskey names, never by comparing the command text with the declared value, and the block never names a command. The tempting shortcut is a string match of the reported command against$bootstrap.output.sdlc_needs. It reports a declared need as undeclared whenever the Consumer's value has another shape (#637). Write the rule intoreview's prompt as a judgement, and check that no sentence inreconcileprints a command. Count the key names inbootstrapyourself: #487 says nine.What this ticket does not decide
docs/adr/README.mdsays to revise inline and extend the Status line withrevised YYYY-MM-DD. Follow that convention: revise item 8 in place and date it on the Status line and in the index row. That meets both texts.Other traps
reported_checks, including the path where theAgenttool is unavailable. There the array is empty, and the block must not say a sub-agent may have run a check.installnever entersreported_checksand is never a reported check.synthesizeputs no check result in "What's good" or anywhere else as a fact.bootstrap's paragraph on checks cites ADR-0026 today. It must cite ADR-0037 §8. Do not edit ADR-0026 or ADR-0030.$node.outputtoken inside a comment of ascript:body is a real dependency edge. Write node ids in plain words in comments.review.jsonand renames a summary heading. It is aminorbump. Search the repository and the other Boxes for a reader that parses the old heading text. If you find one, add a### Breakingentry and say so in the PR.cd. The NDA hook refuses aghcommand that changes directory.The bar that proves it
A read of the YAML at your head, one line per case in the PR body:
typecheckand the outcome, and no command;Agenttool is unavailable:reported_checksis empty, and the block does not say a sub-agent may have run a check;pnpm install: nothing entersreported_checks.Then grep the head for "did not run" and "executed none" in the Box, its doc and the ADR, and put the counts in the PR body. A false pass is a block whose heading changed while a sentence below still says no check ran.
On landing
apps/claude-code/unic-archon-dlc/CHANGELOG.mdunder## [Unreleased], and commit it with the change.pnpm --filter unic-archon-dlc bump minor, and commit the result on its own aschore(unic-archon-dlc): release <version>.Closes #660, the case walk, the grep counts, a line saying the two run-4 criteria of bug(unic-archon-dlc): the summary's § "Checks this review did not run" is false when a sub-agent ran a declared command #487 are checked under #502 and not ticked here, and a line saying the change is unproven in the Consumer until a Consumer run reads it.Report back
Report in your final answer, as your worker prompt's step 7 says, and stop after the handover. The orchestrator may continue you with fix rounds.
Review and handover
The orchestrator runs the review rounds, sends you the findings to fix, and merges when the gate holds. You do not merge, and you do not answer review threads.