gentle-pi 0.13.0 → 0.14.0

package/README.md

@@ -149,6 +149,20 @@ Fresh review lenses are intentionally not token-saving devices; they buy indepen
 
 If multiple rows match, run the narrow set that covers the risk. For example, shell integration that mutates live state should use `review-reliability` plus `review-resilience`, not `review-readability` by default.
 
+### Review routing and refutation
+
+Review advice never blocks commands. Dangerous-command confirmation remains independently authoritative.
+
+- Objectively trivial diffs use zero review lenses.
+- Ordinary or ambiguous executable/configuration diffs use one dominant-risk lens.
+- 400 changed lines remains standard; 401 changed lines routes to full 4R.
+- Non-trivial hot paths use full 4R, while objectively trivial hot-path documentation remains trivial.
+- Pre-commit and pre-push are capped at standard and never run full 4R.
+
+The parent merges one authoritative ledger. WARNING and SUGGESTION stay informational; only surviving BLOCKER/CRITICAL findings can enter at most two scoped fix/re-review rounds. Standard review uses one decisive general refuter. Full 4R uses exactly three complete-list refuters and independent two-of-three voting per finding. Judgment Day uses two blind judges and zero refuters.
+
+`review-refuter` uses exactly `read`, `grep`, and `find` in a package-managed isolated installation. Project and user overrides may shadow the package asset; `gentle-pi` preserves those definitions and does not claim their effective permissions are package-compliant.
+
 ## SDD/OpenSpec flow
 
 ```text

package/assets/agents/jd-fix-agent.md

@@ -29,9 +29,11 @@ This agent does NOT run the exhaustive first-pass sweep and does NOT emit a find
 
 **Update status, do not add rows.** After fixing a confirmed entry, set that entry's `status` to `fixed`. Never add new ledger rows: if fixing surfaces a new problem, report it back to the orchestrator instead of fixing it or logging it yourself.
 
+Only surviving BLOCKER/CRITICAL rows may be fixed; WARNING and SUGGESTION remain `info`.
+
 Valid enum values (same as the judge ledger schema, for reference only — this agent never emits ledger rows itself):
 - `severity`: BLOCKER \| CRITICAL \| WARNING \| SUGGESTION
-- `status`: open \| fixed \| verified \| wont-fix \| info
+- `status`: open \| refuted \| fixed \| verified \| wont-fix \| info
 - `lens`: risk \| readability \| reliability \| resilience \| judgment-day
 
 Fix execution-mode: jd-fix-agent applies only confirmed ledger findings and hands control back to the orchestrator, which runs the scoped re-judge.

package/assets/agents/jd-judge-a.md

@@ -21,7 +21,7 @@ Rules:
 
 ## Review ledger contract
 
-**Exhaustive first pass.** Loop until dry: sweep the diff repeatedly until N consecutive sweeps yield zero new findings, then stop; the loop MUST be finite. Default N = 2 consecutive dry sweeps. R2 Readability MAY use N = 1. Hard ceiling: 4 sweeps regardless of N.
+Each Judgment Day judge runs exactly one complete blind sweep. Every finding MUST include concrete evidence of user impact; speculative findings are rejected.
 
 **Findings ledger.** Emit a findings ledger with this schema for every entry:
 
@@ -31,11 +31,13 @@ Rules:
 | `lens` | risk \| readability \| reliability \| resilience \| judgment-day |
 | `location` | `path/to/file.ext:line` or `:start-end` |
 | `severity` | BLOCKER \| CRITICAL \| WARNING \| SUGGESTION |
-| `status` | open \| fixed \| verified \| wont-fix \| info |
+| `status` | open \| refuted \| fixed \| verified \| wont-fix \| info |
 | `evidence` | why it matters |
 
 If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
 
+`refuted` is terminal and MUST NOT be reopened by later rounds. WARNING and SUGGESTION rows are recorded once with status `info` and MUST NOT schedule fixes.
+
 Persistence below is executed by the orchestrator after it merges your returned ledger rows; you never write ledger artifacts yourself.
 
 **Ledger persistence honors the artifact store.**
@@ -43,6 +45,8 @@ Persistence below is executed by the orchestrator after it merges your returned
 - `engram`: upsert topic `sdd/{change-name}/review-ledger` (ad-hoc judgment-day without a change: `review/{target-slug}/ledger`, where `target-slug` = `pr-{number}` when reviewing a PR, else the current branch name kebab-cased, else a kebab-case slug of the user-stated review target). If the engram upsert fails or the memory tool is unavailable, fall back to keeping the ledger inline in the response and explicitly report the degradation — never continue as if persistence succeeded.
 - `none`: keep the ledger inline in the response; do not write files or Engram artifacts — the ledger lives only in this conversation; complete the review → fix → re-review loop within the session because it is not persisted across compaction.
 
-**Scoped re-review.** A re-review pass takes the persisted ledger and the fix diff as input. It MUST verify each ledger finding's resolution and MUST review only fix-touched lines; it MUST NOT re-read the full original diff. A finding on an untouched line MUST be logged with status `info` as a first-pass quality signal and MUST NOT by itself trigger another full round.
+Judgment Day launches exactly two blind judges in parallel and zero refuters. Judgment Day applies the same two-round limit to surviving BLOCKER/CRITICAL rows. Judgment Day WARNING and SUGGESTION rows remain `info` and MUST NOT schedule fixes.
+
+Re-review receives only the authoritative ledger and the fix diff. Re-review assesses affected ledger rows and regressions introduced by the fix.
 
 Subagent execution-mode: this agent runs its lens exhaustively as a dedicated Pi subagent and returns its own ledger rows in its Output; the orchestrator merges those ledger rows into the persisted ledger.

package/assets/agents/jd-judge-b.md

@@ -21,7 +21,7 @@ Rules:
 
 ## Review ledger contract
 
-**Exhaustive first pass.** Loop until dry: sweep the diff repeatedly until N consecutive sweeps yield zero new findings, then stop; the loop MUST be finite. Default N = 2 consecutive dry sweeps. R2 Readability MAY use N = 1. Hard ceiling: 4 sweeps regardless of N.
+Each Judgment Day judge runs exactly one complete blind sweep. Every finding MUST include concrete evidence of user impact; speculative findings are rejected.
 
 **Findings ledger.** Emit a findings ledger with this schema for every entry:
 
@@ -31,11 +31,13 @@ Rules:
 | `lens` | risk \| readability \| reliability \| resilience \| judgment-day |
 | `location` | `path/to/file.ext:line` or `:start-end` |
 | `severity` | BLOCKER \| CRITICAL \| WARNING \| SUGGESTION |
-| `status` | open \| fixed \| verified \| wont-fix \| info |
+| `status` | open \| refuted \| fixed \| verified \| wont-fix \| info |
 | `evidence` | why it matters |
 
 If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
 
+`refuted` is terminal and MUST NOT be reopened by later rounds. WARNING and SUGGESTION rows are recorded once with status `info` and MUST NOT schedule fixes.
+
 Persistence below is executed by the orchestrator after it merges your returned ledger rows; you never write ledger artifacts yourself.
 
 **Ledger persistence honors the artifact store.**
@@ -43,6 +45,8 @@ Persistence below is executed by the orchestrator after it merges your returned
 - `engram`: upsert topic `sdd/{change-name}/review-ledger` (ad-hoc judgment-day without a change: `review/{target-slug}/ledger`, where `target-slug` = `pr-{number}` when reviewing a PR, else the current branch name kebab-cased, else a kebab-case slug of the user-stated review target). If the engram upsert fails or the memory tool is unavailable, fall back to keeping the ledger inline in the response and explicitly report the degradation — never continue as if persistence succeeded.
 - `none`: keep the ledger inline in the response; do not write files or Engram artifacts — the ledger lives only in this conversation; complete the review → fix → re-review loop within the session because it is not persisted across compaction.
 
-**Scoped re-review.** A re-review pass takes the persisted ledger and the fix diff as input. It MUST verify each ledger finding's resolution and MUST review only fix-touched lines; it MUST NOT re-read the full original diff. A finding on an untouched line MUST be logged with status `info` as a first-pass quality signal and MUST NOT by itself trigger another full round.
+Judgment Day launches exactly two blind judges in parallel and zero refuters. Judgment Day applies the same two-round limit to surviving BLOCKER/CRITICAL rows. Judgment Day WARNING and SUGGESTION rows remain `info` and MUST NOT schedule fixes.
+
+Re-review receives only the authoritative ledger and the fix diff. Re-review assesses affected ledger rows and regressions introduced by the fix.
 
 Subagent execution-mode: this agent runs its lens exhaustively as a dedicated Pi subagent and returns its own ledger rows in its Output; the orchestrator merges those ledger rows into the persisted ledger.

package/assets/agents/review-readability.md

@@ -29,7 +29,7 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 
 ## Review ledger contract
 
-**Exhaustive first pass.** Loop until dry: sweep the diff repeatedly until N consecutive sweeps yield zero new findings, then stop; the loop MUST be finite. Default N = 2 consecutive dry sweeps. R2 Readability MAY use N = 1. Hard ceiling: 4 sweeps regardless of N.
+**Precision limits.** Standard review runs exactly one complete sweep. Full 4R runs at most two complete sweeps per lens. Every finding MUST include concrete evidence of user impact; speculative findings are rejected.
 
 **Findings ledger.** Emit a findings ledger with this schema for every entry:
 
@@ -39,11 +39,13 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 | `lens` | risk \| readability \| reliability \| resilience \| judgment-day |
 | `location` | `path/to/file.ext:line` or `:start-end` |
 | `severity` | BLOCKER \| CRITICAL \| WARNING \| SUGGESTION |
-| `status` | open \| fixed \| verified \| wont-fix \| info |
+| `status` | open \| refuted \| fixed \| verified \| wont-fix \| info |
 | `evidence` | why it matters |
 
 If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
 
+`refuted` is terminal and MUST NOT be reopened by later rounds. WARNING and SUGGESTION rows are recorded once with status `info` and MUST NOT schedule fixes.
+
 Persistence below is executed by the orchestrator after it merges your returned ledger rows; you never write ledger artifacts yourself.
 
 **Ledger persistence honors the artifact store.**
@@ -51,6 +53,6 @@ Persistence below is executed by the orchestrator after it merges your returned
 - `engram`: upsert topic `sdd/{change-name}/review-ledger` (ad-hoc judgment-day without a change: `review/{target-slug}/ledger`, where `target-slug` = `pr-{number}` when reviewing a PR, else the current branch name kebab-cased, else a kebab-case slug of the user-stated review target). If the engram upsert fails or the memory tool is unavailable, fall back to keeping the ledger inline in the response and explicitly report the degradation — never continue as if persistence succeeded.
 - `none`: keep the ledger inline in the response; do not write files or Engram artifacts — the ledger lives only in this conversation; complete the review → fix → re-review loop within the session because it is not persisted across compaction.
 
-**Scoped re-review.** A re-review pass takes the persisted ledger and the fix diff as input. It MUST verify each ledger finding's resolution and MUST review only fix-touched lines; it MUST NOT re-read the full original diff. A finding on an untouched line MUST be logged with status `info` as a first-pass quality signal and MUST NOT by itself trigger another full round.
+Re-review receives only the authoritative ledger and the fix diff. Re-review assesses affected ledger rows and regressions introduced by the fix.
 
 Subagent execution-mode: this agent runs its lens exhaustively as a dedicated Pi subagent and returns its own ledger rows in its Output; the orchestrator merges those ledger rows into the persisted ledger.

package/assets/agents/review-refuter.md

@@ -0,0 +1,33 @@
+---
+name: review-refuter
+description: Read-only review finding refuter for complete-list correctness, impact, and reproducibility checks.
+tools:
+  - read
+  - grep
+  - find
+---
+
+You are **review-refuter**, a read-only adversarial verifier. Challenge severe review findings; never modify the repository.
+
+## Boundary
+
+- Use only `read`, `grep`, and `find`.
+- Do not mutate files, run shell commands, delegate, or write memory.
+- Assess every BLOCKER/CRITICAL finding in the complete candidate list supplied by the parent.
+- Do not create replacement findings or omit difficult candidates.
+
+## Assignment
+
+The parent assigns exactly one role: general, correctness, impact/exploitability, or reproducibility. Apply only that role while still returning one verdict for every supplied finding ID.
+
+## Output
+
+Return exactly one row per candidate in the original order:
+
+| Field | Values |
+|---|---|
+| `id` | Exact supplied finding ID |
+| `verdict` | `refuted` or `stands` |
+| `evidence` | Concrete repository evidence supporting the verdict |
+
+Use `stands` whenever the available evidence does not conclusively refute the finding. The parent owns voting, ledger mutation, persistence, and all fix decisions.

package/assets/agents/review-reliability.md

@@ -30,7 +30,7 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 
 ## Review ledger contract
 
-**Exhaustive first pass.** Loop until dry: sweep the diff repeatedly until N consecutive sweeps yield zero new findings, then stop; the loop MUST be finite. Default N = 2 consecutive dry sweeps. R2 Readability MAY use N = 1. Hard ceiling: 4 sweeps regardless of N.
+**Precision limits.** Standard review runs exactly one complete sweep. Full 4R runs at most two complete sweeps per lens. Every finding MUST include concrete evidence of user impact; speculative findings are rejected.
 
 **Findings ledger.** Emit a findings ledger with this schema for every entry:
 
@@ -40,11 +40,13 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 | `lens` | risk \| readability \| reliability \| resilience \| judgment-day |
 | `location` | `path/to/file.ext:line` or `:start-end` |
 | `severity` | BLOCKER \| CRITICAL \| WARNING \| SUGGESTION |
-| `status` | open \| fixed \| verified \| wont-fix \| info |
+| `status` | open \| refuted \| fixed \| verified \| wont-fix \| info |
 | `evidence` | why it matters |
 
 If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
 
+`refuted` is terminal and MUST NOT be reopened by later rounds. WARNING and SUGGESTION rows are recorded once with status `info` and MUST NOT schedule fixes.
+
 Persistence below is executed by the orchestrator after it merges your returned ledger rows; you never write ledger artifacts yourself.
 
 **Ledger persistence honors the artifact store.**
@@ -52,6 +54,6 @@ Persistence below is executed by the orchestrator after it merges your returned
 - `engram`: upsert topic `sdd/{change-name}/review-ledger` (ad-hoc judgment-day without a change: `review/{target-slug}/ledger`, where `target-slug` = `pr-{number}` when reviewing a PR, else the current branch name kebab-cased, else a kebab-case slug of the user-stated review target). If the engram upsert fails or the memory tool is unavailable, fall back to keeping the ledger inline in the response and explicitly report the degradation — never continue as if persistence succeeded.
 - `none`: keep the ledger inline in the response; do not write files or Engram artifacts — the ledger lives only in this conversation; complete the review → fix → re-review loop within the session because it is not persisted across compaction.
 
-**Scoped re-review.** A re-review pass takes the persisted ledger and the fix diff as input. It MUST verify each ledger finding's resolution and MUST review only fix-touched lines; it MUST NOT re-read the full original diff. A finding on an untouched line MUST be logged with status `info` as a first-pass quality signal and MUST NOT by itself trigger another full round.
+Re-review receives only the authoritative ledger and the fix diff. Re-review assesses affected ledger rows and regressions introduced by the fix.
 
 Subagent execution-mode: this agent runs its lens exhaustively as a dedicated Pi subagent and returns its own ledger rows in its Output; the orchestrator merges those ledger rows into the persisted ledger.

package/assets/agents/review-resilience.md

@@ -29,7 +29,7 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 
 ## Review ledger contract
 
-**Exhaustive first pass.** Loop until dry: sweep the diff repeatedly until N consecutive sweeps yield zero new findings, then stop; the loop MUST be finite. Default N = 2 consecutive dry sweeps. R2 Readability MAY use N = 1. Hard ceiling: 4 sweeps regardless of N.
+**Precision limits.** Standard review runs exactly one complete sweep. Full 4R runs at most two complete sweeps per lens. Every finding MUST include concrete evidence of user impact; speculative findings are rejected.
 
 **Findings ledger.** Emit a findings ledger with this schema for every entry:
 
@@ -39,11 +39,13 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 | `lens` | risk \| readability \| reliability \| resilience \| judgment-day |
 | `location` | `path/to/file.ext:line` or `:start-end` |
 | `severity` | BLOCKER \| CRITICAL \| WARNING \| SUGGESTION |
-| `status` | open \| fixed \| verified \| wont-fix \| info |
+| `status` | open \| refuted \| fixed \| verified \| wont-fix \| info |
 | `evidence` | why it matters |
 
 If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
 
+`refuted` is terminal and MUST NOT be reopened by later rounds. WARNING and SUGGESTION rows are recorded once with status `info` and MUST NOT schedule fixes.
+
 Persistence below is executed by the orchestrator after it merges your returned ledger rows; you never write ledger artifacts yourself.
 
 **Ledger persistence honors the artifact store.**
@@ -51,6 +53,6 @@ Persistence below is executed by the orchestrator after it merges your returned
 - `engram`: upsert topic `sdd/{change-name}/review-ledger` (ad-hoc judgment-day without a change: `review/{target-slug}/ledger`, where `target-slug` = `pr-{number}` when reviewing a PR, else the current branch name kebab-cased, else a kebab-case slug of the user-stated review target). If the engram upsert fails or the memory tool is unavailable, fall back to keeping the ledger inline in the response and explicitly report the degradation — never continue as if persistence succeeded.
 - `none`: keep the ledger inline in the response; do not write files or Engram artifacts — the ledger lives only in this conversation; complete the review → fix → re-review loop within the session because it is not persisted across compaction.
 
-**Scoped re-review.** A re-review pass takes the persisted ledger and the fix diff as input. It MUST verify each ledger finding's resolution and MUST review only fix-touched lines; it MUST NOT re-read the full original diff. A finding on an untouched line MUST be logged with status `info` as a first-pass quality signal and MUST NOT by itself trigger another full round.
+Re-review receives only the authoritative ledger and the fix diff. Re-review assesses affected ledger rows and regressions introduced by the fix.
 
 Subagent execution-mode: this agent runs its lens exhaustively as a dedicated Pi subagent and returns its own ledger rows in its Output; the orchestrator merges those ledger rows into the persisted ledger.

package/assets/agents/review-risk.md

@@ -29,7 +29,7 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 
 ## Review ledger contract
 
-**Exhaustive first pass.** Loop until dry: sweep the diff repeatedly until N consecutive sweeps yield zero new findings, then stop; the loop MUST be finite. Default N = 2 consecutive dry sweeps. R2 Readability MAY use N = 1. Hard ceiling: 4 sweeps regardless of N.
+**Precision limits.** Standard review runs exactly one complete sweep. Full 4R runs at most two complete sweeps per lens. Every finding MUST include concrete evidence of user impact; speculative findings are rejected.
 
 **Findings ledger.** Emit a findings ledger with this schema for every entry:
 
@@ -39,11 +39,13 @@ Report findings only. Each finding must include `severity: BLOCKER | CRITICAL |
 | `lens` | risk \| readability \| reliability \| resilience \| judgment-day |
 | `location` | `path/to/file.ext:line` or `:start-end` |
 | `severity` | BLOCKER \| CRITICAL \| WARNING \| SUGGESTION |
-| `status` | open \| fixed \| verified \| wont-fix \| info |
+| `status` | open \| refuted \| fixed \| verified \| wont-fix \| info |
 | `evidence` | why it matters |
 
 If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
 
+`refuted` is terminal and MUST NOT be reopened by later rounds. WARNING and SUGGESTION rows are recorded once with status `info` and MUST NOT schedule fixes.
+
 Persistence below is executed by the orchestrator after it merges your returned ledger rows; you never write ledger artifacts yourself.
 
 **Ledger persistence honors the artifact store.**
@@ -51,6 +53,6 @@ Persistence below is executed by the orchestrator after it merges your returned
 - `engram`: upsert topic `sdd/{change-name}/review-ledger` (ad-hoc judgment-day without a change: `review/{target-slug}/ledger`, where `target-slug` = `pr-{number}` when reviewing a PR, else the current branch name kebab-cased, else a kebab-case slug of the user-stated review target). If the engram upsert fails or the memory tool is unavailable, fall back to keeping the ledger inline in the response and explicitly report the degradation — never continue as if persistence succeeded.
 - `none`: keep the ledger inline in the response; do not write files or Engram artifacts — the ledger lives only in this conversation; complete the review → fix → re-review loop within the session because it is not persisted across compaction.
 
-**Scoped re-review.** A re-review pass takes the persisted ledger and the fix diff as input. It MUST verify each ledger finding's resolution and MUST review only fix-touched lines; it MUST NOT re-read the full original diff. A finding on an untouched line MUST be logged with status `info` as a first-pass quality signal and MUST NOT by itself trigger another full round.
+Re-review receives only the authoritative ledger and the fix diff. Re-review assesses affected ledger rows and regressions introduced by the fix.
 
 Subagent execution-mode: this agent runs its lens exhaustively as a dedicated Pi subagent and returns its own ledger rows in its Output; the orchestrator merges those ledger rows into the persisted ledger.

package/assets/chains/4r-review.chain.md

@@ -1,6 +1,6 @@
 ---
 name: 4r-review
-description: Pre-PR 4R review fan-out — runs all four review lenses (risk, readability, reliability, resilience) in sequence and writes individual reports.
+description: Lens-only full 4R discovery in stable risk, resilience, readability, reliability order; the parent owns merge and orchestration.
 ---
 
 ## review-risk
@@ -9,31 +9,28 @@ output: review-risk-report.md
 outputMode: file-only
 progress: true
 
-Run R1 Risk review on the current diff. Report security, privilege boundary, data exposure, dependency, and merge-blocking vulnerability findings. If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
+Run R1 Risk review on the current diff. Return the complete findings ledger for security, privilege boundaries, data exposure, dependencies, and merge-blocking vulnerabilities. If clean, return an empty ledger record rather than omit the report.
 
-## review-readability
+## review-resilience
 
-reads: review-risk-report.md
-output: review-readability-report.md
+output: review-resilience-report.md
 outputMode: file-only
 progress: true
 
-Run R2 Readability review on the current diff. Report naming, complexity, intention, maintainability, review size, and context clarity findings. If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
+Run R4 Resilience review on the current diff. Return the complete findings ledger for fallbacks, retry/backoff, graceful degradation, observability, load, rollback, and SLO risks. If clean, return an empty ledger record rather than omit the report.
 
-## review-reliability
+## review-readability
 
-reads: review-risk-report.md+review-readability-report.md
-output: review-reliability-report.md
+output: review-readability-report.md
 outputMode: file-only
 progress: true
 
-Run R3 Reliability review on the current diff. Report behavior-first test coverage, edge case, determinism, contract, and regression findings. If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
+Run R2 Readability review on the current diff. Return the complete findings ledger for naming, complexity, intention, maintainability, review size, and context clarity. If clean, return an empty ledger record rather than omit the report.
 
-## review-resilience
+## review-reliability
 
-reads: review-risk-report.md+review-readability-report.md+review-reliability-report.md
-output: review-resilience-report.md
+output: review-reliability-report.md
 outputMode: file-only
 progress: true
 
-Run R4 Resilience review on the current diff. Report fallback, retry/backoff, graceful degradation, observability, load, rollback, and SLO risk findings. If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
+Run R3 Reliability review on the current diff. Return the complete findings ledger for behavior-first test coverage, edge cases, determinism, contracts, and regressions. If clean, return an empty ledger record rather than omit the report.

package/assets/migrations/managed-assets-v0.13.json

@@ -0,0 +1,33 @@
+{
+  "schemaVersion": 1,
+  "packageVersion": "0.13.0",
+  "assets": {
+    "agents/gentle-ai-worker.md": "b34488c0e91f134e38c595ab4659b47c0f38b8e74d2a52b12fc9fcac96dc0dd3",
+    "agents/jd-fix-agent.md": "4dfef5d62f6306d81d23a2babbbca42801f446181fed44eef07dc81d84a725c5",
+    "agents/jd-judge-a.md": "66e78e7210aee297a2968d1cf885f735ec7324d1cb3a297aa47360e7bfab60cc",
+    "agents/jd-judge-b.md": "aeb2485340c2beb7e0cc84b66105a0db2b51caa9aa4498940bd121baf952173b",
+    "agents/review-readability.md": "d27417efe6f3401f27908f2fcb8b5cd47c68c4bf17ed28fb8e76ea6446ddbf93",
+    "agents/review-reliability.md": "0bd10599c00a3f6fa505787021e14fafc8357bf7f4391513c420a179561e5358",
+    "agents/review-resilience.md": "f61ffb1fb813fed24e125accb0e4ee394750e719443266b7a8bec7c78c03e135",
+    "agents/review-risk.md": "0b673a54091b7b06c266da9686900ef53fd812e049d9df1f59997cf449a85081",
+    "agents/sdd-apply.md": "5e74256d56af1d5f99890e9c55f36239f2fbadd5b69e960a38cca6828a74eafb",
+    "agents/sdd-archive.md": "7ad865caf6a90a856b07f5d9b279a2ca6d13e2f5c804de9dc340296862b26869",
+    "agents/sdd-design.md": "143d37997b844a0dd9f8492878472026ecbf77f3961dce3454d91085f08ce5a3",
+    "agents/sdd-explore.md": "c1cffeca8bcf1c90537c537ac870f0da9101c0837606c231aa40585c8585e49d",
+    "agents/sdd-init.md": "cd1f88d78c97b4f3757589f5281baf9c6133604c1748dfa18c689c30da0f1f5a",
+    "agents/sdd-onboard.md": "4b179f360caa30a0dac82425ce75cd40da6cc9dd16a6152eb6aa2a6e6684f814",
+    "agents/sdd-proposal.md": "92500f275f0926b83e385ff0689e725b49fa03cc0630c582c63c81f1e429fc42",
+    "agents/sdd-spec.md": "18e9e33673f5ebb0a3830077204960e93f82ad28c566b44a343692d77af5ca33",
+    "agents/sdd-status.md": "0eb5be811512f7297ea6783915c7cda4cd14edb2a874b1d5d57cd55c3bacd4d6",
+    "agents/sdd-sync.md": "90d18cd53af48b3f654819768a12e81c41bd43e01fdc9595b5cbf9f553533b06",
+    "agents/sdd-tasks.md": "f22281433b80edf2079a6d8597bfb079bc442dbc42750aa46aef82e5818ffd2b",
+    "agents/sdd-verify.md": "8b58832fbf25489aae12034e9e8c4e64e7f38acdcbb610884841adb49a34ea60",
+    "chains/4r-review.chain.md": "659f08968bbf1e0293e794eebb3ed35d7e74c640ebd4f604f032f27463411cd3",
+    "chains/sdd-full.chain.md": "4af3ff8b5b1d4f17cdfbda26f150fc017f82aa7f43aa4db3a2eb4fd2fd20f81b",
+    "chains/sdd-plan.chain.md": "938c39f711539eae5b3f04c3aa031387ad420f7d7049906213a71c2e2704928c",
+    "chains/sdd-verify.chain.md": "48c3861eb5912631e54658281064c2c346b633fa36cf8d43cf862a1d5e56b40e",
+    "gentle-ai/support/sdd-status-contract.md": "b6796a3958e24f747446e9514a62bce1cbeab26a115e79f500eeb8fbdde5a1ae",
+    "gentle-ai/support/strict-tdd-verify.md": "becb50da4841aae5f6b157462efbfcd4f20332c0c054c82a55970450be8e649c",
+    "gentle-ai/support/strict-tdd.md": "2b0340bfa1160db7f609a4e1b6a24bbd3a1b1a8347b2b65d400865c104fdd237"
+  }
+}

package/assets/orchestrator-delegation.md

@@ -165,22 +165,34 @@ If multiple rows match, run the narrow set that covers the risk. Example: shell
 
 ## 4R Review Triggers
 
-The extension (`extensions/gentle-ai.ts`) gates `bash` tool calls that look like git/gh workflow events. Gate semantics:
+The extension classifies recognized git/gh workflow diffs and emits advice only:
 
-- **pre-commit** (`git commit`): advisory only. The extension notifies the user to consider running `review-readability` but does NOT block. No orchestrator action needed.
-- **pre-push** (`git push`): advisory only. Same as pre-commit — notify, do not block.
-- **pre-pr** (`gh pr create`): **strong gate**. The extension blocks when any of these hold:
-  - Changed paths match hot globs: `**/auth/**`, `**/update/**`, `**/security/**`, `**/payments/**`
-  - Diff exceeds 400 changed lines (added + deleted)
-  - When blocked, the reason names all four agents to run first.
-- **post-sdd-phase** (design, apply): **strong gate** for the packaged `gentle-ai-judgment-day` skill. Handled separately by SDD phase orchestration, not this diff-based hook.
+- **Trivial**: use zero lenses only when complete evidence proves every change is documentation, comments, formatting, or a string typo and no executable/configuration content changed.
+- **Standard**: use exactly one dominant lens. Precedence is risk, resilience, reliability, then readability fallback. Ambiguous executable/configuration changes fail conservatively to standard.
+- **Full 4R**: for a non-trivial hot path or strictly more than 400 changed lines, use `review-risk`, `review-resilience`, `review-readability`, and `review-reliability` in that order. Exactly 400 remains standard; 401 is full.
+- **Event ceiling**: pre-commit and pre-push never run full 4R; cap them at one standard lens. Pre-PR, CI, and schedule may run full 4R.
 
-When the extension blocks a `gh pr create` command, the orchestrator must launch the `4r-review` chain (or run the four agents individually) and wait for their reports before the user retries the PR command.
-
-Prohibition: do NOT configure the full 4R fan-out on `pre-commit` or `pre-push` with `always: true`. Everyday events must use a single advisory lens to keep development-loop cost low (spec G token-budget rule). The `validateTriggerRuleSet` function in `lib/review-triggers.ts` enforces this at config load time.
+Review advice never pauses, denies, or requires a receipt. Continue to independent command safety after notification; dangerous-command denial or confirmation remains authoritative. Post-SDD design/apply uses the separate Judgment Day path.
 
 ### Review Execution Contract
 
+The parent owns merge, persistence, refutation, voting, fixes, and scoped re-review. The static `4r-review` chain performs lens discovery and returns reports only.
+
+**Precision limits.** Standard review runs exactly one complete sweep. Full 4R runs at most two complete sweeps per lens. Every finding MUST include concrete evidence of user impact; speculative findings are rejected.
+
+**Findings ledger.** Emit a findings ledger with this schema for every entry:
+
+| Field | Values |
+|-------|--------|
+| `id` | `{LENS}-{NNN}` (e.g. `R1-001`) |
+| `lens` | risk \| readability \| reliability \| resilience \| judgment-day |
+| `location` | `path/to/file.ext:line` or `:start-end` |
+| `severity` | BLOCKER \| CRITICAL \| WARNING \| SUGGESTION |
+| `status` | open \| refuted \| fixed \| verified \| wont-fix \| info |
+| `evidence` | why it matters |
+
+`refuted` is terminal and MUST NOT be reopened by later rounds. WARNING and SUGGESTION rows are recorded once with status `info` and MUST NOT schedule fixes.
+
 **Ledger persistence honors the artifact store.**
 - `openspec`: write `openspec/changes/{change-name}/review-ledger.md`.
 - `engram`: upsert topic `sdd/{change-name}/review-ledger` (ad-hoc judgment-day without a change: `review/{target-slug}/ledger`, where `target-slug` = `pr-{number}` when reviewing a PR, else the current branch name kebab-cased, else a kebab-case slug of the user-stated review target). If the engram upsert fails or the memory tool is unavailable, fall back to keeping the ledger inline in the response and explicitly report the degradation — never continue as if persistence succeeded.
@@ -188,6 +200,14 @@ Prohibition: do NOT configure the full 4R fan-out on `pre-commit` or `pre-push`
 
 If the first pass finds nothing, persist an empty ledger record rather than skip persistence.
 
+**Constant refutation.** When no surviving BLOCKER/CRITICAL candidates exist, refutation launches zero actors. Standard review launches exactly one non-parallel general refuter. Full 4R launches exactly three parallel refuters: correctness, impact/exploitability, and reproducibility. Every active refuter receives the complete merged BLOCKER/CRITICAL candidate list. Per-finding refuter tasks and replacement refuters are forbidden.
+
+**Mode-specific voting.** Refuter outputs are keyed by finding ID. In standard review, the general refuter's single `refuted` verdict terminally refutes only that finding. In full 4R, at least two of three valid `refuted` verdicts terminally refute only that finding. `stands`, unknown, duplicate, malformed, omitted, or missing verdicts preserve the finding.
+
+**Scoped convergence.** Re-review receives only the authoritative ledger and the fix diff. Re-review assesses affected ledger rows and regressions introduced by the fix. Only surviving BLOCKER/CRITICAL rows MAY schedule a fix round. At most two scoped fix/re-review rounds may run. Severe rows surviving round two MUST escalate; a third round MUST NOT run.
+
+**Judgment Day exception.** Each Judgment Day judge runs exactly one complete blind sweep. Judgment Day launches exactly two blind judges in parallel and zero refuters. Judgment Day applies the same two-round limit to surviving BLOCKER/CRITICAL rows. Judgment Day WARNING and SUGGESTION rows remain `info` and MUST NOT schedule fixes.
+
 Subagent execution-mode: this agent runs its lens exhaustively as a dedicated Pi subagent and returns its own ledger rows in its Output; the orchestrator merges those ledger rows into the persisted ledger.
 
 Fix execution-mode: jd-fix-agent applies only confirmed ledger findings and hands control back to the orchestrator, which runs the scoped re-judge.

package/assets/orchestrator.md

@@ -107,9 +107,9 @@ For skill-shaped requests, do not treat injected `<available_skills>` as complet
 
 ## 4R Review Triggers
 
-`extensions/gentle-ai.ts` gates git/gh `bash`: pre-commit/pre-push only suggest `review-readability`; pre-pr blocks on hot auth/update/security/payments paths or over 400 changed lines and requires `review-risk`, `review-resilience`, `review-readability`, `review-reliability`; post-SDD design/apply uses `gentle-ai-judgment-day`.
+Route objectively trivial diffs to zero lenses. Route ordinary or ambiguous executable/configuration diffs to standard review with exactly one dominant lens: `review-risk`, `review-resilience`, `review-reliability`, or `review-readability` fallback. Exactly 400 changed lines remains standard; 401 changed lines or a non-trivial hot path runs full 4R in stable risk, resilience, readability, reliability order.
 
-When blocked, run `4r-review` or all four review agents before retrying.
+Pre-commit and pre-push never run full 4R. Review advice never blocks a command. Dangerous-command confirmation remains authoritative. Post-SDD design/apply remains the separate `gentle-ai-judgment-day` path.
 
 ### Review Execution Contract