peaks-loop 4.1.1 → 4.1.2

package/dist/cli/program.js

@@ -22,7 +22,6 @@ import { applyRetention } from '../services/log/retention.js';
 import { writeLogEntry, maybeWriteStderr } from '../services/log/logger.js';
 import { printSuperCommandCatalog } from './cli-helpers.js';
 export { printErrorEnvelope, printResult } from './cli-helpers.js';
-// Slice rid-001 (P0-1 envelope closure, fix #4): the prior default
 // `ProgramIO` funneled Commander's `configureOutput().writeErr` callback
 // through raw `console.error`, which bypassed the canonical envelope
 // path and left a `// TODO(g2): legacy console.error without envelope`
@@ -39,7 +38,6 @@ function defaultStdoutSink(text) {
     process.stdout.write(`${text}\n`);
 }
 /**
- * Slice 2026-06-16-cli-logging (G1, G2, G3, G7). One structured
  * `peaks-loop start` entry per CLI invocation, plus a 7-day
  * retention sweep. Wired into the global program so EVERY
  * peaks-loop command — even a bare `peaks` quickstart — writes
@@ -79,7 +77,6 @@ function bootstrapLogger(verbose) {
         maybeWriteStderr(entry, { verbose: true });
     }
 }
-// Slice 2026-06-16-cli-logging (AC1 regression fix, repair cycle 1):
 // Process-scoped guard so the bootstrap log line is written AT MOST
 // once per process, regardless of whether it fires from the
 // `preAction` hook (subcommand path) or from the version action
@@ -107,7 +104,6 @@ Run peaks (no arguments) for a quickstart. You likely want one of:
         writeOut: (text) => io.stdout(text.trimEnd()),
         writeErr: (text) => io.stderr(text.trimEnd())
     })
-        // Slice 2026-06-16-cli-logging (AC1 regression fix, repair cycle 1):
         // We DO NOT use Commander's built-in `.version()` here. Commander's
         // built-in version handler short-circuits the program BEFORE the
         // `preAction` hook fires, which means a bare `peaks --version`
@@ -122,7 +118,6 @@ Run peaks (no arguments) for a quickstart. You likely want one of:
         // per process.
         .option('-v, --version', 'output the version number')
         .option('-V', 'output the version number')
-        // Slice 2026-06-16-cli-logging (G3): global verbose flag. Mirrors
         // the PEAKS_LOG_LEVEL=debug env var; with this set, the logger
         // mirrors every entry to stderr IN ADDITION to the file.
         // Long-only: `-v` is already bound to `--version` by the
@@ -131,7 +126,6 @@ Run peaks (no arguments) for a quickstart. You likely want one of:
         .option('--verbose', 'mirror log lines to stderr (also: PEAKS_LOG_LEVEL=debug)')
         .hook('preAction', () => {
         const opts = program.opts();
-        // Slice 2026-06-16-cli-logging (repair cycle 2): gate the bootstrap on
         // the same `bootstrapRan` guard the version action uses, so a single
         // process that invokes the program twice (vitest, programmatic) does
         // not emit duplicate `peaks-loop start` JSONL entries.
@@ -209,7 +203,6 @@ Run peaks (no arguments) for a quickstart. You likely want one of:
     // registerCoreAndArtifactCommands instead of being created twice.
     autoRegisterAllCommands(program, io);
     registerSkillVisibilityCommand(program, repoRoot);
-    // Slice rid-statusline-stale-ux AC-2: register `peaks session primer`
     // so it appears in `peaks session --help` for LLM `<TAB>`-discovery.
     // Mounted as a CHILD of the existing `session` commander group
     // (verified at src/cli/commands/core/session-command.ts:32). NOT

package/dist/reporters/bdd-reporter.js

@@ -1,6 +1,5 @@
 // src/reporters/bdd-reporter.ts
 //
-// rid-2026-08-05-bdd-test-style Slice C — vitest custom reporter that
 // emits a pure BDD document view of the run. Designed for business
 // reviewers and downstream LLM prompts; it is NOT a replacement for
 // the default reporter.

package/dist/services/24h-mode/auto-engage.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-09-mode-consolidation (Slice B): auto-engage may set the
  * 24h MODE — and ONLY the 24h mode.
  *
  * `24h` is the single mode that may be set without an explicit user pick

package/dist/services/24h-mode/auto-engage.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-09-mode-consolidation (Slice B): auto-engage may set the
  * 24h MODE — and ONLY the 24h mode.
  *
  * `24h` is the single mode that may be set without an explicit user pick

package/dist/services/24h-mode/decider.d.ts

@@ -1,7 +1,6 @@
 /**
  * 24h mode B3 trigger evaluation + attempts counter.
  *
- * Rid-020a (state-only slice). `fireB3` is the single mutating
  * primitive: it increments the per-key counter and escalates with a
  * `B3Escalation` when the count reaches `B3_THRESHOLD` (3). The
  * counter is **per-key** — AC-T3 mandates B1 and B2 retries do not
@@ -95,8 +94,6 @@ export type HandoffExitCondition = (typeof HANDOFF_EXIT_CONDITIONS)[number];
 export declare function isHandoffExitCondition(s: string): s is HandoffExitCondition;
 export declare function isHandoffState(s: State): boolean;
 /**
- * Slice 2026-07-28 (rid-027), re-keyed by slice
- * 2026-09-09-mode-consolidation: resolve the auto-compact mode from
  * the PRESENCE MODE, not the 24h state machine. Returns `'partial'`
  * when the mode is `24h`, otherwise `'standard'`. This is the CLI-side
  * default; the explicit `--mode` flag in `peaks code auto-compact`

package/dist/services/24h-mode/decider.js

@@ -1,7 +1,6 @@
 /**
  * 24h mode B3 trigger evaluation + attempts counter.
  *
- * Rid-020a (state-only slice). `fireB3` is the single mutating
  * primitive: it increments the per-key counter and escalates with a
  * `B3Escalation` when the count reaches `B3_THRESHOLD` (3). The
  * counter is **per-key** — AC-T3 mandates B1 and B2 retries do not
@@ -132,8 +131,6 @@ export function isHandoffState(s) {
     return s === 'HANDOFF';
 }
 /**
- * Slice 2026-07-28 (rid-027), re-keyed by slice
- * 2026-09-09-mode-consolidation: resolve the auto-compact mode from
  * the PRESENCE MODE, not the 24h state machine. Returns `'partial'`
  * when the mode is `24h`, otherwise `'standard'`. This is the CLI-side
  * default; the explicit `--mode` flag in `peaks code auto-compact`

package/dist/services/24h-mode/index.d.ts

@@ -1,9 +1,7 @@
 /**
  * Public barrel for 24h-mode service module.
  *
- * Rid-020a (state-only slice). Exports the 6-state enum, the
  * DecisionKey enum, the persistence API, and the B3 decider API
- * so that the `peaks session 24h-mode` CLI (and future rid-020b
  * `peaks code run --24h`) can consume them without reaching into
  * the internal file layout.
  */

package/dist/services/24h-mode/index.js

@@ -1,9 +1,7 @@
 /**
  * Public barrel for 24h-mode service module.
  *
- * Rid-020a (state-only slice). Exports the 6-state enum, the
  * DecisionKey enum, the persistence API, and the B3 decider API
- * so that the `peaks session 24h-mode` CLI (and future rid-020b
  * `peaks code run --24h`) can consume them without reaching into
  * the internal file layout.
  */

package/dist/services/24h-mode/state.d.ts

@@ -1,7 +1,6 @@
 /**
  * 24h mode state machine — state types + DecisionKey enum.
  *
- * Rid-020a (state-only slice). The proposal defines six states that
  * capture the lifecycle of a 24h code run; the DecisionKey enum is the
  * enumeration of B1/B2 decision keys whose retry counter lives in
  * `AttemptsMap`. Persistence and trigger evaluation live in sibling

package/dist/services/24h-mode/state.js

@@ -1,7 +1,6 @@
 /**
  * 24h mode state machine — state types + DecisionKey enum.
  *
- * Rid-020a (state-only slice). The proposal defines six states that
  * capture the lifecycle of a 24h code run; the DecisionKey enum is the
  * enumeration of B1/B2 decision keys whose retry counter lives in
  * `AttemptsMap`. Persistence and trigger evaluation live in sibling

package/dist/services/24h-mode/store.d.ts

@@ -2,7 +2,6 @@
  * 24h mode persistence — atomic JSON snapshot under
  * `.peaks/_runtime/<sessionId>/24h-state.json`.
  *
- * Rid-020a (state-only slice). The store never invents a session id:
  * the caller passes one (the CLI resolves it from `.peaks/_runtime/session.json`).
  * Writes use the temp-file + rename pattern so a crash mid-write never
  * leaves a half-written state file (atomic on POSIX, near-atomic on

package/dist/services/24h-mode/store.js

@@ -2,7 +2,6 @@
  * 24h mode persistence — atomic JSON snapshot under
  * `.peaks/_runtime/<sessionId>/24h-state.json`.
  *
- * Rid-020a (state-only slice). The store never invents a session id:
  * the caller passes one (the CLI resolves it from `.peaks/_runtime/session.json`).
  * Writes use the temp-file + rename pattern so a crash mid-write never
  * leaves a half-written state file (atomic on POSIX, near-atomic on

package/dist/services/adapter/adapter-registry.js

@@ -1,5 +1,4 @@
 /**
- * Adapter registry — slice S2-a of RD-2.
  *
  * Persists user-registered vendor adapters to
  * `.peaks/runtime/adapters.json` and resolves them by id. The

package/dist/services/artifacts/artifact-prerequisites.d.ts

@@ -49,13 +49,9 @@ export type ArtifactPrerequisite = {
     legacyRelativePath?: string;
     /**
      * Further, older locations, tried **in declared order** after
-     * `legacyRelativePath`. Slice `2026-09-14-audit-artifact-rid-scoping`
      * added this because the two audit artifacts have a two-release
-     * history behind their rid-scoped path: the pre-rid-scoping
      * `audit/security.md` (v2.12.0) and, behind it, the v2.11.x
      * `rd/security-review.md`. Three sessions on disk
-     * (`2026-09-06-session-a87ca4`, `2026-09-10-session-528a63`,
-     * `2026-09-12-session-e37ef0`) hold their security evidence only at
      * the last of those, so the oldest tier still has to resolve.
      */
     legacyRelativePaths?: ReadonlyArray<string>;
@@ -67,7 +63,6 @@ export type PrerequisiteCheckResult = {
         description: string;
     }>;
     /**
-     * v2.13.2 AC-5 — soft-block warnings. Each entry is a prereq
      * path that is currently missing but is in a 1-minor-release
      * back-compat window. The transition gate does not throw on
      * `missing`-only (so legacy callers keep working) but surfaces the

package/dist/services/artifacts/artifact-prerequisites.js

@@ -27,7 +27,6 @@ const BUG_ANALYSIS = {
     description: 'Bug root-cause analysis (reproduction, affected paths, fix approach, regression test plan)',
     mustContain: ['## Root cause', '## Fix approach']
 };
-// Slice `2026-09-14-audit-artifact-rid-scoping`: the rid is part of the
 // filename (`code-review-<rid>.md`). A fixed per-session path cannot hold
 // two slices' evidence at once — the second slice's write silently
 // destroyed the first slice's on 2026-09-13, and the gate stayed green
@@ -66,13 +65,11 @@ const PERF_BASELINE = {
 // handoff (`prd/handoff.md`) — see `AUDIT_REQUIRES_HANDOFF` below.
 //
 // Back-compat: the canonical location is `audit/security-<rid>.md`
-// (and `audit/perf-<rid>.md`); the pre-rid-scoping `audit/security.md`
 // (and `audit/perf.md`) plus the older `rd/security-review.md` (and
 // `rd/perf-baseline.md`) are accepted via `legacyRelativePaths`, in
 // that order, for the back-compat window.
 const AUDIT_SECURITY = {
     relativePath: 'audit/security-<rid>.md',
-    // Two legacy tiers behind the rid-scoped path: the pre-rid-scoping
     // v2.12.0 location, then the v2.11.x one. Both are live on disk.
     legacyRelativePath: 'audit/security.md',
     legacyRelativePaths: ['rd/security-review.md'],
@@ -108,22 +105,18 @@ const AUDIT_PERF = {
 // rd-side CLI hard gate (blocks `rd → qa-handoff`), while qa-side
 // consumption remains soft.
 //
-// v2.13.2 AC-5 — 1-minor-release back-compat window. When
 // `backCompat: true` is set, a MISSING file downgrades to a warning
 // (`mut-report-missing-deprecated-in-v2.14.0`) instead of a hard
 // failure. The hard-fail behavior for `passed: false` is preserved
 // (the body still has to carry `"passed": true` when present).
 // v2.14.0 will remove `backCompat` and re-elevate missing → throw.
 //
-// Slice `2026-09-14-audit-artifact-rid-scoping` deliberately does NOT
-// rid-scope this path, unlike the four audit/review artifacts above. The
 // repo's own producer/reader constant is `mutReportPath()` in
 // `packages/peaks-loop-mut/src/services/mut/report-loader.ts`, which names
 // `mut/mut-report.json`, and `peaks mut run`'s `--out` is supplied by the
 // caller. A `<rid>`-templated requirement here would be a name no producer
 // in the repo can write — a gate that exists only in prose, sitting behind
 // `backCompat: true` so it gates nothing at all. If mut ever gains a
-// rid-scoped producer, the constant and this path move together.
 const MUT_REPORT = {
     relativePath: 'mut/mut-report.json',
     description: 'peaks-mut mutation + weak-assertion report (Plan 2, v2.12.0+). v2.13.1: required at rd:qa-handoff for feature / bugfix / refactor slices. v2.13.2: back-compat window — missing file downgrades to a warning (1-minor-release); passed:false still throws. The body must carry `"passed": true` when present; failed runs are blocked at this gate. CONFIG / DOCS / CHORE slices retain the legacy "no acceptance surface" exemption.',
@@ -137,10 +130,8 @@ const MUT_REPORT = {
 };
 // v2.12.0 Group B Tier 5 — gate that the peaks-prd handoff (the
 // immutable, per-slice handoff capsule at `prd/handoff-<rid>.md`
-// since slice `2026-09-14-prd-capsule-rid-scoping`) exists before any
 // audit skill is allowed to consume it. The peaks-security-audit
 // and peaks-perf-audit CLI commands read frontmatter from the
-// capsule (AC-2.4 / AC-3.4); if the handoff is missing the
 // audit skill aborts — and so should the prereq gate when those
 // audits are required at rd:qa-handoff.
 //
@@ -150,7 +141,6 @@ const MUT_REPORT = {
 // PRD handoff exists for small CONFIG-only commits).
 const AUDIT_REQUIRES_HANDOFF = {
     relativePath: 'prd/handoff-<rid>.md',
-    // Slice `2026-09-14-prd-capsule-rid-scoping`: the rid is part of the
     // filename, like the four audit/review artifacts above. A single slot per
     // SESSION cannot hold two slices' capsules — `peaks prd handoff init`
     // overwrote it on every call, and this gate stayed green because it pinned
@@ -159,9 +149,7 @@ const AUDIT_REQUIRES_HANDOFF = {
     // prerequisite on a capsule written for a different line of work.
     // The bare path stays accepted (see `legacyRelativePath`) so the three
     // sessions on disk that hold only `prd/handoff.md` keep passing. That tier
-    // is rid-blind by design — the scoping binds for capsules written from now
     // on, and every producer (`handoff-service.initHandoff`,
-    // `handoff-auto-regen`, `evidence generate`) writes the rid-scoped name.
     legacyRelativePath: 'prd/handoff.md',
     description: 'PRD handoff capsule (v2.12.0+) — peaks-security-audit / peaks-perf-audit both read frontmatter from this file. Must exist before audit prereqs are evaluated at rd:qa-handoff. The rid is part of the filename so two slices in one session do not collide; the bare pre-rid-scoping location is accepted as the legacy tier.',
     // Empty `mustContain` is fine — file existence is the contract.
@@ -200,7 +188,6 @@ const KARPATHY_REVIEW = {
 // pass the gate. The full envelope lives at the JSON sibling path
 // (`rd/third-party-review.json`); this MD file is the human-readable
 // companion. The body is also expected to declare a `modelFamily`
-// distinct from the karpathy-reviewer's modelFamily (AC-4.4 — the CI
 // gate diffs `rd/third-party-review.json.modelFamily` against
 // `rd/karpathy-review.md` parsed `modelFamily`); equality fails the
 // build. When `~/.peaks/config.json` lacks a `reviewer.providers`
@@ -249,7 +236,6 @@ const PRD_CONTENT = {
 // describe business behavior" — and `it(` is the dominant one by ~8x.
 // Measured 2026-09-16 (`grep -rho '\bit(' tests | wc -l`, same for `test(`):
 // `it(` 3015 vs `test(` 372 across `tests/`; the three test files slice
-// 2026-09-16-codegraph-index-integrity added contain `it(` 58 / `test(` 0.
 // The gate was in fact passing on artifacts whose ONLY `test(` was prose —
 // including this repo's own generated template `buildTestCases`
 // (`src/services/evidence/evidence-generator.ts`), which literally reads
@@ -462,7 +448,6 @@ export async function checkPrerequisites(options) {
     if (options.sessionId !== undefined && isUnsafePathInput(options.sessionId)) {
         throw new Error(`Invalid session id: ${options.sessionId} (must be a single path segment)`);
     }
-    // Slice 006 simplifies the resolution to a 2-tier fallback. The
     // per-change-id scope (`.peaks/_runtime/<sessionId>/<role>/`) is gone — new
     // artifacts go to the session dir directly. The 2 tiers are:
     //   1. `.peaks/_runtime/<sid>/<role>/...` (post-F3 canonical
@@ -481,7 +466,6 @@ export async function checkPrerequisites(options) {
         const relative = resolvePrerequisitePath(prerequisite, options.requestId);
         const absolute = await resolvePrerequisiteAbsolutePathWithFallback(canonicalSessionRoot, legacySessionRoot, prerequisite, options.requestId);
         if (absolute === null) {
-            // v2.13.2 AC-5: back-compat window for MUT_REPORT — missing
             // file downgrades to a warning, NOT a hard failure. v2.14.0
             // will remove this branch and re-elevate missing → throw.
             const backCompat = prerequisite.backCompat === true;
@@ -503,7 +487,6 @@ export async function checkPrerequisites(options) {
             }
         }
     }
-    // GATE C, second half (B2, rid `rid-b2-gate-evidence-wiring`): the capsule's
     // own `gateEvidence` DECLARATION must be true — every path it names must
     // exist. The table loop above owns "which artifacts this type must produce";
     // this owns "the handoff may not claim evidence it does not have". They are
@@ -570,7 +553,6 @@ function emitPrereqTransitionEvent(opts) {
 }
 /**
  * Resolve a prerequisite to an on-disk path, with a 2-tier fallback
- * (slice 006 — the per-change-id tier was dropped because per-change-id
  * dirs are no longer created):
  *   1. `<canonicalSessionRoot>/<relative>` (post-F3 canonical session
  *      home, when `canonicalSessionRoot` is provided).
@@ -586,7 +568,6 @@ function emitPrereqTransitionEvent(opts) {
  * missing. This covers both artifacts that moved location
  * (`rd/security-review.md` → `audit/security.md`) and ones that later
  * gained a rid in the filename (`audit/security.md` →
- * `audit/security-<rid>.md`, slice `2026-09-14-audit-artifact-rid-scoping`).
  */
 async function resolvePrerequisiteAbsolutePathWithFallback(canonicalSessionRoot, legacySessionRoot, prerequisite, requestId) {
     const roots = [canonicalSessionRoot, legacySessionRoot];

package/dist/services/artifacts/artifact-templates.d.ts

@@ -9,7 +9,6 @@ export type RequestArtifactRole = 'prd' | 'ui' | 'rd' | 'qa' | 'sc';
 /**
  * Handoff path helpers.
  *
- * Slice 2026-06-29-change-id-root-removal: all handoff paths now key
  * on the session-id axis (`.peaks/_runtime/<sessionId>/<role>/...`)
  * instead of the deleted change-id axis
  * (`.peaks/_runtime/change/<sessionId>/<role>/...`). The session

package/dist/services/artifacts/artifact-templates.js

@@ -2,7 +2,6 @@ import { PRD_TEMPLATE_BODY, UI_TEMPLATE_BODY, RD_TEMPLATE_BODY, QA_TEMPLATE_BODY
 /**
  * Handoff path helpers.
  *
- * Slice 2026-06-29-change-id-root-removal: all handoff paths now key
  * on the session-id axis (`.peaks/_runtime/<sessionId>/<role>/...`)
  * instead of the deleted change-id axis
  * (`.peaks/_runtime/change/<sessionId>/<role>/...`). The session

package/dist/services/artifacts/request-artifact-service.d.ts

@@ -19,7 +19,6 @@ export type CreateRequestArtifactOptions = {
     requestType?: RequestType;
     clock?: () => string;
     /**
-     * Slice 020 — caller-keyed session binding. The callerId that initiated
      * this artifact creation (resolved via `resolveCallerId` by the CLI).
      * Recorded in the JSON envelope and on the artifact body's frontmatter
      * so a future reader knows which caller produced it. The caller-keyed
@@ -37,13 +36,11 @@ export type CreateRequestArtifactResult = {
     content: string;
     applied: boolean;
     /**
-     * Slice 020 — caller-keyed session binding. The resolved callerId
      * (D4 priority: flag > env > platform fallback) when --caller-id
      * was passed. Omitted from the result when no callerId was set.
      */
     callerId?: string;
     /**
-     * Slice 2026-06-23-request-init-change-scope-leak. The session-axis
      * dir resolved under `.peaks/_runtime/<sid>/`. Always populated so
      * the sub-agent prompt can report a stable, canonical scope
      * location to the writer.
@@ -51,7 +48,6 @@ export type CreateRequestArtifactResult = {
     scopeDir: string;
 };
 /**
- * F-1 (slice 025 security): reject rids that contain path separators, null
  * bytes, or traversal sequences. A request id is a single path segment, so
  * anything that builds a filename from one must test it against this first —
  * it is exported so those call sites reuse it instead of re-declaring a copy
@@ -63,7 +59,6 @@ export type RequestArtifactSummary = {
     role: RequestArtifactRole;
     /**
      * Durable scope of the artifact: the top-level `.peaks/_runtime/<sessionId>/`
-     * directory the file lives in. As of slice 2026-06-05-change-id-as-unit-of-work,
      * the prerequisite gate resolves paths under this dir (not the body
      * `- session:` line), so the file body and the on-disk path agree.
      */

package/dist/services/artifacts/request-artifact-service.js

@@ -4,7 +4,6 @@ import { dirname, join } from 'node:path';
 import { isDirectory, listDirectories } from 'peaks-loop-shared/fs';
 import { checkPrerequisites, DEFAULT_REQUEST_TYPE, isRequestType, VALID_REQUEST_TYPES } from './artifact-prerequisites.js';
 import { ensureSession, getSessionIdCanonical } from '../session/session-manager.js';
-// Slice 2026-06-29-change-id-root-removal: `getCurrentChangeId` was
 // removed with the change-id axis. The change-id binding file is
 // gone; request-artifact callers pass `options.sessionId` explicitly
 // or accept the requestId as the default. Path-safety helpers now
@@ -22,7 +21,6 @@ export { VALID_REQUEST_TYPES, DEFAULT_REQUEST_TYPE, isRequestType };
 // tests) keep importing from this module unchanged. The render templates,
 // handoff-path helpers, and `RequestArtifactRole` type all live in the
 // sibling `artifact-templates.ts` module — see slice
-// 2026-06-24-handoff-path-canonicalization for the rationale.
 //
 // `import type` is required so the type is in scope as a bare identifier
 // within this file (the value re-export alone does not bring types into
@@ -30,7 +28,6 @@ export { VALID_REQUEST_TYPES, DEFAULT_REQUEST_TYPE, isRequestType };
 import { renderTemplate } from './artifact-templates.js';
 export { formatHandoffPath, formatCommitBoundaryPath, formatSkillUsageLessonsPath } from './artifact-templates.js';
 /**
- * F-1 (slice 025 security): reject rids that contain path separators, null
  * bytes, or traversal sequences. A request id is a single path segment, so
  * anything that builds a filename from one must test it against this first —
  * it is exported so those call sites reuse it instead of re-declaring a copy
@@ -65,7 +62,6 @@ function defaultSessionId(iso) {
  * — from `emitObservabilityEvent`'s own session-id check, i.e. after the write.
  */
 function requestArtifactRequestsDir(projectRoot, sessionId, role) {
-    // Slice 2026-09-15 (runtime-path-unrepresentable): the two ids are branded by
     // `guardRuntimeSegment`, which performs the same `isUnsafePathInput` check
     // this function used to spell inline. The join itself now *requires* the
     // brand, so a caller that reaches this dir without a guard does not compile.
@@ -84,7 +80,6 @@ export async function createRequestArtifact(options) {
     // Use provided session ID or get/create current session. The session
     // id is the binding for the artifact file's location.
     //
-    // Slice 006 collapses the per-change-id top-level dirs. The artifact
     // file is now written under the SESSION dir
     // (`.peaks/_runtime/<sid>/<role>/requests/`) instead of the
     // change-id dir. The 2-tier fallback (canonical session → legacy
@@ -100,17 +95,14 @@ export async function createRequestArtifact(options) {
     if (isUnsafePathInput(sessionId)) {
         throw new Error(`Invalid session id: ${sessionId} (must be a single path segment)`);
     }
-    // Slice 2026-06-29-change-id-root-removal: the `current-change`
     // binding file is gone. Resolution order for the change-id (file
     // body metadata) is now:
     //   1. Explicit `options.sessionId` (CLI `--change-id`).
     //   2. The requestId itself (every request is its own scope by default).
     const sessionSlug = options.sessionId ?? options.requestId;
-    // Slice 008 (F21 fix): fail fast when the resolved session id
     // looks like a real session id (matches the date+session prefix)
     // but does NOT correspond to an actual session dir under
     // `.peaks/_runtime/`. Pre-F21 a sub-agent with a typo or stale
-    // binding (e.g. `2025-01-01-session-deadbe`) silently planned
     // to write to a non-existent path. The check is intentionally
     // scoped to "looks like a real session id" — a sid like
     // `test-session` or `s` (no date prefix) is allowed through so
@@ -137,7 +129,6 @@ export async function createRequestArtifact(options) {
         // The writer lowercases the request id into a kebab slug
         // (`buildNumberedFilename`), so the duplicate-detection endsWith must
         // compare against the SAME slug — a mixed-case id like
-        // `2026-09-06-split-batchA` is stored as `...-split-batcha.md`.
         const slug = slugifyDescription(options.requestId);
         const alreadyExists = existingFiles.some((file) => {
             if (file === `${options.requestId}.md`)
@@ -155,7 +146,6 @@ export async function createRequestArtifact(options) {
     const path = join(requestsDir, filename);
     const content = renderTemplate(options.role, options.requestId, sessionId, sessionSlug, timestamp, requestType);
     if (options.apply !== true) {
-        // Slice 2026-06-29-change-id-root-removal: scopeDir is the
         // session-axis dir (`.peaks/_runtime/<sid>/`). Pre-resolved here
         // so dry-run output reports the canonical scope location.
         const scopeDir = runtimeRoot(options.projectRoot).join(guardRuntimeSegment(sessionId, 'session id'));
@@ -312,7 +302,6 @@ export async function showRequestArtifact(options) {
     // Search for files matching the requestId (supports both legacy and numbered formats)
     // The numbered format lowercases the request id into a kebab slug
     // (`buildNumberedFilename`), so the endsWith must compare against the SAME
-    // slug — a mixed-case id like `2026-09-06-split-batchA` is stored as
     // `...-split-batcha.md` and must still resolve here.
     const slug = slugifyDescription(options.requestId);
     const findFileInDir = async (dir) => {
@@ -422,7 +411,6 @@ export async function transitionRequestArtifact(options) {
     // (Removed in v2.11.0 Group A: the tech-doc-presence + tech-doc-mandatory-
     // sections gates. The rd → spec-locked transition now relies on the
     // immutable peaks-prd handoff (sha256-frontmatter) for the same intent;
-    // see PRD for `v2-11-rd-techdoc-removal-and-runtime-friction` AC-3/AC-4.)
     // Type sanity check for PRD handoff
     if (options.typeSanityCheck !== undefined &&
         options.role === 'prd' &&

package/dist/services/artifacts/request-artifact-state-helpers.d.ts

@@ -10,7 +10,6 @@ export declare class PrerequisitesNotSatisfiedError extends Error {
     readonly sessionId: string;
     readonly missing: PrerequisiteCheckResult['missing'];
     /**
-     * v2.13.3 AC-3 — soft-block warnings carried alongside the missing
      * entries. Surfaced in the CLI error response under `data.warnings`
      * so the operator can see which prereqs were soft-blocked under
      * the 1-minor-release back-compat window (e.g. MUT_REPORT). Always

package/dist/services/artifacts/request-artifact-state-helpers.js

@@ -15,7 +15,6 @@ export class PrerequisitesNotSatisfiedError extends Error {
     sessionId;
     missing;
     /**
-     * v2.13.3 AC-3 — soft-block warnings carried alongside the missing
      * entries. Surfaced in the CLI error response under `data.warnings`
      * so the operator can see which prereqs were soft-blocked under
      * the 1-minor-release back-compat window (e.g. MUT_REPORT). Always

package/dist/services/audit/artifact-writer.d.ts

@@ -1,5 +1,4 @@
 /**
- * Audit artifact writer — Slice 2026-06-26-audit-artifact-writer-generalization.
  *
  * Generalizes the original `decision-writer.ts` (which only knew how to
  * persist a `RedLineAudit` snapshot) into a polymorphic writer that

package/dist/services/audit/artifact-writer.js

@@ -1,5 +1,4 @@
 /**
- * Audit artifact writer — Slice 2026-06-26-audit-artifact-writer-generalization.
  *
  * Generalizes the original `decision-writer.ts` (which only knew how to
  * persist a `RedLineAudit` snapshot) into a polymorphic writer that

package/dist/services/audit/decision-writer.js

@@ -116,6 +116,9 @@ export function renderDecisionMarkdown(audit, options) {
         `description: ${description}`,
         'metadata:',
         '  type: decision',
+        // The other three artifact writers all carry `artifactType`; without it a
+        // decision record is the one kind future tooling cannot query by artifact.
+        '  artifactType: decision',
         '  auditType: red-lines',
         `  totalRedLines: ${audit.totalRedLines}`,
         `  cliBacked: ${audit.cliBacked}`,
@@ -213,7 +216,6 @@ export function writeAuditDecision(audit, options) {
     };
 }
 // ---------------------------------------------------------------------------
-// Back-compat re-export — Slice 2026-06-26-audit-artifact-writer-generalization.
 //
 // `writeAuditDecision` is preserved above (no caller signature change).
 // New callers should use `writeDecision` from `artifact-writer.ts` directly.

package/dist/services/audit/enforcer-liveness.js

@@ -1,5 +1,4 @@
 /**
- * Enforcer liveness — A9 of `.peaks/docs/diagnosis-2026-09-15-peaks-loop-state.md`.
  *
  * `cli-backed` used to mean "the `enforcerRef` path exists on disk"
  * (`backing-detector.ts`). It did not mean "the enforcer runs". Ten catalog

package/dist/services/audit/enforcers/active-skill-resolver.d.ts

@@ -32,10 +32,8 @@ export interface ActiveSkillResolution {
      * Mode token recorded on the canonical lease (e.g. `full-auto`,
      * `assisted`, `strict`, `24h`). Normalized on read: a legacy
      * on-disk `'swarm'` surfaces as `'full-auto'` (slice
-     * 2026-09-09-mode-consolidation). `null` when the source is not
      * `canonical` (the legacy `active-skill-*.json` files do not
      * surface a mode field, and the `env` / `none` cases are test
-     * overrides). Slice 2026-08-04-rid-005 surfaced this so the
      * statusline can render the orchestrator's mode alongside the
      * active leaf role.
      */

package/dist/services/audit/enforcers/active-skill-resolver.js

@@ -65,7 +65,6 @@ export function resolveActiveSkillForCaller(projectRoot, opts) {
     // ad-hoc / pre-migration projects) we fall through to the legacy
     // walk below.
     // `getSessionDir` refuses an unsafe session id by throwing (slice
-    // 2026-09-14-getsessiondir-guard). This function's contract is the
     // resolution order's "graceful degradation — never throws", so an unsafe
     // id degrades to the same `source: 'none'` shape an absent session dir
     // produces, exactly as it did before that guard existed. Without this,
@@ -94,7 +93,6 @@ export function resolveActiveSkillForCaller(projectRoot, opts) {
         if (typeof lease.skill !== 'string' || lease.skill.length === 0)
             continue;
         // When a callerId is supplied, restrict the walk to that
-        // caller's lease. Slice 2026-08-04-rid-005 surfaces this for the
         // statusline read so two concurrent sessions bound to the same
         // project session do not see each other's skill.
         if (typeof opts?.callerId === 'string' &&

package/dist/services/audit/red-line-audit-input.d.ts

@@ -0,0 +1,11 @@
+import type { RedLineAudit } from './types.js';
+/** The refusal the CLI reports as `AUDIT_ARTIFACT_INPUT_INVALID`. */
+export declare class RedLineAuditInputError extends Error {
+    constructor(problem: string);
+}
+/**
+ * Parse and validate a RedLineAudit JSON document. Throws
+ * `RedLineAuditInputError` naming the first field that failed; returns the
+ * parsed value typed as `RedLineAudit` once every field holds.
+ */
+export declare function parseRedLineAuditInput(text: string): RedLineAudit;