peaks-loop 4.1.0 → 4.1.2

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;

package/dist/services/audit/red-line-audit-input.js

@@ -0,0 +1,103 @@
+// src/services/audit/red-line-audit-input.ts
+//
+// Validates the JSON a caller hands to `peaks audit artifact write --kind
+// decision`.
+//
+// The input crosses a system boundary — it is a file from disk, usually an
+// archived scan — and the writer it feeds renders whatever it is given into a
+// memory record with no further checks. Without a validator here, a truncated
+// or reshaped JSON would land in `.peaks/memory/audit-decisions/` as if it were
+// a verdict, and the memory index would treat it as one. So the shape is
+// asserted field by field, and every refusal names the field that failed.
+//
+// Why not a schema library: the contract is six fields and two item shapes, all
+// of which already exist as TypeScript types in `./types.js`. A runtime schema
+// would be a second spelling of the same contract, free to drift.
+/** The refusal the CLI reports as `AUDIT_ARTIFACT_INPUT_INVALID`. */
+export class RedLineAuditInputError extends Error {
+    constructor(problem) {
+        super(`decision input is not a RedLineAudit: ${problem}`);
+        this.name = 'RedLineAuditInputError';
+    }
+}
+const COUNT_FIELDS = ['totalRedLines', 'cliBacked', 'partial', 'proseOnly'];
+const ENTRY_FIELDS = ['id', 'rule', 'source', 'backing'];
+const FINDING_FIELDS = ['enforcerId', 'rule', 'severity', 'file', 'detail'];
+const FINDING_SEVERITIES = ['pass', 'warn', 'fail'];
+function asRecord(value, label) {
+    if (typeof value !== 'object' || value === null || Array.isArray(value)) {
+        throw new RedLineAuditInputError(`${label} must be an object`);
+    }
+    return value;
+}
+function requireCounts(audit) {
+    for (const field of COUNT_FIELDS) {
+        const value = audit[field];
+        if (typeof value !== 'number' || !Number.isInteger(value) || value < 0) {
+            throw new RedLineAuditInputError(`${field} must be a non-negative integer`);
+        }
+    }
+}
+function requireEntries(audit) {
+    const entries = audit['audit'];
+    if (!Array.isArray(entries)) {
+        throw new RedLineAuditInputError('audit must be an array of red-line entries');
+    }
+    for (const entry of entries) {
+        const record = asRecord(entry, 'audit[]');
+        for (const field of ENTRY_FIELDS) {
+            if (typeof record[field] !== 'string') {
+                throw new RedLineAuditInputError(`audit[].${field} must be a string`);
+            }
+        }
+        const ref = record['enforcerRef'];
+        if (typeof ref !== 'string' && ref !== null) {
+            throw new RedLineAuditInputError('audit[].enforcerRef must be a string or null');
+        }
+    }
+}
+function requireFindings(audit) {
+    const findings = audit['enforcerFindings'];
+    if (!Array.isArray(findings)) {
+        throw new RedLineAuditInputError('enforcerFindings must be an array');
+    }
+    for (const finding of findings) {
+        const record = asRecord(finding, 'enforcerFindings[]');
+        for (const field of FINDING_FIELDS) {
+            if (typeof record[field] !== 'string') {
+                throw new RedLineAuditInputError(`enforcerFindings[].${field} must be a string`);
+            }
+        }
+        const severity = record['severity'];
+        if (typeof severity !== 'string' ||
+            !FINDING_SEVERITIES.includes(severity)) {
+            throw new RedLineAuditInputError(`enforcerFindings[].severity must be one of ${FINDING_SEVERITIES.join(' | ')}`);
+        }
+    }
+}
+/**
+ * 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 function parseRedLineAuditInput(text) {
+    let parsed;
+    try {
+        parsed = JSON.parse(text);
+    }
+    catch (error) {
+        throw new RedLineAuditInputError(`invalid JSON (${String(error)})`);
+    }
+    const audit = asRecord(parsed, 'the document');
+    requireCounts(audit);
+    requireEntries(audit);
+    requireFindings(audit);
+    return {
+        totalRedLines: Number(audit['totalRedLines']),
+        cliBacked: Number(audit['cliBacked']),
+        partial: Number(audit['partial']),
+        proseOnly: Number(audit['proseOnly']),
+        audit: audit['audit'].map((entry) => entry),
+        enforcerFindings: audit['enforcerFindings'].map((finding) => finding)
+    };
+}

package/dist/services/audit/red-line-catalog-p2-a-bee-runtime.d.ts

@@ -1,6 +1,5 @@
 /**
  * P2-a red lines that bind a specific peaks-* bee: the prose-only-sweep
- * entries (slice 2026-07-29-rid-prose-only-sweep-001 … -010) that make a
  * SKILL.md declare its own runtime contract. Hoisted verbatim out of
  * `red-line-catalog-p2-a.ts` by the b1 file-size campaign — no `id`, `rule`,
  * `markers`, `phrases` or `enforcerRef` value was edited, and the names are

package/dist/services/audit/red-line-catalog-p2-a.js

@@ -27,40 +27,33 @@ export const RED_LINE_CATALOG_P2_A = [
     PEAKS_DOCTOR_SKILL_ACKNOWLEDGED,
     CATALOG_TOTAL_LE_45,
     CATALOG_PROSE_ONLY_RATIO,
-    // Slice 2026-07-29-rid-prose-only-sweep-001: close the first
     // discovered prose-only line. peaks-prd-skill-md-56 was a
     // "MANDATORY first action" marker on a "Skill presence" heading
     // in skills/bee/* SKILL.md. The MANDATORY marker + the heading
     // are now enforced by lint-skill-presence-mandatory.ts.
     SKILL_PRESENCE_MANDATORY,
-    // Slice 2026-07-29-rid-prose-only-sweep-002: close two more
     // peaks-prd discovered lines (md-292, md-301) with one
     // enforcer. The enforcer pattern-scans the source-snapshot
     // placement guidance + prohibited-paths list.
     PRD_SOURCE_SNAPSHOT_PLACEMENT,
-    // Slice 2026-07-29-rid-prose-only-sweep-004: close three
     // peaks-prd discovered lines (md-99 / md-166 / md-193) with
     // one enforcer. The handoff contract requires preserved
     // behavior, step 5.5, and transition verification gates.
     PRD_ARTIFACT_HANDOFF,
-    // Slice 2026-07-29-rid-prose-only-sweep-005: close three
     // peaks-rd discovered lines (md-121 / md-127 / md-162) with
     // two enforcers (handoff + coverage discipline).
     RD_HANDOFF_CONTRACT,
     RD_COVERAGE_DISCIPLINE,
-    // Slice 2026-07-29-rid-prose-only-sweep-006: close four
     // peaks-qa discovered lines (md-26 gateguard + md-113
     // transition gates + md-165 playwright + md-201 openspec).
     QA_GATEGUARD_PREFLIGHT,
     QA_RUNTIME_CONTRACT,
-    // Slice 2026-07-29-rid-prose-only-sweep-007: close six more
     // discovered lines (3 peaks-ui + 2 peaks-txt + 1
     // peaks-perf-audit) with four enforcers.
     PEAKS_UI_SUPERPOWERS_CHAIN,
     PEAKS_UI_INVOLVEMENT,
     PEAKS_TXT_UPSTREAM,
     PEAKS_PERF_AUDIT_SCOPE,
-    // Slice 2026-07-29-rid-prose-only-sweep-008: close six more
     // discovered lines (2 peaks-rd + 1 peaks-sc + 1 peaks-txt +
     // 1 peaks-ui + 1 peaks-ui) with four enforcers in
     // lint-bee-runtime-contract.ts.
@@ -68,12 +61,10 @@ export const RED_LINE_CATALOG_P2_A = [
     PEAKS_UI_TRANSITION_GATES,
     PEAKS_SC_TRANSITION_GATES,
     PEAKS_TXT_RUNTIME_CONTRACT,
-    // Slice 2026-07-29-rid-prose-only-sweep-009: close 13 of the
     // remaining 33 discovered lines (all peaks-code) with one
     // enforcer that checks the peaks-code runbook section-marker
     // skeleton. Single catalog entry; multi-marker enforcer.
     PEAKS_CODE_RUNTIME_CONTRACT,
-    // Slice 2026-07-29-rid-prose-only-sweep-010: 8 of the
     // remaining 22 discovered lines (peaks-audit x4,
     // peaks-content x2, peaks-ide x2) closed with 6 enforcers
     // in one file.

package/dist/services/audit/types.d.ts

@@ -1,8 +1,6 @@
 /**
  * Red-line audit framework — types.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §5
- * PRD:  .peaks/_runtime/2026-06-11-session-f0312d/prd/requests/001-001-l2-1-redlines-audit.md
  * OpenSpec: openspec/changes/2026-06-11-l2-1-redlines-audit/
  *
  * The audit framework classifies MANDATORY / BLOCKING / MUST NOT / RED LINE

package/dist/services/audit/types.js

@@ -1,8 +1,6 @@
 /**
  * Red-line audit framework — types.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §5
- * PRD:  .peaks/_runtime/2026-06-11-session-f0312d/prd/requests/001-001-l2-1-redlines-audit.md
  * OpenSpec: openspec/changes/2026-06-11-l2-1-redlines-audit/
  *
  * The audit framework classifies MANDATORY / BLOCKING / MUST NOT / RED LINE

package/dist/services/audit-independent/perf-audit-service.d.ts

@@ -103,9 +103,7 @@ export declare function detectPerfAudit(input: {
     readonly sessionId: string;
     /**
      * The slice whose capsule this run audits. Slice
-     * `2026-09-14-prd-capsule-rid-scoping` put the rid in the capsule's
      * filename, so a caller that knows it must pass it or the probe resolves
-     * only the pre-rid-scoping bare name. Both callers pass it:
      * `runPerfAudit` always did, and `peaks perf-audit detect` forwards its
      * long-standing `--rid` flag as of the post-verification repair round.
      */

package/dist/services/audit-independent/security-audit-service.d.ts

@@ -2,7 +2,6 @@
  * peaks-security-audit service — independent security audit skill driver.
  *
  * Slice v2.12.0 (Group A, Tier 2). The skill is decoupled from the
- * peaks-rd 5-way fan-out (per PRD AC-2.x) and lives as a standalone
  * CLI surface: `peaks security-audit run --rid <id> ...`.
  *
  * The service owns:
@@ -19,7 +18,6 @@
  * is the pure I/O + validation core; the LLM is the judgement core.
  *
  * Why a service (not inlined in the CLI):
- *   - Unit-testable in isolation (6 case per PRD AC-2.8)
  *   - The 5-state detector mirrors the ecc-bridge detectEcc pattern
  *     (slice 7 Group D), keeping the surface uniform
  *   - Future migration to peaks sub-agent dispatch (peaks-rd main
@@ -37,7 +35,6 @@
  *
  *   - `ready`              — handoff + template + project all present
  *   - `handoff-missing`    — this slice's `.peaks/_runtime/<sid>/prd/handoff-<rid>.md`
- *                        (or the pre-rid-scoping `prd/handoff.md`) absent
  *   - `template-missing`   — `.peaks/project-scan/security-template.md` absent
  *   - `dispatch-failed`    — parent LLM threw before returning the audit envelope
  *   - `envelope-malformed` — parent LLM returned a value that fails `isSecurityAuditEnvelope`
@@ -110,9 +107,7 @@ export declare function detectSecurityAudit(input: {
     readonly sessionId: string;
     /**
      * The slice whose capsule this run audits. Slice
-     * `2026-09-14-prd-capsule-rid-scoping` put the rid in the capsule's
      * filename, so a caller that knows it must pass it or the probe resolves
-     * only the pre-rid-scoping bare name. Both callers pass it:
      * `runSecurityAudit` always did, and `peaks security-audit detect` forwards
      * its long-standing `--rid` flag as of the post-verification repair round.
      */

package/dist/services/audit-independent/security-audit-service.js

@@ -2,7 +2,6 @@
  * peaks-security-audit service — independent security audit skill driver.
  *
  * Slice v2.12.0 (Group A, Tier 2). The skill is decoupled from the
- * peaks-rd 5-way fan-out (per PRD AC-2.x) and lives as a standalone
  * CLI surface: `peaks security-audit run --rid <id> ...`.
  *
  * The service owns:
@@ -19,7 +18,6 @@
  * is the pure I/O + validation core; the LLM is the judgement core.
  *
  * Why a service (not inlined in the CLI):
- *   - Unit-testable in isolation (6 case per PRD AC-2.8)
  *   - The 5-state detector mirrors the ecc-bridge detectEcc pattern
  *     (slice 7 Group D), keeping the surface uniform
  *   - Future migration to peaks sub-agent dispatch (peaks-rd main

package/dist/services/autonomous-swarm/autonomous-swarm-service.d.ts

@@ -1,5 +1,4 @@
 /**
- * autonomous-swarm-service — slice rid-014.
  *
  * Purpose:
  *   Build a dry-run-only autonomous RD swarm planner that turns a
@@ -8,12 +7,8 @@
  *   checkpoint queue, worker-queue placeholders (no spawn), evidence
  *   requirements, and resume instructions.
  *
- * Reuse (per rid-014 plan §1):
  *   - `validateChangeId` + `planArtifactPath` + `buildWorkspaceUnavailable`
- *     from `src/services/openspec/artifact-boundary.ts` (rid-009).
- *   - `getTechStatus` from `src/services/tech/tech-service.ts` (rid-012).
  *   - `planRdSwarmGraph` shape from `src/services/rd-swarm/rd-swarm-service.ts`
- *     (rid-013) — composed as the workerQueue feed.
  *
  * Style:
  *   - Named function exports — matches `rd-swarm-service.ts` + `artifact-boundary.ts`.

package/dist/services/autonomous-swarm/autonomous-swarm-service.js

@@ -1,5 +1,4 @@
 /**
- * autonomous-swarm-service — slice rid-014.
  *
  * Purpose:
  *   Build a dry-run-only autonomous RD swarm planner that turns a
@@ -8,12 +7,8 @@
  *   checkpoint queue, worker-queue placeholders (no spawn), evidence
  *   requirements, and resume instructions.
  *
- * Reuse (per rid-014 plan §1):
  *   - `validateChangeId` + `planArtifactPath` + `buildWorkspaceUnavailable`
- *     from `src/services/openspec/artifact-boundary.ts` (rid-009).
- *   - `getTechStatus` from `src/services/tech/tech-service.ts` (rid-012).
  *   - `planRdSwarmGraph` shape from `src/services/rd-swarm/rd-swarm-service.ts`
- *     (rid-013) — composed as the workerQueue feed.
  *
  * Style:
  *   - Named function exports — matches `rd-swarm-service.ts` + `artifact-boundary.ts`.

package/dist/services/best-practice/language-detector.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-12 best-practice-scan — language detector.
  *
  * Detects the project's primary language from well-known marker files.
  * Returns one of: typescript | javascript | python | go | java | unknown.

package/dist/services/best-practice/output-formatter.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-12 best-practice-scan — output formatter.
  *
  * Renders the 8-row business-decision comparison table (per spec §5) plus
  * the 3-line footer (spec §5 footer + §7 ⚠️ gate). The formatter is the

package/dist/services/best-practice/scan-orchestrator.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-08-12 best-practice-scan — scan orchestrator.
  *
  * Resolves a doc-fragment set for a (intent, language) query via the
  * following priority chain:

package/dist/services/capability-audit-service/types.d.ts

@@ -22,9 +22,7 @@ export type AuditFindingCode =
 /** The observed journey set is not the frozen P0 set. */
 'OBSERVATION_INCOMPLETE'
 /** The frozen baseline's own row set is not the P0 set. */
- | 'BASELINE_ROW_SET_INVALID'
-/** A frozen `sourceFiles` entry no longer exists on disk. */
- | 'SOURCE_FILE_MISSING';
+ | 'BASELINE_ROW_SET_INVALID' | 'SOURCE_FILE_MISSING';
 export interface AuditFinding {
     readonly code: AuditFindingCode;
     readonly journeyId: JourneyId;

package/dist/services/capability-guard-runner/contracts/J08.js

@@ -1,4 +1,4 @@
-import Database from 'better-sqlite3';
+import { openSqlite } from '../../sqlite/sqlite-driver.js';
 import { CrystallizationIntegrityError, CrystallizationService, CrystallizationTaskStateSchema } from '../../crystallization/crystallization-service.js';
 import { combineProbes, fail, missingSourceFiles, pass, probe, requireBaselineRow } from './_shared.js';
 /** Test doubles: `assertReady` never reaches any of them. */
@@ -13,7 +13,7 @@ function probeService() {
         insertLoopRelease: noop,
         insertLoopBeeRelation: noop
     };
-    return new CrystallizationService(new Database(':memory:'), opts);
+    return new CrystallizationService(openSqlite(':memory:'), opts);
 }
 /**
  * Behavioural probe of the crystallization gate.

package/dist/services/changeset/changeset-check-service.d.ts

@@ -1,13 +1,10 @@
 /**
- * rid-011 — peaks changeset check hard gate (Phase 4 slice 2).
  *
  * Module path: src/services/changeset/changeset-check-service.ts
  * Mirror of publish.yml gate-changeset step (lines 220-243). Hard-gate,
  * no warning mode, no opt-out. Auto-wired as step 0 of `peaks release
  * canary` and `peaks release hotfix` BEFORE the rid-010 precheck guard.
  *
- * Decoupling note: rid-010 Layer C (`runChangesetStaged`) is ad-hoc
- * precheck (warning by default, --strict upgrade); rid-011 hard gate is
  * unconditional. Both filters inspect `.changeset/*.md` (excluding
  * README.md) but with different policy semantics.
  */

package/dist/services/changeset/changeset-check-service.js

@@ -1,13 +1,10 @@
 /**
- * rid-011 — peaks changeset check hard gate (Phase 4 slice 2).
  *
  * Module path: src/services/changeset/changeset-check-service.ts
  * Mirror of publish.yml gate-changeset step (lines 220-243). Hard-gate,
  * no warning mode, no opt-out. Auto-wired as step 0 of `peaks release
  * canary` and `peaks release hotfix` BEFORE the rid-010 precheck guard.
  *
- * Decoupling note: rid-010 Layer C (`runChangesetStaged`) is ad-hoc
- * precheck (warning by default, --strict upgrade); rid-011 hard gate is
  * unconditional. Both filters inspect `.changeset/*.md` (excluding
  * README.md) but with different policy semantics.
  */

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

@@ -1,7 +1,6 @@
 /**
  * L1a task classification service.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Hybrid mechanism: signal-based heuristic + user override + audit log.
  *

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

@@ -1,7 +1,6 @@
 /**
  * L1a task classification service.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Hybrid mechanism: signal-based heuristic + user override + audit log.
  *

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

@@ -1,7 +1,6 @@
 /**
  * L1a task classification — types and per-level gate sets.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Five task levels: typo / bug / feature / refactor / migration. Each
  * level has a gate set (the "配套 gate set" — L1b) that the slice

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

@@ -1,7 +1,6 @@
 /**
  * L1a task classification — types and per-level gate sets.
  *
- * Spec: docs/superpowers/specs/2026-06-11-peaks-loop-l1-l2-l3-redesign.md §4
  *
  * Five task levels: typo / bug / feature / refactor / migration. Each
  * level has a gate set (the "配套 gate set" — L1b) that the slice

package/dist/services/code/auto-compact-lifecycle.d.ts

@@ -1,6 +1,4 @@
 /**
- * Auto-compact lifecycle telemetry (v2.13.0 AC-2 + AC-3 + AC-4,
- * slice 2026-08-01-compact-lifecycle Task 5).
  *
  * Extracted from `auto-compact-orchestrator.ts` to keep that file under
  * the 800 LOC cap (mechanical verbatim move). Publishes the stages a
@@ -18,14 +16,12 @@ import { type CompactLifecycleRecord, type CompactLifecycleStage } from '../comp
  * `CompactLifecyclePublisher` and `settleOpenLifecycleRun` for why.
  *
  * `armed` is the honest resting stage for a dispatch that only
- * REGISTERED a trigger (slice 2026-09-12-compact-band-policy, defect B)
  * — see `resolveDispatchedStage`.
  */
 type ObservableDispatchStage = Extract<CompactLifecycleStage, 'queued' | 'preparing' | 'compacting' | 'armed'>;
 /** Stage a failure is attributed to (mirrors the store's `failedAt` domain). */
 type FailableStage = Exclude<CompactLifecycleStage, 'failed' | 'completed'>;
 /**
- * Slice 2026-09-12-compact-band-policy (defect B): which stage a
  * *successful* dispatch can honestly claim.
  *
  * A dispatch is only evidence that a compact is IN FLIGHT when the
@@ -52,7 +48,6 @@ export declare function resolveDispatchedStage(input: {
  */
 export declare function newCompactRunId(now: Date): string;
 /**
- * rid `2026-09-14-compact-dispatch-backoff`: the compact run this session has
  * already DISPATCHED and whose outcome is still unknown — the backoff token.
  *
  * WHY A BACKOFF IS NEEDED AT ALL. Once the ratio crosses the auto-fire
@@ -111,7 +106,6 @@ export declare function readOpenDispatchRun(input: {
     readonly sessionId: string;
 }): OpenDispatchRunRead;
 /**
- * Slice 2026-08-01-compact-lifecycle (Task 5): the local transition
  * builder. Carries `runId`, `triggerRatio` and `redLine` forward from
  * the run that opened, and remembers the prior stage so a failure can
  * name the stage it died in.
@@ -144,7 +138,6 @@ export declare class CompactLifecyclePublisher {
      *
      * `at` overrides that attribution for the case where the failure
      * happened INSIDE a phase that is only named after its outcome
-     * (slice 2026-09-12-compact-band-policy): the dispatch call is the
      * compacting phase even though the resting stage is now chosen from
      * the pathway the dispatch returned. `failedAt` names the phase the
      * attempt died in — it is not a published heartbeat.
@@ -166,7 +159,6 @@ export declare class CompactLifecyclePublisher {
  */
 export declare function summarizeLifecycleError(error: unknown): string;
 /**
- * Slice 2026-08-01-compact-lifecycle (Task 5, Step 4): close out an
  * open compact run using a REAL measurement.
  *
  * This is the integration with the actual post-compact detection path.
@@ -187,7 +179,6 @@ export declare function summarizeLifecycleError(error: unknown): string;
  *     compact has not landed, so the run stays open.
  *
  * Returns the settled record, or `null` when nothing settled. Slice
- * 2026-09-13-auto-compact-trigger-ownership: the caller needs the settled
  * `afterRatio` to append the "observed compaction point" row that makes the
  * intent-vs-observed gap readable after a real session. The return value is
  * telemetry only — callers that ignore it are unaffected.
@@ -221,7 +212,6 @@ export declare function settleOpenLifecycleRun(input: {
     readonly lifecycleWritten: boolean;
 } | null;
 /**
- * rid `2026-09-13-compact-event-settle`: close out an open compact run because
  * the HARNESS said one completed — `PostCompact` — rather than because a later
  * probe noticed the ratio had fallen.
  *
@@ -299,7 +289,6 @@ export declare function settleOpenLifecycleRunOnCompactEvent(input: {
     readonly lifecycleWritten: boolean;
 } | null;
 /**
- * rid `2026-09-13-compact-event-settle` (repair R1): supply the measurement a
  * harness-settled run was left owing.
  *
  * The function above deliberately refuses to launder a post-compact reading

package/dist/services/code/auto-compact-lifecycle.js

@@ -1,6 +1,4 @@
 /**
- * Auto-compact lifecycle telemetry (v2.13.0 AC-2 + AC-3 + AC-4,
- * slice 2026-08-01-compact-lifecycle Task 5).
  *
  * Extracted from `auto-compact-orchestrator.ts` to keep that file under
  * the 800 LOC cap (mechanical verbatim move). Publishes the stages a
@@ -23,7 +21,6 @@ import { tryGetSessionDir } from '../session/getSessionDir.js';
  */
 const COLLAPSED_ERROR_MAX_CHARS = 160;
 /**
- * Slice 2026-09-12-compact-band-policy (defect B): which stage a
  * *successful* dispatch can honestly claim.
  *
  * A dispatch is only evidence that a compact is IN FLIGHT when the
@@ -55,7 +52,6 @@ export function newCompactRunId(now) {
     return `compact-${stamp}-${suffix}`;
 }
 /**
- * Slice 2026-08-01-compact-lifecycle (Task 5): read an open compact
  * record ignoring staleness.
  *
  * The lifecycle store classifies an active record as `stalled` after a
@@ -115,7 +111,6 @@ export function readOpenDispatchRun(input) {
     };
 }
 /**
- * Slice 2026-08-01-compact-lifecycle (Task 5): the local transition
  * builder. Carries `runId`, `triggerRatio` and `redLine` forward from
  * the run that opened, and remembers the prior stage so a failure can
  * name the stage it died in.
@@ -152,7 +147,6 @@ export class CompactLifecyclePublisher {
      *
      * `at` overrides that attribution for the case where the failure
      * happened INSIDE a phase that is only named after its outcome
-     * (slice 2026-09-12-compact-band-policy): the dispatch call is the
      * compacting phase even though the resting stage is now chosen from
      * the pathway the dispatch returned. `failedAt` names the phase the
      * attempt died in — it is not a published heartbeat.
@@ -223,7 +217,6 @@ export function summarizeLifecycleError(error) {
             : collapsed;
 }
 /**
- * Slice 2026-08-01-compact-lifecycle (Task 5, Step 4): close out an
  * open compact run using a REAL measurement.
  *
  * This is the integration with the actual post-compact detection path.
@@ -244,7 +237,6 @@ export function summarizeLifecycleError(error) {
  *     compact has not landed, so the run stays open.
  *
  * Returns the settled record, or `null` when nothing settled. Slice
- * 2026-09-13-auto-compact-trigger-ownership: the caller needs the settled
  * `afterRatio` to append the "observed compaction point" row that makes the
  * intent-vs-observed gap readable after a real session. The return value is
  * telemetry only — callers that ignore it are unaffected.
@@ -340,7 +332,6 @@ function emitLifecycleStage(prior, input, stage, withAfterRatio) {
     return true;
 }
 /**
- * rid `2026-09-13-compact-event-settle`: close out an open compact run because
  * the HARNESS said one completed — `PostCompact` — rather than because a later
  * probe noticed the ratio had fallen.
  *
@@ -447,7 +438,6 @@ export function settleOpenLifecycleRunOnCompactEvent(input) {
     return { ...facts, lifecycleWritten: true };
 }
 /**
- * rid `2026-09-13-compact-event-settle` (repair R1): supply the measurement a
  * harness-settled run was left owing.
  *
  * The function above deliberately refuses to launder a post-compact reading

package/dist/services/code/auto-compact-modes.d.ts

@@ -1,12 +1,10 @@
 /**
- * Slice 2026-07-28 — auto-compact mode table for 24h long-run awareness.
  *
  * The default `'standard'` mode preserves the v2.13.0 zero-pause contract
  * thresholds (autoFire=0.80, preCompact=0.85, redLine=0.95). The `'partial'`
  * mode fires earlier for 24h long-run scenarios where the user has explicitly
  * opted into higher compaction cadence via `peaks session 24h-mode`.
  *
- * Slice 2026-07-29-context-evaluation-accuracy Part 22: a new
  * `autoFire` tier is added between soft-warn and preCompact. peaks-loop
  * preempts and runs `peaks code auto-compact` itself when
  * context crosses `autoFire`; the LLM is NOT asked to "decide"
@@ -32,7 +30,6 @@ export declare function isValidMode(value: string): value is AutoCompactMode;
  * Derived from `AUTO_COMPACT_THRESHOLDS` rather than hand-written. Diagnosis
  * 2026-09-15 (C1) found this string advertising `0.85/0.95` for `standard`
  * while the table had auto-fired at `0.80` since slice
- * 2026-07-29-context-evaluation-accuracy added the `autoFire` tier — the
  * description named only the two thresholds that were left over from the
  * v2.13.0 contract, and skipped the one that actually fires. Reading the
  * numbers out of the table makes that drift unrepresentable.