peaks-loop 4.1.1 → 4.1.2

package/dist/services/prd/gate-evidence-derivation.js

@@ -1,10 +1,8 @@
 /**
  * Where `gateEvidence` comes FROM, and where its promise is checked.
  *
- * B2 (merged with the B1 repair), rid `rid-b2-gate-evidence-wiring`.
  *
  * B1 made the field real at the SERVICE layer and QA found the hole that
- * mattered (F1 of `rid-b1-qa`): all three frontmatter producers passed
  * nothing, so no capsule on disk ever carried the field — the dead surface
  * had moved one layer out, from "no producer function" to "no production
  * caller". This module closes that by DERIVING the map instead of accepting
@@ -56,7 +54,6 @@
  * For `docs`/`chore` nothing ever reads it, so it is not declared: keeping an
  * inert statement in every docs capsule would recreate, in miniature, the exact
  * defect this whole line of work exists to remove — a claim no one reads, which
- * is how the field was dead in the first place (F1 of `rid-b2-qa`). Scope, in
  * one sentence: **this map declares the evidence paths Gate C will check for
  * this slice**, so an empty declaration is the honest one when there is no such
  * gate.
@@ -147,7 +144,6 @@ export function deriveGateEvidence(opts) {
  * so a caller can tell "this slice has nothing to declare" apart from "the
  * artifact could not be read".
  *
- * F4 (`rid-f4-ceiling-breach`). This used to be `catch { return undefined }`,
  * which folded those two into one value — and the repository's own ratchet
  * caught it (`capability-guard-runner/contracts/J03.ts`, rule
  * `catch-return-null`; the ceiling was written for exactly this shape). Nothing
@@ -163,7 +159,6 @@ export function deriveGateEvidence(opts) {
  * worse than a loud, already-duplicated one.
  */
 export async function deriveGateEvidenceForRequest(opts) {
-    // F4 (`rid-f4-ceiling-breach`). The throw from `showRequestArtifact` is
     // propagated, so a caller can tell "this slice has nothing to declare"
     // (artifact missing → `artifact === null` → `requestType === null` →
     // `undefined`) apart from "the artifact could not be read" (an id the

package/dist/services/prd/handoff-auto-regen.js

@@ -1,5 +1,4 @@
 /**
- * v2.13.2 AC-4 — prd/handoff-<rid>.md auto-regen on prd:handed-off.
  *
  * When `peaks request transition --role prd --state handed-off` succeeds
  * and this slice's capsule is missing, this helper writes a sha256-locked
@@ -8,8 +7,6 @@
  * the existing handoff is canonical (it may carry a richer body that
  * peaks-prd produced in an earlier session).
  *
- * Slice `2026-09-14-prd-capsule-rid-scoping`: the path carries the rid, so
- * "already exists" is now asked per SLICE. The pre-rid-scoping bare name is
  * deliberately NOT consulted — writing there would recreate the
  * one-slot-per-session collision for the next slice in the session.
  *
@@ -47,12 +44,10 @@ export async function autoRegenPrdHandoff(opts) {
     }
     const body = artifact.content;
     const sha256 = sha256OfBody(body);
-    // v2.13.3 AC-4 — align with `AUDIT_REQUIRES_HANDOFF` prereq which
     // pins `mustContain: ['schemaVersion: 2', 'sha256:']`. Primary field is
     // `sha256`; `handoffHash` is kept as a literal alias for the readers that
     // still use the old key.
     //
-    // Slice `2026-09-14-handoff-writer-gate-divergence`: this block used to be
     // hand-rolled here while `handoff-service.serializeHandoff` rendered the
     // SAME contract a second, incompatible way. Both now go through
     // `serializeHandoffFrontmatter`, so the two producers cannot drift again.

package/dist/services/prd/handoff-frontmatter-shape.d.ts

@@ -14,7 +14,6 @@ export declare function serializeHandoff(handoff: Handoff): string;
  * readable handoff was satisfied by a handoff the parser would not read, and
  * `peaks prd handoff verify` exited 1 on a healthy file.
  *
- * Slice `2026-09-14-handoff-writer-gate-divergence` then fixed the other half:
  * the writer no longer emits the quoted form at all (see
  * `handoff-frontmatter.ts`). This tolerance stays because handoffs already on
  * disk were written by the old writer and by hand; the writer fix must not
@@ -26,7 +25,6 @@ export declare function isSchemaVersion2(value: unknown): boolean;
  * strings — an ARRAY here is the pre-B1 shape its own test file used to
  * write, and it is a broken declaration, not a claim.
  *
- * F2 of `rid-b1-qa` removed this function's own copy of the shape rule. It
  * used to be a second predicate (same boundary, different downstream result)
  * that let the same bytes read one way here and another way through
  * `readHandoffGateEvidence`; both now ask `classifyGateEvidence`. Only

package/dist/services/prd/handoff-frontmatter-shape.js

@@ -34,7 +34,6 @@ export function serializeHandoff(handoff) {
  * readable handoff was satisfied by a handoff the parser would not read, and
  * `peaks prd handoff verify` exited 1 on a healthy file.
  *
- * Slice `2026-09-14-handoff-writer-gate-divergence` then fixed the other half:
  * the writer no longer emits the quoted form at all (see
  * `handoff-frontmatter.ts`). This tolerance stays because handoffs already on
  * disk were written by the old writer and by hand; the writer fix must not
@@ -48,7 +47,6 @@ export function isSchemaVersion2(value) {
  * strings — an ARRAY here is the pre-B1 shape its own test file used to
  * write, and it is a broken declaration, not a claim.
  *
- * F2 of `rid-b1-qa` removed this function's own copy of the shape rule. It
  * used to be a second predicate (same boundary, different downstream result)
  * that let the same bytes read one way here and another way through
  * `readHandoffGateEvidence`; both now ask `classifyGateEvidence`. Only

package/dist/services/prd/handoff-frontmatter.d.ts

@@ -1,7 +1,6 @@
 /**
  * The ONE canonical serialization of `prd/handoff.md` frontmatter.
  *
- * Why this module exists (slice `2026-09-14-handoff-writer-gate-divergence`):
  * the handoff capsule is written by two producers and read by four
  * consumers, and they did not agree on the bytes:
  *

package/dist/services/prd/handoff-frontmatter.js

@@ -1,7 +1,6 @@
 /**
  * The ONE canonical serialization of `prd/handoff.md` frontmatter.
  *
- * Why this module exists (slice `2026-09-14-handoff-writer-gate-divergence`):
  * the handoff capsule is written by two producers and read by four
  * consumers, and they did not agree on the bytes:
  *
@@ -85,7 +84,6 @@ function blockOptionalSequence(key, values) {
 function gateEvidenceBlock(evidence) {
     if (evidence === undefined)
         return [];
-    // F3 of `rid-b1-qa`: this function used to iterate only the five known keys,
     // so anything else was dropped WITHOUT A TRACE — `initHandoff({gateEvidence:
     // {projectScans: 'typo.md'}})` wrote no block at all and the capsule then
     // read back as `field-absent`, i.e. as if nothing had ever been declared.

package/dist/services/prd/handoff-gate-evidence.d.ts

@@ -56,7 +56,6 @@ export type HandoffGateEvidenceResult = {
 /**
  * THE shape rule for a `gateEvidence` value — one home, two callers.
  *
- * F2 of `rid-b1-qa` found this rule written twice (`handoff-service.ts`'s
  * `isGateEvidenceMap`, added by B1, and this module's own inline checks) with
  * the SAME accept/reject boundary but DIFFERENT results: the same bytes
  * produced a map WITH unknown keys through `readHandoff` and a map WITHOUT

package/dist/services/prd/handoff-gate-evidence.js

@@ -2,7 +2,6 @@
 //
 // The SOLE reader of the handoff frontmatter's `gateEvidence` field.
 //
-// WHAT THE FIELD IS (slice B1, rid `rid-b1-gate-evidence-producer`): a map
 // from one of five fixed gate keys to the PATH of that gate's evidence file.
 // The normative description is
 // `skills/bee/peaks-rd/references/writing-handoff-frontmatter.md:35-41`; the
@@ -12,7 +11,6 @@
 // the defect below. B1 added the producer FUNCTIONS; B2 wired their callers,
 // which is what made the difference — until then every producer passed
 // nothing, so no capsule carried the field and saying otherwise would have
-// described a fact that held only inside tests (F1 of `rid-b1-qa`). At
 // HEAD after B2: the three producers DERIVE the map from the request type
 // (`services/prd/gate-evidence-derivation.ts`), so a capsule written by
 // `peaks prd handoff init`, by the auto-regen on `prd:handed-off`, or by
@@ -24,12 +22,10 @@
 // printed by `peaks prd handoff init` (dry-run and applied), so the key set
 // does not have to be read out of this source file.
 //
-// WHAT THIS FILE USED TO SAY, AND WHY THAT WAS FALSE: its header claimed the
 // field was a `string[]` of "gate names" and that `initHandoff` wrote it.
 // Neither held. `grep -rn gateEvidence src/` hit this file and nothing else —
 // there was no producer (`HandoffFrontmatter` had no such field,
 // `serializeHandoffFrontmatter` never emitted it, `initHandoff` rejected it)
-// and no consumer. The field was prose describing data that did not exist,
 // and the comment asserting a producer was the reason nobody noticed. That
 // paragraph describes the PRE-B1 state; reading it as the current state is
 // the exact misreading that put it here.

package/dist/services/prd/handoff-path-resolution.d.ts

@@ -1,7 +1,6 @@
 /**
  * The canonical capsule path for ONE SLICE, relative to the project root.
  *
- * Slice `2026-09-14-prd-capsule-rid-scoping`: the capsule used to be one slot
  * per SESSION (`prd/handoff.md`), so the second slice's handoff silently
  * overwrote the first slice's — and `AUDIT_REQUIRES_HANDOFF` stayed green
  * because it never checked WHOSE rid the file named. Measured on
@@ -9,24 +8,18 @@
  * capsule left by a different line of work.
  *
  * This is the WRITE target, so it always carries the rid — a consumer-side
- * fallback here would leave a rid-scoped requirement with a bare-name writer,
  * which is the defect shape this slice exists to remove. Readers that must
- * tolerate pre-rid-scoping sessions call `resolveHandoffPath` instead.
  */
 export declare function handoffRelativePath(sessionId: string, requestId: string): string;
 /**
- * The capsule a CONSUMER should read for (session, requestId): the rid-scoped
- * path when it is on disk, else the pre-rid-scoping bare name. Returns null
  * when neither exists.
  *
  * Three sessions on disk still hold only the bare file
- * (`2026-09-06-session-a87ca4`, `2026-09-12-session-e37ef0`,
  * `2026-09-13-session-21878f`), so the legacy tier has to keep resolving for
  * the gate and for every reader below.
  *
  * `requestId` is optional because the detect-only audit surface reaches its
  * service without one. Such a caller can name only the bare path: a session
- * holding nothing but rid-scoped capsules reports missing rather than picking
  * among its siblings' capsules, which would re-open the cross-slice mix-up
  * this scoping exists to close (fail closed, not "some capsule is there").
  */

package/dist/services/prd/handoff-path-resolution.js

@@ -1,6 +1,5 @@
 /**
  * Slice `b1-filesplit-campaign` (wave 3) — verbatim extraction of the handoff
- * capsule PATH layer from `./handoff-service.ts` (the id guard, the rid-scoped
  * write path and the consumer-side resolver) so that module clears the 300
  * raw-line cap. No guard, no message string and no join changed;
  * `handoff-service.ts` re-exports both public names from its own path, so no
@@ -14,8 +13,6 @@ import { isUnsafePathInput } from '../../shared/path-safety.js';
 import { REQUEST_ID_PATTERN } from '../artifacts/request-artifact-service.js';
 /**
  * Both ids in a handoff path are caller-supplied path segments, so both are
- * checked at the join. Added 2026-09-14 (repair R1, security audit F2 of
- * `2026-09-14-cli-id-escape-instrumentation`).
  *
  * This function was introduced by `0536d5bd` — the commit that instrumented
  * this defect class — with neither id checked, and it sat outside rule D's
@@ -48,7 +45,6 @@ function assertSafeHandoffIds(sessionId, requestId) {
 /**
  * The canonical capsule path for ONE SLICE, relative to the project root.
  *
- * Slice `2026-09-14-prd-capsule-rid-scoping`: the capsule used to be one slot
  * per SESSION (`prd/handoff.md`), so the second slice's handoff silently
  * overwrote the first slice's — and `AUDIT_REQUIRES_HANDOFF` stayed green
  * because it never checked WHOSE rid the file named. Measured on
@@ -56,27 +52,21 @@ function assertSafeHandoffIds(sessionId, requestId) {
  * capsule left by a different line of work.
  *
  * This is the WRITE target, so it always carries the rid — a consumer-side
- * fallback here would leave a rid-scoped requirement with a bare-name writer,
  * which is the defect shape this slice exists to remove. Readers that must
- * tolerate pre-rid-scoping sessions call `resolveHandoffPath` instead.
  */
 export function handoffRelativePath(sessionId, requestId) {
     assertSafeHandoffIds(sessionId, requestId);
     return join('.peaks', '_runtime', sessionId, 'prd', `handoff-${requestId}.md`);
 }
 /**
- * The capsule a CONSUMER should read for (session, requestId): the rid-scoped
- * path when it is on disk, else the pre-rid-scoping bare name. Returns null
  * when neither exists.
  *
  * Three sessions on disk still hold only the bare file
- * (`2026-09-06-session-a87ca4`, `2026-09-12-session-e37ef0`,
  * `2026-09-13-session-21878f`), so the legacy tier has to keep resolving for
  * the gate and for every reader below.
  *
  * `requestId` is optional because the detect-only audit surface reaches its
  * service without one. Such a caller can name only the bare path: a session
- * holding nothing but rid-scoped capsules reports missing rather than picking
  * among its siblings' capsules, which would re-open the cross-slice mix-up
  * this scoping exists to close (fail closed, not "some capsule is there").
  */

package/dist/services/prd/handoff-service.d.ts

@@ -4,7 +4,6 @@
  *
  * Owns the immutable handoff at
  * `.peaks/_runtime/<sessionId>/prd/handoff-<rid>.md` (one capsule per slice;
- * the pre-rid-scoping `.peaks/_runtime/<sessionId>/prd/handoff.md` stays
  * readable through `resolveHandoffPath`):
  *
  *   - `initHandoff` — pure; computes sha256 of the body and returns
@@ -50,7 +49,6 @@ export declare function initHandoff(opts: {
      *  read the type itself — so the map can be constructed without touching
      *  the disk; that is why the parameter exists rather than an internal call.
      *
-     *  SHAPE CONTRACT (F2 of `rid-b1-qa`, now enforced in both directions): a
      *  map this accepts is EXACTLY what `readHandoffGateEvidence` reports as
      *  `evidence` — `classifyGateEvidence` is the one shape rule behind both,
      *  and `parseHandoffContent` stores the classified map rather than the raw

package/dist/services/prd/handoff-service.js

@@ -4,7 +4,6 @@
  *
  * Owns the immutable handoff at
  * `.peaks/_runtime/<sessionId>/prd/handoff-<rid>.md` (one capsule per slice;
- * the pre-rid-scoping `.peaks/_runtime/<sessionId>/prd/handoff.md` stays
  * readable through `resolveHandoffPath`):
  *
  *   - `initHandoff` — pure; computes sha256 of the body and returns
@@ -202,7 +201,6 @@ function parseHandoffContent(content) {
  * So `readHandoff` succeeding is NOT evidence that a capsule is verifiable —
  * the tolerance above exists so old capsules stay READABLE, not so they become
  * acceptable. Request §三 bullet 3 asked for exactly this confirmation
- * (rid `2026-09-14-handoff-writer-gate-divergence`).
  */
 function isHandoffFrontmatter(value) {
     if (!value || typeof value !== 'object')

package/dist/services/prd/handoff-types.d.ts

@@ -15,7 +15,6 @@
  *
  * Path convention: the file lands at
  * `.peaks/_runtime/<sessionId>/prd/handoff-<rid>.md` (one capsule per slice;
- * `.peaks/_runtime/<sessionId>/prd/handoff.md` is the pre-rid-scoping tier and
  * stays readable). Gitignored session artifact; the binding to `<sessionId>` lives in
  * `.peaks/_runtime/current-change`). NEVER write under
  * `.peaks/_runtime/<change-id>/...` directly (slice 2.8.3 hard ban).
@@ -106,7 +105,6 @@ export interface HandoffFrontmatter extends HandoffAuthoredFields {
     readonly writtenAt: string;
     /** PRD goal IDs the handoff binds to (e.g. `['G1', 'G2']`). */
     readonly goals: readonly string[];
-    /** PRD acceptance-criteria IDs (e.g. `['AC-1', 'AC-2']`). */
     readonly acceptanceCriteria: readonly string[];
     /** PRD preserved-behavior IDs (e.g. `['P1', 'P12']`). */
     readonly preservedBehavior: readonly string[];

package/dist/services/prd/handoff-types.js

@@ -15,7 +15,6 @@
  *
  * Path convention: the file lands at
  * `.peaks/_runtime/<sessionId>/prd/handoff-<rid>.md` (one capsule per slice;
- * `.peaks/_runtime/<sessionId>/prd/handoff.md` is the pre-rid-scoping tier and
  * stays readable). Gitignored session artifact; the binding to `<sessionId>` lives in
  * `.peaks/_runtime/current-change`). NEVER write under
  * `.peaks/_runtime/<change-id>/...` directly (slice 2.8.3 hard ban).

package/dist/services/prd/project-scan-bootstrap-service.d.ts

@@ -1,5 +1,4 @@
 /**
- * project-scan bootstrap service — slice 2026-07-15-project-scan-bootstrap
  * (PRD G1 + G2 + G4b / AC1-AC10 / R1-R4).
  *
  * Owns the "first time a project enters Peaks-Loop" bootstrap flow:

package/dist/services/prd/project-scan-bootstrap-service.js

@@ -1,5 +1,4 @@
 /**
- * project-scan bootstrap service — slice 2026-07-15-project-scan-bootstrap
  * (PRD G1 + G2 + G4b / AC1-AC10 / R1-R4).
  *
  * Owns the "first time a project enters Peaks-Loop" bootstrap flow:
@@ -35,7 +34,6 @@ const SOURCE_FILE_EXTENSIONS = /\.(tsx?|jsx?|vue|svelte)$/;
 /**
  * Monorepo layout sentinels. A project is monorepo-shaped if it carries
  * one of these config files at its root, even when `src/` is absent.
- * Slice 2026-07-15 hot-fix (ice-cola real-world test, 2026-07-15):
  *   `pnpm-workspace.yaml` is the most common signal; `turbo.json`
  *   (Turborepo) and `nx.json` (Nx) are the others the ecosystem
  *   reaches for. lerna.json is legacy-only and intentionally omitted
@@ -123,7 +121,6 @@ function directoryContainsSourceFiles(rootDir) {
  * 1. `src/` at the root (single-package layout).
  * 2. Any of the monorepo source roots: `packages/`, `apps/`, `libs/`,
  *    `services/`, `workspaces/` — each is checked recursively for at
- *    least one matching source file. Slice 2026-07-15 hot-fix (ice-cola
  *    test, 2026-07-15): the original implementation only looked at
  *    `src/` and mis-classified monorepos as 0-1 (pnpm-workspace layout
  *    puts source under `packages/<pkg>/src/`, not `<root>/src/`).
@@ -145,7 +142,6 @@ function projectHasSourceFiles(projectRoot) {
     return false;
 }
 /** Detect 0-1: no package.json OR no source files.
- *  Slice 2026-07-15 hot-fix (ice-cola test, 2026-07-15): monorepos with
  *  source under packages/<pkg>/ are no longer mis-classified as 0-1. */
 function isZeroToOneProject(projectRoot) {
     const hasPackageJson = existsSync(join(projectRoot, 'package.json'));

package/dist/services/prd/project-scan-types.d.ts

@@ -5,7 +5,6 @@
  * that carries tech-stack snapshot + business-knowledge sediment. It
  * is the load-bearing input to peaks-prd Step 0.8 ("Read project-scan
  * before brainstorm") and the output sink for peaks-txt's sediment
- * step (Group C, AC-5).
  *
  * Layout:
  *   .peaks/project-scan/

package/dist/services/prd/project-scan-types.js

@@ -5,7 +5,6 @@
  * that carries tech-stack snapshot + business-knowledge sediment. It
  * is the load-bearing input to peaks-prd Step 0.8 ("Read project-scan
  * before brainstorm") and the output sink for peaks-txt's sediment
- * step (Group C, AC-5).
  *
  * Layout:
  *   .peaks/project-scan/

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

@@ -11,7 +11,6 @@ export declare function savePreferences(projectRoot: string, overrides: Partial<
  */
 export declare function writeAtomic(filePath: string, prefs: ProjectPreferences): void;
 /**
- * Slice 2026-06-23-audit-4th #C1: migrate a legacy preferences.json
  * (any `schema_version` older than PREFERENCES_SCHEMA_VERSION) to the
  * current shape. Returns the migrated object + a list of changes
  * applied (for surfacing in the CLI envelope and the migration log).

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

@@ -9,7 +9,6 @@ export function preferencesPath(projectRoot) {
 export function loadPreferences(projectRoot) {
     const filePath = preferencesPath(projectRoot);
     if (!existsSync(filePath)) {
-        // Slice 2026-07-22-orchestrator-memory-preflight: when
         // .peaks/preferences.json is missing, this returns a clone of
         // DEFAULT_PREFERENCES, which now carries the `memoryPreflight`
         // block (see preferences-types.ts). Partial overlays fall through
@@ -33,7 +32,6 @@ export function loadPreferences(projectRoot) {
         raw.schema_version !== PREFERENCES_SCHEMA_VERSION) {
         throw new Error(`PREFERENCES_SCHEMA_MISMATCH: expected schema_version=${PREFERENCES_SCHEMA_VERSION} in ${filePath}, got ${raw?.schema_version}`);
     }
-    // Slice 2026-06-24-audit-5th-p2: fail fast on any fanout mode value
     // outside the closed set `['fan-out']`. The previous 'serial' opt-out
     // was removed by user direction — a saved `defaultMode = 'serial'`
     // (or a hand-edited unknown value) now throws at load rather than
@@ -58,7 +56,6 @@ export function savePreferences(projectRoot, overrides) {
     const filePath = preferencesPath(projectRoot);
     const current = loadPreferences(projectRoot);
     const merged = mergePreferences(current, overrides);
-    // Slice 2026-06-23-audit-4th #A2: use tmp + rename so a crash
     // mid-write cannot leave a zero-byte or half-written preferences
     // file. Before the fix, a power-cut or OOM-kill between
     // writeFileSync's open and the final byte would leave
@@ -86,7 +83,6 @@ function mergePreferences(base, overrides) {
     // Shallow merge at the top level, BUT merge the `fanout` object
     // deeply so a partial override like `{"fanout": {"perTouchpoint": {...}}}`
     // does not silently drop `defaultMode`. Slice
-    // 2026-06-23-audit-p0-cleanup: today the fanout schema is 1 level
     // deep, so shallow merge happens to be safe — but the field is
     // likely to grow (perTouchpoint / perRole are obvious next additions),
     // and a future bug fix should not silently regress opt-out callers
@@ -142,7 +138,6 @@ export function migratePreferences(projectRoot, opts = {}) {
         raw.fanout !== null &&
         !Array.isArray(raw.fanout) &&
         raw.fanout.defaultMode === 'serial') {
-        // Slice 2026-06-24-audit-5th-p2: 2.8.3-era preferences.json files
         // that opted into serial dispatch must be migrated to fan-out on
         // load. The user's directive ("禁止单 sub-agent") makes the serial
         // opt-out a breaking change for any project that used it.

package/dist/services/preferences/preferences-types.d.ts

@@ -3,7 +3,6 @@
  * Per spec §8.4 — per-project state lives in `.peaks/preferences.json`,
  * NOT in `~/.peaks/config.json` (which is slim global).
  *
- * Spec reference: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §8.4
  */
 export declare const PREFERENCES_SCHEMA_VERSION = "2.0.0";
 /**
@@ -33,7 +32,6 @@ export interface ClassifyRuleOverrides {
 export interface SwarmSpeculativePreferences {
     /** Whether speculative dispatch is enabled. Default: true */
     readonly enabled: boolean;
-    /** Max concurrent speculative sub-agents. Default: 3 (slice 2026-06-24-efficiency-4p-bundle, G3/P1.1) */
     readonly maxConcurrent: number;
     /** Min hit rate below which speculative auto-disables. Default: 0.5 */
     readonly minHitRate: number;
@@ -47,7 +45,6 @@ export interface ProjectPreferences {
      */
     readonly schema_version: typeof PREFERENCES_SCHEMA_VERSION;
     /**
-     * Slice 2026-06-28-code-mode-bypass-fix: economyMode is a
      * **MODEL-SELECTION** knob only — it chooses between the cheap
      * configured provider (`getConfiguredExecutionModelId`) and the
      * strongest planner/reviewer model (`getStrongestModelId(...)`). It does
@@ -69,7 +66,6 @@ export interface ProjectPreferences {
      */
     readonly economyMode: boolean;
     /**
-     * Slice 2026-06-28: swarmMode controls whether the swarm subgraph
      * (peaks-rd/qa worker graph) is generated at all. It does NOT
      * control fan-out. Fan-out is governed by the slice DAG + the
      * `fanout.defaultMode` preference; swarmMode only decides the
@@ -105,7 +101,6 @@ export interface ProjectPreferences {
      */
     readonly agentShieldEnabled: boolean;
     /**
-     * Slice 2026-06-24-audit-5th-p2: fan-out is now a HARD constraint.
      * The previous opt-out (`defaultMode = 'serial'`) is removed by user
      * direction. Single-sub-agent dispatch is no longer permitted when
      * the slice DAG has ≥ 2 leaves at the same topological level; the
@@ -119,7 +114,6 @@ export interface ProjectPreferences {
      */
     readonly fanout: FanoutPreference;
     /**
-     * Slice 2026-07-22-orchestrator-memory-preflight: orchestrator-side memory
      * preflight knobs. Optional — `resolveMemoryPreflightConfig` (see
      * src/services/context/memory-preflight-config.ts) merges over a hard-coded
      * default block when this key is absent, so legacy preferences.json files
@@ -132,31 +126,23 @@ export interface ProjectPreferences {
         /** Back-compat hot item cap; `hotItemCap` overrides it when set. */
         readonly listCap?: number;
         readonly contentCacheBytes?: number;
-        /** Slice 2026-09-09-memory-retrieval: hard byte cap on the block. */
         readonly maxBytes?: number;
-        /** Slice 2026-09-09-memory-retrieval: max hot items (default 10). */
         readonly hotItemCap?: number;
-        /** Slice 2026-09-09-memory-retrieval: max warm items (default 4; 0 disables). */
         readonly warmItemCap?: number;
-        /** Slice 2026-09-09-memory-retrieval: min task-token hits for warm eligibility. */
         readonly warmMinTokenHits?: number;
-        /** Slice 2026-09-09-memory-retrieval: soft selection wall-clock budget (ms). */
         readonly selectionTimeBudgetMs?: number;
-        /** Slice 2026-09-09-memory-retrieval: inline memo bodies (default false). */
         readonly includeBodies?: boolean;
     };
 }
 export type FanoutMode = 'fan-out';
 export declare const FANOUT_MODES: readonly FanoutMode[];
 /**
- * Runtime type guard for `FanoutMode`. Slice 2026-06-24-audit-5th-p2
  * narrowed the closed set from `['fan-out','serial']` to `['fan-out']`
  * — stale preferences.json files with `"serial"` must now fail-fast at
  * load (see `preferences-service.ts`) instead of being silently coerced.
  */
 export declare function isFanoutMode(value: unknown): value is FanoutMode;
 export interface FanoutPreference {
-    /** Hard-coded mode. Slice 2026-06-24-audit-5th-p2 removed the serial opt-out. */
     readonly defaultMode: FanoutMode;
 }
 export declare const DEFAULT_PREFERENCES: ProjectPreferences;

package/dist/services/preferences/preferences-types.js

@@ -3,12 +3,10 @@
  * Per spec §8.4 — per-project state lives in `.peaks/preferences.json`,
  * NOT in `~/.peaks/config.json` (which is slim global).
  *
- * Spec reference: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §8.4
  */
 export const PREFERENCES_SCHEMA_VERSION = '2.0.0';
 export const FANOUT_MODES = ['fan-out'];
 /**
- * Runtime type guard for `FanoutMode`. Slice 2026-06-24-audit-5th-p2
  * narrowed the closed set from `['fan-out','serial']` to `['fan-out']`
  * — stale preferences.json files with `"serial"` must now fail-fast at
  * load (see `preferences-service.ts`) instead of being silently coerced.
@@ -38,7 +36,6 @@ export const DEFAULT_PREFERENCES = {
     fanout: {
         defaultMode: 'fan-out'
     },
-    // Slice 2026-07-22-orchestrator-memory-preflight: defaults aligned with
     // memory-preflight-config.ts::DEFAULTS. Kept in sync manually because
     // loadPreferences() returns DEFAULT_PREFERENCES verbatim when the on-disk
     // file is absent, and partial overlays rely on memoryPreflight being
@@ -48,7 +45,6 @@ export const DEFAULT_PREFERENCES = {
         maxTokens: 1200,
         listCap: 12,
         contentCacheBytes: 6000,
-        // Slice 2026-09-09-memory-retrieval tiered budget (see
         // memory-preflight-config.ts::DEFAULTS).
         maxBytes: 4800,
         hotItemCap: 10,

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

@@ -31,7 +31,6 @@ import { existsSync, mkdirSync, readFileSync, writeFileSync } from 'node:fs';
 import { dirname, join, resolve } from 'node:path';
 import { getSessionIdCanonical } from '../session/session-manager.js';
 import { findProjectRoot } from '../config/config-safety.js';
-// As of slice 2026-06-06-sub-agent-spawn-bug-and-decouple, the per-session
 // sub-agent state files live under `.peaks/_sub_agents/<sid>/`, NOT under
 // `.peaks/_runtime/<sid>/system/`. The new path mirrors the existing `_runtime/`
 // and `_dogfood/` convention (leading underscore = meta-classification, not

package/dist/services/qa/bdd-test-style-verifier.d.ts

@@ -1,7 +1,6 @@
 /**
  * src/services/qa/bdd-test-style-verifier.ts
  *
- * rid-2026-08-05-bdd-test-style Slice B — peaks-qa verification-time
  * BDD test-style verifier. This is the read-only, post-edit companion
  * to the `scripts/migrate-to-bdd.mjs` AST migrator shipped in Slice A.
  *

package/dist/services/qa/bdd-test-style-verifier.js

@@ -1,7 +1,6 @@
 /**
  * src/services/qa/bdd-test-style-verifier.ts
  *
- * rid-2026-08-05-bdd-test-style Slice B — peaks-qa verification-time
  * BDD test-style verifier. This is the read-only, post-edit companion
  * to the `scripts/migrate-to-bdd.mjs` AST migrator shipped in Slice A.
  *

package/dist/services/qa/browser-event-logger.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-playwright-restart-loop — G4.
  *
  * BrowserEventLogger
  *

package/dist/services/qa/browser-event-logger.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-playwright-restart-loop — G4.
  *
  * BrowserEventLogger
  *

package/dist/services/qa/browser-restart-detector.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-playwright-restart-loop — G1.
  *
  * BrowserRestartDetector
  *

package/dist/services/qa/browser-restart-detector.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-playwright-restart-loop — G1.
  *
  * BrowserRestartDetector
  *

package/dist/services/qa/browser-reuse-hint.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-playwright-restart-loop — G2.
  *
  * The browser-context reuse hint is appended to the sub-agent prompt
  * whenever a peaks-qa-dispatched sub-agent (peaks-ui or general-purpose

package/dist/services/qa/browser-reuse-hint.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-playwright-restart-loop — G2.
  *
  * The browser-context reuse hint is appended to the sub-agent prompt
  * whenever a peaks-qa-dispatched sub-agent (peaks-ui or general-purpose

package/dist/services/qa/qa-business-review-state.js

@@ -60,8 +60,6 @@ export function getQaReviewDir(projectRoot, sessionId) {
     //
     // It does NOT cover the rid axis: the request id is joined one function later,
     // in `getQaReviewPath` below. Corrected 2026-09-14 (repair R1) — this comment
-    // previously said "one guard here covers the whole family", and the security
-    // audit of `2026-09-14-cli-id-escape-instrumentation` (F1b) measured that claim
     // false: `qa-business-review '../../../../…/EVILQA3'` wrote a `.json` file
     // outside the project root under `ok: true`.
     if (isUnsafePathInput(sessionId)) {

package/dist/services/qa/screenshot-archive-service.d.ts

@@ -1,5 +1,4 @@
 /**
- * rid-012 (2026-07-27) — screenshot archive service.
  *
  * Purpose: enforce the peaks-qa SKILL.md "Hard contracts for browser
  * validation" Contract 1 — every Playwright screenshot MUST land under

package/dist/services/qa/screenshot-archive-service.js

@@ -1,5 +1,4 @@
 /**
- * rid-012 (2026-07-27) — screenshot archive service.
  *
  * Purpose: enforce the peaks-qa SKILL.md "Hard contracts for browser
  * validation" Contract 1 — every Playwright screenshot MUST land under

package/dist/services/rd/impl.js

@@ -1,6 +1,5 @@
 /**
  * Per spec §4.3 战术审计 (peaks-rd/战术) — impl.json writer + TACT.sig computation.
- * 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`).
  *
  * Hard constraints: