peaks-loop 4.0.50 → 4.0.52

package/dist/services/workspace/runtime-layout.js

@@ -0,0 +1,148 @@
+/**
+ * The canonical top-level layout of `.peaks/_runtime/`.
+ *
+ * WHY THIS MODULE EXISTS
+ *
+ * `.peaks/_runtime/` holds two populations whose names look identical:
+ *
+ *   1. SESSION DIRS — `<YYYY-MM-DD>-session-<hex>`, one per peaks session.
+ *      Anything else that *looks* like a session id but is not one is a
+ *      defect (a test that passed `--session-id x`, a typo, an old
+ *      `unknown-sid` bucket).
+ *   2. SYSTEM ENTRIES — dirs and files the code itself writes there on
+ *      purpose: `callers/`, `change/`, `benchmarks/`, `session.json`, …
+ *
+ * The doctor check `L3:l3-orphan-sessions` must flag (1) and tolerate (2),
+ * and the only thing that can tell them apart is a list of the system
+ * entries. That list used to live inside the check as a hand-maintained
+ * `new Set(['change'])` — and it had already drifted: `callers/` is a
+ * designed location (`caller-binding-service.ts` stores
+ * `.peaks/_runtime/callers/<callerId>.json`), was never added, and made
+ * `peaks doctor` exit non-zero on a clean workspace *permanently*
+ * (`4 orphan session(s) …: callers, cli, unknown-sid, x`). The check's own
+ * doc comment asked future maintainers to keep a *second* list — the prose
+ * `RUNTIME_SYSTEM_SUBDIRS_DOC` — in sync by hand. Prose cannot enforce
+ * itself, so the two lists diverged exactly as you would expect.
+ *
+ * WHY DERIVATION WAS REJECTED AND A REGISTRY IS THE SOURCE OF TRUTH
+ *
+ * A derivation would have to classify a bare name as "system" or "bogus"
+ * without a list. There is no signal to derive from: `callers` (system) and
+ * `x` (bogus) are the same shape — a lowercase word. The session-id regex
+ * separates them from `2026-09-16-session-5bcf09`, not from each other. So
+ * the alternatives were (a) keep a literal in the check, or (b) put the
+ * literal *and its consumers* in one place. This module is (b): the check
+ * imports the set instead of re-declaring it, and
+ * `tests/unit/workspace/runtime-layout-drift-guard.test.ts` parses `src/**`
+ * and fails when the code writes a `_runtime` child that is not registered
+ * here. The registry can no longer drift silently — it can only drift loudly,
+ * as a red test.
+ *
+ * The guard parses ASTs rather than grepping, because this repository
+ * documents the layout in prose constantly: `migrate-1-4-1-service.ts` has an
+ * array whose two adjacent string literals are `'_runtime', '_sub_agents'`
+ * (they are two *separate* SKIP entries), and `evidence-generator.ts`
+ * describes a past escape as `` `.peaks/_runtime/pwned.md` `` inside a
+ * comment. Both are false positives for a text scan and invisible to an AST
+ * walk. See `tests/unit/runtime/no-runtime-input-guard.test.ts` for the same
+ * decision made the same way.
+ */
+/**
+ * Reserved top-level dir for session-less command output.
+ *
+ * `peaks baseline audit` runs with no bound session (it is the only scorer
+ * that can run inside the secretless OIDC publish gate), so it has no
+ * `<sid>` to write under. It used to pass the literal `'cli'` as its
+ * sessionId, which made `.peaks/_runtime/cli/capability-audit/*.json` look
+ * exactly like a session dir that failed validation — `peaks doctor` has
+ * been red on this repository ever since. The name is underscore-prefixed to
+ * match the tree's existing convention for "machinery, not a session"
+ * (`_runtime`, `_sub_agents`) and to make it impossible to mistake for a
+ * session id.
+ */
+export const RUNTIME_SESSIONLESS_SCOPE = '_audit';
+/**
+ * Every legitimate top-level entry under `.peaks/_runtime/`.
+ *
+ * This is the list `L3:l3-orphan-sessions` tolerates. Adding an entry that
+ * nothing writes is a red test (the drift guard's reverse direction); writing
+ * an entry that is not here is also a red test. Both directions are pinned in
+ * `tests/unit/workspace/runtime-layout-drift-guard.test.ts`.
+ */
+export const RUNTIME_SYSTEM_ENTRIES = [
+    {
+        name: 'change',
+        kind: 'dir',
+        purpose: 'change-id routing root for reviewable artifacts (workflow/artifact-paths.ts, prd/prd-blocks-checker.ts, workspace/reconcile-service.ts)'
+    },
+    {
+        name: 'callers',
+        kind: 'dir',
+        purpose: 'per-caller binding files `.peaks/_runtime/callers/<callerId>.json` (session/caller-binding-service.ts)'
+    },
+    {
+        name: 'benchmarks',
+        kind: 'dir',
+        purpose: '`peaks slice benchmark` artifacts `<rid>.benchmark.json` (cli/commands/slice-commands.ts)'
+    },
+    {
+        name: 'prd',
+        kind: 'dir',
+        purpose: 'read-only PRD artifact root `.peaks/_runtime/prd/requests/<rid>.md` (prd/prd-blocks-checker.ts); the writer lives outside this repo, the check tolerates it'
+    },
+    {
+        name: 'playwright-userdata',
+        kind: 'dir',
+        purpose: 'per-terminal browser profile dirs (cli/commands/playwright-commands.ts)'
+    },
+    {
+        name: 'playwright-sessions',
+        kind: 'dir',
+        purpose: 'playwright session records `<terminalId>.json` (cli/commands/playwright-commands.ts)'
+    },
+    {
+        name: 'test-cache',
+        kind: 'dir',
+        purpose: 'per-test fingerprint cache (cli/commands/test-commands.ts)'
+    },
+    {
+        name: 'sop-state',
+        kind: 'dir',
+        purpose: 'SOP state migrated from `.peaks/sop-state/` (cli/commands/workspace/reconcile-command.ts)'
+    },
+    {
+        name: RUNTIME_SESSIONLESS_SCOPE,
+        kind: 'dir',
+        purpose: 'capability-audit output for session-less runs `.peaks/_runtime/_audit/capability-audit/*.json` (cli/commands/baseline-commands.ts)'
+    },
+    {
+        name: 'session.json',
+        kind: 'file',
+        purpose: 'project-global session binding (session/session-binding-service.ts)'
+    },
+    {
+        name: 'active-skill.json',
+        kind: 'file',
+        purpose: 'active-skill presence marker (skills/skill-presence-service.ts)'
+    },
+    {
+        name: 'generated-artifacts.json',
+        kind: 'file',
+        purpose: 'stamp describing which generated artifacts exist on this machine, so a refresh can tell "stale" from "never generated" (services/workspace/generated-artifacts-stamp.ts)'
+    },
+    {
+        name: '.outer-session-cache.json',
+        kind: 'file',
+        purpose: 'outer (IDE) session cache for CLI sub-processes (cli/commands/outer-cache-commands.ts, session/session-binding-bridge.ts)'
+    },
+    {
+        name: '.rebuild-binding.lock',
+        kind: 'file',
+        purpose: 'binding-store rebuild lock (session/binding-store.ts)'
+    }
+];
+/**
+ * The set `L3:l3-orphan-sessions` filters with. Derived from the registry
+ * above so the check and the census cannot disagree about the same name.
+ */
+export const RUNTIME_SYSTEM_SUBDIRS = new Set(RUNTIME_SYSTEM_ENTRIES.filter((entry) => entry.kind === 'dir').map((entry) => entry.name));

package/dist/services/workspace/workspace-claude-settings-materializer.js

@@ -163,6 +163,20 @@ const PEAKS_GITIGNORE_SNIPPET = [
     '# Both patterns below are PROJECT-ROOT-relative, so this snippet must land',
     '# in the root .gitignore — see `upsertPeaksGitignoreSnippet`.',
     '.peaks/.claude-settings-template.json',
+    '# Codegraph rollback copy (A3, 2026-09-17). Every `peaks codegraph init` /',
+    '# `repair-exclude` / `repair-index` / pre-dispatch preflight / post-slice',
+    '# auto-refresh copies `.codegraph/config.json` here before rewriting it, so',
+    '# this file is LOCAL CHURN: a committed one is silently replaced by the next',
+    '# repair. Upstream\'s own `.codegraph/.gitignore` does not cover it (it names',
+    '# *.db / *.db-wal / *.db-shm, cache/, *.log and .dirty only) and `.codegraph/`',
+    '# is NOT ignored wholesale downstream, so without this line a consumer project',
+    '# commits a file peaks-loop rewrites under it.',
+    '#',
+    '# ONLY the backup, never `config.json` itself: upstream deliberately keeps',
+    '# that config committable (it is a project\'s include/exclude policy, and',
+    '# committing it is how a team shares it), so ignoring it would hide a file',
+    '# people mean to commit. A rollback copy is the opposite kind of file.',
+    '.codegraph/config.json.bak',
     PEAKS_GITIGNORE_FOOTER,
     ''
 ].join('\n');

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "peaks-loop",
-  "version": "4.0.50",
+  "version": "4.0.52",
   "description": "Loop Engineering CLI — workflow primitive / loop guards / evaluators / slice orchestration",
   "author": "SquabbyZ",
   "keywords": [
@@ -102,10 +102,10 @@
     "picomatch": "4.0.4",
     "yaml": "^2.9.0",
     "zod": "^4.4.3",
-    "peaks-loop-mut": "0.1.48",
-    "peaks-loop-internal-runtime": "0.0.35",
-    "peaks-loop-shared-channel": "0.0.52",
-    "peaks-loop-shared": "0.0.84"
+    "peaks-loop-internal-runtime": "0.0.37",
+    "peaks-loop-mut": "0.1.50",
+    "peaks-loop-shared": "0.0.86",
+    "peaks-loop-shared-channel": "0.0.54"
   },
   "devDependencies": {
     "@changesets/cli": "2.31.1",
@@ -128,7 +128,7 @@
     "vitest": "^4.1.10"
   },
   "scripts": {
-    "build": "node ./scripts/sync-version.mjs && node ./scripts/clean-dist.mjs && pnpm -r --filter \"./packages/*\" run build && tsc -p tsconfig.build.json && node ./scripts/copy-templates.mjs && node ./scripts/check-build-integrity.mjs",
+    "build": "node ./scripts/sync-version.mjs && node ./scripts/clean-dist.mjs && pnpm -r --filter \"./packages/*\" run build && tsc -p tsconfig.build.json && node ./scripts/copy-templates.mjs && node ./scripts/check-build-integrity.mjs && node ./scripts/write-dist-stamp.mjs",
     "prepublish": "node ./scripts/sync-version.mjs",
     "postinstall": "node ./scripts/install-skills.mjs",
     "predev": "node ./scripts/sync-version.mjs",

package/scripts/clean-dist.mjs

@@ -10,9 +10,21 @@ const packageRoot = resolve(dirname(fileURLToPath(import.meta.url)), '..');
 // packages/*/dist. Rationale: tsc's incremental-build cache
 // compares files by mtime + size, and a stale dist that
 // survived from a previous build can cause tsc to skip the
-// emission of newly-added src/*.ts (Bug-04 lineage — see
-// tests/unit/scripts/sync-version-invalidation.test.ts for
-// the regression pin on version.ts specifically).
+// emission of newly-added src/*.ts (Bug-04 lineage).
+//
+// E2 (rid 2026-09-17-cli-output-and-stale-refs) — the citation that
+// stood here named a regression pin on version.ts that was deleted
+// in `f17aa377` ("delete 559 legacy unit tests"), and, like the one
+// in `sync-version.mjs`, it was written without backticks so the
+// citation-integrity guard could not see it. Corrected: the pin on
+// the version.ts OUTPUT now lives in the lockstep tests (see
+// `sync-version.mjs` for both names and for what they read).
+//
+// Recorded, not hidden: this wipe itself has no direct pin — no
+// test executes this script, so nothing asserts that a stale
+// packages/*/dist is gone before tsc runs. The `dist-freshness.mjs`
+// module reasons FROM this wipe (it is why a dist mtime can be read
+// as the build time) but does not test it.
 //
 // The wider wipe is safe because:
 //   - watch.mjs only watches src/, schemas/, skills/ — it

package/scripts/sync-version.mjs

@@ -76,8 +76,30 @@ for (const ext of ['js', 'd.ts', 'd.ts.map']) {
 // regression-test pin for Bug-04; the load-bearing dist
 // invalidation moved up to `clean-dist.mjs`, which wipes every
 // packages/*/dist wholesale before any subpackage build runs.
-// This narrow unlink stays because it is unit-tested by
-// tests/unit/scripts/sync-version-invalidation.test.ts and
-// catching the Bug-04 lineage on its own is cheap insurance
-// against future pipeline reorderings.
+// This narrow unlink stays because catching the Bug-04 lineage
+// on its own is cheap insurance against future pipeline
+// reorderings.
+//
+// E2 (rid 2026-09-17-cli-output-and-stale-refs) — the sentence
+// that stood here named a unit test as covering this unlink. That
+// test (file name only, deliberately not spelled as a path: it was
+// deleted in `f17aa377`, "delete 559 legacy unit tests", and a
+// path-shaped token would read as a live citation to the guard
+// that now checks these comments) is `sync-version-invalidation.test.ts`
+// — so the coverage this paragraph claimed has not existed since.
+//
+// What DOES cover this script today, verified rather than
+// assumed: the version lockstep tests pin its two outputs to the
+// root package.json#version — `CLI_VERSION` in
+// packages/peaks-loop-shared/src/version.ts, and the
+// `RUNTIME_VERSION` emit added in slice 2026-09-11 plus the built
+// shared dist/version.js. Both read the artifacts, so they catch a
+// silent no-op in either writer. They are indirect pins, and they
+// are the reason a broken emit cannot ship.
+//
+// NOT COVERED, recorded rather than hidden: the unlink itself has
+// no direct pin. No test executes this script, so nothing asserts
+// that a stale packages/peaks-loop-shared/dist/version.js is
+// actually removed. If you need the unlink pinned, that test has
+// to be written — the one named here no longer exists.
 

package/skills/bee/peaks-perf-audit/SKILL.md

@@ -184,8 +184,8 @@ required fixes deduped by `(file, line, hint)`).
 - Schema: `.peaks/project-scan/audit-output-schema.md`
 - Service: `src/services/audit-independent/perf-audit-service.ts`
 - CLI: `src/cli/commands/perf-audit-commands.ts`
-- Tests: `tests/unit/services/audit-independent/perf-audit-service.test.ts`
-- Companion: `skills/peaks-security-audit/SKILL.md` (symmetric structure)
+- Tests: none — the unit suite for the service was deleted in `f17aa377`.
+- Companion: `skills/bee/peaks-security-audit/SKILL.md` (symmetric structure)
 
 ## Karpathy alignment
 

package/skills/bee/peaks-perf-audit/references/audit-protocol.md

@@ -170,4 +170,4 @@ section is the source of new sediment rows; the format is:
 - Service: `src/services/audit-independent/perf-audit-service.ts`
 - Template: `.peaks/project-scan/perf-template.md`
 - Schema: `.peaks/project-scan/audit-output-schema.md`
-- Companion: `skills/peaks-security-audit/references/audit-protocol.md`
+- Companion: `skills/bee/peaks-security-audit/references/audit-protocol.md`

package/skills/bee/peaks-prd/SKILL.md

@@ -107,7 +107,7 @@ Read persistent project memory via CLI (durable, LLM-authored memories):
 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.)
+This returns durable memories from `.peaks/memory` — decisions, conventions, modules, and rules captured in past sessions. Filter with `--kind <project|decision|convention|rule|reference|feedback|module|lesson|bug|investigation|technical-pattern|project-rule|design|handoff|session-handoff|project-todo|publish-closure|project-closure|slice-closure|slice-pilot-findings|sediment>`. (`.peaks/PROJECT.md` is a human-readable session timeline only.)
 Then display: `Peaks-Loop Skill: peaks-prd | Peaks-Loop Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-prd --project <repo> --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear --project <repo>`.
 
 ## Responsibilities
@@ -147,7 +147,7 @@ PRD 模板在原 7 段基础上,增加 4 个**质量前置必填块**(user 写,A
 3. **UI 装配意图**(页面模式 / 关键交互 / 信息密度;**不画 ASCII 视觉**,视觉由选定的开源组件库自动决定)
 4. **上游基线**(fork 场景必填:当前 fork 基于哪个 tag / 偏离度 / 业务 patch 集)
 
-**反伪选择原则:** user 不参与技术决策(库/框架/语言/性能/安全/架构),只写业务/产品意图。AI 据业务场景块选库选架构。详见 `.peaks/memory/peaks-loop-prd-template-design.md`。
+**反伪选择原则:** user 不参与技术决策(库/框架/语言/性能/安全/架构),只写业务/产品意图。AI 据业务场景块选库选架构。详见 `.peaks/memory/peaks-cli-prd-template-design.md`。
 
 ## Project-scan gate (v2.11.0 D3 — read before brainstorm)
 
@@ -264,7 +264,7 @@ Use gstack as a concrete workflow reference for the product-facing parts of `Thi
 
 ## Authenticated product document workflow
 
-When the source PRD is an authenticated web document such as Feishu/Lark, use the Playwright MCP headed-browser surface rather than unauthenticated fetch tools. Chrome DevTools MCP is a secondary surface that only connects to an already-running Chrome (`--remote-debugging-port=9222`); it does not launch a browser on its own. The canonical browser workflow lives in `peaks-code/references/browser-workflow.md`; the rules below are the PRD-specific application.
+When the source PRD is an authenticated web document such as Feishu/Lark, use the Playwright MCP headed-browser surface rather than unauthenticated fetch tools. Chrome DevTools MCP is a secondary surface that only connects to an already-running Chrome (`--remote-debugging-port=9222`); it does not launch a browser on its own. The canonical browser workflow lives in `../../peaks-code/references/browser-workflow.md`; the rules below are the PRD-specific application.
 
 1. Confirm Playwright MCP is installed: check the LLM tool list for any Playwright MCP entry in the LLM tool list. If absent, the user installs via `claude mcp add playwright -- npx @playwright/mcp@latest` (Claude Code) or the IDE-native install command. Do not hand-edit `.claude/settings.json`.
 2. Before navigation, verify the user-provided document URL uses `https:` and belongs to an approved Feishu/Lark tenant domain such as `*.feishu.cn`, `*.larksuite.com`, `*.larksuite.com.cn`, or a project-configured tenant. Reject `file:`, `data:`, `javascript:`, `http:`, localhost, loopback, link-local, private IP, and raw IP hosts unless the user explicitly approves a controlled local test target.
@@ -294,7 +294,7 @@ Summarize business context only when it changes implementation priority, scope,
 
 When the user explicitly says the target is a frontend project, transform the product document into frontend implementation inputs before RD starts:
 
-> **v2.15.0+ 校准:** UI 视觉 = 开源组件库装配(shadcn / Radix / antd / mui),不是原创设计。prd 不画 ASCII 视觉,只描述"页面模式 + 关键交互 + 信息密度"。AI 据此选组件库 + 装配。详见 `.peaks/memory/peaks-loop-prd-template-design.md`。
+> **v2.15.0+ 校准:** UI 视觉 = 开源组件库装配(shadcn / Radix / antd / mui),不是原创设计。prd 不画 ASCII 视觉,只描述"页面模式 + 关键交互 + 信息密度"。AI 据此选组件库 + 装配。详见 `.peaks/memory/peaks-cli-prd-template-design.md`。
 
 1. identify target pages, routes, components, forms, tables, modals, empty/loading/error states, permissions, data dependencies, edge cases, and affected user flows;
 2. separate frontend-only work from API/backend联调 assumptions;

package/skills/bee/peaks-prd/references/prd-for-multi-pass.md

@@ -46,4 +46,4 @@ Single-service feature → single-pass PRD. Do not force a Pass 2 layer if the w
 - Pass 2 ACs each name a file path under one of the Pass 1 services.
 - A `peaks slice audit-prd --rid <rid>` (when present) returns zero cross-cutting flags.
 
-See `../peaks-slice-decompose/SKILL.md` for the envelope contract and `../peaks-rd/references/reading-v2-slice-results.md` for the RD-side read.
+See `../../../peaks-slice-decompose/SKILL.md` for the envelope contract and `../../peaks-rd/references/reading-v2-slice-results.md` for the RD-side read.

package/skills/bee/peaks-prd/references/workflow.md

@@ -15,7 +15,7 @@ When the product source is an authenticated Feishu/Lark/wiki document:
 7. Do not persist login URLs, redirect URLs, cookies, request or response headers, session tokens, tokens, storage state, QR payloads, raw browser state, raw network logs, browser traces, or screenshots/logs containing PII or SSO/MFA material into artifacts; redact sensitive evidence before writing `.peaks` outputs.
 8. If access remains blocked, record only a redacted document identifier, a sanitized state category such as `login-required`, `mfa-required`, or `access-denied`, and the exact user action needed.
 
-Canonical browser workflow: `../../peaks-code/references/browser-workflow.md`.
+Canonical browser workflow: `../../../peaks-code/references/browser-workflow.md`.
 
 ## Implementation-oriented analysis
 

package/skills/bee/peaks-qa/SKILL.md

@@ -47,7 +47,7 @@ denied again after a long pause. That is the gate resetting, not you regressing.
 
 > **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-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.
+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 *`. Normative by documentation only — the guard that once asserted (a) zero bare `<sid>`, (b) an axis label on every runtime path, and (c) this callout's presence was deleted in `457b9a87`. Comply by convention.
 
 ## peaks-context auto-build (v3.0)
 
@@ -92,7 +92,7 @@ The canonical scope dir for this request is provided as `envelope.data.scopeDir`
 
 When this skill is launched as a sub-agent via `peaks sub-agent dispatch <role>` (then the LLM executes the returned toolCall) from `peaks-code`, the following sections of THIS skill are **suspended** for the sub-agent run: Session id, Skill presence, Workspace initialization, Mode selection, Statusline install. The sub-agent must NOT call `peaks request init` (Code already initialised the slot), and must write `.peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md` with test cases that link to PRD acceptance items. Return only a compact JSON envelope.
 
-> **v2.15.0+ 校准:** 每个 slice 完成,user 必介入做**业务审阅**(4-5 项业务/产品清单:业务流程 / 需求覆盖 / 边界 case / UI 装配 / 能合入下版吗),**不是技术审阅**。业务审过 → 进 final;业务不通过 → 返工。详见 `.peaks/memory/peaks-loop-slice-review-and-qa-perspective.md`。
+> **v2.15.0+ 校准:** 每个 slice 完成,user 必介入做**业务审阅**(4-5 项业务/产品清单:业务流程 / 需求覆盖 / 边界 case / UI 装配 / 能合入下版吗),**不是技术审阅**。业务审过 → 进 final;业务不通过 → 返工。详见 `.peaks/memory/peaks-cli-slice-review-and-qa-perspective.md`。
 
 → see `references/qa-sub-agent-dispatch.md` for the full contract + hard prohibitions.
 
@@ -106,7 +106,7 @@ Project-level security + perf plans live at `.peaks/_runtime/<sessionId>/qa/secu
 
 When peaks-qa is the **main loop** (i.e. it is the active skill and is about to run its own sub-agent dispatch, rather than being a sub-agent itself), it fans out only the **business verification** sub-agent: `qa-business`. Security and performance review are **NOT** peaks-qa's responsibility in v2.11.0 — they are owned by peaks-rd's 4-way audit fan-out (code-review + security-review + perf-baseline + karpathy-review) and the rd-side evidence files (`audit/security-<rid>.md`, `audit/perf-<rid>.md`). peaks-qa reads those files by reference; it does NOT re-do them.
 
-> **v2.15.0+ 校准:** `qa-business` 只跑业务/产品视角的 6 项验收清单(业务流程 / 需求覆盖 / 边界 case / UI 装配 / 异常态语调 / 能上线吗),**不跑技术指标**(覆盖率 / 性能 / 安全)。技术指标由 RD 4-way fan-out 自决,QA 只读 `audit/security-<rid>.md` + `audit/perf-<rid>.md`。详见 `.peaks/memory/peaks-loop-slice-review-and-qa-perspective.md`。
+> **v2.15.0+ 校准:** `qa-business` 只跑业务/产品视角的 6 项验收清单(业务流程 / 需求覆盖 / 边界 case / UI 装配 / 异常态语调 / 能上线吗),**不跑技术指标**(覆盖率 / 性能 / 安全)。技术指标由 RD 4-way fan-out 自决,QA 只读 `audit/security-<rid>.md` + `audit/perf-<rid>.md`。详见 `.peaks/memory/peaks-cli-slice-review-and-qa-perspective.md`。
 
 If the PRD or project warrants it, subdivide `qa-business` further into roles like `qa-business-api` / `qa-business-frontend` / `qa-business-regression`. Subdivision must stay ≤ 2 levels deep (RL-4).
 
@@ -182,7 +182,7 @@ QA must generate test cases, not merely inspect existing ones. Every QA invocati
 
 **Pre-drafted test cases (slice 004 optimization):** when peaks-rd's 4-way parallel fan-out ran a `qa-test-cases-writer` sub-agent, the test plan is pre-drafted at `.peaks/_runtime/<sessionId>/qa/test-cases/<rid>.md` and shipped through the rd:qa-handoff gate. QA main loop is aware of this and treats the pre-drafted file as the canonical starting point. **Missing** the pre-drafted file (sub-agent failed, or the slice was a config/docs/chore that did not fan out) → QA drafts it inline as before, falling back to the standard generation flow.
 
-> **v2.15.0+ 校准:** 业务验证层(user 必审) = 4-5 项业务/产品清单。技术验证层(AI 自决) = 覆盖率 / P99 / 安全扫描 / 自动化。两层解耦:技术不过 → AI 内部重跑;业务不过 → user 反馈修。user **不看**技术指标。详见 `.peaks/memory/peaks-loop-slice-review-and-qa-perspective.md` G5。
+> **v2.15.0+ 校准:** 业务验证层(user 必审) = 4-5 项业务/产品清单。技术验证层(AI 自决) = 覆盖率 / P99 / 安全扫描 / 自动化。两层解耦:技术不过 → AI 内部重跑;业务不过 → user 反馈修。user **不看**技术指标。详见 `.peaks/memory/peaks-cli-slice-review-and-qa-perspective.md` G5。
 
 → see `references/test-case-generation.md` for the full format + acceptance-linkage contract.
 
@@ -198,7 +198,7 @@ QA cannot pass a change until the report contains evidence for every applicable
 
 If Playwright MCP is unavailable, the LLM checks its own tool list for the Playwright MCP server entry; if absent, the LLM tells the user the install command (`claude mcp add playwright -- npx @playwright/mcp@latest` for Claude Code) and marks the gate blocked with the missing capability. Screenshots, logs, manual steps, or other tools must not substitute for the mandatory frontend browser gate. Do not silently downgrade frontend validation to API-only testing.
 
-> **v2.15.0+ 校准:** 存量项目无 UT 兜底,QA 验证必须有"轻量回归"(G14):5-10 分钟跑 10 条关键路径(关键路径来源:prd 业务场景块 / 老板强调的流程 / 历史事故 / G13 影响面扫描),**不跑完整 E2E 1-2 小时**。上线后必须走"观察期"(G15):灰度 → 监控 → 反馈聚合 → 紧急修复 → 修复回灌关键路径(防下次再犯)。详见 `.peaks/memory/peaks-loop-fast-iteration-quality-loop.md`。
+> **v2.15.0+ 校准:** 存量项目无 UT 兜底,QA 验证必须有"轻量回归"(G14):5-10 分钟跑 10 条关键路径(关键路径来源:prd 业务场景块 / 老板强调的流程 / 历史事故 / G13 影响面扫描),**不跑完整 E2E 1-2 小时**。上线后必须走"观察期"(G15):灰度 → 监控 → 反馈聚合 → 紧急修复 → 修复回灌关键路径(防下次再犯)。详见 `.peaks/memory/peaks-cli-fast-iteration-quality-loop.md`。
 
 ## Local intermediate artifacts
 
@@ -297,4 +297,4 @@ QA contracts to assert on the L2 surface (a minimal acceptance test set):
 
 ## Sub-role detached mode (Phase C, slice 2026-08-10)
 
-QA sub-roles (`qa-business`, `qa-perf`, `qa-security`, `qa-business-api`, `qa-business-frontend`, `qa-business-regression`) accept `--mode detached --vendor <vendor>` for parallel test-case execution. Detached mode spawns a real OS process via `peaks sub-agent dispatch --mode detached`, isolated from the orchestrator session. Use detached mode when the test-case writer's expected runtime exceeds 60s OR it processes ≥ 20 source files. The default remains `in-process` (backward compat; existing 106+ dispatch tests untouched). When `--mode detached` is used, the child QA agent receives the `<peaks-auto-compact>` marker (corrected 2026-09-13, rid `2026-09-13-defects-e`): it asks the child to persist durable state to `.peaks/_runtime/<sid>/detached/<rid>/compact/<n>.json` before its own harness compacts the session — the child cannot compact itself, and nothing is spliced back into its prompt. See `peaks-code/references/sub-agent-dispatch.md` §"Detached Mode" for the full contract.
+QA sub-roles (`qa-business`, `qa-perf`, `qa-security`, `qa-business-api`, `qa-business-frontend`, `qa-business-regression`) accept `--mode detached --vendor <vendor>` for parallel test-case execution. Detached mode spawns a real OS process via `peaks sub-agent dispatch --mode detached`, isolated from the orchestrator session. Use detached mode when the test-case writer's expected runtime exceeds 60s OR it processes ≥ 20 source files. The default remains `in-process` (backward compat; existing 106+ dispatch tests untouched). When `--mode detached` is used, the child QA agent receives the `<peaks-auto-compact>` marker (corrected 2026-09-13, rid `2026-09-13-defects-e`): it asks the child to persist durable state to `.peaks/_runtime/<sid>/detached/<rid>/compact/<n>.json` before its own harness compacts the session — the child cannot compact itself, and nothing is spliced back into its prompt. See `skills/peaks-code/references/sub-agent-dispatch.md` §"Detached Mode" for the full contract.

package/skills/bee/peaks-qa/references/external-capability-guidance.md

@@ -5,5 +5,5 @@
 - Playwright MCP is the required path for controlled headed browser and E2E validation (it launches a headed browser on demand). The LLM runtime exposes the Playwright tools under its own server-and-tool namespace (the Playwright MCP); QA invokes them by name from the LLM's tool list. (peaks-loop no longer auto-installs MCPs as of slice #016; the user runs `claude mcp add playwright -- npx @playwright/mcp@latest` themselves when the tool list is empty.)
 - Chrome DevTools MCP is an optional secondary surface for CDP inspection (console, network, performance) of an already-running Chrome started with `--remote-debugging-port=9222`; it does NOT launch a browser on its own. The LLM invokes Chrome DevTools MCP tools directly when present in the tool list.
 - Agent Browser can support browser walkthroughs, but never submit forms, purchase, delete, or mutate authenticated state without explicit confirmation.
-- Canonical browser workflow (URL allow-list, login handoff, sanitization rules, tool mapping): `peaks-code/references/browser-workflow.md`.
+- Canonical browser workflow (URL allow-list, login handoff, sanitization rules, tool mapping): `skills/peaks-code/references/browser-workflow.md`.
 - If Playwright MCP is not installed and the user does not authorize installation, mark frontend browser validation blocked; screenshots, logs, manual steps, or other tools must not substitute for the mandatory headed browser gate.

package/skills/bee/peaks-qa/references/qa-fanout-contract.md

@@ -155,4 +155,4 @@ envelope and into the slice's `reducerReport`.
 
 > Body of `## 业务测试细分 (optional)`. If the PRD or project warrants it, subdivide `qa-business` further into roles like `qa-business-api` / `qa-business-frontend` / `qa-business-regression`; each gets its own `peaks sub-agent dispatch` call. Names are convention not contract — the dispatcher accepts any non-empty string. **Subdivision must stay ≤ 2 levels deep** (RL-4): `qa-business-api` is fine, `qa-business-api-user` is not. Two levels of depth is the empirical sweet spot — past that, the reducer cannot audit the boundaries between sub-agents, and prompts start overlapping.
 
-For the full contract (heartbeat instructions for each sub-agent, batch-id discipline, 30s cadence, 100-truncation, 5min stale) see `skills/peaks-qa/references/qa-fanout-contract.md` and `skills/peaks-code/references/sub-agent-dispatch.md` §G6.
+For the full contract (heartbeat instructions for each sub-agent, batch-id discipline, 30s cadence, 100-truncation, 5min stale) see `skills/bee/peaks-qa/references/qa-fanout-contract.md` and `skills/peaks-code/references/sub-agent-dispatch.md` §G6.

package/skills/bee/peaks-qa/references/qa-skill-presence.md

@@ -18,5 +18,5 @@ Read persistent project memory via CLI (durable, LLM-authored memories):
 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.)
+This returns durable memories from `.peaks/memory` — decisions, conventions, modules, and rules captured in past sessions. Filter with `--kind <project|decision|convention|rule|reference|feedback|module|lesson|bug|investigation|technical-pattern|project-rule|design|handoff|session-handoff|project-todo|publish-closure|project-closure|slice-closure|slice-pilot-findings|sediment>`. (`.peaks/PROJECT.md` is a human-readable session timeline only.)
 Then display: `Peaks-Loop Skill: peaks-qa | Peaks-Loop Gate: startup | Next: <one short action>`. Update with `peaks skill presence:set peaks-qa --project <repo> --mode <mode> --gate <gate>` when gates change. When the role's work ends, run `peaks skill presence:clear --project <repo>`.

package/skills/bee/peaks-qa/references/reading-handoff-frontmatter.md

@@ -4,7 +4,7 @@ QA reads the RD handoff's YAML frontmatter **before** reading the body prose. Th
 
 ## Required frontmatter fields (mirror RD writer)
 
-`requestId`, `scope`, `files`, `decisions[]`, `risks[]`, `nextActions[]`, `gateEvidence`, `schemaVersion: '1.0'`. Field schema: `../peaks-rd/references/writing-handoff-frontmatter.md`.
+`requestId`, `scope`, `files`, `decisions[]`, `risks[]`, `nextActions[]`, `gateEvidence`, `schemaVersion: '1.0'`. Field schema: `../../peaks-rd/references/writing-handoff-frontmatter.md`.
 
 ## Mechanical cross-checks (run before body read)
 
@@ -27,4 +27,4 @@ After the frontmatter passes, read the body prose to derive the test plan:
 
 - All 5 mechanical cross-checks above pass (or are explicitly waived via `--allow-incomplete --confirm`).
 - Test plan covers every new code path mentioned in body prose.
-- Frontmatter YAML parses cleanly (vitest guard: `tests/unit/artifacts/handoff-frontmatter-shape.test.ts`).
+- Frontmatter YAML parses cleanly. No vitest guard covers this; see `../../peaks-rd/references/writing-handoff-frontmatter.md` §Validation for the consumers that read the file.

package/skills/bee/peaks-rd/SKILL.md

@@ -65,7 +65,7 @@ Every RD action MUST align with the 4 Karpathy guidelines (full text at `andrej-
 3. **Surgical Changes** — touch only what the user's request requires. Remove imports / variables / functions that *your* changes made unused. Do not refactor adjacent code. Every changed line must trace to the user's request.
 4. **Goal-Driven Execution** — define verifiable success criteria (`peaks request show --role rd` carries ACs from PRD). For multi-step work, state plan + verify checkpoints before acting.
 
-Cross-references: Slice 1 PRD §AC-1 / `tests/unit/skills/karpathy-prompt-injection.test.ts` (4-point assertion guard). The canonical skill id is `andrej-karpathy-skills:karpathy-guidelines`.
+Cross-references: Slice 1 PRD §AC-1. The 4-point assertion guard that PRD named was deleted in `f17aa377`; the block below is held by documentation only. The canonical skill id is `andrej-karpathy-skills:karpathy-guidelines`.
 
 ## Scope directory (slice 10 — read scopeDir from envelope)
 
@@ -189,7 +189,7 @@ Full dispatch contract (when-to-fan-out rules, dispatch template, prereq gates)
 
 ## Reviewer fan-out detached mode (Phase C, slice 2026-08-10)
 
-Reviewer fan-out may run in detached mode for any of the 3-way fan-out roles (`code-reviewer`, `qa-test-cases-writer`, `karpathy-reviewer`). Detached mode spawns a real OS process via `peaks sub-agent dispatch --mode detached --vendor <vendor>`, isolated from the orchestrator session. Use detached mode when the reviewer's expected runtime exceeds 60s OR processes ≥ 20 source files. Pass `--mode detached` explicitly per reviewer role; the default remains `in-process` (backward compat). The karpathy-reviewer's `<peaks-auto-compact>` marker is honored automatically when `--mode detached` is used. Note what that marker does and does not do (corrected 2026-09-13, rid `2026-09-13-defects-e`): it asks the child to persist durable state to `.peaks/_runtime/<sid>/detached/<rid>/compact/<n>.json` before its own harness compacts the session — the child cannot compact itself, and nothing is spliced back into its prompt. See `peaks-code/references/sub-agent-dispatch.md` §"Detached Mode" for the full contract.
+Reviewer fan-out may run in detached mode for any of the 3-way fan-out roles (`code-reviewer`, `qa-test-cases-writer`, `karpathy-reviewer`). Detached mode spawns a real OS process via `peaks sub-agent dispatch --mode detached --vendor <vendor>`, isolated from the orchestrator session. Use detached mode when the reviewer's expected runtime exceeds 60s OR processes ≥ 20 source files. Pass `--mode detached` explicitly per reviewer role; the default remains `in-process` (backward compat). The karpathy-reviewer's `<peaks-auto-compact>` marker is honored automatically when `--mode detached` is used. Note what that marker does and does not do (corrected 2026-09-13, rid `2026-09-13-defects-e`): it asks the child to persist durable state to `.peaks/_runtime/<sid>/detached/<rid>/compact/<n>.json` before its own harness compacts the session — the child cannot compact itself, and nothing is spliced back into its prompt. See `../../peaks-code/references/sub-agent-dispatch.md` §"Detached Mode" for the full contract.
 
 ## Refactor hard gates
 

package/skills/bee/peaks-rd/references/code-reviewer-4dim-hint.md

@@ -3,7 +3,7 @@
 > Hint block appended to the code-reviewer sub-agent prompt at dispatch
 > time. The RD main loop injects the verbatim block below after the
 > Karpathy-guidelines context block (see
-> `references/rd-sub-agent-dispatch.md` §"Karpathy-guidelines context").
+> `rd-sub-agent-dispatch.md` §"Karpathy-guidelines context").
 > The block is the canonical promotion surface for the convention at
 > `.peaks/standards/typescript/testing.md`.
 

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

@@ -6,4 +6,4 @@
 
 **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-Loop 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: `openspec-cli.md`.

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

@@ -2,7 +2,7 @@
 
 > Body of `## Mandatory perf-baseline output` + numbered perf-baseline steps. **BLOCKING — Do not hand off to QA without a perf-baseline file when the slice has a user-visible performance surface.** The QA stage's Gate A4 (performance check) needs a stable reference to diff against; without an RD-side baseline, the first time Gate A4 runs it has nothing to compare against and any regression it finds is a blind-side surprise. The user-facing pain of leaving perf to QA only has historically been a 3-cycle repair loop. The RD-side baseline closes that loop.
 
-> **Slice 025 — stable across slices within a session; refreshed on trigger.** The perf baseline is a **project-level** artifact (`.peaks/_runtime/<sessionId>/qa/perf-baseline.md`) and is **stable across slices within a session**. It is regenerated only when the slice diff matches the refresh trigger table (see `peaks-qa/references/qa-perf-test-plan.md`). Slices that do not trigger a refresh reference the existing baseline by hash from the per-slice `qa/performance-findings-<rid>.md` (not by regenerating the baseline). The CLI is `peaks workflow plan read|refresh|detect-trigger perf --project <repo>`; the RD-side `peaks perf baseline --apply` workflow below still scaffolds the initial file but the canonical refresh path post-slice-025 is the new `peaks workflow plan refresh` primitive.
+> **Slice 025 — stable across slices within a session; refreshed on trigger.** The perf baseline is a **project-level** artifact (`.peaks/_runtime/<sessionId>/qa/perf-baseline.md`) and is **stable across slices within a session**. It is regenerated only when the slice diff matches the refresh trigger table (see `skills/bee/peaks-qa/references/qa-perf-test-plan.md`). Slices that do not trigger a refresh reference the existing baseline by hash from the per-slice `qa/performance-findings-<rid>.md` (not by regenerating the baseline). The CLI is `peaks workflow plan read|refresh|detect-trigger perf --project <repo>`; the RD-side `peaks perf baseline --apply` workflow below still scaffolds the initial file but the canonical refresh path post-slice-025 is the new `peaks workflow plan refresh` primitive.
 
 **When this applies:**
 - feature / refactor slices that touch a route, hook, API, or any user-perceivable surface

package/skills/bee/peaks-rd/references/ocr-multilang-1.8.md

@@ -12,8 +12,8 @@ status: shipped-4.0.16
 `@alibaba-group/open-code-review@1.8.9` replaces the 2.0.3-era
 GitHub Releases HTTPS download with per-platform `optionalDependencies`
 (`@alibaba-group/ocr-{darwin,linux,win32}-{arm64,x64}`). `npm install`
-hits the registry only; postinstall runs the embedded Node installer
-(`scripts/install.js`) and resolves the platform binary locally.
+hits the registry only; postinstall runs the Node installer the package
+itself ships and resolves the platform binary locally.
 
 Sandbox evidence (2026-08-06, `npm@10.9.4`):
 

package/skills/bee/peaks-rd/references/parallel-review-fanout.md

@@ -9,7 +9,7 @@
 
 The rid is part of the filename (slice `2026-09-14-audit-artifact-rid-scoping`): every slice in a session shares `.peaks/_runtime/<sessionId>/audit/`, so a ridless name means the second slice's audit silently replaces the first slice's. The ridless locations are still read as fallbacks.
 
-Both audit skills consume the immutable peaks-prd handoff (`prd/handoff.md`) and the project-scoped audit templates under `.peaks/project-scan/{security-template, perf-template, audit-output-schema}.md`. The handoff presence is enforced by the `AUDIT_REQUIRES_HANDOFF` prereq. The 1-minor-release back-compat window (`v2.12.0`) keeps the old `rd/{security-review,perf-baseline}.md` paths readable via `mustContainAny` — see `tests/unit/rd/deprecated-reviewer-back-compat.test.ts` (8 cases) and `tests/unit/artifact-prerequisites-typed.test.ts`.
+Both audit skills consume the immutable peaks-prd handoff (`prd/handoff.md`) and the project-scoped audit templates under `.peaks/project-scan/{security-template, perf-template, audit-output-schema}.md`. The handoff presence is enforced by the `AUDIT_REQUIRES_HANDOFF` prereq. The 1-minor-release back-compat window (`v2.12.0`) keeps the old `rd/{security-review,perf-baseline}.md` paths readable via `mustContainAny` — see `RD_DEPRECATED_REVIEWERS` in `src/services/rd/reviewer-dispatch-policy.ts`. The unit tests that once pinned this were deleted in `f17aa377` and have not been replaced.
 
 The current fan-out is therefore **3 sub-agents**:
 
@@ -67,7 +67,7 @@ Note: sub-agent 1 (code-reviewer) and sub-agent 3 (karpathy-reviewer) write to `
 - Read `.peaks/_runtime/<sessionId>/prd/handoff.md` (v2.11.0: architecture summary — the immutable peaks-prd handoff replaces `rd/tech-doc.md`).
 - Output: `.peaks/_runtime/<sessionId>/rd/karpathy-review-<rid>.md` containing a `## Karpathy-Gate` header and the 4 guideline section markers (Think Before Coding / Simplicity First / Surgical Changes / Goal-Driven Execution). (Rid in the filename, same reason as the code review; the ridless `rd/karpathy-review.md` is still read as a fallback.)
 - Required for the `KARPATHY_REVIEW` prereq. The transition CLI gate reads those markers and refuses `rd:qa-handoff` when the file is missing or the markers are absent.
-- See `references/rd-fanout-contracts.md` §"karpathy-reviewer contract" for the JSON envelope shape + file format.
+- See `rd-fanout-contracts.md` §"karpathy-reviewer contract" for the JSON envelope shape + file format.
 
 **Hard prohibitions on all 3 sub-agents:**
 - Do NOT call `Skill(skill="...")` — would re-enter RD or another skill and break the fan-out.

package/skills/bee/peaks-rd/references/rd-fanout-contracts.md

@@ -21,12 +21,13 @@ end of implementation, RD fires 3 sub-agents in parallel via
 > The handoff presence is enforced by the `AUDIT_REQUIRES_HANDOFF` prereq.
 > The 1-minor-release back-compat window (`v2.12.0`) keeps the old
 > `rd/{security-review,perf-baseline}.md` paths readable via `mustContainAny` —
-> see `tests/unit/rd/deprecated-reviewer-back-compat.test.ts` (8 cases) and
-> `tests/unit/artifact-prerequisites-typed.test.ts`.
+> see `RD_DEPRECATED_REVIEWERS` in
+> `src/services/rd/reviewer-dispatch-policy.ts`. The two unit tests that
+> once pinned this were deleted in `f17aa377` and have not been replaced.
 
 ## The 3 sub-agents
 
-> **Karpathy pointer (Slice 1/6):** Each of the 3 sub-agents below operates under the 4 Karpathy guidelines. The canonical reference is `andrej-karpathy-skills:karpathy-guidelines` (full text) and `peaks-rd/SKILL.md` §"Karpathy enforcement". The dispatch primitive also injects the verbatim context block from `rd-sub-agent-dispatch.md` §"Karpathy-guidelines context" into every sub-agent prompt. Sub-agents MUST NOT silently drop the block.
+> **Karpathy pointer (Slice 1/6):** Each of the 3 sub-agents below operates under the 4 Karpathy guidelines. The canonical reference is `andrej-karpathy-skills:karpathy-guidelines` (full text) and `../SKILL.md` §"Karpathy enforcement". The dispatch primitive also injects the verbatim context block from `rd-sub-agent-dispatch.md` §"Karpathy-guidelines context" into every sub-agent prompt. Sub-agents MUST NOT silently drop the block.
 
 - **Sub-agent 1 — code-reviewer** runs `code-review` against the diff and
   writes `rd/code-review-<rid>.md`. **v2.11.0 Tier 7 (Group D) + 2026-09-09-ecc-dynamic:**
@@ -77,9 +78,9 @@ end of implementation, RD fires 3 sub-agents in parallel via
 >   `.peaks/_runtime/<sessionId>/rd/perf-baseline.md` remains readable
 >   via `mustContainAny` for the v2.12.0 1-minor-release window.
 >
-> See `tests/unit/rd/deprecated-reviewer-back-compat.test.ts` (8 cases)
-> and `RD_DEPRECATED_REVIEWERS` in
-> `src/services/rd/reviewer-dispatch-policy.ts`.
+> See `RD_DEPRECATED_REVIEWERS` in
+> `src/services/rd/reviewer-dispatch-policy.ts`. The unit test that once
+> pinned this was deleted in `f17aa377` and has not been replaced.
 
 ## Hard prohibitions on all 3 sub-agents (single block)
 
@@ -201,8 +202,10 @@ failing the gate.
   `mustContainAny: [...]` on the `AUDIT_SECURITY` / `AUDIT_PERF` prereqs
   during the back-compat window. v2.13.0 hard-deletes the legacy paths.
 
-**Pinning:** `tests/unit/rd/deprecated-reviewer-back-compat.test.ts`
-(8 cases) pins the dispatch routing + the legacy-path acceptance.
+**Pinning:** none. The routing + legacy-path acceptance live in
+`RD_DEPRECATED_REVIEWERS` / `isDeprecatedReviewer` in
+`src/services/rd/reviewer-dispatch-policy.ts`; the unit test that pinned
+them (8 cases) was deleted in `f17aa377` and has not been replaced.
 
 ## Gate C evidence (RD-side, type-specific)
 

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

@@ -155,7 +155,7 @@ peaks codegraph affected --project <repo> <changed-files...> --json
 #         --rid <rid> --project <repo> --json
 #     The sub-agent reads `~/.claude/agents/karpathy-reviewer.md` (user-installed)
 #     which is the project-internal draft at
-#     `skills/peaks-rd/references/karpathy-reviewer-prompt.md` plus a
+#     `skills/bee/peaks-rd/references/karpathy-reviewer-prompt.md` plus a
 #     `rd/karpathy-reviewer-agent-handoff.md` install guide.
 #     Hard gate: missing karpathy-reviewer sub-agent OR missing rd/karpathy-review-<rid>.md
 #     → `peaks request transition --state qa-handoff` returns `code: PREREQUISITES_MISSING`.