chore(unic-archon-dlc): every opener counts from the node's artefact, never from `node_output`

Observed

Run 3, unic-dlc-pr-review iteration 1: the review node's node_output in remote_agent_workflow_events rendered two ## SECTION 2 — FINDINGS (JSON) blocks holding 8 and 5 findings. The node's artefact workflows/profile-card/pr-review/findings/review.json held 14. Nothing in node_output says it is abridged. The build opener's § 6 told the session to read synthesize's counts against the review node's node_output; the session reported 13 unmerged where the truth was 14 merged to 13, and caught it from the node's own .remember note.

Also measured: remote_agent_workflow_events holds tool inputs only; runner output lives in ~/.claude/projects/<worktree-path>/*.jsonl, a live directory a same-named worktree reuses.

Why it matters

Every opener and every docs/agents/unic-archon-dlc.md § Recovering a killed run instruction that points at node_output for a count is pointing at an abridgement. node_output length is still a fine zero-check for the #465 shape.

Evidence

• Findings register, § "G. What run 3 taught about the instrument", row G11: 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-26f0f16c…/findings/review.json vs run-26f0f16c…-events-2012-final.json)
• Dispatch record: #457 from comment 5698289748 down

Not decided

• Which documents in both repositories point at node_output for a count, and the one sentence that replaces them.

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

Start with docs/agents/unic-archon-dlc.md § Recovering a killed run and the opener instructions, then search both repositories for count references to node_output. Review the dispatch record in #457 and the cited findings evidence to identify every affected document. Done means each count points to the node artefact, while the existing node_output zero-check remains intact.