bug(unic-archon-dlc): `report.md` says "nothing was flaky" from `verification`'s single final run

Observed

Run 3 build c283e296, report.md § 4: "Nothing was skipped and nothing was flaky. No need came back unresolved." build-state.json, written by the same run, records three retried slices: icon-user2 ("the first two runs failed on Vite dependency optimisation reloading the test file … the third run passed 72/72"), badge-main ("the first run failed …; the second run passed 75/75"), card-profile-main ("the first run failed on Motion alone"). The transcripts show twelve pnpm test runs, eight with failures.

report inherited the sentence from verification, which ran pnpm test once at the end and had no view into the slice loop.

Why it matters

With no CI in the Consumer the report is the only record that a check ran, and "nothing was flaky" is a claim written by a node that could not see the retries. Same shape as #457's PR-description finding (12 tests claimed, 16 ran).

Evidence

• Findings register, § "G. What run 3 taught about the instrument", row G9: https://github.com/unic/unic-agents-plugins/blob/bcf688a/docs/research/2026-08-31-dlc-run-2-findings.md
• Run record and harvested artefacts: ~/Desktop/run3-parked/ on the maintainer's machine (artefacts-c283e296/report.md, build-state.json, run-c283e296-transcripts-1934-final/)
• Dispatch record: #457 from comment 5698289748 down

Not decided

• Whether report reads build-state.json's per-slice notes for retries, or verification's sentence is scoped to "the final run".

Filed 2026-09-17 by wayfinder-orchestrator-10 from run 3's measurements. needs-specs: grill before dispatch.

Read the findings register’s G9 row, dispatch record #457, and the run 3 report.md and build-state.json artefacts. Compare verification’s final-run result with the slice-loop retry records and the twelve pnpm test runs, then resolve the intended scope for retry visibility. Done when the report’s flaky-status wording matches the recorded run evidence and the behavior is verified.