peaks-loop 4.1.0 → 4.1.2

package/dist/services/context/codegraph-unavailable-block.js

@@ -0,0 +1,77 @@
+// src/services/context/codegraph-unavailable-block.ts
+//
+// The `## Codegraph structure` block a dispatch carries when the codegraph index
+// could not be read, and the normalizer that decides which block that is.
+//
+// WHY THIS IS NOT A SECOND FIELD NEXT TO `codegraphBlock`. The production defect
+// was
+//
+//     codegraphBlock = preflight.available ? preflight.block : null;
+//
+// `buildCodegraphPreflightBlock` has ALWAYS reported WHY the read failed — its
+// `{ available: false, note }` arm carries the upstream stderr/stdout summary —
+// and that note was dropped on the floor, so every degraded RD dispatch injected
+//
+//   ## Codegraph structure
+//
+//   codegraph unavailable — proceeding on project-scan only.
+//
+// a line whose only difference from "index read fine" is the word "unavailable".
+// Measured live cause on this machine: `unable to open database file` (the wasm
+// backend cannot open the WAL-mode `.codegraph/codegraph.db`), which never reached
+// a single dispatch record.
+//
+// So the reason travels IN the same value as the block: `preflight.available ?
+// preflight.block : preflight.note` is one expression, and every failure branch of
+// the preflight produces a non-empty note. A future edit cannot drop the reason
+// without dropping the block too, which is loud instead of silent.
+//
+// The block shape is unchanged — a `## Codegraph structure` heading, the same
+// "proceeding on project-scan only" sentence — so nothing downstream re-learns
+// where to look. Only the reason is new.
+/** Opens every codegraph block; the discriminator between a block and a bare note. */
+export const CODEGRAPH_BLOCK_HEADING = '## Codegraph structure';
+/** The sentence shared by the reasonless fallback and the reason-bearing block. */
+export const CODEGRAPH_PROCEEDING = 'codegraph unavailable — proceeding on project-scan only.';
+/**
+ * The sentence the TRULY reasonless fallback renders.
+ *
+ * Load-bearing, not decoration: the pre-fix block said only "codegraph
+ * unavailable", which is byte-for-byte what a reader saw whether upstream printed
+ * `unable to open database file` or printed nothing at all. Naming the missing
+ * reason makes "no reason exists" a claim the reader can check, and leaves "a
+ * reason exists but the dispatch dropped it" with nowhere to hide.
+ */
+export const CODEGRAPH_REASON_MISSING = 'No failure reason was obtained from the codegraph preflight.';
+/** Opens the reason-bearing variant; asserted absent whenever no reason exists. */
+export const CODEGRAPH_REASON_SENTENCE = 'Reason reported by the codegraph preflight: ';
+/**
+ * Render the block for an unavailable codegraph. `note` is the preflight's own
+ * failure note, quoted rather than paraphrased — the point is that the next
+ * reader sees `unable to open database file` instead of re-deriving it.
+ *
+ * The quote is whitespace-collapsed to one line so a multi-line upstream summary
+ * cannot forge a markdown heading further down the prompt; it is otherwise
+ * verbatim, upstream's own SGR color included. Rewriting the failure text here
+ * would put peaks-loop's words where the cause belongs.
+ */
+export function renderCodegraphUnavailableBlock(note) {
+    const reason = typeof note === 'string' ? note.replace(/\s+/g, ' ').trim() : '';
+    const body = reason.length === 0 ? CODEGRAPH_REASON_MISSING : `${CODEGRAPH_REASON_SENTENCE}${reason}`;
+    return `${CODEGRAPH_BLOCK_HEADING}\n\n${CODEGRAPH_PROCEEDING} ${body}\n`;
+}
+/**
+ * The ONE place a `codegraphBlock` value becomes text.
+ *
+ * - `null` (preflight ran, no reason obtained) → the explicit fallback.
+ * - a string already opening with the heading → the pre-composed structure
+ *   block, verbatim.
+ * - any other string → an unavailable block quoting it as the reported reason.
+ *   `buildCodegraphPreflightBlock`'s `{ available: false, note }` arm is the only
+ *   production producer of that shape.
+ */
+export function resolveCodegraphBlock(value) {
+    if (value === null || value.trim().length === 0)
+        return renderCodegraphUnavailableBlock(null);
+    return value.startsWith(CODEGRAPH_BLOCK_HEADING) ? value : renderCodegraphUnavailableBlock(value);
+}

package/dist/services/context/context-audit-hint.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-10-three-fixes (Slice 2) — proactive context-consumer hint.
  *
  * `peaks code context-audit` (Slice A, same day) already reports WHAT fills
  * the window, but only when someone remembers to run it. The Step 0.8

package/dist/services/context/context-audit-hint.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-10-three-fixes (Slice 2) — proactive context-consumer hint.
  *
  * `peaks code context-audit` (Slice A, same day) already reports WHAT fills
  * the window, but only when someone remembers to run it. The Step 0.8

package/dist/services/context/context-audit.d.ts

@@ -1,7 +1,6 @@
 /**
  * `peaks code context-audit` — what actually fills the orchestrator's window.
  *
- * Slice 2026-09-10-context-audit-and-discipline (Slice A).
  *
  * Why this exists: `peaks code context-now` reports a RATIO only. Nothing
  * reported WHAT occupies the window, so the same 40K-token mistake (dumping a

package/dist/services/context/context-audit.js

@@ -1,7 +1,6 @@
 /**
  * `peaks code context-audit` — what actually fills the orchestrator's window.
  *
- * Slice 2026-09-10-context-audit-and-discipline (Slice A).
  *
  * Why this exists: `peaks code context-now` reports a RATIO only. Nothing
  * reported WHAT occupies the window, so the same 40K-token mistake (dumping a

package/dist/services/context/harness-window-config.d.ts

@@ -1,7 +1,5 @@
 /**
  * Harness auto-compact window ownership
- * (slice 2026-09-13-auto-compact-trigger-ownership, rid
- * 2026-09-13-auto-compact-trigger-ownership).
  *
  * The goal (user's words): *when* to trigger auto-compact must be
  * peaks-loop's decision; *how* to compact stays the harness's capability.
@@ -67,7 +65,6 @@ export declare const HARNESS_WINDOW_SYNC_OPTOUT_VALUE = "off";
 export declare const HARNESS_WINDOW_WRITTEN_KEY = "PEAKS_HARNESS_WINDOW_WRITTEN";
 /**
  * The harness's OWN accepted band for its auto-compact window (E1, rid
- * 2026-09-13-defects-e).
  *
  * THE BAND IS A PROPERTY OF THE KEY, NOT OF peaks-loop. `autoCompactWindow` —
  * and the `CLAUDE_CODE_AUTO_COMPACT_WINDOW` env var that shadows it — is
@@ -366,7 +363,6 @@ export declare function resetHarnessWindow(input: {
  *     value it did not write.
  * The next probe reports `skipped / opted-out` and writes nothing.
  *
- * THE H1 HOME GUARD APPLIES HERE TOO (E4, rid 2026-09-13-defects-e).
  *
  * This function used to exempt itself, on the argument that `--disable` is an
  * explicit instruction and "the location's own file is the only place the

package/dist/services/context/harness-window-config.js

@@ -1,7 +1,5 @@
 /**
  * Harness auto-compact window ownership
- * (slice 2026-09-13-auto-compact-trigger-ownership, rid
- * 2026-09-13-auto-compact-trigger-ownership).
  *
  * The goal (user's words): *when* to trigger auto-compact must be
  * peaks-loop's decision; *how* to compact stays the harness's capability.
@@ -70,7 +68,6 @@ export const HARNESS_WINDOW_SYNC_OPTOUT_VALUE = 'off';
 export const HARNESS_WINDOW_WRITTEN_KEY = 'PEAKS_HARNESS_WINDOW_WRITTEN';
 /**
  * The harness's OWN accepted band for its auto-compact window (E1, rid
- * 2026-09-13-defects-e).
  *
  * THE BAND IS A PROPERTY OF THE KEY, NOT OF peaks-loop. `autoCompactWindow` —
  * and the `CLAUDE_CODE_AUTO_COMPACT_WINDOW` env var that shadows it — is
@@ -555,7 +552,6 @@ export function resetHarnessWindow(input) {
  *     value it did not write.
  * The next probe reports `skipped / opted-out` and writes nothing.
  *
- * THE H1 HOME GUARD APPLIES HERE TOO (E4, rid 2026-09-13-defects-e).
  *
  * This function used to exempt itself, on the argument that `--disable` is an
  * explicit instruction and "the location's own file is the only place the

package/dist/services/context/main-session-monitor.d.ts

@@ -54,7 +54,6 @@ export interface MainSessionEvaluation {
  * for tests and future per-IDE capacity overrides. Defaults to the
  * G9 256K proxy (matches G9 for cognitive continuity).
  *
- * @deprecated Slice 2026-07-02-auto-compact-zero-pause: the
  * 50/75/90 tier thresholds pre-date the v2.13.0 auto-compact
  * design. The authoritative tier table for triggering compaction
  * now lives in `evaluateCompactTrigger` (auto-compact-orchestrator.ts)
@@ -76,7 +75,6 @@ export interface InFlightBatchProbe {
  * declaration (`IdeCompactProfile.compactPathway`) rather than from the
  * IDE's name.
  *
- * Slice 2026-09-12-auto-compact-vendor-neutrality: this decision used to
  * be the inline `ide === 'claude-code' ? 'ide-native' : 'llm-self-compress'`
  * — an IDE identity branch in a module that is otherwise pure, reading the
  * IDE's NAME where the adapter registry holds the CAPABILITY. An IDE that

package/dist/services/context/main-session-monitor.js

@@ -34,7 +34,6 @@ export const MAIN_SESSION_THRESHOLD_RATIOS = {
  * for tests and future per-IDE capacity overrides. Defaults to the
  * G9 256K proxy (matches G9 for cognitive continuity).
  *
- * @deprecated Slice 2026-07-02-auto-compact-zero-pause: the
  * 50/75/90 tier thresholds pre-date the v2.13.0 auto-compact
  * design. The authoritative tier table for triggering compaction
  * now lives in `evaluateCompactTrigger` (auto-compact-orchestrator.ts)
@@ -77,7 +76,6 @@ export function evaluateMainSessionThreshold(promptSize, capacityBytes = CONTEXT
  * declaration (`IdeCompactProfile.compactPathway`) rather than from the
  * IDE's name.
  *
- * Slice 2026-09-12-auto-compact-vendor-neutrality: this decision used to
  * be the inline `ide === 'claude-code' ? 'ide-native' : 'llm-self-compress'`
  * — an IDE identity branch in a module that is otherwise pure, reading the
  * IDE's NAME where the adapter registry holds the CAPABILITY. An IDE that

package/dist/services/context/memory-index-reader.d.ts

@@ -1,6 +1,5 @@
 import type { MemoryIndexEntry } from '../memory/memory-search-service.js';
 /**
- * Slice 2026-09-09-memory-retrieval: the two tiers the orchestrator
  * preflight ranks over.
  *
  * - `hot`  — standing rules / feedback / decisions. Always eligible.
@@ -22,7 +21,6 @@ export declare class MemoryIndexReader {
      */
     loadIfStale(): MemoryIndexEntry[];
     /**
-     * Slice 2026-09-09-memory-retrieval: read the index as tiers.
      *
      * Returns `null` when `.peaks/memory/index.json` is absent or
      * unreadable — the caller distinguishes "no index" from "index with

package/dist/services/context/memory-index-reader.js

@@ -15,7 +15,6 @@ export class MemoryIndexReader {
         return this.loadSnapshot()?.entries ?? [];
     }
     /**
-     * Slice 2026-09-09-memory-retrieval: read the index as tiers.
      *
      * Returns `null` when `.peaks/memory/index.json` is absent or
      * unreadable — the caller distinguishes "no index" from "index with

package/dist/services/context/memory-preflight-config.d.ts

@@ -2,7 +2,6 @@ import type { ProjectPreferences } from '../preferences/preferences-types.js';
 export interface MemoryPreflightConfig {
     readonly enabled: boolean;
     /**
-     * Back-compat (slice 2026-07-22): the original single budget knob.
      * Semantics are unchanged — it is the *token* cap, converted to bytes
      * as `maxTokens * 4` when `maxBytes` is not set. Do NOT drop this key:
      * existing `.peaks/preferences.json` files set it.

package/dist/services/context/memory-preflight-service.d.ts

@@ -12,7 +12,6 @@ export declare class MemoryPreflightService {
     private selectAndCompose;
 }
 /**
- * Slice 2026-09-09-memory-retrieval: the query the dispatch site feeds
  * `fetchBlock`. The bare role ("rd") carries almost no relevance signal,
  * so the first line of the task brief is appended (truncated) to give the
  * fuzzy kernel something to rank against. Pure and fail-soft.

package/dist/services/context/memory-preflight-service.js

@@ -1,9 +1,7 @@
 /**
  * MemoryPreflightService — orchestrator-facing API for the
  * "Orchestrator Memory Preflight" slice (see
- * docs/superpowers/specs/2026-07-22-orchestrator-memory-preflight-design.md).
  *
- * Slice 2026-09-09-memory-retrieval (this revision) makes the preflight
  * task-relevant and tiered:
  *   - selection is ranked against `taskTitle` with the deterministic fuzzy
  *     kernel (no network, no embeddings);
@@ -195,7 +193,6 @@ export class MemoryPreflightService {
     }
 }
 /**
- * Slice 2026-09-09-memory-retrieval: the query the dispatch site feeds
  * `fetchBlock`. The bare role ("rd") carries almost no relevance signal,
  * so the first line of the task brief is appended (truncated) to give the
  * fuzzy kernel something to rank against. Pure and fail-soft.

package/dist/services/context/memory-preflight-support.d.ts

@@ -15,15 +15,10 @@ export interface MemoryPreflightResult {
     reason?: string;
     truncated?: boolean | undefined;
     droppedCount?: number | undefined;
-    /** Slice 2026-09-09: hot items emitted. */
     hotSelected?: number | undefined;
-    /** Slice 2026-09-09: warm items emitted. */
     warmSelected?: number | undefined;
-    /** Slice 2026-09-09: bytes of the emitted block (utf8). */
     bytesEmitted?: number | undefined;
-    /** Slice 2026-09-09: true when ANY budget (items / bytes / time) cut content. */
     budgetTruncated?: boolean | undefined;
-    /** Slice 2026-09-09: true when the soft selection time budget was hit. */
     timedOut?: boolean | undefined;
 }
 export interface RankedEntry {

package/dist/services/context/post-compact-reinjection.d.ts

@@ -1,7 +1,6 @@
 /**
  * Post-compact engineering-state re-injection
  * (rid `2026-09-13-a2-post-compact-reinject`, session
- * `2026-09-12-session-e37ef0`).
  *
  * THE PROBLEM THIS SOLVES
  *

package/dist/services/context/post-compact-reinjection.js

@@ -1,7 +1,6 @@
 /**
  * Post-compact engineering-state re-injection
  * (rid `2026-09-13-a2-post-compact-reinject`, session
- * `2026-09-12-session-e37ef0`).
  *
  * THE PROBLEM THIS SOLVES
  *

package/dist/services/context/summary-view.d.ts

@@ -1,7 +1,6 @@
 /**
  * `--summary` — bounded, additive views of large CLI envelopes.
  *
- * Slice 2026-09-10-context-audit-and-discipline (Slice B, part 1).
  *
  * Rationale (measured, session 2026-09-07-session-245530): dumping a full
  * `peaks memory reindex --json` array four times cost ≈ 160 KB ≈ 40K tokens

package/dist/services/context/summary-view.js

@@ -1,7 +1,6 @@
 /**
  * `--summary` — bounded, additive views of large CLI envelopes.
  *
- * Slice 2026-09-10-context-audit-and-discipline (Slice B, part 1).
  *
  * Rationale (measured, session 2026-09-07-session-245530): dumping a full
  * `peaks memory reindex --json` array four times cost ≈ 160 KB ≈ 40K tokens

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

@@ -1,4 +1,4 @@
-import type Database from 'better-sqlite3';
+import { type SqliteDatabase } from '../sqlite/sqlite-driver.js';
 import { z } from 'zod';
 import { type CrystallizationEvent, type CrystallizationEventInput, type CrystallizationEventStatus, type EvidenceBrief } from './crystallization-types.js';
 import { listCrystallizationEvents } from './crystallization-store.js';
@@ -11,8 +11,8 @@ type LoopBeeRelationZodSchema = {
         parse: (input: unknown) => unknown;
     };
 };
-type InsertLoopReleaseFn = (db: Database.Database, row: unknown) => void;
-type InsertLoopBeeRelationFn = (db: Database.Database, row: unknown) => unknown;
+type InsertLoopReleaseFn = (db: SqliteDatabase, row: unknown) => void;
+type InsertLoopBeeRelationFn = (db: SqliteDatabase, row: unknown) => unknown;
 /**
  * CrystallizationService — spec §5 (post-run crystallization)
  * + §4.5 + §4.7 + §10 RL-2 / RL-3 / RL-7.
@@ -20,25 +20,19 @@ type InsertLoopBeeRelationFn = (db: Database.Database, row: unknown) => unknown;
  * Hard rules enforced at THIS layer (defense in depth; the Zod
  * schemas above and the brief refine guard add the second wall):
  *
- *   - AC-4 / RL-2: a crystallization_event is written only when the
  *     candidate task has `task_status === 'completed'` AND
  *     `gates_passed === true` AND `evidence_collected === true`.
  *     Any pre-run attempt (status !== 'completed') is rejected
  *     with `CRYSTALLIZATION_PRE_RUN`. This is the pre-run block
- *     enforced by AC-4, AC-5, AC-6, AC-15, AC-16, AC-17 of the M5
  *     slice.
- *   - AC-6 / RL-3: writing a (loop_release, main_bee_release,
  *     loop_bee_relation) pair happens in a SINGLE TRANSACTION. The
  *     brief persist on crystallization_event also lives inside
  *     the same transaction (the brief is the durable evidence;
  *     dropping either side would break consistency).
- *   - AC-7 / RL-1: this layer never asks the user to hand-author
  *     JSON / manifest / CLI verb; all inputs are typed payloads
  *     the LLM submits on the user's behalf.
- *   - AC-15 / RL-7: the brief is mandatory; the
  *     `EvidenceBriefSchema.refine` guard rejects partial briefs
  *     at the parse boundary.
- *   - AC-16 / RL-7: the brief has all 4 sections
  *     (what_happened / why_it_matters / what_learned /
  *     what_action). The service throws `BriefSectionError` if the
  *     payload fails the guard.
@@ -162,7 +156,7 @@ export interface CrystallizationOptions {
 export declare class CrystallizationService {
     private readonly db;
     private readonly opts;
-    constructor(db: Database.Database, opts: CrystallizationOptions);
+    constructor(db: SqliteDatabase, opts: CrystallizationOptions);
     /**
      * Read a CrystallizationEvent by id.
      */
@@ -216,7 +210,7 @@ export declare class CrystallizationService {
     /**
      * Run the post-run crystallization flow.
      *
-     * Steps (all in ONE better-sqlite3 transaction, atomic):
+     * Steps (all in ONE transaction through the sqlite seam, atomic):
      *
      *   1. Pre-run gate (task must be completed / gates_passed /
      *      evidence_collected).

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

@@ -1,3 +1,4 @@
+import { transaction } from '../sqlite/sqlite-driver.js';
 import { z, ZodError } from 'zod';
 import { CrystallizationEventSchema, EvidenceBriefSchema } from './crystallization-types.js';
 import { BriefSectionError } from './evidence-brief-builder.js';
@@ -9,25 +10,19 @@ import { CRYSTALLIZATION_SCHEMA_VERSION, ensureCrystallizationEventTable, getCry
  * Hard rules enforced at THIS layer (defense in depth; the Zod
  * schemas above and the brief refine guard add the second wall):
  *
- *   - AC-4 / RL-2: a crystallization_event is written only when the
  *     candidate task has `task_status === 'completed'` AND
  *     `gates_passed === true` AND `evidence_collected === true`.
  *     Any pre-run attempt (status !== 'completed') is rejected
  *     with `CRYSTALLIZATION_PRE_RUN`. This is the pre-run block
- *     enforced by AC-4, AC-5, AC-6, AC-15, AC-16, AC-17 of the M5
  *     slice.
- *   - AC-6 / RL-3: writing a (loop_release, main_bee_release,
  *     loop_bee_relation) pair happens in a SINGLE TRANSACTION. The
  *     brief persist on crystallization_event also lives inside
  *     the same transaction (the brief is the durable evidence;
  *     dropping either side would break consistency).
- *   - AC-7 / RL-1: this layer never asks the user to hand-author
  *     JSON / manifest / CLI verb; all inputs are typed payloads
  *     the LLM submits on the user's behalf.
- *   - AC-15 / RL-7: the brief is mandatory; the
  *     `EvidenceBriefSchema.refine` guard rejects partial briefs
  *     at the parse boundary.
- *   - AC-16 / RL-7: the brief has all 4 sections
  *     (what_happened / why_it_matters / what_learned /
  *     what_action). The service throws `BriefSectionError` if the
  *     payload fails the guard.
@@ -47,7 +42,6 @@ import { CRYSTALLIZATION_SCHEMA_VERSION, ensureCrystallizationEventTable, getCry
  *     unexpected SQL errors.
  */
 /* ---------------------------------------------------------------------- */
-/* Pre-run task gate — AC-4 / RL-2                                        */
 /* ---------------------------------------------------------------------- */
 export const CRYSTALLIZATION_TASK_STATUSES = [
     'completed',
@@ -192,7 +186,7 @@ export class CrystallizationService {
     /**
      * Run the post-run crystallization flow.
      *
-     * Steps (all in ONE better-sqlite3 transaction, atomic):
+     * Steps (all in ONE transaction through the sqlite seam, atomic):
      *
      *   1. Pre-run gate (task must be completed / gates_passed /
      *      evidence_collected).
@@ -220,7 +214,6 @@ export class CrystallizationService {
     crystallize(payload) {
         const task = this.assertReady(payload.task);
         // Re-validate the 4-section brief up-front; the schema refines
-        // guard rejects partial briefs. This is the AC-15 / AC-16 / AC-17
         // gate.
         let brief;
         try {
@@ -267,7 +260,7 @@ export class CrystallizationService {
         let beeReleaseId = -1;
         let relationId = -1;
         let eventPersistedId = eventId;
-        const tx = this.db.transaction(() => {
+        const tx = transaction(this.db, () => {
             // 1. Insert loop_release.
             this.opts.insertLoopRelease(this.db, loopRow);
             // 2. Insert bee_release header. The existing
@@ -314,7 +307,6 @@ export class CrystallizationService {
             const relationRow = this.opts.insertLoopBeeRelation(this.db, fullRelation);
             relationId = relationRow.id;
             // 5. Persist the crystallization_event row with the brief inline
-            // (the brief is the durable evidence — AC-17).
             const eventInput = {
                 trigger: payload.trigger,
                 evidence_brief: brief,

package/dist/services/crystallization/crystallization-store.d.ts

@@ -1,4 +1,4 @@
-import type Database from 'better-sqlite3';
+import type { SqliteDatabase } from '../sqlite/sqlite-driver.js';
 import { type CrystallizationEvent, type CrystallizationEventInput, type CrystallizationEventStatus } from './crystallization-types.js';
 /**
  * Low-level SQLite access for the `crystallization_event` table.
@@ -26,7 +26,7 @@ declare const SCHEMA_VERSION: "peaks.crystallization/1";
  * already-open database. Used by tests that build their own DB
  * without the openStateDb pipeline. Idempotent.
  */
-export declare function ensureCrystallizationEventTable(db: Database.Database): void;
+export declare function ensureCrystallizationEventTable(db: SqliteDatabase): void;
 /**
  * Insert a CrystallizationEvent row. The row's `schema_version` is
  * taken from the input (must equal `peaks.crystallization/1`);
@@ -38,15 +38,15 @@ export declare function ensureCrystallizationEventTable(db: Database.Database):
  *
  * Returns the persisted row.
  */
-export declare function insertCrystallizationEvent(db: Database.Database, row: CrystallizationEventInput): CrystallizationEvent;
+export declare function insertCrystallizationEvent(db: SqliteDatabase, row: CrystallizationEventInput): CrystallizationEvent;
 /** Read a single CrystallizationEvent row by id; returns undefined if absent. */
-export declare function getCrystallizationEvent(db: Database.Database, id: string): CrystallizationEvent | undefined;
+export declare function getCrystallizationEvent(db: SqliteDatabase, id: string): CrystallizationEvent | undefined;
 /**
  * List CrystallizationEvent rows. Filter by `lifecycle_status` and/or
  * any of the optional FK pointers. When ALL filters are omitted, lists
  * every event (newest-first by `created_at`).
  */
-export declare function listCrystallizationEvents(db: Database.Database, opts?: {
+export declare function listCrystallizationEvents(db: SqliteDatabase, opts?: {
     lifecycle_status?: CrystallizationEventStatus;
     created_loop_release_id?: string;
     updated_loop_release_id?: string;
@@ -61,7 +61,7 @@ export declare function listCrystallizationEvents(db: Database.Database, opts?:
  * decides whether `stable` requires a user_confirmation_pointer or
  * other evidence (mirroring the evolution-store design).
  */
-export declare function updateCrystallizationEventStatus(db: Database.Database, id: string, next: CrystallizationEventStatus): CrystallizationEvent | undefined;
+export declare function updateCrystallizationEventStatus(db: SqliteDatabase, id: string, next: CrystallizationEventStatus): CrystallizationEvent | undefined;
 /**
  * Test seam: produce a fresh id for a CrystallizationEvent row.
  * Format: `crys-<hex>` (12 hex chars). Matches the Zod

package/dist/services/dispatch/await-batch-helpers.js

@@ -76,7 +76,6 @@ export function createSlotTable(recordPaths, startedAt) {
  *
  * The default readOutcome returns the on-disk `status`. We map
  * a small set of values to the per-dispatch status union.
- * Slice 2026-07-30-nightshift: also capture the optional
  * `outcome` field so the per-IDE note can surface the human
  * reason (e.g. "mock failure at leaf-2"). The `outcome` is read
  * alongside the `status` via `readRecord` and surfaced into
@@ -147,7 +146,6 @@ export function sleepTick(schedule) {
 /**
  * The per-IDE note for one slot.
  *
- * Slice 2026-07-30-nightshift: the per-IDE note construction is
  * rewritten to match the 1.4 dogfood contract:
  *   - claude-code (no notePrefix): note = slot.note (the raw
  *     outcome, or null when done/cancelled)
@@ -175,7 +173,6 @@ function resolveSlotNote(slot, baseNote) {
         // Non-failed terminal slot with a non-null note (e.g. cursor /
         // claude-code `stale` → status=timeout, note='stale'):
         // `${notePrefix} — ${note}` so the human reason is surfaced.
-        // Slice 2026-07-30-nightshift: previously this branch dropped
         // the slot's note entirely (the bare-prefix else swallowed
         // it). The 1.4 dogfood for `stale` flips the contract.
         note = `${baseNote} — ${slot.note}`;

package/dist/services/dispatch/await-batch.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S4 — unified batch
  * awaiter.
  *
  * Pre-S4, `awaitClaudeCodeBatch` and `pollDispatchRecords` were two

package/dist/services/dispatch/await-batch.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S4 — unified batch
  * awaiter.
  *
  * Pre-S4, `awaitClaudeCodeBatch` and `pollDispatchRecords` were two
@@ -114,7 +113,6 @@ function emptyBatchResult(timeoutMs, options) {
     };
 }
 /**
- * The wait budget. S4 (AC-3.2) — surface the clamp. A caller-supplied
  * timeout above the hard cap is reported as `clamped`; the effective
  * budget is what the loop actually waited.
  */
@@ -145,12 +143,10 @@ function resolveSeams(options) {
  *   - `timed-out` — at least one slot is still pending and the
  *     effective budget elapsed
  *   - `clamped` — the caller's `requestedTimeoutMs` exceeded the
- *     hard cap (AC-3.2). The loop still ran the effective budget;
  *     `clamped` takes precedence over `timed-out` because the
  *     caller specifically asked for more than the cap and the
  *     caller needs to know the cap was applied (the timeout is
  *     secondary information).
- *   - `no-progress` — the watchdog fired (AC-3.4)
  */
 function resolveBatchOutcome(batchOutcome, slots, requestedClamped) {
     let outcome = batchOutcome;

package/dist/services/dispatch/batch-counter.js

@@ -46,7 +46,6 @@ export function readBatchCount(projectRoot, sid, batchId) {
 /** Increment the counter and return the new value (with any warning). */
 export function noteDispatched(projectRoot, sid, batchId, now = () => new Date()) {
     const path = batchCounterPath(projectRoot, sid, batchId);
-    // Slice 2026-06-23-audit-4th #A1: wrap the read-modify-write in a
     // file lock. Two concurrent `peaks sub-agent dispatch` invocations
     // for the same (sid, batchId) would otherwise race — both call
     // readBatchCount first, both see the same N, both write N+1, and

package/dist/services/dispatch/conflict-replay.d.ts

@@ -1,7 +1,6 @@
 /**
  * conflict-replay — pure envelope builder for the auto re-dispatch path.
  *
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 5). When the parent
  * session's merge-back attempt conflicts (see planMergeBack), the
  * merge-back-runner (Task 9) calls `buildConflictReplay` to compose
  * the envelope the parent passes back into the sub-agent dispatch

package/dist/services/dispatch/conflict-replay.js

@@ -1,7 +1,6 @@
 /**
  * conflict-replay — pure envelope builder for the auto re-dispatch path.
  *
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 5). When the parent
  * session's merge-back attempt conflicts (see planMergeBack), the
  * merge-back-runner (Task 9) calls `buildConflictReplay` to compose
  * the envelope the parent passes back into the sub-agent dispatch

package/dist/services/dispatch/contract-store.d.ts

@@ -22,10 +22,8 @@ export declare class ContractStoreError extends Error {
     readonly code: "CONTRACT_STORE_ERROR";
     constructor(message: string);
 }
-/** Slice 2026-06-23-audit-4th #A3: default TTL for slice contracts. */
 export declare const CONTRACT_TTL_DAYS = 30;
 /**
- * Slice 2026-06-23-audit-4th #A3: is this contract an orphan
  * (older than CONTRACT_TTL_DAYS or already GC'd)? Mirrors
  * `isOrphanChannel` and `isOrphanDispatchRecord` so a future
  * `peaks sub-agent cleanup` umbrella can run all three sweeps

package/dist/services/dispatch/contract-store.js

@@ -28,10 +28,8 @@ export class ContractStoreError extends Error {
         this.name = 'ContractStoreError';
     }
 }
-/** Slice 2026-06-23-audit-4th #A3: default TTL for slice contracts. */
 export const CONTRACT_TTL_DAYS = 30;
 /**
- * Slice 2026-06-23-audit-4th #A3: is this contract an orphan
  * (older than CONTRACT_TTL_DAYS or already GC'd)? Mirrors
  * `isOrphanChannel` and `isOrphanDispatchRecord` so a future
  * `peaks sub-agent cleanup` umbrella can run all three sweeps

package/dist/services/dispatch/dispatch-record-input-types.d.ts

@@ -18,7 +18,6 @@ export type WriteInitialDispatchInput = {
     /** Override the timestamp (testing). */
     now?: () => Date;
     /**
-     * Slice 2026-07-29-worktree-l2-extended Part 3.A: the worktree
      * lease id this dispatch owns (set by `peaks sub-agent dispatch
      * --isolation worktree`). Persisted so the finalize-time release
      * hook in `markCompleted` can fire even after the dispatch
@@ -27,7 +26,6 @@ export type WriteInitialDispatchInput = {
      */
     leaseId?: string | null;
     /**
-     * Slice 2026-07-29-worktree-l2-extended Part 7: ISO timestamp
      * when the isolation mode was set up. Optional on the input
      * (defaults to `null`); dispatch-commands.ts passes the spawn
      * time when `--isolation` is requested.