peaks-loop 4.1.1 → 4.1.2

package/dist/services/ide/adapters/qoder-adapter.js

@@ -1,5 +1,4 @@
 /**
- * Qoder IDE adapter (slice 2026-07-25-qoder-adapter-ship) — peaks-loop
  * 第八个内置 IDE 适配器(填表)。
  *
  * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
@@ -9,14 +8,12 @@
  *   - hookEvent = 'PreToolUse'             : 现代 IDE 通用约定(UNVERIFIED — 待真实 Qoder 安装验证)
  *   - toolMatcher = 'Bash'                 : 同上(UNVERIFIED)
  *
- * Slice 2026-07-25-qoder-adapter-ship 状态:
  *   - Slim adapter shape 跟 hermes-adapter.ts / claude-code-adapter.ts 同型,
  *     验证 slice #1 抽出的形状在第 8 个 IDE 上仍然可以"填表"接入。
  *   - 5 fields (dirName / settingsFileName / envVar / hookEvent / toolMatcher)
  *     均为占位值并标记 UNVERIFIED;待真实 Qoder 安装可用后再走 VERIFIED 路径
  *     (见 PRD §3 step 5 + 多 IDE 治理政策
  *     .peaks/memory/2026-07-24-multi-ide-adapter-policy.md)。
- *   - 见 [[2026-07-24-multi-ide-adapter-policy]] 了解 UNVERIFIED → VERIFIED
  *     的迁移路径与 7-step checklist。
  *   - 本 slice 不修改 src/services/ide/ide-types.ts(IdeId union 已经在
  *     line 21 包含 'qoder'),不修改既有 adapter 文件,不修改既有测试。
@@ -38,12 +35,10 @@ export const QODER_ADAPTER = {
     envVar: 'QODER_PROJECT_DIR', // UNVERIFIED
     hookEvent: 'PreToolUse', // UNVERIFIED
     toolMatcher: 'Bash', // UNVERIFIED
-    // Slice 2026-07-25-qoder-adapter-ship: Qoder sub-agent dispatcher UNVERIFIED —
     // pending real Qoder dogfood. Reusing the Trae dispatcher as a uniform
     // placeholder (same rationale as hermes-adapter.ts: byte-stable shape
     // across placeholder adapters).
     subAgentDispatcher: traeSubAgentDispatcher,
-    // Slice 2026-07-25-qoder-adapter-ship: Qoder PreToolUse is the assumed hook
     // path. UNVERIFIED — will be re-evaluated against a real Qoder install.
     promptSizeAware: true,
     installHints: ['Restart Qoder (or reload the workspace) so the PreToolUse hooks take effect.'],

package/dist/services/ide/adapters/tongyi-lingma-adapter.d.ts

@@ -1,5 +1,4 @@
 /**
- * Tongyi Lingma IDE adapter (slice 2026-07-25-tongyi-lingma-adapter-ship) —
  * peaks-loop 第九个内置 IDE 适配器(填表)。
  *
  * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
@@ -10,7 +9,6 @@
  *   - toolMatcher = 'Bash'                         (UNVERIFIED)
  *
  * 这些字段在真实 Tongyi Lingma 安装 dogfood 完成前不得标记 VERIFIED。
- * 见 [[2026-07-24-multi-ide-adapter-policy]] §3 step 5。
  */
 import type { IdeAdapter } from '../ide-types.js';
 export declare const TONGYI_LINGMA_ADAPTER: IdeAdapter;

package/dist/services/ide/adapters/tongyi-lingma-adapter.js

@@ -1,5 +1,4 @@
 /**
- * Tongyi Lingma IDE adapter (slice 2026-07-25-tongyi-lingma-adapter-ship) —
  * peaks-loop 第九个内置 IDE 适配器(填表)。
  *
  * 不可消除的 per-IDE 字段(本 slice 填表;字段值暂为占位):
@@ -10,7 +9,6 @@
  *   - toolMatcher = 'Bash'                         (UNVERIFIED)
  *
  * 这些字段在真实 Tongyi Lingma 安装 dogfood 完成前不得标记 VERIFIED。
- * 见 [[2026-07-24-multi-ide-adapter-policy]] §3 step 5。
  */
 import { homedir } from 'node:os';
 import { join, resolve } from 'node:path';

package/dist/services/ide/adapters/trae-adapter.d.ts

@@ -4,10 +4,7 @@ import type { IdeAdapter } from '../ide-types.js';
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *   - envVar = 'TRAE_PROJECT_DIR'    : Trae 注入的 env 变量(用于 ${...} 占位)
- *   - hookEvent = 'beforeToolCall'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
- *   - toolMatcher = 'terminal'      (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *
  * Slice #1 的 slim `IdeAdapter` shape 在 slice #1 RD 中被锁为"填表"模式。
  * 本文件是 slice #2 第一个真实客户,验证 slice #1 抽出的形状真的可以

package/dist/services/ide/adapters/trae-adapter.js

@@ -6,10 +6,7 @@ import { traeSubAgentDispatcher } from '../../dispatch/sub-agent-dispatcher.js';
  *
  * 不可消除的 per-IDE 字段(slice #1 锁定):
  *   - settings.dirName = '.trae'            : Trae 项目根下的配置目录
- *   - settings.settingsFileName = 'settings.json'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *   - envVar = 'TRAE_PROJECT_DIR'    : Trae 注入的 env 变量(用于 ${...} 占位)
- *   - hookEvent = 'beforeToolCall'  (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
- *   - toolMatcher = 'terminal'      (VERIFIED against Trae 1.x fixture, slice 009-009-2026-06-07-trae-dogfood)
  *
  * Slice #1 的 slim `IdeAdapter` shape 在 slice #1 RD 中被锁为"填表"模式。
  * 本文件是 slice #2 第一个真实客户,验证 slice #1 抽出的形状真的可以
@@ -46,15 +43,15 @@ export const TRAE_ADAPTER = {
     displayName: 'Trae',
     settings: {
         dirName: '.trae',
-        settingsFileName: 'settings.json', // VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07)
+        settingsFileName: 'settings.json',
         resolveSettingsFile: (scope, projectRoot) => {
             const root = scope === 'global' ? homedir() : resolve(projectRoot ?? homedir());
             return join(root, '.trae', 'settings.json');
         }
     },
     envVar: 'TRAE_PROJECT_DIR',
-    hookEvent: 'beforeToolCall', // VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07); fixture at tests/fixtures/trae/trae-1x-payload.json
-    toolMatcher: 'terminal', // VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07); fixture pins `parameters.tool: 'terminal'`
+    hookEvent: 'beforeToolCall',
+    toolMatcher: 'terminal',
     // Slice #009: Trae's sub-agent dispatcher is UNVERIFIED — Trae sub-agent
     // tool name TBD on real dogfood; byte-level identical to claude-code by
     // design so the dispatcher shape is uniform across both adapters. Awaiting

package/dist/services/ide/adapters/zcode-adapter.js

@@ -1,5 +1,4 @@
 /**
- * z-code IDE adapter (slice 2026-07-09-add-zcode-adapter) — peaks-loop 的第九个
  * 内置 IDE 适配器。
  *
  * z-code 是一个 VS Code-style 的 Anthropic-compatible 桌面应用:
@@ -171,7 +170,6 @@ export const ZCODE_ADAPTER = {
     hookEvent: 'PreToolUse',
     // UNVERIFIED — 同上,占位用 `Bash` matcher。
     toolMatcher: 'Bash',
-    // Slice 2026-07-09: z-code 桌面应用没有公开 Task 工具 dispatch 协议,
     // 用 `nullSubAgentDispatcher` 占位 — peaks sub-agent dispatch CLI 在
     // z-code 上返回 SubAgentNotSupportedError,符合 slice #008 P-5 capability
     // 检查契约 (CLI 不崩溃)。

package/dist/services/ide/current-model-detector.js

@@ -1,5 +1,4 @@
 /**
- * Runtime current-model detector (Slice 2026-07-09 add-zcode-adapter, Slice C).
  *
  * Walks the registered IDE adapter chain and asks the IDE adapter
  * (when it opts in via `IdeAdapter.detectCurrentModel?`) to report the

package/dist/services/ide/hook-protocol.d.ts

@@ -11,13 +11,11 @@ export declare const CLAUDE_CODE_DENY_SHAPE: Record<string, unknown>;
 export declare const CLAUDE_CODE_DENY_TRANSPORT: PeaksDecisionTransport;
 /**
  * Compute the deny decision shape for Trae (Cursor-style sibling IDE).
- * VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07).
  * Shape is the standard Cursor/Claude sibling envelope: `hookSpecificOutput`
  * with `hookEventName`, `permissionDecision`, `permissionDecisionReason`.
  * The hookEventName is `'beforeToolCall'` for Trae vs `'PreToolUse'` for
  * Claude Code — the only field that differs between the two siblings.
  * Fixture: tests/fixtures/trae/trae-1x-payload.json. Constant NAME preserved
- * (per slice 009 PRD R-3); only the shape was already correct from slice #3.
  */
 export declare const TRAE_DENY_SHAPE: Record<string, unknown>;
 export declare const TRAE_DENY_TRANSPORT: PeaksDecisionTransport;

package/dist/services/ide/hook-protocol.js

@@ -19,13 +19,11 @@ export const CLAUDE_CODE_DENY_TRANSPORT = {
 };
 /**
  * Compute the deny decision shape for Trae (Cursor-style sibling IDE).
- * VERIFIED against Trae 1.x fixture — slice 009-009-2026-06-07-trae-dogfood (2026-06-07).
  * Shape is the standard Cursor/Claude sibling envelope: `hookSpecificOutput`
  * with `hookEventName`, `permissionDecision`, `permissionDecisionReason`.
  * The hookEventName is `'beforeToolCall'` for Trae vs `'PreToolUse'` for
  * Claude Code — the only field that differs between the two siblings.
  * Fixture: tests/fixtures/trae/trae-1x-payload.json. Constant NAME preserved
- * (per slice 009 PRD R-3); only the shape was already correct from slice #3.
  */
 export const TRAE_DENY_SHAPE = {
     hookSpecificOutput: {

package/dist/services/ide/ide-compact-types.d.ts

@@ -21,7 +21,6 @@ export interface IdeCompactProfile {
      * spawns this via `child_process.spawn` (shell-exec pathway) or
      * writes it to an IDE hook file (ide-native pathway).
      *
-     * ZERO EXECUTOR as of slice 2026-09-13-auto-compact-trigger-ownership: every
      * `shell-exec` branch now only REPORTS that it will not spawn (see
      * `auto-compact-dispatcher.ts`), and the `ide-native` branch registers a
      * harness-side trigger instead. The field is retained because the sibling
@@ -50,7 +49,6 @@ export interface IdeCompactProfile {
      * declared, peaks-loop writes the window it computes its ratio against
      * into the adapter's machine-local settings `env` block, under this key,
      * so both sides reference one number instead of two independent
-     * resolutions (slice 2026-09-13-auto-compact-trigger-ownership).
      *
      * `undefined` = this IDE exposes no such knob. peaks-loop then cannot
      * close the drift; `peaks compact harness-window` reports that instead of
@@ -76,13 +74,11 @@ export interface IdeCompactProfile {
      * that do not opt in simply omit the field; new IDEs are addable
      * without touching the generic reader.
      *
-     * Added in slice 2026-09-02-vendor-neutral-context-probe.
      */
     readonly readContextPercentFallback?: (input: ContextPercentFallbackInput) => ContextPercentProbe | null;
     /**
      * Optional locator for the IDE's per-session transcript file (jsonl),
      * keyed by the OUTER (harness) session id. `peaks code context-audit`
-     * (slice 2026-09-10-context-audit-and-discipline, Slice A) uses it to
      * group the session's tool results by tool + short input key, so the
      * generic audit service never learns any vendor's on-disk layout.
      *
@@ -101,7 +97,6 @@ export interface IdeCompactProfile {
  * owns the vendor-specific fallback logic (statusline poll, transcript
  * lookup, etc.); the generic reader stays IDE-agnostic.
  *
- * Added in slice 2026-09-02-vendor-neutral-context-probe.
  */
 export interface ContextPercentFallbackInput {
     /** Project root (the probe's `--project` anchor). */
@@ -122,7 +117,6 @@ export interface ContextPercentFallbackInput {
      * of config-path knowledge. UNVALIDATED — the adapter validates it via
      * `parseContextWindowOverride` and warns on a bad value.
      *
-     * Slice 2026-09-09-context-window-override.
      */
     readonly configWindowTokens?: unknown;
     /**
@@ -131,7 +125,6 @@ export interface ContextPercentFallbackInput {
      * key name) — the window peaks-loop configured for the harness. Feeds the
      * `harness-env` layer of `resolveContextWindow`.
      *
-     * Slice 2026-09-13-auto-compact-trigger-ownership.
      */
     readonly harnessWindowTokens?: unknown;
     /**

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

@@ -68,8 +68,6 @@ export interface IdeAdapter {
      * this field, calls `supportsRole` + `buildToolCall`, and returns the
      * resulting tool-call descriptor in the JSON envelope. Encapsulates the per-IDE sub-agent dispatch surface (slice #009). The dispatcher's `buildToolCall` returns the IDE-native tool-call descriptor at runtime.
      *
-     * Added in slice 2026-06-07-sub-agent-dispatch-decouple. See PRD #002
-     * G1 (AC-1, AC-2) + [[slim-ideadapter-shape-is-the-contract]].
      */
     readonly subAgentDispatcher: SubAgentDispatcher;
     /**
@@ -83,8 +81,6 @@ export interface IdeAdapter {
      * the threshold regardless of this field — `promptSizeAware` only
      * controls the hook layer (R-15: G9 hook is LLM-platform-specific).
      *
-     * Added in slice 2026-06-07-sub-agent-context-governance. See PRD
-     * #003 G9.2 + AC-56. Default `false` to preserve slice #009's
      * `peaks hooks install` output byte-stability.
      */
     readonly promptSizeAware: boolean;
@@ -100,7 +96,6 @@ export interface IdeAdapter {
      * value (Claude Code), are annotated UNVERIFIED for future slices
      * (Trae, slice #012+), or omit it entirely (not-yet-registered IDEs).
      *
-     * Added in slice 011-2026-06-07-ide-adapter-resource-profile.
      */
     readonly standardsProfile?: IdeStandardsProfile;
     /**
@@ -111,21 +106,17 @@ export interface IdeAdapter {
      * this; adapters that don't (Trae in slice 1.3.2) leave it undefined
      * and follow the legacy path with a warning.
      *
-     * Added in slice 011-2026-06-07-ide-adapter-resource-profile.
      */
     readonly skillInstall?: IdeSkillInstall;
     /**
-     * v2.13.0 auto-compact (AC-1 + AC-3): per-IDE compact-capability
      * descriptor. When `undefined`, peaks-loop falls back to the
      * `llm-self-compress` pathway (the LLM summarizes its own context).
      * Adapters that fill this expose a 4-stage protocol so peaks-loop
      * can drive compact autonomously:
      *
      *   1. `envVarForContextPercent` — env-var the IDE sets per turn
-     *      (e.g. `CLAUDE_CONTEXT_USAGE_PERCENT`). Read by AC-1.
      *   2. `compactCommand` — slash command or shell-call the IDE
      *      accepts to trigger compact (e.g. `/compact`). Dispatched
-     *      by AC-3.
      *   3. `compactPathway` — `'shell-exec' | 'ide-native' |
      *      'llm-self-compress' | 'noop'`. `shell-exec` means peaks-loop
      *      spawns `compactCommand` via `child_process.spawn` (zero IDE
@@ -140,7 +131,6 @@ export interface IdeAdapter {
      * `compactPathway: 'llm-self-compress'` until L2-dogfood verifies
      * each IDE's actual compact surface.
      *
-     * Added in slice 2026-06-27-auto-compact-protocol. See
      * `.peaks/memory/2026-06-27-auto-compact-design.md`.
      */
     readonly compact?: IdeCompactProfile;
@@ -162,7 +152,6 @@ export interface IdeAdapter {
      * locally and return `undefined`. The orchestration layer also
      * catches, but defense in depth.
      *
-     * Added in slice 2026-07-09 add-zcode-adapter (Slice C); only the
      * `zcode` adapter opts in this slice. Future slices can opt in
      * other IDEs without changing this signature (optional method).
      */
@@ -185,7 +174,6 @@ export interface IdeAdapter {
 }
 /**
  * Per-IDE standards-file location + format profile. Used by the
- * `peaks standards init` dispatch layer (slice 011) to write the
  * project-level standards files at the IDE-specific path, not the
  * Claude Code hardcoded one. Adapters that omit this field trigger
  * the legacy Claude Code path with a stderr warning.

package/dist/services/ide/resource-profile.d.ts

@@ -1,7 +1,6 @@
 /**
  * Resource profile accessors for the per-IDE dispatch layer.
  *
- * Slice #011-2026-06-07-ide-adapter-resource-profile introduced two new
  * optional fields on the `IdeAdapter` interface:
  *
  *   - `standardsProfile` — where the IDE reads its project-level

package/dist/services/job/job-commit-verification.d.ts

@@ -1,10 +1,8 @@
 /**
- * D2 (rid 2026-10-03-job-ledger-truthfulness) — can this commit sha be proved to
  * exist in this repository?
  *
  * WHY THIS EXISTS. `peaks job checkpoint --state done --commit-sha <sha>` checked
  * only `sha.length >= 7` (`job-orchestrator.ts:55`), so a typo'd sha was accepted
- * and written into the ledger. Measured 2026-10-02 on `2026-10-02-c-wave9`, and
  * again for this slice against the committed build: a 12-hex string that
  * `git cat-file` calls `Not a valid object name` produced `ok: true` and a
  * `state.json` whose `commitSha` named it. A ledger that points at a commit which

package/dist/services/job/job-commit-verification.js

@@ -1,10 +1,8 @@
 /**
- * D2 (rid 2026-10-03-job-ledger-truthfulness) — can this commit sha be proved to
  * exist in this repository?
  *
  * WHY THIS EXISTS. `peaks job checkpoint --state done --commit-sha <sha>` checked
  * only `sha.length >= 7` (`job-orchestrator.ts:55`), so a typo'd sha was accepted
- * and written into the ledger. Measured 2026-10-02 on `2026-10-02-c-wave9`, and
  * again for this slice against the committed build: a 12-hex string that
  * `git cat-file` calls `Not a valid object name` produced `ok: true` and a
  * `state.json` whose `commitSha` named it. A ledger that points at a commit which

package/dist/services/job/job-orchestrator.d.ts

@@ -36,7 +36,6 @@ export declare class JobOrchestrator {
     constructor(store: JobStateStore);
     init(input: JobInitInput): JobState;
     /**
-     * D1 (rid 2026-10-03-job-ledger-truthfulness) — register one more slice on an
      * existing job.
      *
      * WHY THIS EXISTS. The slice list was decided once, at `peaks job init

package/dist/services/job/job-orchestrator.js

@@ -27,7 +27,6 @@ export class JobOrchestrator {
         return this.store.init(input);
     }
     /**
-     * D1 (rid 2026-10-03-job-ledger-truthfulness) — register one more slice on an
      * existing job.
      *
      * WHY THIS EXISTS. The slice list was decided once, at `peaks job init

package/dist/services/job/job-progress-store.d.ts

@@ -24,7 +24,6 @@
 import { z } from 'zod';
 export declare const JOB_PROGRESS_SCHEMA_VERSION: 1;
 /**
- * D3 (rid 2026-10-03-job-ledger-truthfulness) — what the mirror says when the
  * ledger has no pending slice.
  *
  * `currentSlice` is required by the schema below (it is a `string`, and readers
@@ -80,7 +79,6 @@ export interface NextSliceFacts {
     readonly currentSlice: string;
 }
 /**
- * criterion (c) (rid 2026-10-03-job-ledger-repair1) — the one sentence the reader
  * acts on, built from the mirror instead of guessed at.
  *
  * WHY THIS EXISTS. The parent slice made `currentSlice` honest (§2.38: it used to

package/dist/services/job/job-progress-store.js

@@ -29,7 +29,6 @@ import { guardRuntimeSegment, runtimeRoot } from '../../shared/runtime-root.js';
  * The single place a job-progress directory is built, and therefore the single
  * place the two ids that reach it are guarded.
  *
- * Slice 2026-09-15 (runtime-path-unrepresentable): this join used to be written
  * at three sites, none of them guarded, and the shipped text rule could not see
  * them — they sit in the service layer, outside the command layer it scans.
  * Both ids are caller-supplied (`peaks job checkpoint` takes them from flags).
@@ -41,7 +40,6 @@ function jobProgressDir(projectRoot, sessionId, jobId) {
 }
 export const JOB_PROGRESS_SCHEMA_VERSION = 1;
 /**
- * D3 (rid 2026-10-03-job-ledger-truthfulness) — what the mirror says when the
  * ledger has no pending slice.
  *
  * `currentSlice` is required by the schema below (it is a `string`, and readers
@@ -114,7 +112,6 @@ function addSliceAdvice(jobId) {
     return `peaks job add-slice --job-id ${jobId ?? '<job-id>'} --slice-label ${ADD_SLICE_LABEL_SLOT}`;
 }
 /**
- * criterion (c) (rid 2026-10-03-job-ledger-repair1) — the one sentence the reader
  * acts on, built from the mirror instead of guessed at.
  *
  * WHY THIS EXISTS. The parent slice made `currentSlice` honest (§2.38: it used to

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

@@ -99,7 +99,6 @@ export const JobCheckpointInputSchema = z
 })
     .superRefine((v, ctx) => {
     if (v.state === 'done') {
-        // D2 (rid 2026-10-03-job-ledger-truthfulness). Two rules, in this order,
         // both on the same claim about the same field.
         //
         // 1. THE SHAPE RULE. It stays exactly where the defect was measured

package/dist/services/job-snapshot/snapshot.js

@@ -29,7 +29,6 @@ export function collectResourceSnapshot(jobDir) {
 // Non-enumerable internal attachment for test-time access via
 // `collectResourceSnapshot.dirSizeMb`. NOT a public export — keeps
 // the prod module surface clean per PRD while still allowing
-// targeted AC-1/AC-2/AC-3 unit tests to drive `dirSizeMb` directly.
 Object.defineProperty(collectResourceSnapshot, 'dirSizeMb', {
     value: dirSizeMb,
     enumerable: false,

package/dist/services/karpathy-cost/karpathy-cost-check-service.js

@@ -1,6 +1,5 @@
 // src/services/karpathy-cost/karpathy-cost-check-service.ts
 //
-// Slice 2026-07-30-karpathy-cost-self-review (slice 2/4). The
 // karpathy-reviewer's JSON envelope is extended with `evaluationCost`
 // + `costRatio` (see agents/karpathy-reviewer.md §4). This service
 // is the orchestrator-side consumer of those fields.

package/dist/services/legacy/legacy-detector.js

@@ -25,7 +25,6 @@ const PATTERNS = [
 ];
 /**
  * NOT the file-size cap, and NOT a second copy of it — decided 2026-09-30, rid
- * `2026-09-30-cap-unify-01` repair cycle (F6), and recorded in
  * `.peaks/docs/lint-gate.md` §4b row 7 so the next reader does not re-litigate it.
  *
  * This is a legacy SMELL heuristic: a number above which a file is big enough to

package/dist/services/log/log-commands-service.d.ts

@@ -1,7 +1,6 @@
 /**
  * Service layer for `peaks log tail` and `peaks log ls` subcommands.
  *
- * Slice 2026-06-16-cli-logging (G4). Pure helpers that the
  * commander layer in `src/cli/commands/log-commands.ts` wraps.
  * Separated from `logger.ts` so the surface is small + testable
  * without spinning up a Commander program.
@@ -30,7 +29,6 @@ export type TailLogOptions = {
     /** Override the date (PRD AC2: PEAKS_LOG_DATE_OVERRIDE). */
     dateOverride?: string;
     /**
-     * Slice 2026-06-23-audit-4th #B2: filter by batchId. When set,
      * only entries whose `batchId` field matches are returned (and
      * the trailing-window accounting respects the post-filter total
      * so a busy day does not push old matching entries out of view).

package/dist/services/log/log-commands-service.js

@@ -1,7 +1,6 @@
 /**
  * Service layer for `peaks log tail` and `peaks log ls` subcommands.
  *
- * Slice 2026-06-16-cli-logging (G4). Pure helpers that the
  * commander layer in `src/cli/commands/log-commands.ts` wraps.
  * Separated from `logger.ts` so the surface is small + testable
  * without spinning up a Commander program.
@@ -64,7 +63,6 @@ export function tailLog(opts = {}) {
     if (total === 0) {
         return { file: null, entries: [], total: 0 };
     }
-    // Slice 2026-06-23-audit-4th #B2: batchId filter — apply AFTER the
     // read but BEFORE the trailing window, so a single batch's
     // interleaved log lines surface as a coherent sequence instead of
     // being pushed out by sibling-batch lines.

package/dist/services/log/logger.d.ts

@@ -1,7 +1,6 @@
 /**
  * JSONL file logger for peaks-loop.
  *
- * Slice 2026-06-16-cli-logging (G1, G2, G5, G6, G7).
  *
  * Default-on file logging: every peaks-loop invocation writes a
  * structured log entry to `<homedir>/.peaks/logs/peaks-loop-YYYY-MM-DD.log`

package/dist/services/log/logger.js

@@ -1,7 +1,6 @@
 /**
  * JSONL file logger for peaks-loop.
  *
- * Slice 2026-06-16-cli-logging (G1, G2, G5, G6, G7).
  *
  * Default-on file logging: every peaks-loop invocation writes a
  * structured log entry to `<homedir>/.peaks/logs/peaks-loop-YYYY-MM-DD.log`

package/dist/services/log/redact.d.ts

@@ -1,7 +1,6 @@
 /**
  * Secret redaction for peaks-loop JSONL log lines.
  *
- * Slice 2026-06-16-cli-logging (G6). The logger must NEVER write
  * a raw secret to disk. We redact at two levels:
  *  1. Field level — when a structured payload contains a key whose
  *     name matches a secret pattern (`api_key`, `password`, `token`,

package/dist/services/log/redact.js

@@ -1,7 +1,6 @@
 /**
  * Secret redaction for peaks-loop JSONL log lines.
  *
- * Slice 2026-06-16-cli-logging (G6). The logger must NEVER write
  * a raw secret to disk. We redact at two levels:
  *  1. Field level — when a structured payload contains a key whose
  *     name matches a secret pattern (`api_key`, `password`, `token`,

package/dist/services/log/retention.d.ts

@@ -1,7 +1,6 @@
 /**
  * 7-day log rotation for peaks-loop.
  *
- * Slice 2026-06-16-cli-logging (G2). Cheapest possible rotation:
  * daily files are named by UTC date, so a "new day" automatically
  * means a new file. The retention sweep runs at the start of every
  * peaks-loop invocation and removes any `peaks-loop-*.log` whose

package/dist/services/log/retention.js

@@ -1,7 +1,6 @@
 /**
  * 7-day log rotation for peaks-loop.
  *
- * Slice 2026-06-16-cli-logging (G2). Cheapest possible rotation:
  * daily files are named by UTC date, so a "new day" automatically
  * means a new file. The retention sweep runs at the start of every
  * peaks-loop invocation and removes any `peaks-loop-*.log` whose

package/dist/services/loop/loop-bee-relation-service.d.ts

@@ -1,4 +1,4 @@
-import type Database from 'better-sqlite3';
+import { type SqliteDatabase } from '../sqlite/sqlite-driver.js';
 import { ZodError } from 'zod';
 import { type LoopBeeRelation, type LoopBeeRelationInput, type LoopBeeRelationRole } from './loop-bee-relation-types.js';
 /**
@@ -46,7 +46,7 @@ export declare class LoopBeeRelationIntegrityError extends Error {
  *      — enforced at DB level (UNIQUE).
  *      — surfaced as DUP_RELATION for friendlier errors.
  *
- * The constructor takes an open better-sqlite3 database (the existing
+ * The constructor takes an open SQLite database (the existing
  * `peaks state` boundary) so callers do not have to thread a path
  * through this layer; this matches the LoopReleaseService pattern.
  *
@@ -55,7 +55,7 @@ export declare class LoopBeeRelationIntegrityError extends Error {
  */
 export declare class LoopBeeRelationService {
     private readonly db;
-    constructor(db: Database.Database);
+    constructor(db: SqliteDatabase);
     /**
      * Persist a new LoopBeeRelation row.
      *

package/dist/services/loop/loop-bee-relation-service.js

@@ -1,3 +1,4 @@
+import { constraintKind } from '../sqlite/sqlite-driver.js';
 import { ZodError } from 'zod';
 import { LoopBeeRelationSchema } from './loop-bee-relation-types.js';
 import { ensureLoopBeeRelationTable, insertLoopBeeRelation, listLoopBeeRelationsByLoop, listLoopBeeRelationsByBee, updateLoopBeeRelationRole, removeLoopBeeRelation, getLoopBeeRelation } from './loop-bee-relation-store.js';
@@ -39,7 +40,7 @@ export class LoopBeeRelationIntegrityError extends Error {
  *      — enforced at DB level (UNIQUE).
  *      — surfaced as DUP_RELATION for friendlier errors.
  *
- * The constructor takes an open better-sqlite3 database (the existing
+ * The constructor takes an open SQLite database (the existing
  * `peaks state` boundary) so callers do not have to thread a path
  * through this layer; this matches the LoopReleaseService pattern.
  *
@@ -111,15 +112,16 @@ export class LoopBeeRelationService {
             return insertLoopBeeRelation(this.db, parsed);
         }
         catch (err) {
-            const code = typeof err === 'object' && err !== null && 'code' in err ? err.code : undefined;
+            // The driver's error CODE is not portable across SQLite bindings, so the question
+            // "which constraint failed" is asked of the seam, which reads node:sqlite's `errcode`
+            // (2067 / 787) and better-sqlite3's `code` alike.
+            const kind = constraintKind(err);
             // Partial unique index on (loop_release_id) WHERE role='main'.
-            // better-sqlite3 surfaces this as SQLITE_CONSTRAINT_UNIQUE with
-            // a message naming only `loop_bee_relation.loop_release_id`
-            // (the column the partial index covers), NOT the index name.
-            // It is distinguished from the (loop_release_id, bee_release_id)
-            // composite UNIQUE violation by the absence of bee_release_id
-            // in the message.
-            if (code === 'SQLITE_CONSTRAINT_UNIQUE') {
+            // It surfaces as a UNIQUE violation whose message names only
+            // `loop_bee_relation.loop_release_id` (the column the partial index covers), NOT the
+            // index name. It is distinguished from the (loop_release_id, bee_release_id)
+            // composite UNIQUE violation by the absence of bee_release_id in the message.
+            if (kind === 'unique') {
                 const msg = err instanceof Error ? err.message : String(err);
                 if (msg.includes('loop_bee_relation.bee_release_id')) {
                     // Composite UNIQUE(loop_release_id, bee_release_id).
@@ -138,8 +140,8 @@ export class LoopBeeRelationService {
                     }
                 ]);
             }
-            // FK violations from better-sqlite3 (foreign_keys = ON).
-            if (code === 'SQLITE_CONSTRAINT_FOREIGNKEY') {
+            // FK violations (foreign_keys = ON, which `openStateDb` turns on).
+            if (kind === 'foreign-key') {
                 // Distinguish by re-checking which row is missing; the friendly
                 // pre-check above should have caught these, but defense in depth.
                 const loopStill = this.db
@@ -183,8 +185,7 @@ export class LoopBeeRelationService {
             return updateLoopBeeRelationRole(this.db, id, newRole);
         }
         catch (err) {
-            const code = typeof err === 'object' && err !== null && 'code' in err ? err.code : undefined;
-            if (code === 'SQLITE_CONSTRAINT_UNIQUE') {
+            if (constraintKind(err) === 'unique') {
                 const existing = getLoopBeeRelation(this.db, id);
                 const loopId = existing?.loop_release_id ?? '<unknown>';
                 throw new LoopBeeRelationIntegrityError('TWO_MAIN_BEES', `loop '${loopId}' already has a main bee`, [{ path: 'role', message: 'at most one main bee per loop' }]);

package/dist/services/loop/loop-bee-relation-store.d.ts

@@ -1,4 +1,4 @@
-import type Database from 'better-sqlite3';
+import type { SqliteDatabase } from '../sqlite/sqlite-driver.js';
 import type { LoopBeeRelation, LoopBeeRelationRole } from './loop-bee-relation-types.js';
 /**
  * Low-level SQLite access for the `loop_bee_relation` table. The
@@ -10,13 +10,12 @@ import type { LoopBeeRelation, LoopBeeRelationRole } from './loop-bee-relation-t
  *
  * Defense in depth:
  *   - FK constraints enforce loop_release and bee_release referential
- *     integrity (better-sqlite3 + foreign_keys = ON).
+ *     integrity (foreign_keys = ON, applied by `openStateDb`).
  *   - Partial unique index `WHERE role = 'main'` enforces "at most one
  *     main bee per loop" at the storage layer (the service layer adds
  *     a friendlier error path on top).
  *   - UNIQUE (loop_release_id, bee_release_id) prevents accidental
  *     duplicate relations between the same loop and same bee release.
- *   - The migration does NOT touch any 4.x `bee_release` column (AC-3).
  *   - Lifecycle_status check on loop_release is NOT a DB-level constraint
  *     (the retirement rule is enforced in the service layer — see
  *     `LoopBeeRelationService.create`) so the DB stays decoupled from
@@ -27,7 +26,7 @@ import type { LoopBeeRelation, LoopBeeRelationRole } from './loop-bee-relation-t
  * database. Used by tests that build their own DB without the
  * openStateDb pipeline. Idempotent.
  */
-export declare function ensureLoopBeeRelationTable(db: Database.Database): void;
+export declare function ensureLoopBeeRelationTable(db: SqliteDatabase): void;
 /**
  * Insert a LoopBeeRelation row. The row's `schema_version` is taken from
  * the input (must equal `peaks.loop-bee-relation/1`); `id` and
@@ -40,14 +39,14 @@ export declare function ensureLoopBeeRelationTable(db: Database.Database): void;
  *
  * Returns the persisted row (with `id` filled in).
  */
-export declare function insertLoopBeeRelation(db: Database.Database, row: Omit<LoopBeeRelation, 'id' | 'created_at'>): LoopBeeRelation;
+export declare function insertLoopBeeRelation(db: SqliteDatabase, row: Omit<LoopBeeRelation, 'id' | 'created_at'>): LoopBeeRelation;
 /** Read a single LoopBeeRelation row by id; returns undefined if absent. */
-export declare function getLoopBeeRelation(db: Database.Database, id: number): LoopBeeRelation | undefined;
+export declare function getLoopBeeRelation(db: SqliteDatabase, id: number): LoopBeeRelation | undefined;
 /** List LoopBeeRelation rows for a given loop_release_id (optionally filtered by role). */
-export declare function listLoopBeeRelationsByLoop(db: Database.Database, loop_release_id: string, role?: LoopBeeRelationRole): LoopBeeRelation[];
+export declare function listLoopBeeRelationsByLoop(db: SqliteDatabase, loop_release_id: string, role?: LoopBeeRelationRole): LoopBeeRelation[];
 /** List LoopBeeRelation rows for a given bee_release_id (optionally filtered by role). */
-export declare function listLoopBeeRelationsByBee(db: Database.Database, bee_release_id: number, role?: LoopBeeRelationRole): LoopBeeRelation[];
+export declare function listLoopBeeRelationsByBee(db: SqliteDatabase, bee_release_id: number, role?: LoopBeeRelationRole): LoopBeeRelation[];
 /** Update the role of an existing relation. Returns the new row, or undefined if absent. */
-export declare function updateLoopBeeRelationRole(db: Database.Database, id: number, newRole: LoopBeeRelationRole): LoopBeeRelation | undefined;
+export declare function updateLoopBeeRelationRole(db: SqliteDatabase, id: number, newRole: LoopBeeRelationRole): LoopBeeRelation | undefined;
 /** Remove a LoopBeeRelation row by id. Returns true if a row was deleted. */
-export declare function removeLoopBeeRelation(db: Database.Database, id: number): boolean;
+export declare function removeLoopBeeRelation(db: SqliteDatabase, id: number): boolean;