peaks-loop 3.0.0 → 3.0.2

package/skills/peaks-qa/references/qa-transition-gates.md

@@ -13,21 +13,21 @@
 
 Security and performance evidence surface under `rd/security-review.md` and `rd/perf-baseline.md` (peaks-rd's audit fan-out) and are referenced by reference from the QA test report body. The pre-v2.11.0 `qa/security-findings.md` / `qa/performance-findings.md` files are no longer required; existing ones are kept for auditability but ignored by the gate.
 
-**Peaks-Cli Gate A — After test-case generation:**
+**Peaks-Loop Gate A — After test-case generation:**
 ```bash
 ls .peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md
 # Expected: .peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md
 # "No such file" → STOP, generate test cases first.
 ```
 
-**Peaks-Cli Gate A2 — After test execution: tests actually ran (CRITICAL):**
+**Peaks-Loop Gate A2 — After test execution: tests actually ran (CRITICAL):**
 ```bash
 npx vitest run --changed --reporter=verbose 2>&1 | tail -30
 # Expected: exit code 0, actual test output
 # "0 tests executed" or "no test files found" → BLOCKED.
 ```
 
-**Peaks-Cli Gate A3 — Security review referenced (v2.11.0 D1/D4: read-only reference, NOT a separate QA file):**
+**Peaks-Loop Gate A3 — Security review referenced (v2.11.0 D1/D4: read-only reference, NOT a separate QA file):**
 ```bash
 # peaks-qa does NOT own a qa/security-findings.md. peaks-rd's audit fan-out
 # produces rd/security-review.md; QA references it by path in the test report body.
@@ -36,7 +36,7 @@ grep -E "rd/security-review\\.md|security-review" .peaks/_runtime/<sessionId>/qa
 # Empty → BLOCKED: the test report must cite where security evidence lives.
 ```
 
-**Peaks-Cli Gate A4 — Performance baseline referenced (v2.11.0 D1/D4: read-only reference, NOT a separate QA file):**
+**Peaks-Loop Gate A4 — Performance baseline referenced (v2.11.0 D1/D4: read-only reference, NOT a separate QA file):**
 ```bash
 # peaks-qa does NOT own a qa/performance-findings.md. peaks-rd's audit fan-out
 # produces rd/perf-baseline.md; QA references it by path in the test report body.
@@ -45,14 +45,14 @@ grep -E "rd/perf-baseline\\.md|perf-baseline" .peaks/_runtime/<sessionId>/qa/tes
 # Empty → BLOCKED: the test report must cite where perf evidence lives.
 ```
 
-**Peaks-Cli Gate B — After test-report write (MUST contain execution results):**
+**Peaks-Loop Gate B — After test-report write (MUST contain execution results):**
 ```bash
 ls .peaks/_runtime/<sessionId>/qa/test-reports/<rid>.md
 grep -c "pass\|fail\|blocked" .peaks/_runtime/<sessionId>/qa/test-reports/<rid>.md
 # Zero → the report is empty/template-only. Tests were not executed.
 ```
 
-**Peaks-Cli Gate C — Before issuing verdict:**
+**Peaks-Loop Gate C — Before issuing verdict:**
 ```bash
 ls .peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md \
    .peaks/_runtime/<sessionId>/qa/test-reports/<rid>.md \
@@ -62,7 +62,7 @@ ls .peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md \
 # QA cites them by reference from the test-report body (see Gates A3/A4).
 ```
 
-**Peaks-Cli Gate E — Acceptance coverage:**
+**Peaks-Loop Gate E — Acceptance coverage:**
 ```bash
 peaks scan acceptance-coverage --rid <rid> --project <repo> --session-id <session-id> --json
 # Expected: ok=true. exit 0.
@@ -70,13 +70,13 @@ peaks scan acceptance-coverage --rid <rid> --project <repo> --session-id <sessio
 # invalidReferences[] non-empty → BLOCKED.
 ```
 
-**Peaks-Cli Gate F — QA artifact body has no unfilled placeholders:**
+**Peaks-Loop Gate F — QA artifact body has no unfilled placeholders:**
 ```bash
 peaks request lint <rid> --role qa --project <repo> --session-id <session-id> --json
 # Expected: ok=true. exit 0.
 ```
 
-**Peaks-Cli Gate D — Frontend browser evidence (BLOCKING when frontend is in scope):**
+**Peaks-Loop Gate D — Frontend browser evidence (BLOCKING when frontend is in scope):**
 ```bash
 ls .peaks/_runtime/<sessionId>/qa/screenshots/*.png 2>&1
 # Expected: one or more .png files

package/skills/peaks-qa/references/regression-gates.md

@@ -9,7 +9,7 @@ QA must be involved before refactor implementation.
 - baseline report;
 - acceptance checks;
 - API validation evidence when API behavior is in scope;
-- Playwright MCP browser E2E evidence when a frontend exists or UI is in scope (the LLM checks its tool list for `mcp__playwright__*`; if absent, the user installs via `claude mcp add playwright -- npx @playwright/mcp@latest` for Claude Code, or the IDE-native install command otherwise — peaks-cli no longer auto-installs as of slice #016; capture with `browser_snapshot`, `browser_take_screenshot`, `browser_console_messages`, `browser_network_requests`), with mandatory visible-browser confirmation;
+- Playwright MCP browser E2E evidence when a frontend exists or UI is in scope (the LLM checks its tool list for `mcp__playwright__*`; if absent, the user installs via `claude mcp add playwright -- npx @playwright/mcp@latest` for Claude Code, or the IDE-native install command otherwise — peaks-loop no longer auto-installs as of slice #016; capture with `browser_snapshot`, `browser_take_screenshot`, `browser_console_messages`, `browser_network_requests`), with mandatory visible-browser confirmation;
 - security check evidence;
 - performance check evidence;
 - validation report;

package/skills/peaks-rd/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: peaks-rd
-description: Research and development skill for Peaks. Use for engineering analysis, refactor planning, project scanning, code standards, unit-test coverage gates, implementation contracts, task graphs, and RD handoffs. Always use this for Peaks-Cli refactor workflows.
+description: Research and development skill for Peaks. Use for engineering analysis, refactor planning, project scanning, code standards, unit-test coverage gates, implementation contracts, task graphs, and RD handoffs. Always use this for Peaks-Loop refactor workflows.
 ---
 
 ## Single-scope-axis naming convention
@@ -30,9 +30,9 @@ Cross-references: Slice 1 PRD §AC-1 / `tests/unit/skills/karpathy-prompt-inject
 
 The canonical scope dir for this request is provided as `envelope.data.scopeDir` (absolute path). Write all reviewable files under that path. **NEVER** construct paths like `.peaks/_runtime/<sessionId>/...` from frontmatter — the path has already been resolved by the CLI.
 
-# Peaks-Cli RD
+# Peaks-Loop RD
 
-Peaks-Cli RD owns engineering analysis, implementation planning, and refactor execution contracts.
+Peaks-Loop RD owns engineering analysis, implementation planning, and refactor execution contracts.
 
 ## Hard contracts for browser self-test (BLOCKING — read before any browser_take_screenshot / login flow)
 
@@ -95,7 +95,7 @@ After `peaks scan libraries` lands the dependency list under `## Library version
 
 ## GStack integration and code dry-runs
 
-Map gstack stages to Peaks-Cli RD risk matrices, task graphs, and slice contracts. Adapt gstack concepts into Peaks-Cli artifacts; do not invoke gstack commands as runtime deps. Dry-run before planning, after each slice, before handoff.
+Map gstack stages to Peaks-Loop RD risk matrices, task graphs, and slice contracts. Adapt gstack concepts into Peaks-Loop artifacts; do not invoke gstack commands as runtime deps. Dry-run before planning, after each slice, before handoff.
 
 → see `references/rd-gstack-integration.md` for the full integration contract.
 
@@ -107,7 +107,7 @@ Before every code or mock change, RD must write and then enforce a red-line scop
 2. name adjacent surfaces explicitly out of scope (list pages, delete/update flows, unrelated API endpoints, existing data records, auth, permissions, shared runtime config);
 3. reject any implementation that modifies, deletes, mocks, or replaces out-of-scope behavior just to make validation pass;
 4. for API/mock work, mock only the exact request path and method required by the approved slice;
-5. before handoff, run `peaks scan diff-vs-scope --rid <rid> --project <repo>` (Peaks-Cli Gate B8). The CLI auto-allows test files and `.peaks/` artifacts.
+5. before handoff, run `peaks scan diff-vs-scope --rid <rid> --project <repo>` (Peaks-Loop Gate B8). The CLI auto-allows test files and `.peaks/` artifacts.
 
 ## Mandatory tech-doc output (RD-side)
 
@@ -133,7 +133,7 @@ The THREE review activities run in parallel via `peaks sub-agent dispatch <role>
 
 > **v2.12.0 collapse (Group A):** the 5-way fan-out moved `security-reviewer` + `perf-baseline-reviewer` into standalone audit skills (`peaks-security-audit` + `peaks-perf-audit`). → `references/v2-12-fanout-collapse.md`.
 
-> **v2.15.0+:** 技术决策 AI 据 prd 业务场景块自决,user 不参与;存量项目无 UT,改 A 前跑 `peaks impact scan`(G13);fork 场景 tech-doc 列上游基线+业务 patch 集(G11)。详见 `.peaks/memory/peaks-cli-user-role-and-tech-decision.md`。
+> **v2.15.0+:** 技术决策 AI 据 prd 业务场景块自决,user 不参与;存量项目无 UT,改 A 前跑 `peaks impact scan`(G13);fork 场景 tech-doc 列上游基线+业务 patch 集(G11)。详见 `.peaks/memory/peaks-loop-user-role-and-tech-decision.md`。
 
 > **Slice 2026-06-24-efficiency-4p-bundle / G4 (P1.3) — karpathy-skip policy authoritative.** Decision table at `src/services/rd/reviewer-dispatch-policy.ts` (`shouldDispatchKarpathy`, `reviewerListFor`). Pinned by `tests/unit/rd/karpathy-skip-on-config-docs-chore.test.ts`.
 
@@ -141,7 +141,7 @@ The THREE review activities run in parallel via `peaks sub-agent dispatch <role>
 
 The `karpathy-reviewer` sub-agent is a **hard gate** for `rd:qa-handoff`. Per `andrej-karpathy-skills:karpathy-guidelines` §1 Think Before Coding ("state your assumptions") + §3 Surgical Changes ("touch only what the user asked"), `peaks request transition --state qa-handoff` is BLOCKED by the CLI gate until `.peaks/_runtime/<sessionId>/rd/karpathy-review.md` exists with the `## Karpathy-Gate` header and at least one of the 4 guideline section markers. The file is enforced by the `KARPATHY_REVIEW` prerequisite in `src/services/artifacts/artifact-prerequisites.ts` (added in Slice 5). The escape hatch is `peaks request transition --allow-incomplete --confirm` (assisted mode). The companion `peaks scan karpathy` CLI is a structural scanner for the same file (`src/services/scan/karpathy-service.ts`); the semantic review is the sub-agent's job.
 
-### Peaks-Cli Gate C — type-specific RD evidence
+### Peaks-Loop Gate C — type-specific RD evidence
 
 The CLI gate at `rd:qa-handoff` is the authoritative check. Missing any required file → DO NOT attempt the qa-handoff transition; CLI will reject with `PREREQUISITES_MISSING`.
 
@@ -170,9 +170,9 @@ For non-trivial RD changes, use OpenSpec when the project already has `openspec/
 
 Create or update `openspec/changes/<change-id>/proposal.md`, `design.md`, `tasks.md`, and `specs/**/spec.md` before implementation slices begin. If the repository uses a different existing OpenSpec layout, follow that layout and record the file paths in the RD handoff.
 
-OpenSpec artifacts are durable project specification files, not Peaks-Cli runtime swarm artifacts. They may live in the target repository root under `openspec/changes/...`. Swarm/runtime outputs such as task graphs, worker briefs, worker reports, reducer reports, scan reports, validation evidence, and compact handoffs must remain in the configured Peaks-Cli artifact workspace outside the target repository.
+OpenSpec artifacts are durable project specification files, not Peaks-Loop runtime swarm artifacts. They may live in the target repository root under `openspec/changes/...`. Swarm/runtime outputs such as task graphs, worker briefs, worker reports, reducer reports, scan reports, validation evidence, and compact handoffs must remain in the configured Peaks-Loop artifact workspace outside the target repository.
 
-Peaks-Cli PRD/RD/QA gates remain authoritative: OpenSpec structures the durable spec, while Peaks-Cli artifacts still carry role handoffs, coverage gates, QA evidence, swarm coordination, and execution state.
+Peaks-Loop PRD/RD/QA gates remain authoritative: OpenSpec structures the durable spec, while Peaks-Loop artifacts still carry role handoffs, coverage gates, QA evidence, swarm coordination, and execution state.
 
 → see `references/openspec-cli.md` for the CLI recipes.
 
@@ -190,7 +190,7 @@ When RD work creates a frontend application and the user has not specified a tec
 
 ## Artifact and standards output
 
-When project identification or scanning produces reports, matrices, maps, plans, or validation files, write them under the configured Peaks-Cli artifact workspace (default: `.peaks/_runtime/<sessionId>/rd/`). Do not default to a git-backed artifact repository or external artifact sync. Route standards mutations through `peaks standards init/update`; do not hand-write. Do not update user-global `~/.claude/rules/**` from this workflow.
+When project identification or scanning produces reports, matrices, maps, plans, or validation files, write them under the configured Peaks-Loop artifact workspace (default: `.peaks/_runtime/<sessionId>/rd/`). Do not default to a git-backed artifact repository or external artifact sync. Route standards mutations through `peaks standards init/update`; do not hand-write. Do not update user-global `~/.claude/rules/**` from this workflow.
 
 → see `references/artifact-and-standards-output.md` for the full contract.
 
@@ -206,17 +206,17 @@ The handoff artifact carries **mandatory YAML frontmatter** (`requestId`, `scope
 
 ## Codegraph project analysis
 
-Codegraph is local project-analysis evidence, scoped to red-line scope boundaries (changed files / symbols) and read via `peaks codegraph affected --project <path> <changed-files...> --json`. Peaks-Cli RD gates remain authoritative; codegraph is untrusted supporting evidence. Do not let codegraph output drive scope, design, or QA verdict decisions, and never mutate agent settings, Claude settings, or hooks from codegraph. Do not commit `.codegraph/` artifacts or persist generated `.codegraph/` databases into git. Codegraph context is written to `.peaks/_runtime/<sessionId>/rd/codegraph-context.md` for handoff to QA / TXT.
+Codegraph is local project-analysis evidence, scoped to red-line scope boundaries (changed files / symbols) and read via `peaks codegraph affected --project <path> <changed-files...> --json`. Peaks-Loop RD gates remain authoritative; codegraph is untrusted supporting evidence. Do not let codegraph output drive scope, design, or QA verdict decisions, and never mutate agent settings, Claude settings, or hooks from codegraph. Do not commit `.codegraph/` artifacts or persist generated `.codegraph/` databases into git. Codegraph context is written to `.peaks/_runtime/<sessionId>/rd/codegraph-context.md` for handoff to QA / TXT.
 
 ## Matt Pocock skills integration
 
-Matt Pocock skills (`diagnose` / `triage` / `tdd` / `improve-codebase-architecture` / `prototype`): engineering references only. Inspect before applying; Peaks-Cli RD gates remain authoritative. Understand Anything: `peaks understand status/show --json`. Codegraph: local analysis only, never commit `.codegraph/` artifacts. Other external resources: `peaks capabilities --source access-repo/mcp-server --json` for capability discovery.
+Matt Pocock skills (`diagnose` / `triage` / `tdd` / `improve-codebase-architecture` / `prototype`): engineering references only. Inspect before applying; Peaks-Loop RD gates remain authoritative. Understand Anything: `peaks understand status/show --json`. Codegraph: local analysis only, never commit `.codegraph/` artifacts. Other external resources: `peaks capabilities --source access-repo/mcp-server --json` for capability discovery.
 
 → see `references/external-references.md` + `references/matt-pocock-integration.md` + `references/codegraph-project-analysis.md`.
 
 ## Boundaries
 
-Do not bypass PRD/QA artifacts. Do not install hooks, agents, MCP, or settings. Ask the Peaks-Cli CLI to handle runtime side effects.
+Do not bypass PRD/QA artifacts. Do not install hooks, agents, MCP, or settings. Ask the Peaks-Loop CLI to handle runtime side effects.
 
 Do not bypass the parallel review fan-out when the slice has a code-review / qa-test-cases / karpathy-review surface — see `## Parallel review fan-out` above. The three review activities are fan-out, not sequential; sequential re-implementation of the same logic by the main RD loop defeats the wall-clock benefit and is treated as a red-line violation.
 

package/skills/peaks-rd/references/artifact-and-standards-output.md

@@ -1,6 +1,6 @@
 # Artifact and standards output (RD)
 
-> Body of `## Artifact and standards output`. When project identification or scanning produces reports, matrices, maps, plans, or validation files, write them under the configured Peaks-Cli artifact workspace. By default, use local non-git storage at `.peaks/_runtime/<sessionId>/rd/` in the target project or the Peaks-Cli CLI-provided local workspace. If the artifact workspace is unknown, create or request `.peaks/_runtime/<sessionId>/` before writing generated outputs. Use one session directory consistently so generated outputs stay grouped.
+> Body of `## Artifact and standards output`. When project identification or scanning produces reports, matrices, maps, plans, or validation files, write them under the configured Peaks-Loop artifact workspace. By default, use local non-git storage at `.peaks/_runtime/<sessionId>/rd/` in the target project or the Peaks-Loop CLI-provided local workspace. If the artifact workspace is unknown, create or request `.peaks/_runtime/<sessionId>/` before writing generated outputs. Use one session directory consistently so generated outputs stay grouped.
 
 Do not default to a git-backed artifact repository, external artifact sync, or automatic commits for intermediate artifacts. Git inclusion or sync requires explicit user confirmation or an active profile that clearly authorizes it. Browser evidence must be sanitized before retention: do not store login URLs, cookies, headers, tokens, storage state, browser traces, or screenshots/logs containing PII or SSO/MFA material.
 

package/skills/peaks-rd/references/codegraph-project-analysis.md

@@ -2,4 +2,4 @@
 
 > Body of `## Codegraph project analysis`. RD may use `peaks codegraph affected --project <path> <changed-files...> --json` as local project-analysis evidence to inform red-line scope boundaries before writing tech-doc or starting implementation. Treat the output as untrusted supporting evidence — verify against the actual code before relying on it.
 
-Do not run upstream installer flows, mutate agent settings, or commit `.codegraph/` artifacts. Peaks-Cli RD gates remain authoritative for handoff and acceptance.
+Do not run upstream installer flows, mutate agent settings, or commit `.codegraph/` artifacts. Peaks-Loop RD gates remain authoritative for handoff and acceptance.

package/skills/peaks-rd/references/external-references.md

@@ -1,11 +1,11 @@
 # External references (RD)
 
-> Body of `## External references`. **Matt Pocock skills** (`diagnose`, `triage`, `tdd`, `improve-codebase-architecture`, `prototype`): Engineering references only. Inspect before applying; Peaks-Cli RD gates remain authoritative.
+> Body of `## External references`. **Matt Pocock skills** (`diagnose`, `triage`, `tdd`, `improve-codebase-architecture`, `prototype`): Engineering references only. Inspect before applying; Peaks-Loop RD gates remain authoritative.
 
 **Understand Anything**: Consume via `peaks understand status/show --json`. Fall back to `peaks codegraph context` or local project scan when absent.
 
 **Codegraph**: Optional local analysis via `peaks codegraph context/affected`. Output as untrusted supporting evidence; never commit `.codegraph/` artifacts.
 
-**Other external resources** (Context7, SearchCode, everything-claude-code, GitNexus, etc.): Use `peaks capabilities --source access-repo/mcp-server --json` for capability discovery before recommending. References only — do not execute upstream installers, do not install upstream resources, do not persist sensitive examples. Peaks-Cli RD gates remain authoritative.
+**Other external resources** (Context7, SearchCode, everything-claude-code, GitNexus, etc.): Use `peaks capabilities --source access-repo/mcp-server --json` for capability discovery before recommending. References only — do not execute upstream installers, do not install upstream resources, do not persist sensitive examples. Peaks-Loop RD gates remain authoritative.
 
-**OpenSpec CLI**: Route through Peaks-Cli CLI (`peaks openspec show/to-rd/render`). Do not hand-edit `openspec/changes/**`. Recipes: `references/openspec-cli.md`.
+**OpenSpec CLI**: Route through Peaks-Loop CLI (`peaks openspec show/to-rd/render`). Do not hand-edit `openspec/changes/**`. Recipes: `references/openspec-cli.md`.

package/skills/peaks-rd/references/karpathy-reviewer-prompt.md

@@ -1,2 +1,2 @@
 # Canonical karpathy-reviewer prompt lives at: agents/karpathy-reviewer.md
-# This file is a 2-line pointer. Edit the canonical file instead. (peaks-cli 2.0 rules convention)
+# This file is a 2-line pointer. Edit the canonical file instead. (peaks-loop 2.0 rules convention)

package/skills/peaks-rd/references/mandatory-perf-baseline.md

@@ -39,4 +39,4 @@ peaks perf baseline --project <repo> --apply --reason "capturing baseline for Ga
 
 **Idempotency:** re-running `peaks perf baseline --apply` on a session where the file already exists is a no-op (the CLI does not overwrite hand-edited content). This is the normal RD retry pattern (re-measurement, threshold adjustment, etc.). If the RD really does want to overwrite, delete the file first and re-run.
 
-**The role of the CLI vs. the actual measurement:** the CLI is the *scaffolding*. It writes the file, exposes the path, and keeps the file's structure stable so QA can rely on it. The CLI does NOT call lighthouse / k6 / autocannon — those are project-shape dependent and the right tool is a project-local concern, not a peaks-cli concern. The CLI is justified (4-grounds check): it gates the QA-side decision on a stable artefact, it requires --apply for a destructive write, and it is invokable from a hook on session init. It is *not* a machine-enforced gate that prose cannot enforce — the measurement is the RD's responsibility.
+**The role of the CLI vs. the actual measurement:** the CLI is the *scaffolding*. It writes the file, exposes the path, and keeps the file's structure stable so QA can rely on it. The CLI does NOT call lighthouse / k6 / autocannon — those are project-shape dependent and the right tool is a project-local concern, not a peaks-loop concern. The CLI is justified (4-grounds check): it gates the QA-side decision on a stable artefact, it requires --apply for a destructive write, and it is invokable from a hook on session init. It is *not* a machine-enforced gate that prose cannot enforce — the measurement is the RD's responsibility.

package/skills/peaks-rd/references/matt-pocock-integration.md

@@ -1,6 +1,6 @@
 ## Matt Pocock skills integration (RD)
 
-> Body of `## Matt Pocock skills integration`. Engineering methods from `mattpocock/skills` can inform RD work but never replace Peaks-Cli gates. Inspect upstream skill content before applying any method.
+> Body of `## Matt Pocock skills integration`. Engineering methods from `mattpocock/skills` can inform RD work but never replace Peaks-Loop gates. Inspect upstream skill content before applying any method.
 
 - `diagnose` — root-cause investigation before fixing
 - `triage` — prioritize bug surface area
@@ -8,4 +8,4 @@
 - `improve-codebase-architecture` — opportunistic refactor framing
 - `prototype` — throwaway exploration before committing to a slice
 
-These are references only; Peaks-Cli RD gates remain authoritative for handoff, acceptance, and slice closure.
+These are references only; Peaks-Loop RD gates remain authoritative for handoff, acceptance, and slice closure.

package/skills/peaks-rd/references/ocr-integration.md

@@ -1,11 +1,11 @@
 # OCR (Open Code Review) integration
 
 > Soft-optional second-opinion code review for peaks-rd Gate B3.
-> Mirrors the ECC 64-agents pattern (spec §7.2): peaks-cli ships
+> Mirrors the ECC 64-agents pattern (spec §7.2): peaks-loop ships
 > `@alibaba-group/open-code-review` as an **`optionalDependency`**
 > (was promoted to `dependencies` in 2.0.1 and reverted in 2.0.3
 > because its postinstall downloads a Go binary via HTTPS and would
-> otherwise abort `npm i -g peaks-cli` in restricted/proxied
+> otherwise abort `npm i -g peaks-loop` in restricted/proxied
 > environments). The LLM endpoint config still lives under
 > `peaksConfig.ocr.llm` in the user's `~/.peaks/config.json` (single
 > source of truth, user-managed). When the user installs + configures
@@ -40,10 +40,10 @@ ships without the second opinion.
 ## Install
 
 `@alibaba-group/open-code-review` is an **`optionalDependency`** of
-peaks-cli 2.0.3+ (was a required `dependency` in 2.0.1/2.0.2; reverted
+peaks-loop 2.0.3+ (was a required `dependency` in 2.0.1/2.0.2; reverted
 because the postinstall downloads a Go binary via HTTPS, which fails in
 restricted/proxied environments and would otherwise abort
-`npm i -g peaks-cli`). peaks-cli does NOT auto-install it. To enable
+`npm i -g peaks-loop`). peaks-loop does NOT auto-install it. To enable
 the second-opinion review:
 
 ```bash
@@ -61,17 +61,17 @@ Five possible states:
 
 | state | Meaning | Recovery |
 |---|---|---|
-| `ready` | Installed + binary downloaded + peaks-cli's `peaksConfig.ocr.llm` valid | Nothing — `run-ocr` will work. |
-| `package-missing` | npm dep not installed (peaks-cli 2.0.3+ ships with ocr as an `optionalDependency`, so the common cause is the user has not installed it yet, or it was removed from node_modules) | `npm i -g @alibaba-group/open-code-review` (peaks-cli no longer auto-installs it; under pnpm also run `pnpm approve-builds @alibaba-group/open-code-review`) |
+| `ready` | Installed + binary downloaded + peaks-loop's `peaksConfig.ocr.llm` valid | Nothing — `run-ocr` will work. |
+| `package-missing` | npm dep not installed (peaks-loop 2.0.3+ ships with ocr as an `optionalDependency`, so the common cause is the user has not installed it yet, or it was removed from node_modules) | `npm i -g @alibaba-group/open-code-review` (peaks-loop no longer auto-installs it; under pnpm also run `pnpm approve-builds @alibaba-group/open-code-review`) |
 | `binary-missing` | npm dep present but Go binary did not download | `pnpm approve-builds @alibaba-group/open-code-review`, OR run `node node_modules/@alibaba-group/open-code-review/scripts/install.js`, OR manually fetch from https://github.com/alibaba/open-code-review/releases and place the binary at the path shown in `nextActions[2]`. |
 | `config-missing` | binary present but `peaksConfig.ocr.llm` is empty or partial | See "Configure" below. |
 | `detection-failed` | Unexpected error during detection | Inspect stderr; re-run probe. |
 
-## Configure (one-time, per user) — peaks-cli does NOT auto-configure
+## Configure (one-time, per user) — peaks-loop does NOT auto-configure
 
-The LLM endpoint config is **user-maintained inside peaks-cli's own
+The LLM endpoint config is **user-maintained inside peaks-loop's own
 config** at `~/.peaks/config.json` under the `ocr.llm` key. The user
-is the only party that touches their LLM token / URL / model. peaks-cli
+is the only party that touches their LLM token / URL / model. peaks-loop
 never auto-writes the config and never writes `~/.opencodereview/config.json`.
 
 ```bash
@@ -105,7 +105,7 @@ env vars** (ocr's highest-priority config path). The mapping is:
 | `authHeader` | `OCR_LLM_AUTH_HEADER` | One of `authorization` (default Bearer), `x-api-key` (for `sk-ant-*` keys), or `bearer` |
 
 The `~/.opencodereview/config.json` file the user might have set up
-for 2.0.0 is no longer consulted by peaks-cli. The user may delete it
+for 2.0.0 is no longer consulted by peaks-loop. The user may delete it
 at their discretion — the ocr subprocess ignores the file when peaks-
 cli's env vars are present (and the env-var surface is highest priority).
 
@@ -171,7 +171,7 @@ even when ocr is not ready or the subprocess fails. The envelope
 `ok` field carries the success signal; the caller (peaks-rd) is
 expected to pattern-match on `data.state` and proceed without the
 second opinion if needed. This matches the ECC 64-agents
-soft-fail policy and the peaks-cli "minimal user operation"
+soft-fail policy and the peaks-loop "minimal user operation"
 tenet — missing ocr should never block a slice.
 
 ## Security
@@ -181,12 +181,12 @@ tenet — missing ocr should never block a slice.
   tool you opt into: don't point it at a free public endpoint
   for proprietary code; use a vendor / self-hosted endpoint with
   appropriate data controls.
-- peaks-cli does NOT auto-configure ocr. Your `ocr.llm.authToken`
+- peaks-loop does NOT auto-configure ocr. Your `ocr.llm.authToken`
   is yours. Rotate as needed. The token is stored only in the
   user-layer `~/.peaks/config.json` (project layer rejects writes
   to any key matching `isSensitiveConfigPath`), and
   `peaks config get` redacts it as `***`.
-- peaks-cli's wrapper records ocr's `stdout` verbatim in the
+- peaks-loop's wrapper records ocr's `stdout` verbatim in the
   envelope (and in `code-review.md` when peaks-rd merges
   findings). Don't put secrets in your code being reviewed.
 - The `peaks code-review config-template` snippet embeds the
@@ -199,10 +199,10 @@ These are the actual failure modes the wrapper has been
 dogfooded against:
 
 1. **Network blocked from GitHub Releases** during postinstall →
-   `binary-missing`. peaks-cli still runs cleanly because ocr
+   `binary-missing`. peaks-loop still runs cleanly because ocr
    is detected as not-ready; user manually fetches the binary
    and places it at `nextActions[2]`'s path.
-2. **pnpm-installed peaks-cli** → ocr postinstall blocked by
+2. **pnpm-installed peaks-loop** → ocr postinstall blocked by
    pnpm's safe-by-default policy → `binary-missing`. Recover
    with `pnpm approve-builds @alibaba-group/open-code-review`.
 3. **No / partial LLM config** → `config-missing` with
@@ -213,17 +213,17 @@ dogfooded against:
    wrapper soft-fails (`ok: false`, `warnings[0]` includes the
    exit code, `stderr` carries ocr's own error message).
 5. **User 2.0.0 → 2.0.1 migration** — they configured
-   `~/.opencodereview/config.json` for 2.0.0; peaks-cli 2.0.1
+   `~/.opencodereview/config.json` for 2.0.0; peaks-loop 2.0.1
    no longer reads that file. They paste the same values into
-   `~/.peaks/config.json` under `ocr.llm` (peaks-cli handles the
+   `~/.peaks/config.json` under `ocr.llm` (peaks-loop handles the
    camelCase conversion in the template).
 
 ## See also
 
 - ocr upstream: https://github.com/alibaba/open-code-review
-- peaks-cli source: `src/services/code-review/ocr-service.ts`,
+- peaks-loop source: `src/services/code-review/ocr-service.ts`,
   `src/cli/commands/code-review-commands.ts`
-- peaks-cli config schema: `src/services/config/config-types.ts`
+- peaks-loop config schema: `src/services/config/config-types.ts`
   (`OcrLlmConfig`, `OcrConfig`, `PeaksConfig.ocr?`)
 - ECC 64-agents soft-optional pattern (mirrored):
   `src/services/agent/ecc-agent-service.ts`

package/skills/peaks-rd/references/openspec-cli.md

@@ -2,7 +2,7 @@
 
 Peaks RD reads OpenSpec change packs through the Peaks CLI rather than re-parsing markdown or spawning subprocesses by hand. The CLI returns the same stable envelope shape (`{ ok, command, data, warnings, nextActions }`) so RD can capture it as artifact JSON.
 
-> **Slice #016 (2026-06-09)**: this document used to live at `openspec-mcp-cli.md` and contained a section on the now-retired peaks-cli MCP install / call verbs. The MCP subsystem was retired in slice #016; the LLM's own tool list is now the source of truth for installed MCPs. The OpenSpec CLI recipes below are unchanged.
+> **Slice #016 (2026-06-09)**: this document used to live at `openspec-mcp-cli.md` and contained a section on the now-retired peaks-loop MCP install / call verbs. The MCP subsystem was retired in slice #016; the LLM's own tool list is now the source of truth for installed MCPs. The OpenSpec CLI recipes below are unchanged.
 
 ## Loading an existing OpenSpec change as RD input
 
@@ -55,7 +55,7 @@ claude mcp add context7 -- npx @upstash/context7-mcp
 # Restart the IDE after install; the runtime picks up the new server only after a fresh process.
 ```
 
-peaks-cli does not install MCPs on the user's behalf as of slice #016; the LLM is the executor and the IDE is the dispatcher. Evidence of the lookup (sanitized query + response summary) goes into the RD artifact, not full network bodies or secrets.
+peaks-loop does not install MCPs on the user's behalf as of slice #016; the LLM is the executor and the IDE is the dispatcher. Evidence of the lookup (sanitized query + response summary) goes into the RD artifact, not full network bodies or secrets.
 
 ## Boundary
 

package/skills/peaks-rd/references/rd-gstack-integration.md

@@ -2,15 +2,15 @@
 
 > Body of `## GStack integration and code dry-runs`. Use gstack as a concrete engineering workflow reference for `Think → Plan → Build → Review → Test → Ship → Reflect`:
 
-- map plan engineering review to Peaks-Cli RD risk matrices, task graphs, and slice contracts;
+- map plan engineering review to Peaks-Loop RD risk matrices, task graphs, and slice contracts;
 - map build/review discipline to strict spec-first implementation and code-review gates;
 - map investigate/careful/guard concepts to root-cause analysis, risky-action confirmation, and scoped edit boundaries;
-- adapt gstack concepts into Peaks-Cli artifacts rather than invoking gstack commands as runtime dependencies.
+- adapt gstack concepts into Peaks-Loop artifacts rather than invoking gstack commands as runtime dependencies.
 
-When Peaks-Cli RD produces or changes code, dry-run repeatedly instead of only during preflight:
+When Peaks-Loop RD produces or changes code, dry-run repeatedly instead of only during preflight:
 
 1. run standards dry-runs before planning or implementation;
-2. run the relevant Peaks-Cli dry-run again after each meaningful implementation slice or standards-affecting decision;
+2. run the relevant Peaks-Loop dry-run again after each meaningful implementation slice or standards-affecting decision;
 3. after implementation, run required unit tests, code review, and security review before any completion claim;
-4. only after those checks pass, run the relevant Peaks-Cli dry-run before handoff, review, or retention-boundary work;
+4. only after those checks pass, run the relevant Peaks-Loop dry-run before handoff, review, or retention-boundary work;
 5. record commands, results, coverage evidence, reviewer/security findings, dry-run result, and remaining action in the RD handoff capsule.

package/skills/peaks-rd/references/rd-runbook.md

@@ -90,7 +90,7 @@ peaks codegraph affected --project <repo> <changed-files...> --json
 
 # 6. record red-line scope, slice contract, coverage status into the RD artifact, then implement
 
-# 6.5 BEFORE tech-doc: verify EVERY path in the tech-doc against actual project structure (Peaks-Cli Gate A2)
+# 6.5 BEFORE tech-doc: verify EVERY path in the tech-doc against actual project structure (Peaks-Loop Gate A2)
 #     ls every directory path in the tech-doc — zero "No such file" allowed
 #     This is the most common RD failure mode. Do not skip it.
 
@@ -159,21 +159,21 @@ peaks codegraph affected --project <repo> <changed-files...> --json
 #     → `peaks request transition --state qa-handoff` returns `code: PREREQUISITES_MISSING`.
 #     Escape hatch (assisted mode): `--allow-incomplete --confirm`.
 
-# 6.6 BEFORE implementation: verify CLAUDE.md + .claude/rules/ exist (Peaks-Cli Gate A3)
+# 6.6 BEFORE implementation: verify CLAUDE.md + .claude/rules/ exist (Peaks-Loop Gate A3)
 #     Missing standards files → run `peaks standards init --project .` first
 #     Without project rules, security review and code review triggers won't fire.
 
 # 7. AFTER implementation, BEFORE QA handoff — RUN THESE GATES:
-#    Peaks-Cli Gate B2: unit tests exist and pass for the changed surface → npx vitest run --changed (or project equivalent; the changed-only mode is the peaks slice check default as of run 017; use --run-tests for the full suite, or invoke /peaks-solo-test to run the full suite standalone)
-#    Peaks-Cli Gate B3: code review evidence → .peaks/_runtime/<sessionId>/rd/code-review.md
-#    Peaks-Cli Gate B4: security review evidence → .peaks/_runtime/<sessionId>/rd/security-review.md
-#    Peaks-Cli Gate B5 (NEW): RD artifact body has no unfilled placeholders.
+#    Peaks-Loop Gate B2: unit tests exist and pass for the changed surface → npx vitest run --changed (or project equivalent; the changed-only mode is the peaks slice check default as of run 017; use --run-tests for the full suite, or invoke /peaks-solo-test to run the full suite standalone)
+#    Peaks-Loop Gate B3: code review evidence → .peaks/_runtime/<sessionId>/rd/code-review.md
+#    Peaks-Loop Gate B4: security review evidence → .peaks/_runtime/<sessionId>/rd/security-review.md
+#    Peaks-Loop Gate B5 (NEW): RD artifact body has no unfilled placeholders.
 peaks request lint <rid> --role rd --project <repo> --session-id <session-id> --json
-#    Peaks-Cli Gate B6 (NEW): declared --type still matches the actual diff after implementation.
+#    Peaks-Loop Gate B6 (NEW): declared --type still matches the actual diff after implementation.
 peaks scan request-type-sanity --project <repo> --type <type> --json
-#    Peaks-Cli Gate B7 (NEW, repair cycles only): we have not exceeded the 3-cycle cap.
+#    Peaks-Loop Gate B7 (NEW, repair cycles only): we have not exceeded the 3-cycle cap.
 peaks request repair-status <rid> --project <repo> --session-id <session-id> --json
-#    Peaks-Cli Gate B8 (NEW): every changed file matches the RD red-line scope (no out-of-bounds writes).
+#    Peaks-Loop Gate B8 (NEW): every changed file matches the RD red-line scope (no out-of-bounds writes).
 peaks scan diff-vs-scope --rid <rid> --project <repo> --session-id <session-id> --json
 #    All six non-zero → BLOCKED. Fix and re-check before attempting the qa-handoff transition.
 

package/skills/peaks-rd/references/rd-standards-preflight.md

@@ -1,6 +1,6 @@
 # Project standards preflight (RD)
 
-> Body of `## Project standards preflight`. Before RD planning or implementation work in a code repository, call the Peaks-Cli CLI:
+> Body of `## Project standards preflight`. Before RD planning or implementation work in a code repository, call the Peaks-Loop CLI:
 
 - `peaks standards init --project <path> --dry-run`
 - `peaks standards update --project <path> --dry-run`

package/skills/peaks-rd/references/rd-transition-gates.md

@@ -1,4 +1,4 @@
-# Peaks-Cli RD transition verification gates
+# Peaks-Loop RD transition verification gates
 
 > Extracted from `skills/peaks-rd/SKILL.md` on 2026-06-09 (slice 019 — slim skill files to references) to keep SKILL.md under the 800-line cap from `common/coding-style.md`. The content below is the verbatim "Transition verification gates" section that was previously inline; nothing was paraphrased, just relocated.
 
@@ -17,14 +17,14 @@ You cannot declare a phase complete from memory. Each gate below is a `ls` or `g
 >
 > The escape hatch `--allow-incomplete --reason "<text>"` still exists for one-off exceptions; the bypass is recorded in the artifact transition note.
 
-**Peaks-Cli Gate A — After project-scan read (before any implementation):**
+**Peaks-Loop Gate A — After project-scan read (before any implementation):**
 ```bash
 ls .peaks/_runtime/<sessionId>/rd/project-scan.md
 # Expected output: .peaks/_runtime/<sessionId>/rd/project-scan.md
 # "No such file" → STOP, create the project-scan first. Do not write code.
 ```
 
-**Peaks-Cli Gate A2 — Before tech-doc write: project structure verified (PATH CORRECTNESS — CRITICAL):**
+**Peaks-Loop Gate A2 — Before tech-doc write: project structure verified (PATH CORRECTNESS — CRITICAL):**
 ```bash
 # Verify EVERY file path and directory in the tech-doc exists in the actual project.
 # Do not assume paths. Do not guess directory structures. Open the files and verify.
@@ -36,7 +36,7 @@ ls <every-single-directory-path-in-tech-doc> 2>&1 | grep -c "No such file"
 # breaks the implementation, and forces the user to correct the engineer.
 ```
 
-**Peaks-Cli Gate A3 — Before implementation: project standards files exist (CLAUDE.md + .claude/rules/):**
+**Peaks-Loop Gate A3 — Before implementation: project standards files exist (CLAUDE.md + .claude/rules/):**
 ```bash
 ls CLAUDE.md .claude/rules/common/coding-style.md .claude/rules/common/code-review.md .claude/rules/common/security.md 2>&1 | grep -c "No such file"
 # Expected: 0 (all four files exist)
@@ -45,14 +45,14 @@ ls CLAUDE.md .claude/rules/common/coding-style.md .claude/rules/common/code-revi
 # Without CLAUDE.md and .claude/rules/, code review and security review triggers won't fire.
 ```
 
-**Peaks-Cli Gate B — Before QA handoff:**
+**Peaks-Loop Gate B — Before QA handoff:**
 ```bash
 ls .peaks/_runtime/<sessionId>/rd/requests/<rid>.md \
    .peaks/_runtime/<sessionId>/rd/tech-doc.md
 # Both must exist. Missing either → BLOCKED, do not hand off to QA
 ```
 
-**Peaks-Cli Gate B2 — Before QA handoff: unit tests exist and pass for the changed surface:**
+**Peaks-Loop Gate B2 — Before QA handoff: unit tests exist and pass for the changed surface:**
 ```bash
 # Run the project's test command against changed files. Record the output.
 # Example (adapt to project test runner):
@@ -66,7 +66,7 @@ npx vitest run --changed --reporter=verbose 2>&1 | tail -20
 # `--run-tests` flag is the CLI opt-in.
 ```
 
-**Peaks-Cli Gate B3 — Before QA handoff: code review evidence exists:**
+**Peaks-Loop Gate B3 — Before QA handoff: code review evidence exists:**
 ```bash
 ls .peaks/_runtime/<sessionId>/rd/code-review.md 2>&1
 # Expected: .peaks/_runtime/<sessionId>/rd/code-review.md
@@ -74,7 +74,7 @@ ls .peaks/_runtime/<sessionId>/rd/code-review.md 2>&1
 # record findings, fix CRITICAL/HIGH issues, then re-check.
 ```
 
-**Peaks-Cli Gate B4 — Before QA handoff: security review evidence exists:**
+**Peaks-Loop Gate B4 — Before QA handoff: security review evidence exists:**
 ```bash
 ls .peaks/_runtime/<sessionId>/rd/security-review.md 2>&1
 # Expected: .peaks/_runtime/<sessionId>/rd/security-review.md
@@ -82,7 +82,7 @@ ls .peaks/_runtime/<sessionId>/rd/security-review.md 2>&1
 # fix CRITICAL/HIGH issues, record findings, then re-check.
 ```
 
-**Peaks-Cli Gate B5 — RD artifact body has no unfilled placeholders:**
+**Peaks-Loop Gate B5 — RD artifact body has no unfilled placeholders:**
 ```bash
 peaks request lint <rid> --role rd --project <repo> --session-id <session-id> --json
 # Expected: ok=true. exit 0.
@@ -90,7 +90,7 @@ peaks request lint <rid> --role rd --project <repo> --session-id <session-id> --
 # and TBD/TODO marker with line numbers. Fill them in before attempting handoff.
 ```
 
-**Peaks-Cli Gate B6 — Declared --type matches the actual diff:**
+**Peaks-Loop Gate B6 — Declared --type matches the actual diff:**
 ```bash
 peaks scan request-type-sanity --project <repo> --type <type> --json
 # Expected: consistent=true. exit 0.
@@ -99,7 +99,7 @@ peaks scan request-type-sanity --project <repo> --type <type> --json
 # (`peaks request init` with the corrected --type) or trim the scope.
 ```
 
-**Peaks-Cli Gate B7 — Repair cycle cap (only relevant during RD↔QA repair loop):**
+**Peaks-Loop Gate B7 — Repair cycle cap (only relevant during RD↔QA repair loop):**
 ```bash
 peaks request repair-status <rid> --project <repo> --session-id <session-id> --json
 # Expected: atCap=false. exit 0.
@@ -107,7 +107,7 @@ peaks request repair-status <rid> --project <repo> --session-id <session-id> --j
 # handoff via Solo rather than entering a fourth cycle.
 ```
 
-**Peaks-Cli Gate B8 — Diff stays inside the declared red-line scope:**
+**Peaks-Loop Gate B8 — Diff stays inside the declared red-line scope:**
 ```bash
 peaks scan diff-vs-scope --rid <rid> --project <repo> --session-id <session-id> --json
 # Expected: ok=true. exit 0.
@@ -121,7 +121,7 @@ peaks scan diff-vs-scope --rid <rid> --project <repo> --session-id <session-id>
 #   before re-running. Auto-allowed paths (test files, .peaks/, __mocks__/) never need a pattern.
 ```
 
-**Peaks-Cli Gate B9 — RD-side perf-baseline output present (when slice has a user-perceivable perf surface):**
+**Peaks-Loop Gate B9 — RD-side perf-baseline output present (when slice has a user-perceivable perf surface):**
 ```bash
 ls .peaks/_runtime/<sessionId>/rd/perf-baseline.md 2>&1
 # Expected: .peaks/_runtime/<sessionId>/rd/perf-baseline.md

package/skills/peaks-rd/references/skill-presence-and-title.md

@@ -19,4 +19,4 @@ peaks project memories --project <repo> --json
 ```
 
 This returns durable memories from `.peaks/memory` — decisions, conventions, modules, and rules captured in past sessions. Filter with `--kind <decision|convention|module|rule|reference|project>`. (`.peaks/PROJECT.md` is a human-readable session timeline only.)
-Then display: `Peaks-Cli Skill: peaks-rd | Peaks-Cli Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-rd --project <repo> --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear --project <repo>`.
+Then display: `Peaks-Loop Skill: peaks-rd | Peaks-Loop Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-rd --project <repo> --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear --project <repo>`.

package/skills/peaks-reviewer/SKILL.md

@@ -7,13 +7,13 @@ description: Third-party independent code-review skill for Peaks. Use as a paral
 
 > **Read once at the top of this file; the rest of the skill is written against it.**
 
-The `.peaks/` workspace is partitioned by a **single scope axis** (session-id, at `.peaks/_runtime/<sessionId>/...`) with a nested **sub-agent axis** under `.peaks/_sub_agents/<sessionId>/...`. Use `<sessionId>` placeholders (NEVER bare `<sid>`). The peaks-cli change-id axis was removed in slice `2026-06-29-change-id-root-removal`; reviewable artifacts now live under `.peaks/_runtime/<sessionId>/<role>/...` only. OpenSpec's independent `openspec/changes/<change-id>/` vocabulary (L4) is preserved untouched. CLI mapping: session-id → `peaks session *`; sub-agent → `peaks sub-agent *`. Regression test `tests/unit/skills/skills-skill-md-naming.test.ts` enforces (a) zero bare `<sid>`, (b) every `.peaks/_runtime/<X>/` has an axis label, (c) this callout is present.
+The `.peaks/` workspace is partitioned by a **single scope axis** (session-id, at `.peaks/_runtime/<sessionId>/...`) with a nested **sub-agent axis** under `.peaks/_sub_agents/<sessionId>/...`. Use `<sessionId>` placeholders (NEVER bare `<sid>`). The peaks-loop change-id axis was removed in slice `2026-06-29-change-id-root-removal`; reviewable artifacts now live under `.peaks/_runtime/<sessionId>/<role>/...` only. OpenSpec's independent `openspec/changes/<change-id>/` vocabulary (L4) is preserved untouched. CLI mapping: session-id → `peaks session *`; sub-agent → `peaks sub-agent *`. Regression test `tests/unit/skills/skills-skill-md-naming.test.ts` enforces (a) zero bare `<sid>`, (b) every `.peaks/_runtime/<X>/` has an axis label, (c) this callout is present.
 
 ## peaks-context auto-build (v3.0)
 
 The peaks-reviewer workflow automatically runs `peaks context build --audience peaks-reviewer` before the LLM is invoked. No manual setup needed.
 
-# Peaks-Cli Third-Party Reviewer (v2.14.0 G4)
+# Peaks-Loop Third-Party Reviewer (v2.14.0 G4)
 
 `peaks-reviewer` is a **parallel** reviewer to `karpathy-reviewer`. It is intentionally **not** a replacement: karpathy-reviewer keeps enforcing the 4 guidelines; peaks-reviewer adds an out-of-band perspective from a different model family to mitigate single-LLM self-dogfood blind spots.