peaks-loop 4.1.1 → 4.1.2

package/dist/services/rd/rd-service.d.ts

@@ -17,7 +17,6 @@ export type RdModelRole = 'strongest' | 'execution';
 export type RdSwarmPlanRequest = {
     skill: RdSkill;
     /**
-     * Slice 2026-06-29-change-id-root-removal: change-id is metadata-only.
      * It is no longer used for filesystem routing (the session-axis
      * `getSessionDir` is the canonical authority), but it is retained
      * on the request type for trace correlation and to avoid sweeping
@@ -32,7 +31,6 @@ export type RdSwarmPlanRequest = {
     workspace?: WorkspaceConfig;
     requiresTechApproval?: boolean;
     executionModelId?: string;
-    /** Project root for the missing-standards diagnostic (slice 2026-06-16-peaks-rd-no-gates). */
     projectRoot?: string;
     /** Opt-in strict mode: hard-fail when project-local standards are missing. */
     strictStandards?: boolean;
@@ -64,7 +62,6 @@ export type RdConflictGroup = {
 export type RdPlanResult = {
     available: true;
     /**
-     * Slice 2026-06-29-change-id-root-removal: change-id is metadata-only.
      * It is no longer emitted in the planner envelope at runtime, but
      * retained on the result type for trace correlation and to avoid
      * breaking 30+ tests that assert against it.
@@ -89,7 +86,6 @@ export type RdPlanResult = {
         skipReason?: string;
         /** Gate list (code-review / security / performance) reflecting standards availability. */
         standardsGates?: ReadonlyArray<RdStandardGate>;
-        /** Diagnostic line emitted to stderr when standards are missing (slice 2026-06-16-peaks-rd-no-gates). */
         standardsDiagnostic?: string;
         /** When `--strict-standards` is on AND standards are missing, the stable error code. */
         standardsErrorCode?: typeof import('./standards-diagnostic.js').EPEAKS_NO_STANDARDS;
@@ -118,7 +114,6 @@ export type RdPlanResult = {
         skipReason?: string;
         /** Gate list (code-review / security / performance) reflecting standards availability. */
         standardsGates?: ReadonlyArray<RdStandardGate>;
-        /** Diagnostic line emitted to stderr when standards are missing (slice 2026-06-16-peaks-rd-no-gates). */
         standardsDiagnostic?: string;
         /** When `--strict-standards` is on AND standards are missing, the stable error code. */
         standardsErrorCode?: typeof import('./standards-diagnostic.js').EPEAKS_NO_STANDARDS;

package/dist/services/rd/rd-service.js

@@ -19,7 +19,6 @@ const RD_FIXED_TASK_BOUNDARY = RD_IMPLEMENTATION_BAND_START;
 const RD_QUALITY_GATE_BAND_SIZE = 5;
 const RD_TASK_ID_PAD_WIDTH = 3;
 /**
- * 2.0.1-bug1: the slim 2.0 `~/.peaks/config.json` no longer carries a
  * `providers` block (legacy model config lives in
  * `.peaks/preferences.json` per spec §10.4). `buildPlan` is a pure
  * planner function and historically took its execution model from a
@@ -242,7 +241,6 @@ function getConcreteTargetAreas(request, artifactWorkspacePath, hasApprovedTechA
         !hasPlannerArtifactWorkspace(request, artifactWorkspacePath)) {
         return [];
     }
-    // Slice 2026-06-29-change-id-root-removal: read path now resolves via
     // the session-axis `getSessionDir(root, sessionId)` (the change-id
     // identifier is reused as the session-dir name for tech-artifact
     // reads, matching the test helper `writeApprovedTechArtifacts` and
@@ -268,7 +266,6 @@ function buildStandardsOverlay(request) {
         projectRoot: request.projectRoot,
         strict: request.strictStandards === true
     });
-    // Slice 2026-06-16-peaks-rd-no-gates — Repair cycle 1:
     // thread BOTH diagnostic and errorCode so strict-mode callers still
     // surface `EPEAKS_NO_STANDARDS`. The pre-fix version early-returned
     // on `diagnostic !== null` and dropped `errorCode` (QA#4 AC3 violation).
@@ -279,12 +276,10 @@ function buildStandardsOverlay(request) {
         : withDiagnostic;
 }
 function buildPlan(request, standardsOverlay) {
-    // Slice 2026-06-29-change-id-root-removal: change-id is metadata-only;
     // no structural validation gate fires here.
     const goal = normalizeGoal(request.goal);
     const swarmMode = request.swarmMode ?? true;
     const executionModelId = request.executionModelId?.trim() || resolveExecutionModelId();
-    // Slice 2026-07-09 add-zcode-adapter (A.3): strongest planner/reviewer
     // model is resolved dynamically (config.model → env-var fallback).
     const strongestModelId = getStrongestModelId();
     const { workerTarget, blockedReasons } = resolveWorkerTarget(request.maxWorkers);

package/dist/services/rd/reviewer-dispatch-policy.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-24-efficiency-4p-bundle / G4 (P1.3) — karpathy-skip policy
  * Slice v2.12.0 Group B (Tier 4) — collapse 5-way → 3-way fanout.
  *
  * Background — peaks-rd's "Parallel review fan-out" (SKILL.md §130) is
@@ -34,9 +33,7 @@
  * reason every export below sat at zero importers until slice F2.
  *
  * Pinning is half-done. The two test files this block used to cite —
- * `tests/unit/rd/karpathy-skip-on-config-docs-chore.test.ts` (the 5 → 3
  * element pinning) and
- * `tests/unit/rd/deprecated-reviewer-back-compat.test.ts` (the 8
  * back-compat cases) — were both deleted in `f17aa377`. The **predicate
  * half** was re-pinned by `tests/unit/rd/reviewer-dispatch-policy.test.ts`
  * (`7191140f`, 6 cases: `RD_DEPRECATED_REVIEWERS` + `isDeprecatedReviewer`).
@@ -44,7 +41,6 @@
  * membership, `reviewerListFor`, `karpathySlotIndex`,
  * `shouldDispatchKarpathy` — still has no pin.
  *
- * Slice F2 (rid-f2-ac1-wiring) gave this module its FIRST caller in
  * `src/cli/commands/sub-agent-shared.ts` (`deprecatedReviewerWarnings`),
  * invoked from the dispatch chokepoint in
  * `src/cli/commands/dispatch-commands.ts` and pinned by

package/dist/services/rd/reviewer-dispatch-policy.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-24-efficiency-4p-bundle / G4 (P1.3) — karpathy-skip policy
  * Slice v2.12.0 Group B (Tier 4) — collapse 5-way → 3-way fanout.
  *
  * Background — peaks-rd's "Parallel review fan-out" (SKILL.md §130) is
@@ -34,9 +33,7 @@
  * reason every export below sat at zero importers until slice F2.
  *
  * Pinning is half-done. The two test files this block used to cite —
- * `tests/unit/rd/karpathy-skip-on-config-docs-chore.test.ts` (the 5 → 3
  * element pinning) and
- * `tests/unit/rd/deprecated-reviewer-back-compat.test.ts` (the 8
  * back-compat cases) — were both deleted in `f17aa377`. The **predicate
  * half** was re-pinned by `tests/unit/rd/reviewer-dispatch-policy.test.ts`
  * (`7191140f`, 6 cases: `RD_DEPRECATED_REVIEWERS` + `isDeprecatedReviewer`).
@@ -44,7 +41,6 @@
  * membership, `reviewerListFor`, `karpathySlotIndex`,
  * `shouldDispatchKarpathy` — still has no pin.
  *
- * Slice F2 (rid-f2-ac1-wiring) gave this module its FIRST caller in
  * `src/cli/commands/sub-agent-shared.ts` (`deprecatedReviewerWarnings`),
  * invoked from the dispatch chokepoint in
  * `src/cli/commands/dispatch-commands.ts` and pinned by

package/dist/services/rd/standards-diagnostic.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-peaks-rd-no-gates — missing-project-standards diagnostic
  * + JSON gate list shape for the RD bootstrap path.
  *
  * Background: when `peaks-rd` (or `peaks-qa` / `peaks-code`) starts in a

package/dist/services/rd/tactical-stage.js

@@ -1,7 +1,6 @@
 /**
  * Per spec §4.3 战术审计 (peaks-rd/战术) — orchestrator.
  * Runs AST gate first; only writes TACT.sig if gate passes.
- * Spec anchor: docs/superpowers/specs/2026-06-21-context-audit-redesign-design.md §4.3
  * (R1-W3 consolidation; previously referenced as §4.2 which is `peaks-mut`).
  */
 import { dirname } from 'node:path';

package/dist/services/rd-swarm/rd-swarm-types.d.ts

@@ -2,7 +2,6 @@
  * rd-swarm-types — the pure declaration surface of the RD swarm dry-run
  * planner (`rd-swarm-service.ts`).
  *
- * Slice rid-013 owns the planner behavior; this module owns only the graph
  * shapes (wave names, task records, conflict groups, and the task-graph
  * envelope). `rd-swarm-service.ts` imports and re-exports every name here, so
  * importers keep resolving them from the original path.

package/dist/services/rd-swarm/rd-swarm-types.js

@@ -2,7 +2,6 @@
  * rd-swarm-types — the pure declaration surface of the RD swarm dry-run
  * planner (`rd-swarm-service.ts`).
  *
- * Slice rid-013 owns the planner behavior; this module owns only the graph
  * shapes (wave names, task records, conflict groups, and the task-graph
  * envelope). `rd-swarm-service.ts` imports and re-exports every name here, so
  * importers keep resolving them from the original path.

package/dist/services/recommendations/installed-capability-detector.d.ts

@@ -3,7 +3,6 @@
  * detector for the capability catalog (`peaks capability status` /
  * `peaks capabilities --source ...`).
  *
- * Slice B1 of 2026-09-09-ecc-dynamic-and-cleanup: the previous
  * `getInstalledCapabilityIds()` returned `[]` unconditionally, so the
  * catalog could never report anything as installed. This module answers
  * the question from evidence that already exists on disk — no install

package/dist/services/recommendations/installed-capability-detector.js

@@ -3,7 +3,6 @@
  * detector for the capability catalog (`peaks capability status` /
  * `peaks capabilities --source ...`).
  *
- * Slice B1 of 2026-09-09-ecc-dynamic-and-cleanup: the previous
  * `getInstalledCapabilityIds()` returned `[]` unconditionally, so the
  * catalog could never report anything as installed. This module answers
  * the question from evidence that already exists on disk — no install

package/dist/services/release/version-precheck-service.d.ts

@@ -1,12 +1,10 @@
 /**
- * rid-010 — peaks release precheck (Phase 4 slice 1).
  *
  * Module path: src/services/release/version-precheck-service.ts
  * Mirrors publish.yml gate-cli-version §(A) — verified in code 2026-10-03, not
  * just per the old comment: `runRootVsShared` covers §(A)'s shared-dist check;
  * §(A′) (runtime RUNTIME_VERSION) has no layer here, and the §(B)
  * tarball-content gate (Layer 5 of the 5-layer root cause) stays CI-only —
- * AC-7 grep test pins publish.yml so §(B) cannot drift silently.
  *
  * 4-layer version precheck. Designed to run BEFORE `peaks release canary` so
  * developers catch CLI_VERSION lag / tag collision / changeset staged /

package/dist/services/release/version-precheck-service.js

@@ -1,12 +1,10 @@
 /**
- * rid-010 — peaks release precheck (Phase 4 slice 1).
  *
  * Module path: src/services/release/version-precheck-service.ts
  * Mirrors publish.yml gate-cli-version §(A) — verified in code 2026-10-03, not
  * just per the old comment: `runRootVsShared` covers §(A)'s shared-dist check;
  * §(A′) (runtime RUNTIME_VERSION) has no layer here, and the §(B)
  * tarball-content gate (Layer 5 of the 5-layer root cause) stays CI-only —
- * AC-7 grep test pins publish.yml so §(B) cannot drift silently.
  *
  * 4-layer version precheck. Designed to run BEFORE `peaks release canary` so
  * developers catch CLI_VERSION lag / tag collision / changeset staged /
@@ -54,7 +52,6 @@ export function runRootVsShared(opts) {
     try {
         const raw = readFileSync(sharedDist, 'utf8');
         // Quote-tolerant: the old double-quote-only regex blanked on prettier's
-        // single-quoted emit (rid 2026-10-03-release-gate-quote-brittle).
         const match = raw.match(/CLI_VERSION\s*=\s*(?:"([^"]+)"|'([^']+)'|`([^`]+)`)/);
         const captured = match?.[1] ?? match?.[2] ?? match?.[3];
         if (captured !== undefined) {

package/dist/services/retrospective/retrospective-index.d.ts

@@ -2,7 +2,6 @@
  * retrospective-index — load `.peaks/retrospective/index.json`, parse to
  * `RetrospectiveEntry[]`, return the index envelope.
  *
- * Slice 023 (R3). Pure read on the hot path: a single `fs.readFile` of
  * the index, no MD-tree fallback. The migration script (G9) is the only
  * writer; this loader is read-only.
  */

package/dist/services/retrospective/retrospective-index.js

@@ -2,7 +2,6 @@
  * retrospective-index — load `.peaks/retrospective/index.json`, parse to
  * `RetrospectiveEntry[]`, return the index envelope.
  *
- * Slice 023 (R3). Pure read on the hot path: a single `fs.readFile` of
  * the index, no MD-tree fallback. The migration script (G9) is the only
  * writer; this loader is read-only.
  */

package/dist/services/retrospective/retrospective-show.d.ts

@@ -3,7 +3,6 @@
  * body on-demand from `artifactPaths` (concatenate with `---` separator),
  * apply `formatMdCompact` by default, return the JSON envelope.
  *
- * Slice 023 (R3). The on-disk MD form is gone after the G9 migration; the
  * body is re-hydrated from the source PRD / RD / QA / TXT artifacts. If
  * a referenced artifact is missing on disk, `show` returns a
  * `ARTIFACT_MISSING` envelope (PRD R3) and does not crash.

package/dist/services/retrospective/retrospective-show.js

@@ -3,7 +3,6 @@
  * body on-demand from `artifactPaths` (concatenate with `---` separator),
  * apply `formatMdCompact` by default, return the JSON envelope.
  *
- * Slice 023 (R3). The on-disk MD form is gone after the G9 migration; the
  * body is re-hydrated from the source PRD / RD / QA / TXT artifacts. If
  * a referenced artifact is missing on disk, `show` returns a
  * `ARTIFACT_MISSING` envelope (PRD R3) and does not crash.

package/dist/services/reviewer/model-family.js

@@ -1,6 +1,5 @@
 /**
  * model-family.ts — derive `modelFamily` from a `modelId` for the G4
- * third-party reviewer. AC-4.4 requires that
  * `third-party-review.json.modelFamily !== karpathy-review.json.modelFamily`,
  * so the family bucket must be stable, provider-distinguishing, and
  * version-tolerant (e.g. `claude-opus-4-8` and `claude-haiku-4-5` both

package/dist/services/reviewer/reviewer-config.js

@@ -1,6 +1,5 @@
 /**
  * reviewer-config.ts — load the `reviewer` section from
- * `~/.peaks/config.json`. AC-4.1 mandates:
  *   - providers[] (>=2 entries; ollama / anthropic / openai supported)
  *   - selection: 'round-robin' | 'hash(rid)' | 'random'
  *   - rdProviderName: string | null

package/dist/services/reviewer/reviewer-service.d.ts

@@ -16,7 +16,6 @@ export declare function extractFirstJsonObject(text: string): unknown | null;
 export declare function runReviewer(input: ReviewerRunInput): Promise<ReviewerRunOutput>;
 /**
  * Compute the distinctness verdict: returns true when the third-party
- * reviewer's modelFamily differs from the karpathy reviewer's. AC-4.4
  * mandates this is a CI gate — equality fails the build.
  */
 export declare function distinctFromKarpathy(thirdPartyFamily: string, karpathyFamily: string): boolean;

package/dist/services/reviewer/reviewer-service.js

@@ -1,7 +1,6 @@
 /**
  * reviewer-service.ts — orchestrator for the G4 third-party reviewer.
  *
- * Flow (per AC-4.1 .. AC-4.6):
  *   1. Load `reviewer` section from `~/.peaks/config.json` (reviewer-config).
  *      Missing section => `{ ok: false, reason: 'no-reviewer-config' }`.
  *   2. Pick a provider by selection mode (round-robin / hash / random).
@@ -243,7 +242,6 @@ export async function runReviewer(input) {
         };
     }
     // Stamp modelFamily from the actual modelId we called — prevents the LLM
-    // from lying about its family and bypassing AC-4.4.
     const stamped = {
         ...validated,
         modelId: result.provider.model,
@@ -254,7 +252,6 @@ export async function runReviewer(input) {
 }
 /**
  * Compute the distinctness verdict: returns true when the third-party
- * reviewer's modelFamily differs from the karpathy reviewer's. AC-4.4
  * mandates this is a CI gate — equality fails the build.
  */
 export function distinctFromKarpathy(thirdPartyFamily, karpathyFamily) {

package/dist/services/reviewer/selection-strategies.js

@@ -1,6 +1,5 @@
 /**
  * selection-strategies.ts — pick a provider per rid for the G4 third-party
- * reviewer. AC-4.6 requires:
  *   - `round-robin` cycles across providers across slices
  *   - `hash(rid)` is stable per rid (deterministic replay)
  *   - `random` is uniform over the provider set

package/dist/services/runtime/runtime-detector.js

@@ -1,5 +1,4 @@
 /**
- * Runtime detector — slice S2-a of RD-2.
  *
  * Given the current process environment, decide which vendor (if any)
  * is the active AI runtime. Detection order matters: Claude Code is

package/dist/services/runtime/runtime-service.d.ts

@@ -1,5 +1,4 @@
 /**
- * Runtime service — slice S2-a of RD-2.
  *
  * Orchestrator that wires the runtime detector + vendor adapter
  * registry into a small surface that the CLI commands call. The
@@ -12,7 +11,6 @@
  *  - The service is a thin orchestrator — it does NOT contain any
  *    vendor verb strings (claude / codex / copilot). All vendor verbs
  *    live in `src/services/runtime/vendors/<vendor>.ts`. Verified by
- *    AC-1.
  *  - When `compactVia(id)` is called with an unknown id, the service
  *    returns a "no-op" result with exitCode=0 and a warning instead of
  *    throwing — vendor-neutrality means peaks-loop MUST keep working

package/dist/services/runtime/vendor-adapter.d.ts

@@ -1,5 +1,4 @@
 /**
- * Vendor adapter contract — slice S2-a of RD-2 (2026-07-08 session).
  *
  * Each `VendorAdapter` is a thin wrapper around ONE AI runtime (Claude
  * Code / Codex / Copilot / custom) that knows how to:
@@ -25,11 +24,9 @@
  * orchestrates these adapters (runtime-service.ts) and the CLI commands
  * (`peaks runtime compact --via <id>`) MUST NOT contain vendor verbs.
  *
- * Slice 2026-09-12-auto-compact-vendor-neutrality widened AC-1's scope from
  * `src/services/code/` to ALL of `src/`, and had to change how it is
  * enforced. Both changes came from measurement:
  *
- *   - The old scope excluded the files that carried the defect AC-1
  *     describes — the compact dispatcher (`src/services/context/`) and the
  *     hook installer (`src/services/hooks/`) — so it returned 0 by
  *     construction. A grep over a directory that does not contain the code
@@ -40,15 +37,11 @@
  *     in `src/services/ide/adapters/claude-code-adapter.ts` — the one place
  *     the string is supposed to be. A text grep measures prose, not code.
  *
- * AC-1 is therefore enforced by the AST-based check in
  * `tests/unit/runtime/vendor-neutral-identity-guard.test.ts`: no vendor
  * verb in any STRING LITERAL of `src/` outside the adapter implementations.
  * Parsed, the count is 1 and the single hit is that adapter — which is the
- * property AC-1 was always about.
  *
- * AC-1 covers VERB STRINGS only. The compact path's defects were IDENTITY
  * COMPARISONS (`ideId !== 'claude-code'`), a second shape the same guard
- * file covers and AC-1 never could. Read that guard's header for what
  * neither check catches before treating vendor neutrality as proven.
  *
  * See `.peaks/_runtime/2026-07-08-session-17918f/prd/002-adapter-runtime-and-polyrepo.md`

package/dist/services/runtime/vendors/claude-code.js

@@ -1,5 +1,4 @@
 /**
- * Claude Code vendor adapter — slice S2-a.
  *
  * Stubs the compact verb to `claude --compact` (the canonical vendor
  * verb for Claude Code). The actual binary is invoked via spawn so

package/dist/services/runtime/vendors/codex.js

@@ -1,5 +1,4 @@
 /**
- * Codex vendor adapter — slice S2-a.
  *
  * Stub adapter (PRD out-of-scope: full implementation lands in a
  * future slice). The detect() heuristic is intentionally permissive:

package/dist/services/runtime/vendors/copilot.js

@@ -1,5 +1,4 @@
 /**
- * Copilot vendor adapter — slice S2-a.
  *
  * Stub adapter (PRD out-of-scope: full implementation lands in a
  * future slice). Copilot's compact verb is `copilot compact`

package/dist/services/sc/sc-service.js

@@ -87,7 +87,6 @@ function mapSyncState(syncStatus) {
 }
 function getCurrentArtifactDir(artifactWorkspacePath) {
     const peaksPath = getPeaksPath(artifactWorkspacePath);
-    // Slice 2026-06-29-change-id-root-removal: the `.peaks/_runtime/current-change`
     // binding file is gone. Resolve the active change-id from the workspace
     // session binding instead. When no session is bound, fall back to
     // `unknown-session` (matches the previous behaviour for an unbound workspace).
@@ -102,7 +101,6 @@ function getCurrentArtifactDir(artifactWorkspacePath) {
     };
 }
 function getRetentionChangeDir(artifactWorkspacePath, sliceId) {
-    // Slice 2026-06-29-change-id-root-removal: retention slice dirs
     // remain under the legacy `.peaks/<sliceId>/` shape (they're shipped
     // / frozen artifacts, not session-scoped workspace state). Only the
     // ACTIVE session-dir resolution uses `_runtime/` — retention slices
@@ -163,7 +161,6 @@ function readActiveSkillSessionId(projectRoot) {
  * Read the workspace session binding and return its `sessionId`,
  * or null when the file is missing / malformed.
  *
- * As of slice 2026-06-05-peaks-runtime-layer the canonical home is
  * `<projectRoot>/.peaks/_runtime/session.json`. The legacy
  * `<projectRoot>/.peaks/.session.json` is consulted as a
  * one-minor-release back-compat fallback: if the new path is
@@ -199,7 +196,6 @@ function readSessionJsonBinding(projectRoot) {
  * session does not own the slice.
  */
 function sessionOwnsSlice(projectRoot, sessionId, sliceId) {
-    // As of slice 2026-06-05-change-id-as-unit-of-work, the same
     // session id can live at multiple umbrella locations:
     //   - `.peaks/_runtime/<sessionId>/` (legacy or top-level active)
     //   - `.peaks/retrospective/<sessionId>/` (shipped slice)
@@ -238,7 +234,6 @@ function findSessionOwningSlice(projectRoot, sliceId) {
         return null;
     }
     topLevel.sort();
-    // As of slice 2026-06-05-change-id-as-unit-of-work, shipped slices
     // are archived under `.peaks/retrospective/<dir>/` and dogfood
     // evidence lives under `.peaks/_dogfood/<dir>/`. Both umbrellas host
     // scopes at one level deeper than the top-level `.peaks/_runtime/<dir>/`
@@ -369,7 +364,6 @@ export function getChangeTraceabilityStatus() {
         const artifactPath = resolve(changeDir, ...artifact.path);
         return {
             name: artifact.name,
-            // Slice 2026-06-29-change-id-root-removal: the reported path
             // matches the canonical single-axis layout
             // `.peaks/_runtime/<sid>/...`.
             path: resolve(peaksPath, '_runtime', sessionId ?? '<session-id>', ...artifact.path),

package/dist/services/scan/acceptance-coverage-service.js

@@ -107,10 +107,8 @@ export async function getAcceptanceCoverage(options) {
     if (prdArtifact === null) {
         return { kind: 'prd-not-found' };
     }
-    // As of slice 2026-06-05-change-id-as-unit-of-work, test-cases live
     // under the same change-id dir as the PRD itself (the on-disk scope),
     // not under the body's `- session:` line. Slice
-    // 2026-06-29-change-id-root-removal stripped the legacy
     // `.peaks/_runtime/change/<id>/` indirection — test-cases now live
     // under the canonical session dir `.peaks/_runtime/<sid>/qa/test-cases/`.
     // `prdArtifact.sessionId` is the bare session id (the dir the PRD was

package/dist/services/scan/api-diff-recorded.d.ts

@@ -3,7 +3,6 @@
  * plus the candidate name-grep.
  *
  *   1. `.peaks/_runtime/<sid>/rd/mock-plan.md`  (most recent by mtime)
- *   2. recorded `*-api.types.ts` interfaces     (from (1) + `src/services/types`)
  *   3. the `## API Migration` endpoint list in `.peaks/_runtime/<sid>/txt/*.md`
  *
  * All three are OPTIONAL: absence is reported in the report's `notes`, never

package/dist/services/scan/api-diff-recorded.js

@@ -3,7 +3,6 @@
  * plus the candidate name-grep.
  *
  *   1. `.peaks/_runtime/<sid>/rd/mock-plan.md`  (most recent by mtime)
- *   2. recorded `*-api.types.ts` interfaces     (from (1) + `src/services/types`)
  *   3. the `## API Migration` endpoint list in `.peaks/_runtime/<sid>/txt/*.md`
  *
  * All three are OPTIONAL: absence is reported in the report's `notes`, never

package/dist/services/scan/api-diff-service.d.ts

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — `peaks scan api-diff <doc>` (design
- * `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md` §2.1/§2.3).
  *
  * Read-only. Parses an OpenAPI 3.x document (JSON or YAML — `yaml` is already a
  * runtime dependency) and diffs it against the three sources a consumer project

package/dist/services/scan/api-diff-service.js

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — `peaks scan api-diff <doc>` (design
- * `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md` §2.1/§2.3).
  *
  * Read-only. Parses an OpenAPI 3.x document (JSON or YAML — `yaml` is already a
  * runtime dependency) and diffs it against the three sources a consumer project

package/dist/services/scan/api-diff-types.d.ts

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — shared types for `peaks scan api-diff <doc>`
- * (design `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md`
  * §2.1/§2.3).
  *
  * GOVERNING PRINCIPLE (QA repair): exactness requires BOTH sides to be fully

package/dist/services/scan/api-diff-types.js

@@ -1,6 +1,5 @@
 /**
  * S1 / rid=api-diff-report — shared types for `peaks scan api-diff <doc>`
- * (design `docs/superpowers/specs/2026-09-12-frontend-acl-contract-design.md`
  * §2.1/§2.3).
  *
  * GOVERNING PRINCIPLE (QA repair): exactness requires BOTH sides to be fully

package/dist/services/scan/archetype-service.js

@@ -98,7 +98,6 @@ function decideArchetype(detected) {
     }
     // Monorepo detection runs BEFORE the backend check: a monorepo with
     // a packages/server dir is a fullstack-monorepo, NOT legacy-fullstack.
-    // Slice 2026-07-15 ice-cola hot-fix: previously a monorepo with a
     // backend sub-package fell through to `legacy-fullstack` because
     // `hasBackend` includes `backendDirsPresent.length > 0`, which the
     // L199 guard above couldn't handle. We now treat `hasMonorepoConfig`

package/dist/services/scan/file-size-policy.d.ts

@@ -26,7 +26,6 @@ export declare function inFileSizeScope(file: string): boolean;
  * of a scope extension. Both consumers read this instead of each carrying its own
  * half of the rule.
  *
- * WHY IT MATTERS (F3 of the repair cycle, rid `2026-09-30-cap-unify-01`). The
  * census enumerated its scope with `git ls-files <dirs>` plus the extension test,
  * while the scan measured EVERY changed non-exempt file at `fileSizeCapFor`'s
  * else-branch 300 — including paths in neither list. The two disagreed about the

package/dist/services/scan/file-size-policy.js

@@ -7,7 +7,6 @@
 // `scripts/lint/file-size-census.ts` (the whole-tree count the husky gate
 // ratchets). Neither may restate a number.
 //
-// WHY ONE MODULE (rid 2026-09-30-cap-unify-01). The policy was written twice,
 // in two units: `max-lines: [error, {max: 400, skipBlankLines, skipComments}]`
 // in `config/eslint/.peaks-rules.cjs` and a raw `DEFAULT_FILE_SIZE_THRESHOLD`
 // of 800 here. Two spellings of one decision drift by construction, and the only
@@ -30,7 +29,6 @@
 // A row that silently excluded them would not equal its own measurement — the
 // same class of hole as lint-gate §4b (a surface asserted but never counted).
 //
-// NUMBERS THIS MODULE DOES NOT OWN, DECIDED 2026-09-30 (F6 of the repair cycle).
 // A line-count constant elsewhere in the repo is a second copy of THIS policy only
 // if it decides the same question — "may this file be committed at this size?".
 // Three that do not, recorded here so the next reader does not re-litigate them:
@@ -43,7 +41,6 @@
 //     this cap and is NOT folded into it — folding it in would silently change what
 //     the legacy report says. Its name does not match the census's `CAP_NAME`
 //     second-copy rule on purpose; see lint-gate §4b row 7.
-//   - `src/services/skills/lint-reference-shape.ts` 800: the shape of an
 //     example lint report, not a cap.
 /** Raw-line cap for `src/`, `scripts/` and `packages/` — including a `tests` directory inside a package. */
 export const FILE_SIZE_CAP_DEFAULT = 300;
@@ -84,7 +81,6 @@ export function inFileSizeScope(file) {
  * of a scope extension. Both consumers read this instead of each carrying its own
  * half of the rule.
  *
- * WHY IT MATTERS (F3 of the repair cycle, rid `2026-09-30-cap-unify-01`). The
  * census enumerated its scope with `git ls-files <dirs>` plus the extension test,
  * while the scan measured EVERY changed non-exempt file at `fileSizeCapFor`'s
  * else-branch 300 — including paths in neither list. The two disagreed about the
@@ -128,7 +124,6 @@ export function fileSizeScopeBucket(file) {
 }
 // ---------------------------------------------------------------------------
 // THE SECOND SCOPE — `.husky/`, the directory the ratchet itself lives in
-// (backlog §2.32, rid 2026-10-02-hooks-size-rows)
 // ---------------------------------------------------------------------------
 //
 // WHAT WAS INVISIBLE. `FILE_SIZE_SCOPE_DIRS` names four directories, and `.husky`

package/dist/services/scan/file-size-scan.d.ts

@@ -49,7 +49,6 @@ export type FileSizeScanResult = {
      *  four scope directories, or with an extension it does not count. Reported
      *  rather than silently skipped, for the same reason `exemptFiles` is.
      *
-     *  WHY THEY ARE NOT VIOLATIONS (F3, rid 2026-09-30-cap-unify-01). Every file
      *  the scan checked used to be measured against `fileSizeCapFor`, whose
      *  else-branch is 300 — a number that is only defined for `src`/`packages`/
      *  `scripts`. So an out-of-scope path (a `.md`, a file under `.husky/`) could

package/dist/services/security/safe-settings-path.js

@@ -1,7 +1,6 @@
 /**
  * R-2 path-safety guard for sub-agent state files.
  *
- * Slice 2026-06-07-sub-agent-dispatch-decouple (G4) — reuses the same
  * R-2 symlink/junction guard as `assertSafeSettingsFile` for
  * `.peaks/_sub_agents/<sid>/dispatch-<rid>-<ts>.json` paths.
  *

package/dist/services/session/binding-store.d.ts

@@ -6,7 +6,6 @@
  *
  * v2.16.0 schema is a multi-instance registry with conflict-detection
  * sentinel fields (ownerHint, pid, lastHeartbeat, instances Map).
- * See PRD `001-2026-06-29-v2-16-0-change-id-axis-removal` AC-8.
  *
  * The store keeps a one-shot migration from the legacy schema:
  * legacy single-session binding → v2.16.0 instances Map with one entry,
@@ -80,13 +79,11 @@ export declare function registerInstance(projectRoot: string, opts: {
 };
 /**
  * Touch the `lastHeartbeat` for a specific instance. Used by the
- * Doctor periodic loop (AC-10) and by the Skill presence `startup`
  * gate.
  */
 export declare function heartbeat(projectRoot: string, sid: string): Binding | null;
 /**
  * Drop an instance entry from the binding. Used when the last peaks-*
- * skill on a Claude instance exits (AC-7: all skills inactive →
  * no record). Returns the updated binding (or null if no instances
  * remain and the caller wants to delete the binding entirely).
  */
@@ -94,7 +91,6 @@ export declare function dropInstance(projectRoot: string, sid: string): Binding
 /**
  * Drop stale instances (lastHeartbeat older than `ttlMs`). Returns
  * the list of dropped sid values so the caller can log them. Used
- * by AC-10 Doctor.
  */
 export declare function dropStale(projectRoot: string, ttlMs: number): {
     binding: Binding | null;