peaks-loop 4.1.1 → 4.1.3

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

@@ -9,10 +9,8 @@ export interface Heartbeat {
 export type HeartbeatStatus = 'queued' | 'running' | 'finalizing' | 'done' | 'failed' | 'stale' | 'cancelled' | 'no-execution' | 'never-started' | 'unreadable';
 export type DispatchRecordStatus = 'queued' | 'running' | 'finalizing' | 'done' | 'failed' | 'cancelled' | 'no-execution' | 'stale' | 'never-started' | 'unreadable';
 export type DispatchOutcome = 'success' | 'failed' | 'timeout' | 'cancelled' | 'no-execution';
-/** G2+G5+G6 dispatch record schema (AC-26 + AC-34). */
 export interface DispatchRecord {
     /**
-     * Slice 2026-07-29-worktree-l2-extended Part 4.C: schema v3 makes
      * `leaseId` a structurally required field (was `leaseId?: string | null`
      * in v2). The v3 upgrade is a "fill in" migration: every dispatch
      * writer knows its lease id at construction time (Part 2.C's
@@ -23,7 +21,6 @@ export interface DispatchRecord {
      * moves the optional off the type and adds the field to the
      * 4 literal sites in one pass.
      *
-     * Slice 2026-07-29-worktree-l2-extended Part 7: schema v3.1 adds
      * `isolationStartedAt: string | null` for the L4 isolation
      * bridge (Part 8 container POC). It's the ISO timestamp of
      * when the isolation mode was set up (e.g. when the worktree
@@ -51,15 +48,12 @@ export interface DispatchRecord {
     readonly sessionId: string;
     readonly prompt: string;
     readonly toolCall: SubAgentToolCall;
-    /** G5 batch id (AC-27) — uuid-like opaque token grouping one batch. */
     readonly batchId: string;
-    /** G6 fields (AC-34) — backward compat: defaults on read. */
     readonly heartbeats: readonly Heartbeat[];
     readonly lastBeatAt: string | null;
     readonly status: DispatchRecordStatus;
     readonly stage: string | null;
     /**
-     * Slice 2026-07-29-worktree-l2-extended Part 3.A + Part 4.C: the
      * worktree lease id stamped on this dispatch (via `peaks sub-agent
      * dispatch --isolation worktree`). The release hook (see
      * markCompleted + `peaks sub-agent heartbeat --status done`)
@@ -76,7 +70,6 @@ export interface DispatchRecord {
      */
     readonly leaseId: string | null;
     /**
-     * Slice 2026-07-29-worktree-l2-extended Part 7: ISO timestamp of
      * when the isolation mode was set up. For `--isolation worktree`
      * this is the moment `peaks worktree spawn` returned; for
      * `--isolation container` (Part 8) it's when the container
@@ -87,7 +80,6 @@ export interface DispatchRecord {
      */
     readonly isolationStartedAt: string | null;
     /**
-     * Slice 2026-08-01-subagent-merge-and-e2e (Task 7): v3.2 schema
      * bump. One entry per pid the parent best-effort-killed during
      * the service-shutdown phase of the merge-back pipeline (see
      * src/services/dispatch/service-shutdown.ts). Empty array when
@@ -107,7 +99,6 @@ export interface DispatchRecord {
         readonly reason?: string;
     }>;
     /**
-     * Slice 2026-08-01-subagent-merge-and-e2e (Task 7): v3.2 schema
      * bump. Counts how many merge attempts the parent session has
      * made against this dispatch's branch. The conflict-replay
      * orchestrator bumps this on each retry (bounded to ONE re-dispatch
@@ -198,7 +189,6 @@ export type LifecycleInput = {
     artifactPaths?: readonly string[];
     now?: () => Date;
     /**
-     * Slice 2026-06-23-audit-4th #A4: trusted project root. Required
      * so the active-dispatches index can be updated without deriving
      * the root from the recordPath (the same anti-pattern that
      * audit-3rd #1 fixed for heartbeat). The CLI / LLM-side runner

package/dist/services/dispatch/dispatch-record-upgrade-fields.js

@@ -10,13 +10,11 @@ export function parseUpgradeRecordLegacyFields(obj) {
     const requestId = stringField(obj, 'requestId');
     const sessionId = stringField(obj, 'sessionId');
     const prompt = stringField(obj, 'prompt');
-    // Slice 2026-06-23-audit-4th #C2: preserve toolCallVersion on read.
     const toolCall = parseLegacyToolCallField(obj);
     const createdAt = stringField(obj, 'createdAt');
     return { role, requestId, sessionId, prompt, toolCall, createdAt };
 }
 /**
- * Slice 2026-06-23-audit-4th #C2 — pre-versioning records default to
  * '2.0.0' (the pre-#C2 implicit shape; matches the version stamped by
  * every current dispatcher). Throws exactly where the inline block threw.
  */
@@ -40,7 +38,6 @@ function parseLegacyToolCallField(obj) {
 function parseLegacyStateFields(obj) {
     const heartbeats = Array.isArray(obj.heartbeats) ? obj.heartbeats.filter(isValidHeartbeat) : [];
     const lastBeatAt = typeof obj.lastBeatAt === 'string' ? obj.lastBeatAt : null;
-    // Slice 2026-07-29-dispatch-stall-governance / S1 (UQ-1) — `no-execution`
     // keeps its natural "dispatched, never executed" reading; an unparseable
     // status field now resolves to a *distinct* `unreadable` label so the
     // caller can tell "corrupt record" apart from "record written, no first
@@ -104,17 +101,14 @@ export function parseUpgradeRecordMigrationFields(obj) {
     };
 }
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S5 (AC-5.1 / PB-2)
  * — legacy records (pre-slice) had no `stage` field. The reader
  * defaults to `null` so the watch surface can tell "no stage ever
  * emitted" apart from "stage: ''" (which is itself a *valid*
  * round-trip through the writer — an empty stage is rejected by
  * `setStage`, but a record that round-tripped through a non-strict
  * tool would land here).
- * Slice 2026-07-29-worktree-l2-extended Part 3.A: legacy records
  * have no `leaseId`; default to `null` so the auto-release hook
  * in `markCompleted` is a clean no-op for them.
- * Slice 2026-07-29-worktree-l2-extended Part 7: v3 → v3.1
  * migration. Legacy records have no `isolationStartedAt`; default
  * to `null`. v3.1 readers can treat the field as opt-in.
  */
@@ -128,7 +122,6 @@ function parseStallGovernanceFields(obj) {
     };
 }
 /**
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 7): v3.1 → v3.2
  * migration. Legacy v3.1 records have no `serviceKill` or
  * `mergeBackAttempts` fields. Default to [] and 0 so the
  * merge-back-runner (Task 9) can read either schema on disk.

package/dist/services/dispatch/dispatch-record-upgrade-guards.js

@@ -23,7 +23,6 @@ function isHeartbeatStatus(v) {
         v === 'done' ||
         v === 'failed' ||
         v === 'stale' ||
-        // Slice 2026-07-29-dispatch-stall-governance / S2 — accept the
         // S1 terminal members so a sub-agent can report `cancelled`,
         // `no-execution`, `never-started`, or `unreadable` through the
         // heartbeat CLI.
@@ -41,7 +40,6 @@ export function isDispatchStatus(v) {
         v === 'cancelled' ||
         v === 'no-execution' ||
         v === 'stale' ||
-        // Slice 2026-07-29-dispatch-stall-governance / S1 — accept the two
         // new terminal members from the startup-timeout service.
         v === 'never-started' ||
         v === 'unreadable');

package/dist/services/dispatch/dispatch-record-writer.d.ts

@@ -21,17 +21,14 @@ export interface ActiveDispatchEntry {
     readonly status: 'queued' | 'running' | 'finalizing' | 'done' | 'failed' | 'cancelled' | 'stale' | 'no-execution' | 'never-started' | 'unreadable';
 }
 /**
- * Slice 2026-06-23-audit-4th #A4: read the active-dispatches index
  * for a session. Returns the current map<recordPath, entry>. Used
  * by the LLM-side runner to discover in-flight records on restart.
  * Returns an empty map when the index file is missing or corrupt
  * (the on-disk records directory is the next fallback).
  */
 export declare function readActiveDispatchIndex(projectRoot: string, sessionId: string): Record<string, ActiveDispatchEntry>;
-/** Slice 2026-06-23-audit-4th #A3: default TTL for dispatch records. */
 export declare const DISPATCH_RECORD_TTL_DAYS = 30;
 /**
- * Slice 2026-06-23-audit-4th #A3: is this dispatch record an orphan
  * (older than DISPATCH_RECORD_TTL_DAYS or already GC'd)? Mirrors
  * `isOrphanChannel` in shared-channel.ts so a future
  * `peaks sub-agent cleanup` umbrella can run all three sweeps
@@ -55,7 +52,6 @@ export declare function applyTruncation(entries: readonly Heartbeat[]): {
     truncated: boolean;
 };
 /**
- * Slice 2026-07-29-worktree-l2-extended Part 3.A: fire-and-forget
  * auto-release for the lease owned by a dispatch. Called from
  * `markCompleted` (terminal status) and from the heartbeat CLI
  * (`--status done`).
@@ -91,7 +87,6 @@ export declare function markDisposed(recordPath: string, now?: () => Date): {
     record: DispatchRecord;
 };
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S5 (AC-5.1) — promote
  * the record's `stage` field. Rejects unknown values with
  * `INVALID_STAGE`; the LLM-side runner surfaces the error so the
  * sub-agent can pick from the bounded enum in ./stage-enum.ts.

package/dist/services/dispatch/dispatch-record-writer.js

@@ -1,12 +1,9 @@
 /**
- * Dispatch record writer — slice 2026-06-07-sub-agent-dispatch-decouple (G2 + G5 + G6).
  *
  * Owns the on-disk format of `.peaks/_sub_agents/<sid>/dispatch-<rid>-<ts>.json`:
  *   - G2: atomic write helper (mkdirSync recursive + tmp + rename) and
  *     R-2 guard (path must live under `.peaks/_sub_agents/<sid>/`).
  *   - G5: lifecycle schema (`createdAt` / `completedAt` / `outcome` /
- *     `artifactPaths` / `disposed` / `disposedAt`) per AC-26 + RL-6..RL-9.
- *   - G6: heartbeat schema upgrade per AC-33/AC-34 — `heartbeats[]` +
  *     `lastBeatAt` + `status` aggregate. Read-side backward compat
  *     supplies defaults for old records missing the G6 fields.
  *
@@ -47,7 +44,6 @@ export function writeInitialDispatchRecord(input) {
     const safePath = assertSafeDispatchRecordPath(path, projectRoot);
     const record = buildInitialDispatchRecord(input, now);
     writeAtomic(safePath, record);
-    // Slice 2026-06-23-audit-4th #A4: register the path in the
     // session's active-dispatches index so a future restart can
     // discover in-flight records without scanning the directory.
     // The index is best-effort (no lock): the on-disk record is the
@@ -85,7 +81,6 @@ function buildInitialDispatchRecord(input, now) {
         requestId,
         sessionId,
         prompt,
-        // Slice 2026-06-23-audit-4th #C2: propagate toolCallVersion.
         // The dispatcher's buildToolCall already stamps it (claude-code 2.0.0
         // etc.); we re-default to '2.0.0' if absent so the on-disk record
         // is self-describing without reading the dispatcher source.
@@ -94,11 +89,9 @@ function buildInitialDispatchRecord(input, now) {
         heartbeats: [],
         lastBeatAt: null,
         status: 'queued',
-        // Slice 2026-07-29-dispatch-stall-governance / S5 (AC-5.1) — new
         // records start with `stage: null`; the sub-agent promotes it
         // through `setStage` / the heartbeat CLI's `--stage` flag.
         stage: null,
-        // Slice 2026-07-29-worktree-l2-extended Part 3.A: when the
         // dispatch was issued with --isolation worktree, persist the
         // lease id so the finalize-time release hook in markCompleted
         // can fire. Validation is the same 16-hex regex the gate uses
@@ -108,7 +101,6 @@ function buildInitialDispatchRecord(input, now) {
         leaseId: typeof input.leaseId === 'string' && /^[a-f0-9]{16}$/.test(input.leaseId)
             ? input.leaseId
             : null,
-        // Slice 2026-07-29-worktree-l2-extended Part 7: v3.1 field.
         // ISO timestamp when the isolation mode was set up. Default
         // null when the dispatch did not request isolation. We do
         // NOT validate the format — the writer is the source of
@@ -117,7 +109,6 @@ function buildInitialDispatchRecord(input, now) {
         isolationStartedAt: typeof input.isolationStartedAt === 'string' && input.isolationStartedAt.length > 0
             ? input.isolationStartedAt
             : null,
-        // Slice 2026-08-01-subagent-merge-and-e2e (Task 7): v3.2 fields.
         // New records start with empty serviceKill and zero attempts;
         // the merge-back-runner (Task 9) populates them in place.
         serviceKill: [],
@@ -218,7 +209,6 @@ function unregisterActiveDispatch(input) {
     }
     if (input.recordPath in index) {
         index[input.recordPath] = { ...index[input.recordPath], status: input.status };
-        // Slice 2026-07-29-dispatch-stall-governance / S1 — `never-started`
         // and `unreadable` are terminal (the startup-timeout service writes
         // them as terminal markers). Unregister on the full terminal set.
         if (input.status === 'done' ||
@@ -235,7 +225,6 @@ function unregisterActiveDispatch(input) {
     }
 }
 /**
- * Slice 2026-06-23-audit-4th #A4: read the active-dispatches index
  * for a session. Returns the current map<recordPath, entry>. Used
  * by the LLM-side runner to discover in-flight records on restart.
  * Returns an empty map when the index file is missing or corrupt
@@ -262,10 +251,8 @@ export function readActiveDispatchIndex(projectRoot, sessionId) {
         return {};
     }
 }
-/** Slice 2026-06-23-audit-4th #A3: default TTL for dispatch records. */
 export const DISPATCH_RECORD_TTL_DAYS = 30;
 /**
- * Slice 2026-06-23-audit-4th #A3: is this dispatch record an orphan
  * (older than DISPATCH_RECORD_TTL_DAYS or already GC'd)? Mirrors
  * `isOrphanChannel` in shared-channel.ts so a future
  * `peaks sub-agent cleanup` umbrella can run all three sweeps
@@ -308,7 +295,6 @@ export function appendHeartbeat(input) {
         lastBeatAt: entry.at,
         status: mapStatusToAggregate(status, existing.status)
     };
-    // Slice 2026-06-23-audit-3rd #3: wrap the read-then-write in a file
     // lock. Without the lock, a heartbeat arriving 100ms before
     // markCompleted can be silently discarded — the parent's view of the
     // sub-agent shows "completed" but the last progress update is lost.
@@ -349,7 +335,6 @@ function mapStatusToAggregate(latest, current) {
     return latest;
 }
 /**
- * Slice 2026-07-29-worktree-l2-extended Part 3.A: fire-and-forget
  * auto-release for the lease owned by a dispatch. Called from
  * `markCompleted` (terminal status) and from the heartbeat CLI
  * (`--status done`).
@@ -439,7 +424,6 @@ async function spawnLeaseReleaseChild(args) {
         child.unref();
     }
     catch (e) {
-        // Slice 2026-07-29-worktree-l2-extended Part 4.A: surface
         // auto-release failures to the observability stream so the
         // dashboard can alert. The spawn-attempt itself threw (not
         // a child-process exit-code failure — those are not
@@ -471,7 +455,6 @@ async function spawnLeaseReleaseChild(args) {
 }
 /** Mark a record as completed (success / failed / cancelled / no-execution). */
 export function markCompleted(input) {
-    // Slice 2026-06-23-audit-3rd #3: lock + re-read so a concurrent
     // heartbeat arriving just before markCompleted is preserved in the
     // final record.
     const result = withFileLockSync(input.recordPath, () => {
@@ -502,7 +485,6 @@ export function markCompleted(input) {
         result.record.graphRef !== null) {
         scheduleGraphEnvelopeTransition(input, result.record);
     }
-    // Slice 2026-06-23-audit-4th #A4: update the active-dispatches
     // index. Best-effort (the on-disk record is the source of truth);
     // we only attempt the update when the trusted projectRoot is
     // available so a malicious recordPath cannot redirect the index
@@ -521,7 +503,6 @@ export function markCompleted(input) {
             /* best-effort */
         }
     }
-    // Slice 2026-07-29-worktree-l2-extended Part 3.A: finalize-time
     // lease release. The terminal status (done/failed/cancelled/
     // no-execution) means the sub-agent is no longer using the
     // worktree; auto-release closes the loop. The release is detached
@@ -625,7 +606,6 @@ export function markDisposed(recordPath, now = () => new Date()) {
     });
 }
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S5 (AC-5.1) — promote
  * the record's `stage` field. Rejects unknown values with
  * `INVALID_STAGE`; the LLM-side runner surfaces the error so the
  * sub-agent can pick from the bounded enum in ./stage-enum.ts.
@@ -692,7 +672,6 @@ export function readRecords(paths) {
 }
 function writeAtomic(path, record) {
     const dir = dirname(path);
-    // Slice 2026-06-23-audit-3rd #11: skip mkdirSync when the dir already
     // exists (every heartbeat + every dispatch read-modify-write).
     if (!existsSync(dir)) {
         mkdirSync(dir, { recursive: true });

package/dist/services/dispatch/dispatch-sub-agent.d.ts

@@ -1,5 +1,4 @@
 /**
- * F5 follow-up (sediment 2026-08-11-rid-001-redo-fake-green-recovery-closure
  * §Lesson 1): synchronous anti-fake-green file-existence gate. Runs
  * `git ls-files <glob>` against `projectRoot` and returns the matching
  * tracked file paths (relative to projectRoot). Empty array when no

package/dist/services/dispatch/dispatch-sub-agent.js

@@ -1,5 +1,4 @@
 /**
- * F5 follow-up (sediment 2026-08-11-rid-001-redo-fake-green-recovery-closure
  * §Lesson 1): synchronous anti-fake-green file-existence gate. Runs
  * `git ls-files <glob>` against `projectRoot` and returns the matching
  * tracked file paths (relative to projectRoot). Empty array when no

package/dist/services/dispatch/e2e-fixtures.js

@@ -1,7 +1,6 @@
 /**
  * e2e-fixtures — pure reader for `qa/e2e/<slice>/<scenario>/*.md`.
  *
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 4). The parent session
  * calls `peaks e2e verify --slice <rid>` after the merge-back step. The
  * CLI delegates to `runE2EVerify` (Task 10), which uses this reader to
  * enumerate the fixtures for the slice. The reader returns one of

package/dist/services/dispatch/file-overlap-wave-planner.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-10-dispatch-token-and-swarm §3 — file-overlap-aware
  * parallel scheduling.
  *
  * Problem: fan-out is mandatory, but the orchestrator serializes whenever

package/dist/services/dispatch/file-overlap-wave-planner.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-10-dispatch-token-and-swarm §3 — file-overlap-aware
  * parallel scheduling.
  *
  * Problem: fan-out is mandatory, but the orchestrator serializes whenever

package/dist/services/dispatch/isolation-lease.d.ts

@@ -1,5 +1,4 @@
 /**
- * Part 2.C (slice 2026-07-29-worktree-l2-extended) — spawn a worktree
  * lease by shelling out to `peaks worktree spawn` (avoid re-implementing
  * the lease-write + git-worktree-add sequence in this file). The CLI
  * does the lease write, the git worktree add, AND the error handling;
@@ -23,7 +22,6 @@ export declare function spawnWorktreeLease(args: {
     expiresAt: number;
 }>;
 /**
- * Slice 2026-07-29-worktree-l2-extended Part 12: container
  * isolation bridge. Shells out to `peaks container spawn` to
  * run `docker run` + write the container lease. Returns the
  * leaseId the dispatch record needs to persist. The shape is

package/dist/services/dispatch/isolation-lease.js

@@ -1,6 +1,5 @@
 import { spawn as childProcessSpawn } from 'node:child_process';
 /**
- * Part 2.C (slice 2026-07-29-worktree-l2-extended) — spawn a worktree
  * lease by shelling out to `peaks worktree spawn` (avoid re-implementing
  * the lease-write + git-worktree-add sequence in this file). The CLI
  * does the lease write, the git worktree add, AND the error handling;
@@ -85,7 +84,6 @@ export function spawnWorktreeLease(args) {
     });
 }
 /**
- * Slice 2026-07-29-worktree-l2-extended Part 12: container
  * isolation bridge. Shells out to `peaks container spawn` to
  * run `docker run` + write the container lease. Returns the
  * leaseId the dispatch record needs to persist. The shape is

package/dist/services/dispatch/service-shutdown.js

@@ -2,7 +2,6 @@
  * service-shutdown — best-effort kill helper for sub-agent-registered
  * local services.
  *
- * Slice 2026-08-01-subagent-merge-and-e2e (Task 3). The parent session
  * reads `.peaks/_runtime/<sid>/dispatch/<dispatchId>/service-registrations.json`
  * (written by `peaks sub-agent shutdown register --pid <pid> --name <label>`)
  * and calls `killRegisteredServices` BEFORE the merge-back step so a

package/dist/services/dispatch/session-capsule.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-09-10-dispatch-token-and-swarm §4 — session capsule reader.
  *
  * The orchestrator publishes already-known background ONCE per session
  * through the existing G8.4 channel:

package/dist/services/dispatch/slice-dag-types.d.ts

@@ -39,7 +39,6 @@ export interface SliceNode {
      */
     readonly complexity?: SliceComplexity;
     /**
-     * Slice 2026-09-10-dispatch-token-and-swarm §3: files this slice is
      * expected to touch. When EVERY node of a topological level declares
      * `files`, `--from-dag` emits a file-overlap wave plan (`firstLevelWaves`)
      * so the LLM can fan the level out without serializing on a shared file.

package/dist/services/dispatch/slice-dag.js

@@ -82,7 +82,6 @@ export function validateDag(dag) {
         if (n.complexity !== undefined && !isSliceComplexity(n.complexity)) {
             throw new InvalidSliceDagError(`node ${n.id} complexity must be one of ${SLICE_COMPLEXITIES.join('|')} when present`);
         }
-        // Slice 2026-09-10 §3: optional file list. Only shape-checked when
         // present so pre-existing DAGs stay valid.
         if (n.files !== undefined &&
             (!isArray(n.files) || n.files.some((f) => typeof f !== 'string' || f.length === 0))) {
@@ -205,7 +204,6 @@ export function serializeDag(dag) {
         ...(n.foundation !== undefined ? { foundation: n.foundation } : {}),
         ...(n.upstreamSync !== undefined ? { upstreamSync: n.upstreamSync } : {}),
         ...(n.complexity !== undefined ? { complexity: n.complexity } : {}),
-        // Slice 2026-09-10 §3: only present when declared, so the hash of a
         // file-less DAG is unchanged.
         ...(n.files !== undefined ? { files: [...n.files] } : {})
     }));

package/dist/services/dispatch/stage-enum.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S5 — bounded stage
  * vocabulary.
  *
  * Why a bounded enum (not a free-form string):

package/dist/services/dispatch/stage-enum.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S5 — bounded stage
  * vocabulary.
  *
  * Why a bounded enum (not a free-form string):

package/dist/services/dispatch/startup-timeout.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S1 — startup-timeout service.
  *
  * Why a separate module (vs adding the logic inline to
  * `dispatch-record-writer.ts`):

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

@@ -34,7 +34,6 @@ import { awaitBatch as awaitBatchUnified } from './await-batch.js';
  *    for the MVP; the real cross-process version uses heartbeat polling).
  */
 export async function awaitClaudeCodeBatch(input) {
-    // Slice 2026-07-29-dispatch-stall-governance / S4 (G8) — this
     // function is now a thin wrapper around the unified `awaitBatch`
     // service. The back-compat envelope shape is preserved (one
     // `SubAgentBatchResult` per record path) so the S3 characterization
@@ -42,7 +41,6 @@ export async function awaitClaudeCodeBatch(input) {
     // codex / cursor wrappers below. The new typed outcome
     // lives on the unified service; the S4 fail-fast test pins it.
     //
-    // Slice 2026-07-30-nightshift: claude-code does NOT use a
     // per-IDE note prefix. The 1.4 dogfood contract says the done
     // note is `null` (raw outcome) and the failed note is the raw
     // `outcome` string with no prefix. The 3 non-Claude IDEs
@@ -58,7 +56,6 @@ export async function awaitClaudeCodeBatch(input) {
     return unified.results;
 }
 export async function pollDispatchRecords(input, opts) {
-    // Slice 2026-07-29-dispatch-stall-governance / S4 (G8) — this
     // function is now a thin wrapper around the unified `awaitBatch`
     // service. Pre-S4 it diverged from `awaitClaudeCodeBatch` in
     // (a) the default-fallback source and (b) the `Math.max(deadline, 0)`

package/dist/services/dispatch/sub-agent-dispatcher-types.d.ts

@@ -34,7 +34,6 @@ export interface SubAgentToolCall {
     readonly name: string;
     readonly args: Readonly<Record<string, unknown>>;
     /**
-     * Slice 2026-06-23-audit-4th #C2: toolCall version. The IDE's
      * arg shape can change between versions (e.g. Claude Code's
      * `subagent_type: "general-purpose"` may become
      * `subagent_type: "claude-code-3.5"` in a future release). The

package/dist/services/dispatch/sub-agent-dispatcher.js

@@ -24,7 +24,6 @@
  * `peaks sub-agent dispatch <role>`, and the IDE-private tool
  * name flows through the returned `data.toolCall` at runtime.
  *
- * Cross-reference: PRD #002 G1 (AC-1..AC-5); RD tech-doc-002 §2.
  */
 import { existsSync, readFileSync } from 'node:fs';
 import { awaitClaudeCodeBatch, pollDispatchRecords } from './sub-agent-batch-await.js';
@@ -48,7 +47,6 @@ export const claudeCodeSubAgentDispatcher = {
             description: `${role} for rid=${requestId}`,
             prompt
         },
-        // Slice 2026-06-23-audit-4th #C2: stamp the IDE-arg shape
         // version. When Claude Code changes the Task args shape (e.g.
         // a new subagent_type value), bump this and the dispatch record
         // propagates it so a future reader can detect a stale record.

package/dist/services/dispatch/test-tool-detection.d.ts

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-24-test-tool-detection-injection.
  *
  * The Test Tool Detection block is prepended to every sub-agent prompt
  * dispatched by peaks-loop (both the single-dispatch chokepoint in
@@ -27,7 +26,6 @@
  *  the dispatch CLI always prepends it. This is a guarantee, not a
  *  suggestion.
  *
- * 2026-09-10-dispatch-block-d (Option D): ONE block for EVERY role. The
  * runner-table EXAMPLES were dropped — they were never rules, and
  * `package.json#scripts.test` is the source of truth at run time — while
  * the one missing real rule is stated inline: PB-5, i.e. repo-defined
@@ -46,7 +44,6 @@ export declare const TEST_TOOL_DETECTION_BLOCK = "## Test Tool Detection (mandat
  */
 export declare function formatTestToolDetection(): string;
 /**
- * Slice 2026-07-29-dispatch-stall-governance / S5 (AC-4.1 / AC-4.2) —
  * pure scope classifier. Returns a typed result so callers (the
  * dispatch prompt template, future test-runner bridges) can decide
  * whether the command is allowed, refused, or requires the explicit

package/dist/services/dispatch/test-tool-detection.js

@@ -1,5 +1,4 @@
 /**
- * Slice 2026-06-24-test-tool-detection-injection.
  *
  * The Test Tool Detection block is prepended to every sub-agent prompt
  * dispatched by peaks-loop (both the single-dispatch chokepoint in
@@ -27,7 +26,6 @@
  *  the dispatch CLI always prepends it. This is a guarantee, not a
  *  suggestion.
  *
- * 2026-09-10-dispatch-block-d (Option D): ONE block for EVERY role. The
  * runner-table EXAMPLES were dropped — they were never rules, and
  * `package.json#scripts.test` is the source of truth at run time — while
  * the one missing real rule is stated inline: PB-5, i.e. repo-defined

package/dist/services/distribution/mcp-install-runner.d.ts

@@ -0,0 +1,21 @@
+import type { McpInstallCommand, McpInstallOutcome, McpInstallRunner } from './mcp-install.js';
+/**
+ * Ceiling on ONE harness command. `spawnSync` without `timeout` has no ceiling
+ * at all, and the failure it lets through is measured, not hypothetical: a
+ * real harness binary on this host starts and then does not return within 25 s.
+ * Unbounded, that blocks `peaks mcp install` in the foreground forever. Same
+ * class the MCP CLI executor bounds (`cli-executor.ts`), set to twice its 15 s
+ * because the child is the harness's binary and its startup is its own to
+ * spend. A plan is at most three commands, so the install is bounded at 3x.
+ */
+export declare const MCP_INSTALL_TIMEOUT_MS = 30000;
+/**
+ * One harness command, with the deadline applied. `windowsHide` is the tree's
+ * spawn contract: a CLI that briefly runs a harness must not flash a console
+ * window on a desktop OS. `timeoutMs` is a parameter only so a test can watch
+ * the deadline fire without waiting out the production value — callers want
+ * `spawnMcpInstallRunner`, which fixes it.
+ */
+export declare function spawnMcpInstallCommand(command: McpInstallCommand, timeoutMs?: number): McpInstallOutcome;
+/** The production runner: the deadline above, and nothing else left to decide. */
+export declare const spawnMcpInstallRunner: McpInstallRunner;

package/dist/services/distribution/mcp-install-runner.js

@@ -0,0 +1,59 @@
+// src/services/distribution/mcp-install-runner.ts
+//
+// The production runner behind the vendor-neutral MCP registration engine
+// (`mcp-install.ts`): it runs one harness command under a deadline and reports
+// what the process said. It lives in its own module only so the engine keeps its
+// size; the engine RE-EXPORTS it, so every caller still imports it from
+// `mcp-install.js` and no import path moved.
+//
+// THE FIELD THIS MODULE EXISTS FOR. A run that exits non-zero ANSWERED the
+// question — "no such registration" — and a run the deadline kills, or one that
+// never launches, did not: `answered: false` is the only place that distinction
+// is born, and it is what stops `peaks mcp uninstall` from reporting a hung
+// harness's scope as "nothing was there".
+import { spawnSync } from 'node:child_process';
+/**
+ * Ceiling on ONE harness command. `spawnSync` without `timeout` has no ceiling
+ * at all, and the failure it lets through is measured, not hypothetical: a
+ * real harness binary on this host starts and then does not return within 25 s.
+ * Unbounded, that blocks `peaks mcp install` in the foreground forever. Same
+ * class the MCP CLI executor bounds (`cli-executor.ts`), set to twice its 15 s
+ * because the child is the harness's binary and its startup is its own to
+ * spend. A plan is at most three commands, so the install is bounded at 3x.
+ */
+export const MCP_INSTALL_TIMEOUT_MS = 30_000;
+/**
+ * One harness command, with the deadline applied. `windowsHide` is the tree's
+ * spawn contract: a CLI that briefly runs a harness must not flash a console
+ * window on a desktop OS. `timeoutMs` is a parameter only so a test can watch
+ * the deadline fire without waiting out the production value — callers want
+ * `spawnMcpInstallRunner`, which fixes it.
+ */
+export function spawnMcpInstallCommand(command, timeoutMs = MCP_INSTALL_TIMEOUT_MS) {
+    const result = spawnSync(command.command, [...command.args], {
+        stdio: 'pipe',
+        windowsHide: true,
+        encoding: 'utf8',
+        timeout: timeoutMs
+    });
+    if (result.error !== undefined) {
+        // `spawnSync` kills the child at the deadline and reports its own timeout as
+        // ETIMEDOUT. A deadline and a launch failure are different facts, but they
+        // share the one that matters here: the harness never rendered a verdict.
+        const timedOut = result.error.code === 'ETIMEDOUT';
+        return {
+            ok: false,
+            answered: false,
+            detail: timedOut
+                ? `timed out after ${timeoutMs} ms and was killed: ${command.command} ${command.args.join(' ')}`
+                : result.error.message
+        };
+    }
+    if (result.status === 0) {
+        return { ok: true, detail: '' };
+    }
+    const stderr = (result.stderr ?? '').trim();
+    return { ok: false, detail: stderr.length > 0 ? stderr : `exit ${result.status ?? 'unknown'}` };
+}
+/** The production runner: the deadline above, and nothing else left to decide. */
+export const spawnMcpInstallRunner = (command) => spawnMcpInstallCommand(command);