peaks-loop 4.1.0 → 4.1.2

package/dist/services/skills/skill-statusline-service.js

@@ -21,7 +21,6 @@ export { parseStatusLineStdin, read24hOverlay } from './skill-statusline-model.j
  * skill-presence-service.ts, it never deletes or rewrites the presence file:
  * the statusLine runs on every turn and must have zero side effects.
  *
- * Slice 2026-08-05-statusline-sid-scoped-lease-B: the read no longer falls
  * back to the project-level `.peaks/_runtime/active-skill.json` (or its
  * legacy `.peaks/.active-skill.json`). The canonical lease projection is
  * the only source. When `callerId === null` (non-IDE caller), the read
@@ -35,7 +34,6 @@ const STALE_THRESHOLD_MS = 24 * 60 * 60 * 1000;
  * absent (idle) and a sentinel object for malformed content (invalid-presence).
  *
  * Both branches now route through the canonical sid-scoped lease projection
- * (slice 2026-08-05-statusline-sid-scoped-lease-B):
  *   - `callerId !== null` → `resolveActiveSkillForCaller` with the canonical
  *     (non-legacy) lease projection, filtered to this callerId. When the
  *     callerId-filtered resolution returns `source: 'none'` (no lease under
@@ -43,7 +41,6 @@ const STALE_THRESHOLD_MS = 24 * 60 * 60 * 1000;
  *     to the session's most-recent in-flight lease. AC4 multi-tenant isolation
  *     is preserved: when callerId A DOES have a lease, the first call returns
  *     it and the fallback never fires — callerId B's lease is never surfaced
- *     to callerId A. (Slice 2026-08-05-statusline-empty-render-and-short-sid-suffix.)
  *   - `callerId === null` → enumerate `listPresenceLeases` for the
  *     canonical session and pick the most recent in-flight lease. Back-compat
  *     for non-IDE callers (e.g. legacy CLI invocations) that have no callerId.
@@ -119,7 +116,6 @@ function readPresenceReadOnly(projectRoot, callerId) {
     // spreads `input.mode` when present); the typed `SkillPresenceLease` does
     // not declare it, so widen the read shape here. Normalized on read: a
     // legacy `'swarm'` lease renders as `'full-auto'` (slice
-    // 2026-09-09-mode-consolidation).
     const latestMode = normalizeSkillPresenceMode(latest.mode);
     return {
         presence: {
@@ -137,7 +133,6 @@ export function buildStatusLineModel(stdin, nowMs) {
     // and reads `.peaks/_runtime/<sid>/compact-lifecycle.json` (or its legacy
     // fallbacks). It replaces the active skill content when kind != 'none'.
     const compact = readCompactState(projectRoot, nowMs);
-    // Slice 2026-08-05-statusline-sid-only-marker: resolve the canonical
     // session id once, up front, so the renderer can read it from the model
     // without re-running `getSessionIdCanonical`. `null` when the project
     // root is unbound OR when no `.peaks/_runtime/<sid>/` session exists.
@@ -221,7 +216,6 @@ export function buildStatusLineModel(stdin, nowMs) {
     catch {
         activeLeaf = null;
     }
-    // Slice rid-statusline-24h-overlay (2026-08-10): read the 24h-mode
     // overlay snapshot ONLY when state === 'active'. Stale / idle /
     // invalid-presence / idle-via-outer-mismatch never carry the suffix
     // (per PRD §Non-goals.6 — "不在 idle / stale / invalid-presence

package/dist/services/skills/skill-statusline-sid-suffix.d.ts

@@ -2,7 +2,6 @@
  * Pure short-sid suffix helpers for the Peaks statusLine.
  *
  * Extracted from `skill-statusline-renderer.ts` (slice
- * 2026-08-05-statusline-sid-only-marker-and-multi-binary-drift-guard
  * repair cycle) to keep the renderer under the Karpathy 800-line cap.
  * The module is I/O-free and only depends on the read-only
  * `StatusLineModel` shape from `skill-statusline-service.ts` plus the
@@ -32,7 +31,6 @@ export interface SidSuffixPalette {
  * the input is empty. Pure; safe for ASCII rendering across
  * PowerShell, Git Bash, and zsh (AC7).
  *
- * Slice 2026-08-05-statusline-empty-render-and-short-sid-suffix.
  */
 export declare function formatShortSid(sessionId: string): string;
 /**

package/dist/services/skills/skill-statusline-sid-suffix.js

@@ -2,7 +2,6 @@
  * Pure short-sid suffix helpers for the Peaks statusLine.
  *
  * Extracted from `skill-statusline-renderer.ts` (slice
- * 2026-08-05-statusline-sid-only-marker-and-multi-binary-drift-guard
  * repair cycle) to keep the renderer under the Karpathy 800-line cap.
  * The module is I/O-free and only depends on the read-only
  * `StatusLineModel` shape from `skill-statusline-service.ts` plus the
@@ -22,7 +21,6 @@
  * the input is empty. Pure; safe for ASCII rendering across
  * PowerShell, Git Bash, and zsh (AC7).
  *
- * Slice 2026-08-05-statusline-empty-render-and-short-sid-suffix.
  */
 export function formatShortSid(sessionId) {
     if (sessionId.length === 0)

package/dist/services/skills/statusline-palette.d.ts

@@ -1,6 +1,5 @@
 /**
  * Visual / palette / SGR rendering block extracted from
- * `skill-statusline-renderer.ts` (slice 2026-09-06-split-batch-b) so the
  * renderer stays under the 800-line cap. Behaviour-preserving verbatim move;
  * `export` keywords were added to the symbols the renderer still imports.
  */
@@ -36,7 +35,6 @@ interface CompactPalette {
     readonly preparing: string;
     readonly compacting: string;
     /**
-     * Slice 2026-09-12-compact-band-policy: a trigger is registered but no
      * compaction is running. Rendered WITHOUT a bar — see
      * `renderCompact` in skill-statusline-renderer.ts.
      */

package/dist/services/skills/statusline-palette.js

@@ -1,6 +1,5 @@
 /**
  * Visual / palette / SGR rendering block extracted from
- * `skill-statusline-renderer.ts` (slice 2026-09-06-split-batch-b) so the
  * renderer stays under the 800-line cap. Behaviour-preserving verbatim move;
  * `export` keywords were added to the symbols the renderer still imports.
  */
@@ -105,7 +104,6 @@ function buildPalette(capability, noColor) {
         return {
             active: '*',
             idle: 'o',
-            // Slice rid-statusline-stale-ux AC-1: stale residue uses the same
             // glyph as `idle` (`o`) but stays static (no slow-blink — the user
             // is reading a *previous* session's residue, not a live idle state).
             // The neutral copy `(previous session · N days ago)` is the
@@ -133,7 +131,6 @@ function buildPalette(capability, noColor) {
     return {
         active: brandGlyph('●'),
         idle: blinkBrand('○'),
-        // Slice rid-statusline-stale-ux AC-1: muted slate (`#AAAAC8` dim)
         // — slow-blink OFF, distinct from `idle` (slow-blink brand) and
         // `warning` (yellow invalid-presence). The stale branch is
         // semantically "previous-session residue" (neutral), NOT an error.

package/dist/services/slice/slice-archive-service.js

@@ -2,7 +2,6 @@
  * Slice #009 / G5 RL-8 — sub-agent dispatch record archival + 30-day GC.
  *
  * Called by the `peaks session finish` / `peaks session abandon` /
- * new-rid-startup hooks. Walks the per-session `.peaks/_sub_agents/<sid>/`
  * tree and moves completed + disposed records to
  * `.peaks/_runtime/<sid>/_archive/_sub_agents/<sliceId>/`.
  *

package/dist/services/slice/slice-benchmark-service.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice benchmark wrapper (slice 2026-06-14-fzf-rollout).
  *
  * Wraps `decomposeSlices` with a thin observability layer that records
  * total wall time, codegraph call count, confidence distribution, and

package/dist/services/slice/slice-benchmark-service.js

@@ -1,5 +1,4 @@
 /**
- * Slice benchmark wrapper (slice 2026-06-14-fzf-rollout).
  *
  * Wraps `decomposeSlices` with a thin observability layer that records
  * total wall time, codegraph call count, confidence distribution, and

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

@@ -2,7 +2,6 @@ import { execFileSync } from 'node:child_process';
 import { existsSync, readFileSync, statSync } from 'node:fs';
 import { join } from 'node:path';
 import { isDirectory } from 'peaks-loop-shared/fs';
-// Slice 2026-06-29-change-id-root-removal: `getCurrentChangeId` was
 // removed with the change-id axis. Slice check resolves the rid from
 // `options.rid` only; the binding file at `.peaks/_runtime/current-change`
 // is no longer read. Path-safety helpers now live at
@@ -206,7 +205,6 @@ async function runUnitTests(projectRoot, runTests) {
     // related to git-changed files. Cost drops from 30s+ to ~1-3s in steady
     // state. Opt-in to the full suite via `runTests: true` (CLI flag
     // `--run-tests`). See `references/runbook.md` for the rationale and
-    // `tests/unit/slice-check-service.test.ts` for the regression net.
     // Per Windows npx ENOENT (observations 2317+2792), resolve
     // the project-local vitest binary instead of shelling out
     // through npx. 2026-09-10 C6: that binary is the package's JS
@@ -245,7 +243,6 @@ async function runUnitTests(projectRoot, runTests) {
         }
     };
 }
-// Slice `2026-09-14-audit-artifact-rid-scoping`: the evidence filenames
 // carry the rid now. Candidate order is canonical-first, then the
 // back-compat tiers — the same order `artifact-prerequisites.ts` resolves
 // in, so this boundary gate and the transition gate agree on which file is
@@ -257,7 +254,6 @@ const REVIEW_FILES = [
         label: 'code-review'
     },
     // v2.12.0 collapse: security + perf moved to standalone audit skills.
-    // `slice check` accepts the rid-scoped audit path, the bare v2.12.0 path
     // OR the v2.11.x legacy path during the 1-minor-release back-compat
     // window (v2.13.0 hard-deletes the legacy paths — see CHANGELOG [2.12.0]).
     {
@@ -301,7 +297,6 @@ async function runReviewFanout(projectRoot, rid, refresh) {
         let hit = null;
         // Back-compat: each entry lists multiple candidate paths. First hit (in
         // declared order) wins; canonical paths come first so a current slice
-        // preferentially reports its own rid-scoped evidence even when a legacy
         // file is also present during migration.
         const candidates = review.paths.map((candidate) => candidate.replace('<rid>', rid));
         for (const candidate of candidates) {
@@ -375,7 +370,6 @@ export async function sliceCheck(options) {
     if (!(await isDirectory(peaksRoot))) {
         throw new Error(`.peaks/ not found at ${options.projectRoot}. Run peaks workspace init first.`);
     }
-    // Slice 2026-06-29-change-id-root-removal: resolve rid from the
     // explicit `--rid` option only. The `current-change` binding file is
     // gone; the CLI is the single source of truth for the rid.
     if (options.rid === undefined) {

package/dist/services/slice/slice-check-types.d.ts

@@ -69,7 +69,6 @@ export type SliceCheckResult = {
 };
 export type SliceCheckOptions = {
     projectRoot: string;
-    /** REQUIRED. The `.peaks/_runtime/current-change` binding file is gone (slice 2026-06-29-change-id-root-removal); when omitted, slice check throws rather than guessing. */
     rid?: string;
     /**
      * When true, re-run the 3-way review fan-out (peaks-rd's code-review +

package/dist/services/slice/slice-pick-service.d.ts

@@ -1,7 +1,6 @@
 /**
  * Slice Pick Service — thin wrapper around the generic fzf picker.
  *
- * v2 (slice 2026-06-14-fzf-rollout): the actual fzf
  * integration is now in `src/services/fuzzy-matching/fzf-pick-service.ts`.
  * This file only knows how to format / parse SliceCandidate rows and
  * pick the output path. The algorithm itself (slice-decompose-service)

package/dist/services/slice/slice-pick-service.js

@@ -1,7 +1,6 @@
 /**
  * Slice Pick Service — thin wrapper around the generic fzf picker.
  *
- * v2 (slice 2026-06-14-fzf-rollout): the actual fzf
  * integration is now in `src/services/fuzzy-matching/fzf-pick-service.ts`.
  * This file only knows how to format / parse SliceCandidate rows and
  * pick the output path. The algorithm itself (slice-decompose-service)

package/dist/services/slice/slice-review-state.js

@@ -47,8 +47,6 @@ export function getReviewDir(projectRoot, sessionId) {
     //
     // It does NOT cover the slice-id axis: the slice id is joined one function
     // later, in `getReviewPath` below. Corrected 2026-09-14 (repair R1) — this
-    // comment previously said one guard covered the whole family; the security
-    // audit of `2026-09-14-cli-id-escape-instrumentation` (F1b) measured that
     // false: `slice-review '../../../../…/EVILSL'` wrote a `.json` file outside
     // the project root under `ok: true`.
     if (isUnsafePathInput(sessionId)) {

package/dist/services/sqlite/sqlite-driver.d.ts

@@ -0,0 +1,118 @@
+/**
+ * The SQLite driver seam for every store in this CLI.
+ *
+ * WHY A SEAM AT ALL. `better-sqlite3` is a native addon: a consumer either got a prebuilt
+ * binary matching their exact Node ABI or they needed a C++ toolchain, and the failure was
+ * discovered at runtime, not at install. Node ships `node:sqlite`, so the stores do not
+ * need that requirement. But the two are NOT the same library — the three places they
+ * genuinely differ are the whole reason this file exists, and each is a behaviour, not an
+ * import path:
+ *
+ *   - **there is no `pragma()`.** `exec('PRAGMA …')` sets a pragma but returns nothing, so
+ *     reading one back needs a statement (`pragmaValue`). A pragma that is silently not
+ *     applied is worse than no pragma: `foreign_keys = ON` is what makes the skillhub
+ *     schema's REFERENCES clauses mean anything.
+ *   - **`BEGIN` inside a transaction throws.** better-sqlite3's `db.transaction(fn)` nests
+ *     with SAVEPOINTs for free, so a store whose body called another store's body worked.
+ *     Here nesting is explicit and counted, and the inner unit rolls back on its own.
+ *   - **a read-only open must not create the file.** `codegraph-index-integrity` opens the
+ *     index read-only; an empty database created by the open is indistinguishable from an
+ *     index with no rows, and the staleness gate would report a clean graph for a project
+ *     that was never indexed.
+ *   - **`foreign_keys` is ON by default here and was OFF in better-sqlite3.** Measured on
+ *     Node 24.21 (`PRAGMA foreign_keys` answers 1 on a fresh database). The stores that
+ *     asked for it are unaffected; a site that never asked — the capability guard's
+ *     `:memory:` probe — gains enforcement, so write order that used to work can start
+ *     throwing. That is why the call sites keep saying the pragma out loud.
+ *
+ * WHAT THIS IS NOT. It is not an ORM and not a query builder: statements stay at the call
+ * sites, and `prepare`/`run`/`get`/`all`/`exec`/`close` are node:sqlite's own. Only the
+ * three behaviours above are wrapped, because those are the ones a port gets wrong quietly.
+ */
+import { DatabaseSync } from 'node:sqlite';
+/** The database handle the stores hold. Exported so call sites stop naming the addon. */
+export type SqliteDatabase = DatabaseSync;
+/**
+ * What SQLite accepts as a bound value, and what it hands back.
+ *
+ * Re-exported from the seam rather than imported from `node:sqlite` at the call sites for
+ * one reason: `SQLInputValue` EXCLUDES `undefined`, while better-sqlite3 silently bound
+ * `undefined` as NULL. Every store that builds a parameter list wants to say "these are the
+ * values I bind" once, in the name the driver actually enforces — and if that name is
+ * spelled differently in twenty files, the twenty drift.
+ */
+export type { SQLInputValue as SqlInputValue, SQLOutputValue as SqlOutputValue } from 'node:sqlite';
+export type OpenSqliteOptions = {
+    /**
+     * Open without creating. A missing file is an error, not an empty database — the
+     * read-only caller's question is "what does the existing index say", and an empty
+     * database answers that in the most misleading way available.
+     */
+    readonly readOnly?: boolean;
+};
+/**
+ * Open (or create) the SQLite file at `path`.
+ *
+ * `readOnly` on a path that does not exist throws here rather than producing a handle over
+ * a freshly created empty file — see the option.
+ */
+export declare function openSqlite(path: string, options?: OpenSqliteOptions): SqliteDatabase;
+/**
+ * Apply each `PRAGMA` setting, in order.
+ *
+ * A `;` is refused rather than passed through: these strings are literals today, and the
+ * shape that would hurt is a future caller interpolating a name into one and landing a
+ * second statement inside a single `exec`.
+ */
+export declare function applyPragmas(db: SqliteDatabase, pragmas: readonly string[]): void;
+/**
+ * Read one `PRAGMA` back.
+ *
+ * `journal_mode` answers with a row keyed `journal_mode`; `foreign_keys` answers with a
+ * row keyed `foreign_keys`. Both come back as the FIRST column, whatever the name, so that
+ * is what this returns.
+ */
+export declare function pragmaValue(db: SqliteDatabase, name: string): unknown;
+/**
+ * Run `body` as ONE unit of work: commit if it returns, roll back everything it wrote if
+ * it throws, and let the error continue.
+ *
+ * Nesting is by SAVEPOINT, which is what `db.transaction(fn)` did in better-sqlite3: an
+ * inner unit that fails undoes only itself, and an outer unit that fails undoes both. The
+ * alternative — a bare `BEGIN` — throws the moment one store body calls another, which is
+ * the least-tested path in the product and the reason this function is not five lines.
+ */
+export declare function withTransaction<T>(db: SqliteDatabase, body: () => T): T;
+/**
+ * Which constraint a thrown SQLite error violated.
+ *
+ * WHY THIS EXISTS. `loop-bee-relation-service` turns a duplicate relation into the
+ * documented `DUP_RELATION` / `TWO_MAIN_BEES` errors and an absent parent into `FK_*` by
+ * asking which constraint failed. It used to ask
+ * `err.code === 'SQLITE_CONSTRAINT_UNIQUE'`, which better-sqlite3 set. node:sqlite sets
+ * `code` to the generic `ERR_SQLITE_ERROR` for every SQL failure and puts the real
+ * extended result code in `errcode` — measured on this host: 2067 for
+ * `SQLITE_CONSTRAINT_UNIQUE`, 787 for `SQLITE_CONSTRAINT_FOREIGNKEY`. A `.code` comparison
+ * therefore does not throw the wrong error, it throws NOTHING: the branch is skipped and a
+ * raw driver message reaches the operator where the CLI promised an integrity code. That
+ * failure is invisible to the type checker and to any test that does not drive a real
+ * violation, which is why the classifier has its own arms.
+ *
+ * Three readings, in order of trustworthiness: `errcode` (node:sqlite), `code`
+ * (better-sqlite3, and any error shaped like it), then the message. The message is a last
+ * resort rather than the primary because it is the only one of the three that SQLite
+ * documents as human-readable and free to change.
+ */
+export type SqliteConstraintKind = 'unique' | 'foreign-key';
+export declare function constraintKind(error: unknown): SqliteConstraintKind | undefined;
+/**
+ * Bind `body` as a unit of work WITHOUT running it, returned as a callable — the shape
+ * `better-sqlite3`'s `db.transaction(fn)` had, and the shape five stores in this repo are
+ * written in (`const tx = db.transaction(…)`, then `tx()` — sometimes more than once).
+ *
+ * This exists so the port is a name change and not a restructure, because the reuse is
+ * load-bearing: each invocation is its own unit, so a second call that fails must not undo
+ * a first call that committed. An arm in the driver's test calls it twice to prove that,
+ * since no other arm in this file would notice if it were written to run once.
+ */
+export declare function transaction<T>(db: SqliteDatabase, body: () => T): () => T;

package/dist/services/sqlite/sqlite-driver.js

@@ -0,0 +1,159 @@
+/**
+ * The SQLite driver seam for every store in this CLI.
+ *
+ * WHY A SEAM AT ALL. `better-sqlite3` is a native addon: a consumer either got a prebuilt
+ * binary matching their exact Node ABI or they needed a C++ toolchain, and the failure was
+ * discovered at runtime, not at install. Node ships `node:sqlite`, so the stores do not
+ * need that requirement. But the two are NOT the same library — the three places they
+ * genuinely differ are the whole reason this file exists, and each is a behaviour, not an
+ * import path:
+ *
+ *   - **there is no `pragma()`.** `exec('PRAGMA …')` sets a pragma but returns nothing, so
+ *     reading one back needs a statement (`pragmaValue`). A pragma that is silently not
+ *     applied is worse than no pragma: `foreign_keys = ON` is what makes the skillhub
+ *     schema's REFERENCES clauses mean anything.
+ *   - **`BEGIN` inside a transaction throws.** better-sqlite3's `db.transaction(fn)` nests
+ *     with SAVEPOINTs for free, so a store whose body called another store's body worked.
+ *     Here nesting is explicit and counted, and the inner unit rolls back on its own.
+ *   - **a read-only open must not create the file.** `codegraph-index-integrity` opens the
+ *     index read-only; an empty database created by the open is indistinguishable from an
+ *     index with no rows, and the staleness gate would report a clean graph for a project
+ *     that was never indexed.
+ *   - **`foreign_keys` is ON by default here and was OFF in better-sqlite3.** Measured on
+ *     Node 24.21 (`PRAGMA foreign_keys` answers 1 on a fresh database). The stores that
+ *     asked for it are unaffected; a site that never asked — the capability guard's
+ *     `:memory:` probe — gains enforcement, so write order that used to work can start
+ *     throwing. That is why the call sites keep saying the pragma out loud.
+ *
+ * WHAT THIS IS NOT. It is not an ORM and not a query builder: statements stay at the call
+ * sites, and `prepare`/`run`/`get`/`all`/`exec`/`close` are node:sqlite's own. Only the
+ * three behaviours above are wrapped, because those are the ones a port gets wrong quietly.
+ */
+import { existsSync } from 'node:fs';
+import { DatabaseSync } from 'node:sqlite';
+/**
+ * Open (or create) the SQLite file at `path`.
+ *
+ * `readOnly` on a path that does not exist throws here rather than producing a handle over
+ * a freshly created empty file — see the option.
+ */
+export function openSqlite(path, options = {}) {
+    const readOnly = options.readOnly === true;
+    if (readOnly && !existsSync(path)) {
+        throw new Error(`no such file (opened read-only): ${path}`);
+    }
+    return new DatabaseSync(path, { readOnly });
+}
+/**
+ * Apply each `PRAGMA` setting, in order.
+ *
+ * A `;` is refused rather than passed through: these strings are literals today, and the
+ * shape that would hurt is a future caller interpolating a name into one and landing a
+ * second statement inside a single `exec`.
+ */
+export function applyPragmas(db, pragmas) {
+    for (const pragma of pragmas) {
+        if (pragma.includes(';')) {
+            throw new Error(`a pragma must be one statement, got: ${pragma}`);
+        }
+        db.exec(`PRAGMA ${pragma}`);
+    }
+}
+/**
+ * Read one `PRAGMA` back.
+ *
+ * `journal_mode` answers with a row keyed `journal_mode`; `foreign_keys` answers with a
+ * row keyed `foreign_keys`. Both come back as the FIRST column, whatever the name, so that
+ * is what this returns.
+ */
+export function pragmaValue(db, name) {
+    if (name.includes(';')) {
+        throw new Error(`a pragma name must be one statement, got: ${name}`);
+    }
+    const row = db.prepare(`PRAGMA ${name}`).get();
+    if (row === undefined)
+        return undefined;
+    const values = Object.values(row);
+    return values[0];
+}
+/** The depth of open transactions per handle, so nesting is counted, not guessed. */
+const transactionDepth = new WeakMap();
+/**
+ * Run `body` as ONE unit of work: commit if it returns, roll back everything it wrote if
+ * it throws, and let the error continue.
+ *
+ * Nesting is by SAVEPOINT, which is what `db.transaction(fn)` did in better-sqlite3: an
+ * inner unit that fails undoes only itself, and an outer unit that fails undoes both. The
+ * alternative — a bare `BEGIN` — throws the moment one store body calls another, which is
+ * the least-tested path in the product and the reason this function is not five lines.
+ */
+export function withTransaction(db, body) {
+    const depth = transactionDepth.get(db) ?? 0;
+    transactionDepth.set(db, depth + 1);
+    const savepoint = `peaks_sp_${String(depth + 1)}`;
+    if (depth === 0) {
+        db.exec('BEGIN');
+    }
+    else {
+        db.exec(`SAVEPOINT ${savepoint}`);
+    }
+    try {
+        const result = body();
+        if (depth === 0) {
+            db.exec('COMMIT');
+        }
+        else {
+            db.exec(`RELEASE ${savepoint}`);
+        }
+        return result;
+    }
+    catch (error) {
+        if (depth === 0) {
+            db.exec('ROLLBACK');
+        }
+        else {
+            db.exec(`ROLLBACK TO ${savepoint}`);
+            db.exec(`RELEASE ${savepoint}`);
+        }
+        throw error;
+    }
+    finally {
+        transactionDepth.set(db, depth);
+    }
+}
+/** `SQLITE_CONSTRAINT_UNIQUE` — 19 | (8 << 8). */
+const SQLITE_ERRCODE_CONSTRAINT_UNIQUE = 2067;
+/** `SQLITE_CONSTRAINT_FOREIGNKEY` — 19 | (3 << 8). */
+const SQLITE_ERRCODE_CONSTRAINT_FOREIGNKEY = 787;
+export function constraintKind(error) {
+    if (typeof error !== 'object' || error === null)
+        return undefined;
+    const shaped = error;
+    if (shaped.errcode === SQLITE_ERRCODE_CONSTRAINT_UNIQUE)
+        return 'unique';
+    if (shaped.errcode === SQLITE_ERRCODE_CONSTRAINT_FOREIGNKEY)
+        return 'foreign-key';
+    if (shaped.code === 'SQLITE_CONSTRAINT_UNIQUE')
+        return 'unique';
+    if (shaped.code === 'SQLITE_CONSTRAINT_FOREIGNKEY')
+        return 'foreign-key';
+    const message = error instanceof Error ? error.message : '';
+    if (message.includes('UNIQUE constraint failed'))
+        return 'unique';
+    if (message.includes('FOREIGN KEY constraint failed'))
+        return 'foreign-key';
+    return undefined;
+}
+/**
+ * Bind `body` as a unit of work WITHOUT running it, returned as a callable — the shape
+ * `better-sqlite3`'s `db.transaction(fn)` had, and the shape five stores in this repo are
+ * written in (`const tx = db.transaction(…)`, then `tx()` — sometimes more than once).
+ *
+ * This exists so the port is a name change and not a restructure, because the reuse is
+ * load-bearing: each invocation is its own unit, so a second call that fails must not undo
+ * a first call that committed. An arm in the driver's test calls it twice to prove that,
+ * since no other arm in this file would notice if it were written to run once.
+ */
+export function transaction(db, body) {
+    return () => withTransaction(db, body);
+}

package/dist/services/standards/ide-aware-standards-service.d.ts

@@ -1,7 +1,6 @@
 /**
  * IDE-aware wrapper for `peaks standards init` / `peaks standards update`.
  *
- * Slice #011-2026-06-07-ide-adapter-resource-profile: the original
  * `executeProjectStandardsInit` / `executeProjectStandardsUpdate` always
  * wrote to `CLAUDE.md` + `.claude/rules/**` regardless of which IDE
  * the user was running. This wrapper dispatches on the IDE detected
@@ -76,7 +75,6 @@ export declare function executeProjectStandardsUpdateIdeAware(options: ProjectSt
 /**
  * Test seam + integration-test helper: returns the resolved IDE id
  * for the call, plus the active standards profile. Exported for
- * the integration test in `tests/unit/standards/ide-aware-standards-service.test.ts`
  * to assert the dispatch decision without running the full write.
  */
 export declare function inspectStandardsDispatch(options: {

package/dist/services/standards/ide-aware-standards-service.js

@@ -73,7 +73,6 @@ export function executeProjectStandardsUpdateIdeAware(options) {
 /**
  * Test seam + integration-test helper: returns the resolved IDE id
  * for the call, plus the active standards profile. Exported for
- * the integration test in `tests/unit/standards/ide-aware-standards-service.test.ts`
  * to assert the dispatch decision without running the full write.
  */
 export function inspectStandardsDispatch(options) {

package/dist/services/standards/loop-engineering-readiness-lint.d.ts

@@ -71,7 +71,6 @@ export declare const LOOP_ENGINEERING_GUIDELINE_PATHS: readonly [".peaks/standar
  * The allowlist of CLI verbs that a peaks-* SKILL.md may legitimately
  * instruct an LLM to invoke on the user's behalf. These are the
  * sediment / asset / evolution surface verbs introduced in
- * 2026-07-07-loop-engineering-crystallization-design §7.4 plus the
  * 18-verb sediment pool from 2026-07-04-peaks-maker-dynamic-skill-
  * sediment-design §4.2.
  *

package/dist/services/standards/loop-engineering-readiness-lint.js

@@ -65,7 +65,6 @@ export const LOOP_ENGINEERING_GUIDELINE_PATHS = [
  * The allowlist of CLI verbs that a peaks-* SKILL.md may legitimately
  * instruct an LLM to invoke on the user's behalf. These are the
  * sediment / asset / evolution surface verbs introduced in
- * 2026-07-07-loop-engineering-crystallization-design §7.4 plus the
  * 18-verb sediment pool from 2026-07-04-peaks-maker-dynamic-skill-
  * sediment-design §4.2.
  *

package/dist/services/standards/migrate-claude-rules-service.js

@@ -1,6 +1,5 @@
 /**
  * peaks standards migrate — .claude/rules/ tree thinning.
- * Slice: 2026-06-12-standards-migrate-claude-rules.
  *
  * The 1.x peaks-loop install copied a thick .claude/rules
  * tree (skill-first / CLI-auxiliary / dogfood / commit-trailer
@@ -110,7 +109,6 @@ export function migrateClaudeRules(input) {
     // earlier migration run. The backup is real content (not a pointer),
     // so without this filter a second run would treat the backup dir as
     // a fresh thick tree and re-thin / re-scaffold over it
-    // (slice 2026-07-15-ice-cola-dogfood).
     const BACKUP_DIR_PREFIX = '.peaks-2.0-backup-';
     const thickFiles = existingRulesFiles.filter((f) => {
         if (isAlreadyPointer(f))
@@ -149,7 +147,6 @@ export function migrateClaudeRules(input) {
                     // the top-level backup dir, not the nested language pack
                     // dirs. Without this mkdirSync, the first file written to
                     // a nested subdir ENOENTs and the whole backup silently
-                    // becomes empty (slice 2026-07-15-ice-cola-dogfood).
                     mkdirSync(dirname(destPath), { recursive: true });
                     writeFileSync(destPath, body, 'utf8');
                 }

package/dist/services/standards/migrate-service.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 028 (Q2=A): `peaks standards migrate` rewrites a consumer
  * project's `CLAUDE.md` to drop the legacy heartbeat block.
  *
  * The legacy block (rendered by `peaks standards init` / `peaks

package/dist/services/standards/migrate-service.js

@@ -1,7 +1,6 @@
 import { existsSync, readFileSync, writeFileSync } from 'node:fs';
 import { isAbsolute, resolve } from 'node:path';
 /**
- * Slice 028 (Q2=A): `peaks standards migrate` rewrites a consumer
  * project's `CLAUDE.md` to drop the legacy heartbeat block.
  *
  * The legacy block (rendered by `peaks standards init` / `peaks

package/dist/services/standards/missing-standards-detector.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-peaks-code-auto-scaffold (RD#7) — missing-standards-detector.
  *
  * Read-side companion to the `peaks standards init` / `peaks standards update`
  * writers in `./project-standards-service.ts`. The writer KNOWS how to scaffold
@@ -71,7 +70,6 @@ export declare function diagnoseStandardsTree(projectRoot: string, language: Sta
  * Detect whether a consumer project's `.peaks/standards/` tree (2.0
  * canonical) is missing or empty.
  *
- * Rules (per PRD R2, slice 2026-07-15):
  *   - `.peaks/standards/common/` MUST exist AND contain at least one
  *     `.md` file.
  *   - `.peaks/standards/<language>/` MUST exist AND contain at least one

package/dist/services/standards/missing-standards-detector.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-16-peaks-code-auto-scaffold (RD#7) — missing-standards-detector.
  *
  * Read-side companion to the `peaks standards init` / `peaks standards update`
  * writers in `./project-standards-service.ts`. The writer KNOWS how to scaffold
@@ -44,7 +43,6 @@ function renderForPlatform(projectRoot) {
     // the same separator via the literal '\\' join below.
     //
     // 2.0 canonical location: `<projectRoot>/.peaks/standards/`
-    // (slice 2026-07-15-missing-standards-on-fresh-project — the 2.0
     // writer scaffolds the rules tree under `.peaks/standards/`, not
     // the legacy `.claude/rules/`).
     if (process.platform === 'win32') {
@@ -84,7 +82,6 @@ export function diagnoseStandardsTree(projectRoot, language) {
  * Detect whether a consumer project's `.peaks/standards/` tree (2.0
  * canonical) is missing or empty.
  *
- * Rules (per PRD R2, slice 2026-07-15):
  *   - `.peaks/standards/common/` MUST exist AND contain at least one
  *     `.md` file.
  *   - `.peaks/standards/<language>/` MUST exist AND contain at least one

package/dist/services/standards/project-standards-service.d.ts

@@ -102,7 +102,6 @@ export type ProjectStandardsInitOptions = {
 };
 /**
  * Public alias for `detectLanguageInternal` so callers outside this
- * module (e.g. `workspace-service.ts` for the slice 2026-06-16 RD#7
  * auto-detect path) can ask the same heuristic without re-implementing
  * the file-probe logic.
  */

package/dist/services/standards/project-standards-service.js

@@ -109,7 +109,6 @@ function detectLanguageInternal(projectRoot) {
 }
 /**
  * Public alias for `detectLanguageInternal` so callers outside this
- * module (e.g. `workspace-service.ts` for the slice 2026-06-16 RD#7
  * auto-detect path) can ask the same heuristic without re-implementing
  * the file-probe logic.
  */