McRitchie Studio

Reconciled kind feature->docs: deliverable is a pure markdown operating-model module (docs/agents/modules/result-distillation.md) + one index.md line, no code surface. shape=backend was a mis-fit; dor-check now passes via the designed EXEMPT-kind path. checks_run carries a [full-suite-bypass] record; the full Rails suite was not run (no runtime surface to certify).

Scout report: merge-ready - Light review: all 3 acceptance criteria met; coupled-pair #431 verbs resolve; 2 non-blocking nits Reporter: jasper Outcome: merge-ready Findings: - AC1-3 met: result-distillation.md documents policy, validate->resolve->finding shape, two nested grains (action finding + activity verdict) - Coupled-pair OK: bin/agent-activity loads atomic-event so 'action --summary' resolves to the verb #431 extends; #431 drop rule (tool-results/ dir Reads dropped, all else kept) matches doc's suppression claim - NIT: doc illustration 'reopening a file to see the next chunk' is broader than #431 (only drops spilled tool-results/ reads, keeps real-file chunk-paging) - NIT: doc examples omit --finding, so recorded findings land kind=bash not #431's queryable 'finding' verb Questions: - none Checks: - gh pr diff 430/431 read-only; referenced atomic-capture-hook.md exists; index link convention matches siblings

Scout report: request-changes - Policy doc is clear, standalone, meets all 3 acceptance criteria; but its finding-recording command omits #431's --finding flag, so agents following it stamp kind=bash not kind=finding — a doc/code divergence in the coupled pair. Reporter: carl Outcome: request-changes Findings: - BLOCKER coupled-pair divergence: result-distillation.md:38 and :58 tell agents to record findings with 'bin/agent-activity action --summary ...' WITHOUT --finding; #431 adds --finding specifically to stamp kind=finding and render 'FINDING · ...' queryable as one class. Following the doc verbatim yields kind=bash rows, defeating #431's atomic-event half. Fix: add --finding to the command examples. - NIT clarity: result-distillation.md:46 describes suppressed paging as 'reopening a file only to see the next chunk'; #431 only drops Reads under a tool-results/ dir (the agent's OWN spilled output), and explicitly KEEPS re-reads of real source files. Tighten to 'its own spilled tool-output file' to match the code. - PASS acceptance: (1) new module documents the policy result-distillation.md:1; (2) validate->resolve->finding defined :29-38; (3) two grains action-level + activity-level table :56-59. Questions: - none Checks: - gh pr diff 430 read; gh pr diff 431 cross-checked; bin/agent-activity confirmed = bin/atomic-event shim; link targets exist

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.

Added --finding to the command examples so the policy matches the coupled #431 verb; tightened the paging line to specify the harness tool-results/ spill files (real source paging kept).

Rework addressed Carl+Jasper's coupled-pair finding: added --finding to all command examples (aligns with #431's verb) + scoped the paging line to tool-results/ spill files. dor-check green (docs-exempt), CI green. Advancing to reviewed.