Coupled-pair doc/code divergence (Carl primary: REQUEST-CHANGES; Jasper light flagged the same as a coherence nit). The policy tells agents to record findings with 'bin/agent-activity action --summary "…"' WITHOUT the --finding flag (docs/agents/modules/result-distillation.md — the validate->resolve->finding example ~:38, the grain table ~:58, and the 'How to record a finding' section). But the coupled PR #431 ships a bare --finding verb (FINDING_KIND="finding" in bin/atomic-event) whose entire purpose is to render 'FINDING · <conclusion>' / kind=finding rows and keep distilled findings queryable as one class; without --finding an 'action' defaults to kind=bash. So an agent following this doc verbatim produces kind=bash rows, not the finding rows #431 exists to create — the governing policy never instructs the flag its coupled code adds. FIX: add --finding to the command examples (:38, :58, and 'How to record a finding'). ALSO tighten the paging phrasing at ~:46 ('reopening a file only to see the next chunk') to something like 'reopening its own spilled tool-output file' — #431 suppresses ONLY re-reads under a tool-results/ dir and explicitly KEEPS real-source-file paging, so the current wording can read as claiming all chunk-paging is dropped. All 3 acceptance criteria otherwise PASS and CI is green — this is a light, trivial doc fix to make the pair consistent; resubmit after and post a note --resolves-feedback.