Tune ops review guidance

AGENTS.md

@@ -62,6 +62,13 @@ or dashboards. Treat changes that make archived, parked, experiment, or
 active-product status look healthier or more current than the source evidence
 as merge-relevant.
 
+Treat exact output contracts and mutation boundaries as first-class review
+surfaces. CLI JSON keys, workbook columns, Markdown provenance markers, operator
+queue fields, writeback targets, dry-run behavior, and GitHub/Notion mutation
+paths must not drift silently. Any change that turns a read-only/dry-run path
+into an external write, or reports stale/generated state as current canonical
+truth, is merge-relevant.
+
 For docs-only PRs, comment only when a doc claims current portfolio state,
 published readiness, generated report truth, or operator guidance that is not
 backed by the latest canonical truth path or reviewed commands.

src/AGENTS.md

@@ -0,0 +1,19 @@
+# AGENTS.md - GithubRepoAuditor Source
+
+## Review guidelines
+
+Treat source changes as portfolio-truth contract changes when they affect
+`output/portfolio-truth-latest.json`, operator queues, generated workbooks,
+dashboards, badges, Markdown reports, or seam-linter results. Review for stale
+state reporting, generated-vs-canonical confusion, dropped provenance markers,
+schema drift, and fields that make parked, archived, experiment, or held work
+look active.
+
+Mutation boundaries are merge-relevant. Review `auto_apply`, `ops_writeback`,
+GitHub clients, Notion sync/export code, automation executors, and approval
+ledger paths for dry-run preservation, explicit target selection, idempotent
+recovery, and no silent external writes.
+
+Exact output matters. If CLI JSON, workbook columns, Markdown headings,
+operator queue fields, or report sections change, require tests or fixtures
+that pin the intended contract and update docs that cite the old shape.