peaks-loop 4.1.0 → 4.1.2

package/dist/cli/commands/verdict-aggregate-command.js

@@ -8,11 +8,8 @@ import { isUnsafePathInput } from '../../shared/path-safety.js';
 import { DEFAULT_REQUEST_TYPE } from '../../services/artifacts/artifact-prerequisites.js';
 import { REQUEST_ID_PATTERN } from '../../services/artifacts/request-artifact-service.js';
 import { contractEvidencePaths } from '../../services/workflow/pipeline-verify-gate-support.js';
-// Slice `2026-09-14-audit-artifact-rid-scoping`: the audit/review evidence
 // filenames carry the rid. The ridless names are the pre-rid locations and
-// stay readable during the back-compat window. `mut/` is NOT rid-scoped —
 // see `MUT_REPORT` in `artifact-prerequisites.ts`: no producer in the repo
-// can write a rid-scoped mut report, so probing a templated name here would
 // look for a file that no writer can create.
 //
 // The candidate lists are read FROM the contract — the same
@@ -27,7 +24,6 @@ const MUT_REL = 'mut/mut-report.json';
 const QA_REL = 'qa/test-reports';
 /**
  * The declared tiers for one artifact name, primary first. Probed by the name
- * this command used before the rid-scoping (the table matches it as either
  * the primary or a legacy tier), so the lookup survives the primary moving.
  * `verdict aggregate` is request-type-agnostic and every fanout-trigger type
  * declares these artifacts identically, so the default type's list is the
@@ -94,7 +90,6 @@ export function registerVerdictAggregateCommands(program, io) {
         }
         try {
             const sources = {
-                // v2.13.3 AC-1: use the canonical markdown-aware parser from
                 // envelopes.ts. The old inline `parseSecurityFromMarkdown`
                 // only understood shape A (`- [SEV] dim @ file:line — hint`),
                 // so real dogfood fixtures using shape B (`- HIGH: hint in file:line`)
@@ -157,7 +152,6 @@ export function registerVerdictAggregateCommands(program, io) {
     });
 }
 function readAudit(projectRoot, sid, rid, rels, parse) {
-    // Canonical rid-scoped location first, then the pre-rid locations.
     for (const rel of rels) {
         const path = join(projectRoot, '.peaks', '_runtime', sid, rel.replace('<rid>', rid));
         if (existsSync(path))
@@ -195,7 +189,6 @@ function readQa(projectRoot, sid, rid) {
 function parseMutJson(json) {
     return parseMutEnvelope(json);
 }
-// v2.13.3 AC-1: removed inline `parseSecurityFromMarkdown` /
 // `parsePerfFromMarkdown` (only handled shape A). The canonical
 // `parseSecurityEnvelope` / `parsePerfEnvelope` in envelopes.ts now
 // own the markdown parse + JSON back-compat fallback.

package/dist/cli/commands/vm-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * `peaks vm spawn | release` — slice 2026-07-29-worktree-l2-extended Part 35.
  *
  * L4 VM isolation runtime. Parallels the design of
  * `container-commands.ts` (Part 12, docker) and

package/dist/cli/commands/vm-commands.js

@@ -1,5 +1,4 @@
 /**
- * `peaks vm spawn | release` — slice 2026-07-29-worktree-l2-extended Part 35.
  *
  * L4 VM isolation runtime. Parallels the design of
  * `container-commands.ts` (Part 12, docker) and
@@ -34,6 +33,8 @@ import { findProjectRoot } from '../../services/config/config-safety.js';
 import { getCurrentSessionId } from '../../services/skills/skill-presence-service.js';
 import { atomicWriteJson } from '../../services/ide/shared/atomic-json.js';
 import { DEFAULT_VM_IMAGE, deserializeVmLease, finalizeVmLease, generateVmLeaseId, markVmReleased, ttlForVmRole, vmLeaseFilePath } from '../../services/vm/vm-lease.js';
+import { detectHypervisor } from './vm-hypervisor-probe.js';
+import { registerVmStatusCommand } from './vm-status-command.js';
 function joinPathSession(projectRoot, sessionId) {
     return `${projectRoot.replace(/[\\/]+$/, '')}/.peaks/_runtime/${sessionId}`;
 }
@@ -45,34 +46,6 @@ function resolveTtlMs(raw, role) {
         return ttlForVmRole(role);
     return parsed;
 }
-function detectHypervisor(requested) {
-    let binary;
-    switch (requested) {
-        case 'kvm':
-            binary = 'virsh';
-            break;
-        case 'hyperkit':
-            binary = 'hvftool';
-            break;
-        case 'hyperv':
-            binary = 'hvc';
-            break;
-    }
-    try {
-        const v = execSync(`${binary} --version`, {
-            stdio: ['ignore', 'pipe', 'pipe'],
-            encoding: 'utf8',
-            windowsHide: true
-        });
-        if (requested === 'kvm' && !existsSync('/dev/kvm')) {
-            return { ok: false, stderr: 'KVM kernel module not loaded (/dev/kvm absent)' };
-        }
-        return { ok: true, binary: `${binary} (${v.trim().split('\n')[0] ?? ''})` };
-    }
-    catch (err) {
-        return { ok: false, stderr: err.message };
-    }
-}
 function spawnVmWithHypervisor(args) {
     if (args.hypervisor === 'kvm') {
         // virsh create expects a domain XML file. We emit a minimal
@@ -134,6 +107,9 @@ export function registerVmCommand(program, io) {
     const cmd = program
         .command('vm')
         .description('L4 VM isolation: spawn/release VM leases via kvm | hyperkit | hyperv (Part 35; pairs with --isolation vm on dispatch).');
+    // The host probe rides on the same parent, so `peaks vm status`
+    // can say which prerequisite is missing before a spawn fails.
+    registerVmStatusCommand(cmd, io);
     addJsonOption(cmd
         .command('spawn')
         .description('Spawn a VM via the requested hypervisor (kvm | hyperkit | hyperv) and write a VM lease. ' +

package/dist/cli/commands/vm-hypervisor-probe.d.ts

@@ -0,0 +1,27 @@
+import type { VmHypervisor } from '../../services/vm/vm-lease.js';
+export type HypervisorProbeRow = {
+    readonly hypervisor: VmHypervisor;
+    readonly binary: string;
+    readonly available: boolean;
+    /** The version line when available; why not when it is not. */
+    readonly detail: string;
+};
+/** Every hypervisor the CLI can dispatch to, and the binary it shells out to. */
+export declare const VM_HYPERVISOR_BINARIES: ReadonlyArray<{
+    hypervisor: VmHypervisor;
+    binary: string;
+}>;
+export declare function binaryForHypervisor(requested: VmHypervisor): string;
+/**
+ * Is this hypervisor usable here right now? `kvm` needs both the libvirt CLI
+ * and the kernel device node; the others need their binary to answer.
+ */
+export declare function detectHypervisor(requested: VmHypervisor): {
+    ok: true;
+    binary: string;
+} | {
+    ok: false;
+    stderr: string;
+};
+/** Probe every dispatchable hypervisor, in the order the CLI lists them. */
+export declare function probeHypervisors(): HypervisorProbeRow[];

package/dist/cli/commands/vm-hypervisor-probe.js

@@ -0,0 +1,78 @@
+// src/cli/commands/vm-hypervisor-probe.ts
+//
+// The host-side question every `peaks vm` path has to answer: is there a
+// hypervisor on this machine that a VM could actually be created with?
+//
+// Split out of `vm-commands.ts` because two consumers need it — `vm spawn`
+// (fail-fast before leasing) and `vm status` (report every hypervisor,
+// including the ones that are absent) — and because a command file that both
+// registers commands and answers host questions is the shape this repo keeps
+// paying for in `max-lines` findings.
+//
+// Detection is a real probe, not a platform guess: the binary must answer
+// `--version`, and for KVM the kernel device node must exist. That means the
+// answer can change between two calls (an operator installs libvirt mid-run),
+// which is exactly why `vm status` reports it instead of caching it.
+import { execSync } from 'node:child_process';
+import { existsSync } from 'node:fs';
+/** Every hypervisor the CLI can dispatch to, and the binary it shells out to. */
+export const VM_HYPERVISOR_BINARIES = [
+    { hypervisor: 'kvm', binary: 'virsh' },
+    { hypervisor: 'hyperkit', binary: 'hvftool' },
+    { hypervisor: 'hyperv', binary: 'hvc' }
+];
+export function binaryForHypervisor(requested) {
+    const entry = VM_HYPERVISOR_BINARIES.find((row) => row.hypervisor === requested);
+    if (entry === undefined) {
+        throw new Error(`unknown hypervisor: ${requested}`);
+    }
+    return entry.binary;
+}
+/**
+ * Is this hypervisor usable here right now? `kvm` needs both the libvirt CLI
+ * and the kernel device node; the others need their binary to answer.
+ */
+export function detectHypervisor(requested) {
+    const binary = binaryForHypervisor(requested);
+    try {
+        const version = execSync(`${binary} --version`, {
+            stdio: ['ignore', 'pipe', 'pipe'],
+            encoding: 'utf8',
+            windowsHide: true
+        });
+        if (requested === 'kvm' && !existsSync('/dev/kvm')) {
+            return { ok: false, stderr: 'KVM kernel module not loaded (/dev/kvm absent)' };
+        }
+        return { ok: true, binary: `${binary} (${version.trim().split('\n')[0] ?? ''})` };
+    }
+    catch (error) {
+        const message = error.message;
+        // A binary that is not installed fails at exec time, and on Windows that
+        // error arrives in the console codepage — it renders as mojibake in the
+        // terminal. Name the cause instead of quoting it.
+        const absent = /not recognized|not found|ENOENT|Command failed/i.test(message);
+        return {
+            ok: false,
+            stderr: absent ? `${binary} is not on PATH` : (message.split('\n')[0] ?? '')
+        };
+    }
+}
+/** Probe every dispatchable hypervisor, in the order the CLI lists them. */
+export function probeHypervisors() {
+    return VM_HYPERVISOR_BINARIES.map((entry) => {
+        const detected = detectHypervisor(entry.hypervisor);
+        return detected.ok
+            ? {
+                hypervisor: entry.hypervisor,
+                binary: entry.binary,
+                available: true,
+                detail: detected.binary
+            }
+            : {
+                hypervisor: entry.hypervisor,
+                binary: entry.binary,
+                available: false,
+                detail: detected.stderr
+            };
+    });
+}

package/dist/cli/commands/vm-status-command.d.ts

@@ -0,0 +1,3 @@
+import type { Command } from 'commander';
+import { type ProgramIO } from '../cli-helpers.js';
+export declare function registerVmStatusCommand(vm: Command, io: ProgramIO): void;

package/dist/cli/commands/vm-status-command.js

@@ -0,0 +1,50 @@
+// src/cli/commands/vm-status-command.ts
+//
+// `peaks vm status` — the read-only host probe that rides on the `vm` parent.
+//
+// `peaks vm spawn` refuses with VM_RUNTIME_UNAVAILABLE and
+// `peaks sub-agent dispatch --isolation vm` refuses with
+// ISOLATION_VM_NOT_YET_IMPLEMENTED, but neither said WHICH prerequisite is
+// missing on the machine actually running the command: the hypervisor binary,
+// the KVM device node, or a host with no hypervisor at all. The only way to
+// find out was to attempt a spawn that was going to fail.
+//
+// This reports it, and it does not pretend the runtime exists: a probe that
+// finds libvirt on PATH still leaves `--isolation vm` refused, because the
+// missing piece is peaks' VM runtime (image, `vm exec`, per-OS bindings), not
+// the hypervisor. The envelope says so rather than letting a green probe read
+// as "vm works now".
+//
+import { probeHypervisors } from './vm-hypervisor-probe.js';
+import { addJsonOption, printResult } from '../cli-helpers.js';
+import { fail, ok } from 'peaks-loop-shared/result';
+export function registerVmStatusCommand(vm, io) {
+    addJsonOption(vm
+        .command('status')
+        .description('Report which VM hypervisor this host offers (read-only probe; the peaks VM runtime is a separate rid)')).action((options) => {
+        const rows = probeHypervisors();
+        const anyAvailable = rows.some((row) => row.available);
+        const data = {
+            platform: process.platform,
+            hypervisors: rows,
+            anyAvailable,
+            // The runtime statement, kept next to the probe result so the two can
+            // never be read apart.
+            dispatchIsolationVm: 'not implemented'
+        };
+        for (const row of rows) {
+            io.stdout(`${row.hypervisor}  ${row.available ? 'present' : 'absent'}  ${row.binary}: ${row.detail}`);
+        }
+        io.stdout(`platform:  ${process.platform}`);
+        const nextActions = [
+            'The peaks VM runtime (image build, `peaks vm exec`, Hyper-V/HyperKit bindings) is not implemented yet: `peaks sub-agent dispatch --isolation vm` stays refused even when a hypervisor is present.',
+            'For isolation today use --isolation worktree (L2, production) or --isolation container (L4, docker/podman).'
+        ];
+        if (!anyAvailable) {
+            printResult(io, fail('vm.status', 'VM_RUNTIME_UNAVAILABLE', `no VM hypervisor is usable on ${process.platform}: install one of virsh (KVM/libvirt, Linux), hvftool (HyperKit, macOS) or hvc (Hyper-V, Windows) — and on Linux the /dev/kvm device node — or drop --isolation and use worktree/container.`, data, nextActions), options.json);
+            process.exitCode = 1;
+            return;
+        }
+        printResult(io, ok('vm.status', data, [], nextActions), options.json);
+    });
+}

package/dist/cli/commands/wave-plan-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * `peaks sub-agent wave-plan` — slice 2026-09-10-dispatch-token-and-swarm §3.
  *
  * Nested under the existing `sub-agent` verb (no new top-level verb, per the
  * project-level rule that users never learn a new CLI surface; the LLM runs

package/dist/cli/commands/web-lifecycle-commands.d.ts

@@ -1,6 +1,5 @@
 /**
  * `peaks web status|stop|install|login` — the daemon-lifecycle, acquisition and
- * persistent-login verbs (slice S2, file 13; S3 adds `install`; S4 adds `login`).
  *
  * Attaches to the `web` parent handed in by `web-commands.ts` rather than
  * looking it up: the lookup needs a fallback branch for "parent not registered

package/dist/cli/commands/workflow-commands.js

@@ -15,18 +15,14 @@ import { verifyPipeline } from '../../services/workflow/pipeline-verify-service.
 import { applySkip, detectCallerKind } from '../../services/workflow/workflow-skip-service.js';
 import { fail, ok } from 'peaks-loop-shared/result';
 import { addJsonOption, failUnsupportedNonDryRun, getErrorMessage, isRecommendationWorkflow, printResult } from '../cli-helpers.js';
-// Slice 015 — typed error → envelope code routing. Used by the four
 // catch sites below (tech.plan / workflow.route / workflow.autonomous /
 // swarm.plan) so provider-config errors surface as `INVALID_PROVIDERS`
 // instead of being silently re-labelled `INVALID_GOAL`.
 import { mapServiceError } from './_cli-error-envelope.js';
-// Slice rid-012 — change-id-axis tech subcommands (`peaks tech plan-change-id` /
 // `peaks tech status-change-id`). Additive; the existing session-axis
 // `peaks tech plan` / `peaks tech status` registrations are untouched.
 import { registerTechCommands } from './tech-commands.js';
 import { registerSwarmCommands } from './swarm-commands.js';
-// Slice rid-014 — autonomous RD swarm planner (`peaks workflow autonomous`).
-// Additive; the existing rid-013 `registerSwarmCommands` and rid-012
 // `registerTechCommands` registrations are byte-for-byte untouched.
 import { registerAutonomousSwarmCommands } from './autonomous-swarm-commands.js';
 // Slice 4.0.8 — workflow lifecycle (init / graph show / graph list / node
@@ -133,7 +129,6 @@ function runTechPlan(io, options) {
     try {
         validatePlanningInput(options.goal);
         const workspaceContext = getCurrentWorkspaceContext();
-        // Slice 2026-06-29-change-id-root-removal: the change-id axis is
         // gone. The planner derives scope from the active session; the
         // legacy `sessionId` field is passed as empty string for back-compat
         // with the existing service signature.
@@ -274,7 +269,6 @@ async function runSwarmPlan(io, options) {
             ...(options.strictStandards ? { strictStandards: true } : {}),
             ...workspaceContext
         });
-        // Slice 2026-06-16-peaks-rd-no-gates — wire the strict-mode exit code.
         // The service-layer stamps `standardsErrorCode` onto the envelope; the
         // CLI is responsible for translating it into a non-zero exit.
         if (plan.gateStatus.standardsErrorCode === 'EPEAKS_NO_STANDARDS') {
@@ -293,7 +287,6 @@ async function runAutonomousResumeInit(io, options) {
         if (!options.project || !options.project.trim()) {
             throw new Error('Project path must be non-empty');
         }
-        // Slice 2026-06-29-change-id-root-removal: the change-id axis is
         // gone. The CLI surfaces a deterministic placeholder
         // (`session-default`) when the user does not pass a change-id, so
         // the on-disk session-dir join via `getSessionDir` succeeds (the
@@ -387,7 +380,6 @@ export function registerWorkflowCommands(program, io) {
     addTechStatusOptions(tech.command('status')).action((options) => runTechStatus(io, options));
     addTechPlanOptions(program.command('tech-plan')).action((options) => runTechPlan(io, options));
     addTechStatusOptions(program.command('tech-status')).action((options) => runTechStatus(io, options));
-    // Slice rid-012 — add the change-id-axis tech subcommands
     // (`peaks tech plan-change-id` / `peaks tech status-change-id`).
     // Additive; the session-axis registrations above are byte-for-byte untouched.
     registerTechCommands(program, io);
@@ -429,11 +421,9 @@ export function registerWorkflowCommands(program, io) {
             process.exitCode = 1;
         }
     });
-    // Slice 2026-06-13-peaks-workflow-skip — `peaks workflow skip`.
     // Mark gates as bypassed for a specific rid, so the next
     // `verify-pipeline` reports them as `status: 'skipped'` instead of
     // missing-evidence violations. See RD
-    // `.peaks/_runtime/<sid>/rd/requests/001-2026-06-13-peaks-workflow-skip.md`
     // for the three-rule classifier (type allowlist, one-time
     // semantics, role-based auth).
     addJsonOption(workflow
@@ -493,11 +483,9 @@ export function registerWorkflowCommands(program, io) {
             process.exitCode = 1;
         }
     });
-    // Slice rid-013 — `peaks swarm plan-change-id` is delegated to
     // `registerSwarmCommands` (a thin wrapper around the new
     // `planRdSwarmGraph` service). The legacy `peaks swarm plan` /
     // `peaks swarm-plan` registrations above stay in-place for back-compat
-    // with the existing test suite (`tests/unit/cli-program.workflow.test.ts`).
     const swarm = program.command('swarm').description('Plan RD swarm dry-run graphs');
     addSwarmPlanOptions(swarm.command('plan'), true).action(async (options) => {
         await runSwarmPlan(io, options);
@@ -506,8 +494,6 @@ export function registerWorkflowCommands(program, io) {
         await runSwarmPlan(io, options);
     });
     registerSwarmCommands(program, io);
-    // Slice rid-014 — autonomous RD swarm planner. Additive; the rid-013
-    // `registerSwarmCommands` and rid-012 `registerTechCommands` calls
     // above are byte-for-byte untouched.
     registerAutonomousSwarmCommands(program, io);
     // Slice 4.0.8 — workflow lifecycle CLI (init / graph show / graph list /

package/dist/cli/commands/workflow-plan-commands-actions.js

@@ -1,5 +1,4 @@
 /**
- * Action handlers for the `peaks workflow plan` subcommands (slice 025).
  *
  * Extracted from `workflow-plan-commands.ts` (strict-remediation c1). The
  * command registration re-exports these as its programmatic test entry points.
@@ -14,7 +13,6 @@ import { refreshPlan } from '../../services/workflow/plan-refresher.js';
 import { detectTrigger } from '../../services/workflow/plan-trigger-detector.js';
 import { resolveProjectRoot, resolveSessionId } from './workflow-plan-commands-session.js';
 const VALID_TYPES = ['security', 'perf'];
-// F-1 (slice 025 security): reject rids that contain path separators,
 // null bytes, or traversal sequences.
 const REQUEST_ID_PATTERN = /^[A-Za-z0-9][A-Za-z0-9._-]*$/;
 function isPlanType(value) {

package/dist/cli/commands/workflow-plan-commands-session.js

@@ -1,6 +1,5 @@
 /**
  * Shared session-id / project-root resolution for the `peaks workflow plan`
- * command family (slice 025).
  *
  * Extracted from `workflow-plan-commands.ts` (strict-remediation c1) so one
  * implementation backs every plan subcommand instead of the per-command copies
@@ -12,7 +11,6 @@ import { fail } from 'peaks-loop-shared/result';
 import { printResult } from '../cli-helpers.js';
 import { getSessionId } from '../../services/session/session-manager.js';
 import { findProjectRoot } from '../../services/config/config-safety.js';
-// F-1 (slice 025 security): reject session ids that look like path
 // traversal payloads. Canonical pattern is YYYY-MM-DD-<slug>.
 const SESSION_ID_PATTERN = /^\d{4}-\d{2}-\d{2}-[a-z][a-z0-9-]*[a-z0-9]$/;
 export function isValidSessionId(value) {

package/dist/cli/commands/workflow-plan-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * `peaks workflow plan <read|refresh|detect-trigger>` — slice 025 CLI.
  *
  * Three subcommands under the existing `peaks workflow` verb:
  * - `read <security|perf> --project <repo> --json`

package/dist/cli/commands/workspace/clean-command.d.ts

@@ -1,6 +1,5 @@
 /**
  * `peaks workspace clean` — slice 0.5 Task 9 (runtime-only after
- * slice 2026-06-27-archive-feature-removal).
  *
  * Prunes _runtime/<sid>/ directories older than --older-than hours.
  * Dry-run by default; pass --apply to commit. The previous

package/dist/cli/commands/workspace/clean-command.js

@@ -1,6 +1,5 @@
 /**
  * `peaks workspace clean` — slice 0.5 Task 9 (runtime-only after
- * slice 2026-06-27-archive-feature-removal).
  *
  * Prunes _runtime/<sid>/ directories older than --older-than hours.
  * Dry-run by default; pass --apply to commit. The previous

package/dist/cli/commands/workspace/helpers.d.ts

@@ -2,7 +2,6 @@
  * Shared helpers for `peaks workspace <sub-command>` implementations.
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) so multiple sub-command files can
  * reuse the same hooks-decision marker + prompt logic. Pure helpers
  * only — no commander / no service calls. Keeping these here means the
  * per-subcommand files stay focused on their command wiring and option

package/dist/cli/commands/workspace/helpers.js

@@ -2,7 +2,6 @@
  * Shared helpers for `peaks workspace <sub-command>` implementations.
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) so multiple sub-command files can
  * reuse the same hooks-decision marker + prompt logic. Pure helpers
  * only — no commander / no service calls. Keeping these here means the
  * per-subcommand files stay focused on their command wiring and option

package/dist/cli/commands/workspace/init-command.d.ts

@@ -1,8 +1,6 @@
 /**
- * `peaks workspace init` — slice 006 + 007 + 014 + 018 + 2026-06-16-peaks-code-auto-scaffold.
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) to keep that entry file under the
  * 800-line Karpathy cap. Owns:
  *   - commander option wiring (`--project`, `--session-id`, `--change-id`, etc.)
  *   - canonical project-root resolution
@@ -21,7 +19,6 @@ export type WorkspaceInitOptions = {
     json?: boolean;
     allowSessionRebind?: boolean;
     /**
-     * Slice 018 opt-out, commander-convention form. The user-facing
      * flag is `--no-rotate-on-outer-mismatch`; commander strips the
      * `--no-` prefix and assigns the boolean to this property (default
      * `true`, set to `false` when the flag is passed). The wrapper
@@ -49,7 +46,6 @@ export type WorkspaceInitOptions = {
      */
     claudeHooks?: boolean;
     /**
-     * Slice 2026-06-16-peaks-code-auto-scaffold (RD#7): opt-in flag to
      * auto-scaffold `.claude/rules/{common,<language>}/` when missing.
      * Default `false` — the diagnostic fires but no write happens.
      * Set to `true` (via `--init-standards`) to also run
@@ -57,7 +53,6 @@ export type WorkspaceInitOptions = {
      */
     initStandards?: boolean;
     /**
-     * Slice 2026-07-15-project-scan-bootstrap (G2 / G4b / AC9 / AC10):
      * commander-style `--no-project-scan-bootstrap` opt-out. Default
      * (no flag) leaves this `undefined` (treated as `true`). Pass the
      * flag to set `options.projectScanBootstrap === false`, which the
@@ -65,7 +60,6 @@ export type WorkspaceInitOptions = {
      */
     projectScanBootstrap?: boolean;
     /**
-     * Slice 2026-07-15-project-scan-bootstrap (G2 / G4b / AC10):
      * `--force-project-scan-templates` flag. Default (no flag)
      * leaves this `undefined`. Pass the flag to set
      * `options.forceProjectScanTemplates === true`, which forces the

package/dist/cli/commands/workspace/init-command.js

@@ -1,8 +1,6 @@
 /**
- * `peaks workspace init` — slice 006 + 007 + 014 + 018 + 2026-06-16-peaks-code-auto-scaffold.
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) to keep that entry file under the
  * 800-line Karpathy cap. Owns:
  *   - commander option wiring (`--project`, `--session-id`, `--change-id`, etc.)
  *   - canonical project-root resolution
@@ -13,7 +11,6 @@
  * Imports the shared hooks-decision marker helpers from `./helpers.ts`.
  */
 import { initWorkspace, InvalidSessionIdError, ConflictingSessionError, LegacyChangeIdSiblingError } from '../../../services/workspace/workspace-service.js';
-// Slice 2026-06-29-change-id-root-removal: `LegacyChangeIdBindingError`
 // was removed with the change-id axis. The legacy symlink-detection
 // branch below no longer fires — the binding file at
 // `.peaks/_runtime/current-change` is no longer written by init
@@ -75,7 +72,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
             // a guard placed after it would leave a `.peaks/_runtime/` tree in the
             // user's home even though the init was refused.
             const projectRoot = resolveWritableProjectRoot(options.project);
-            // Slice 018: outer-session-mismatch auto-rotation. When the
             // user did NOT pass --session-id explicitly, run
             // `ensureSessionWithRotation` so the binding is rotated on
             // outer-mismatch before `initWorkspace` is called. The
@@ -121,13 +117,11 @@ export function registerWorkspaceInitCommand(workspace, io) {
                 // `false`, so the default is "install hooks" (the bypass is
                 // on). Pass `--no-claude-hooks` to opt out.
                 noClaudeHooks: options.claudeHooks === false,
-                // Slice 2026-06-16-peaks-code-auto-scaffold (RD#7): opt-in
                 // auto-apply for the missing-standards scaffold. Default false
                 // — only the diagnostic is emitted. Pass --init-standards to
                 // also run `executeProjectStandardsInit({ apply: true })`.
                 initStandards: options.initStandards === true
             });
-            // Slice 2026-07-15-project-scan-bootstrap (G2 / G4b / AC9):
             // After the workspace dir is initialized, also bootstrap the
             // `.peaks/project-scan/` artifact tree (project-scan.md + 4
             // bundled audit/business templates). Idempotent — when the user
@@ -176,7 +170,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
                 nextActions.push(`Auto-rotated session binding: outer session id changed (was "${rotation.previousSessionId}"). ` +
                     `New binding is "${sessionId}". The previous session dir is preserved at .peaks/_runtime/${rotation.previousSessionId}/. ` +
                     `Re-run with --no-rotate-on-outer-mismatch to suppress this rotation.`);
-                // Slice 002 (v2.15.0) AC-1: a presence marker stamped by the
                 // OLD outer session is now stale (defect A from the PRD).
                 // peaks-code Step 1 would otherwise pick up the old `mode`
                 // field and silently lock the new session into a mode the
@@ -229,7 +222,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
                     'again without --no-claude-hooks, or drop the contents of ' +
                     '`.peaks/.claude-settings-template.json` into `.claude/settings.local.json` manually.');
             }
-            // Slice 2026-06-13-selfheal-claude-settings-template: surface
             // the self-heal outcome for the offline
             // `.peaks/.claude-settings-template.json` copy. When the offline
             // file was refreshed (i.e. the previous peaks-loop release left
@@ -257,7 +249,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
                 nextActions.push(`Wrote .peaks/.claude-settings-template.json (action: written) — ` +
                     'the offline recovery anchor is now in place for future manual recoveries.');
             }
-            // Slice 2026-07-15-project-scan-bootstrap (G2): surface the
             // bootstrap outcome. The envelope carries the write counts and
             // duration so the LLM (and the human) see what landed. The
             // nextAction only fires when the project-scan tree is fresh —
@@ -283,7 +274,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
             else if (hooksOutcome.action === 'first-decision' && hooksOutcome.decision === 'skipped') {
                 nextActions.push('Skipped peaks-managed hook install for this project. Re-run with --install-hooks=auto (or peaks hooks install) to install later.');
             }
-            // Slice 2026-06-16-peaks-code-auto-scaffold (RD#7):
             //   - When the consumer project's `.claude/rules/` is missing or
             //     empty, emit the copy-pasteable diagnostic to stderr (via
             //     the JSON envelope `warnings` array) AND surface the
@@ -324,7 +314,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
                     `wrote ${report.standardsApplied.writtenFiles.length} file(s), ` +
                     `kept ${report.standardsApplied.skippedFiles.length} existing file(s).`);
             }
-            // Slice 2026-07-15-project-scan-bootstrap (G2): surface the
             // bootstrap outcome. The envelope carries the write counts and
             // duration so the LLM (and the human) see what landed. The
             // nextAction only fires when the project-scan tree is fresh —
@@ -344,9 +333,7 @@ export function registerWorkspaceInitCommand(workspace, io) {
             if (report.standardsMissing.missing) {
                 markStandardsChecked(projectRoot, sessionId);
             }
-            // rid-CG-001 (revised): auto-stake a peaks-loop-managed `.codegraph/`
             // directory after a successful workspace init. Calls the conflict
-            // guard (rid-CG-006) BEFORE writing so a foreign schema is never
             // silently overwritten. We now run a REAL upstream `codegraph init`
             // (not just mkdir + marker) so the schema actually has a
             // `codegraph.db`, which is what post-slice auto-refresh and the
@@ -389,7 +376,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
             }
             printResult(io, ok('workspace.init', {
                 ...report,
-                // Slice 018: surface outer-session-mismatch rotation in the
                 // JSON envelope so the LLM and the human both see the swap.
                 // Field is omitted (not null) when no rotation fired.
                 ...(rotation.previousSessionId !== null && rotation.reason !== null
@@ -406,9 +392,7 @@ export function registerWorkspaceInitCommand(workspace, io) {
                     scope: hooksOutcome.scope,
                     ...(hooksOutcome.reason !== undefined ? { reason: hooksOutcome.reason } : {})
                 },
-                // rid-CG-001: surface codegraph auto-stake outcome.
                 ...(codegraphAutoOutcome !== null ? { codegraphAutoStake: codegraphAutoOutcome } : {}),
-                // Slice 2026-07-15-project-scan-bootstrap (G2): envelope
                 // for the .peaks/project-scan/ bootstrap. Always present
                 // (even when skipped / errored) so downstream readers can
                 // rely on the shape.
@@ -476,7 +460,6 @@ export function registerWorkspaceInitCommand(workspace, io) {
                 process.exitCode = 1;
                 return;
             }
-            // Slice 2026-06-29-change-id-root-removal: the
             // `LegacyChangeIdBindingError` catch branch is gone — the change-id
             // binding file at `.peaks/_runtime/current-change` is no longer
             // written by init, so there is no legacy binding to detect.

package/dist/cli/commands/workspace/migrate-command.d.ts

@@ -1,8 +1,6 @@
 /**
- * `peaks workspace migrate` — slice 003 (--to-runtime).
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) to keep that entry file under the
  * 800-line Karpathy cap. Migrates legacy `.peaks/_runtime/<sid>/<role>/<file>`
  * into the new `.peaks/retrospective/<change-id>/<role>/<file>` layout.
  */

package/dist/cli/commands/workspace/migrate-command.js

@@ -1,8 +1,6 @@
 /**
- * `peaks workspace migrate` — slice 003 (--to-runtime).
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) to keep that entry file under the
  * 800-line Karpathy cap. Migrates legacy `.peaks/_runtime/<sid>/<role>/<file>`
  * into the new `.peaks/retrospective/<change-id>/<role>/<file>` layout.
  */

package/dist/cli/commands/workspace/reconcile-command.d.ts

@@ -1,8 +1,6 @@
 /**
- * `peaks workspace reconcile` — slice 006 + slice 0.5.
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) to keep that entry file under the
  * 800-line Karpathy cap. Scans the legacy 2026-MM-DD-session dirs and
  * consolidates the runtime state.
  *

package/dist/cli/commands/workspace/reconcile-command.js

@@ -1,8 +1,6 @@
 /**
- * `peaks workspace reconcile` — slice 006 + slice 0.5.
  *
  * Extracted from `src/cli/commands/workspace-commands.ts` (slice
- * 2026-06-16-workspace-commands-split) to keep that entry file under the
  * 800-line Karpathy cap. Scans the legacy 2026-MM-DD-session dirs and
  * consolidates the runtime state.
  *
@@ -14,7 +12,6 @@ import { resolveCanonicalProjectRoot } from '../../../services/config/config-ser
 import { fail, ok } from 'peaks-loop-shared/result';
 import { addJsonOption, getErrorMessage, printResult } from '../../cli-helpers.js';
 // Inlined from the original 925-line workspace-commands.ts; the import
-// path '../../../shared/duration.js' did not exist and the constants
 // were used as bare identifiers in the legacy file. Future refactor:
 // move to a shared module.
 const DEFAULT_RECONCILE_AGE_DAYS = 7;