peaks-loop 4.1.1 → 4.1.3

package/dist/cli/commands/core/skill-registry-commands.js

@@ -0,0 +1,117 @@
+import { runDoctor } from '../../../services/doctor/index.js';
+import { listSkills } from '../../../services/skills/skill-registry.js';
+import { runSkillSync, SYNC_PLATFORMS } from '../../../services/skills/sync-service.js';
+import { ok, fail } from 'peaks-loop-shared/result';
+import { addJsonOption, getErrorMessage, printResult } from '../../cli-helpers.js';
+const PLATFORM_IDS = SYNC_PLATFORMS.join(', ');
+const LIST_DESCRIPTION = 'List skills derived from skills/*/SKILL.md';
+const LIST_INCLUDE_INTERNAL_HELP = 'include skills with visibility: internal (default: hide them)';
+const DOCTOR_DESCRIPTION = 'Run skill-related doctor checks';
+const SYNC_DESCRIPTION = `Sync the peaks-* skill family to one or all of the 8 supported LLM-CLI platforms (${PLATFORM_IDS}). Idempotent.`;
+const SYNC_PLATFORM_HELP = `sync only one platform (default: --all). Valid: ${PLATFORM_IDS}`;
+const SYNC_ALL_HELP = 'sync all 8 platforms (default if --platform is omitted)';
+const SYNC_DRY_RUN_HELP = 'do not write; emit the same shape with applied=false';
+const SYNC_RECONCILE_HELP = 'repair Peaks-managed skill Junctions whose targets were deleted with a host worktree';
+const SYNC_PROJECT_HELP = 'project root (default: cwd)';
+function sortSkillsForDisplay(skills) {
+    return [...skills].sort((a, b) => {
+        // door) — list it FIRST so users discover the dispatcher before
+        // any specific leaf. Followed by peaks-sop (current default
+        // runbook showcase) and peaks-code (canonical code-domain
+        // orchestrator); everything else falls back to alphabetical.
+        if (a.name === 'peaks-solo')
+            return -1;
+        if (b.name === 'peaks-solo')
+            return 1;
+        if (a.name === 'peaks-sop')
+            return -1;
+        if (b.name === 'peaks-sop')
+            return 1;
+        if (a.name === 'peaks-code')
+            return -1;
+        if (b.name === 'peaks-code')
+            return 1;
+        return a.name.localeCompare(b.name);
+    });
+}
+function runSkillList(options, io) {
+    return listSkills().then((all) => {
+        const skills = options.includeInternal === true ? all : all.filter((s) => s.visibility !== 'internal');
+        if (options.json === true) {
+            printResult(io, ok('skill.list', { skills }), true);
+            return;
+        }
+        for (const skill of sortSkillsForDisplay(skills)) {
+            io.stdout(`  ${skill.name.padEnd(14)}${skill.description}`);
+        }
+        io.stdout(`\n  Invoke any skill by typing its name in conversation (e.g. \`peaks-sop\`).`);
+    });
+}
+function runSkillDoctor(options, io) {
+    return runDoctor().then((report) => {
+        const skillChecks = report.checks.filter((check) => check.id.startsWith('skill'));
+        const failed = skillChecks.filter((check) => !check.ok).length;
+        if (options.json === true) {
+            printResult(io, ok('skill.doctor', { checks: skillChecks, ok: failed === 0 }), true);
+        }
+        else {
+            for (const check of skillChecks) {
+                const icon = check.ok ? '+' : '×';
+                io.stdout(`  ${icon}  ${check.message}`);
+            }
+            io.stdout(`\n  ${skillChecks.length - failed} passed, ${failed} failed`);
+            if (failed > 0) {
+                io.stderr('\nOne or more skill checks failed.');
+            }
+        }
+        if (failed > 0) {
+            process.exitCode = 1;
+        }
+    });
+}
+async function runSkillSyncCommand(options, io) {
+    try {
+        const projectRoot = options.project ?? process.cwd();
+        const platforms = options.platform !== undefined ? [options.platform] : undefined;
+        const result = await runSkillSync({
+            projectRoot,
+            ...(platforms !== undefined ? { platforms } : {}),
+            ...(options.dryRun === true ? { dryRun: true } : {}),
+            ...(options.reconcileJunctions === true ? { reconcileJunctions: true } : {})
+        });
+        const envelope = ok('skill.sync', result, [], [
+            `syncedCount: ${result.syncedCount}/${result.perPlatform.length} platforms`,
+            `totalInstalled: ${result.totalInstalled} skill symlinks`,
+            result.failedCount > 0
+                ? `failedCount: ${result.failedCount} (run \`peaks skill status\` for details)`
+                : 'no failures'
+        ]);
+        printResult(io, envelope, options.json);
+        if (result.failedCount > 0) {
+            process.exitCode = 1;
+        }
+    }
+    catch (error) {
+        const message = getErrorMessage(error);
+        printResult(io, fail('skill.sync', 'SKILL_SYNC_FAILED', message, { applied: false }, [message]), options.json);
+        process.exitCode = 1;
+    }
+}
+export function registerSkillRegistryCommands(skill, io) {
+    addJsonOption(skill
+        .command('list')
+        .description(LIST_DESCRIPTION)
+        .option('--include-internal', LIST_INCLUDE_INTERNAL_HELP)).action((options) => runSkillList(options, io));
+    addJsonOption(skill.command('doctor').description(DOCTOR_DESCRIPTION)).action((options) => runSkillDoctor(options, io));
+    // Slice #12 final piece (per spec §9 line 1105):
+    // `peaks skills sync 8 平台分发`. Idempotent: re-running is a
+    // no-op when the symlinks are already correct.
+    addJsonOption(skill
+        .command('sync')
+        .description(SYNC_DESCRIPTION)
+        .option('--platform <id>', SYNC_PLATFORM_HELP)
+        .option('--all', SYNC_ALL_HELP)
+        .option('--dry-run', SYNC_DRY_RUN_HELP)
+        .option('--reconcile-junctions', SYNC_RECONCILE_HELP)
+        .option('--project <path>', SYNC_PROJECT_HELP)).action((options) => runSkillSyncCommand(options, io));
+}

package/dist/cli/commands/core/skill-runbook-command.d.ts

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

package/dist/cli/commands/core/skill-runbook-command.js

@@ -0,0 +1,29 @@
+import { inspectSkillRunbook } from '../../../services/skills/skill-runbook-service.js';
+import { fail, ok } from 'peaks-loop-shared/result';
+import { addJsonOption, getErrorMessage, printResult } from '../../cli-helpers.js';
+export function registerSkillRunbookCommand(skill, io) {
+    addJsonOption(skill
+        .command('runbook <name>')
+        .description('Inspect a skill Default runbook section and its --apply authorization-note status')).action(async (name, options) => {
+        try {
+            const inspection = await inspectSkillRunbook(name);
+            const result = inspection.ok
+                ? ok('skill.runbook', inspection)
+                : fail('skill.runbook', inspection.hasRunbook ? 'SKILL_RUNBOOK_APPLY_UNGATED' : 'SKILL_RUNBOOK_MISSING', inspection.hasRunbook
+                    ? `Skill ${inspection.name} has ${inspection.destructiveApplyLines.length} destructive --apply command(s) without an authorization/dry-run note`
+                    : `Skill ${inspection.name} is missing a ## Default runbook section`, inspection, inspection.hasRunbook
+                    ? [
+                        'Add an authorization or --dry-run note next to destructive --apply lines in the runbook section'
+                    ]
+                    : ['Add a `## Default runbook` section to the skill SKILL.md']);
+            printResult(io, result, options.json);
+            if (!inspection.ok) {
+                process.exitCode = 1;
+            }
+        }
+        catch (error) {
+            printResult(io, fail('skill.runbook', 'SKILL_NOT_FOUND', getErrorMessage(error), { name }), options.json);
+            process.exitCode = 1;
+        }
+    });
+}

package/dist/cli/commands/core-artifact-commands.d.ts

@@ -4,7 +4,6 @@ export type { DoctorLogsSection, BindingSource } from './core/doctor-command.js'
 /**
  * Top-level CLI command registrar for the "core + artifact" surface.
  *
- * Slice 2026-06-24-handoff-path-canonicalization split this orchestrator
  * out of a single 889-line file so each subcommand group lives in its
  * own module under `src/cli/commands/core/`. The orchestrator stays
  * thin (~this file) and forwards to the per-group registrars; the

package/dist/cli/commands/core-artifact-commands.js

@@ -10,7 +10,6 @@ import { registerStandardsCommand } from './core/standards-command.js';
 /**
  * Top-level CLI command registrar for the "core + artifact" surface.
  *
- * Slice 2026-06-24-handoff-path-canonicalization split this orchestrator
  * out of a single 889-line file so each subcommand group lives in its
  * own module under `src/cli/commands/core/`. The orchestrator stays
  * thin (~this file) and forwards to the per-group registrars; the

package/dist/cli/commands/cron-commands-actions.d.ts

@@ -17,7 +17,6 @@
  * throw, exit code, or emitted byte — and a new sibling must be clean outright.
  *
  * ONE thing has since been restructured, and it is not the verbatim move above:
- * rid `2026-10-01-cron-last-run-at-01` repair cycle 1 replaced `runCronTasks`'s
  * own fold-and-write (a `runTargets` that built the next file from the snapshot
  * read before the runs, stamping every record including killed ones) with the
  * scheduler's `persistLastRunAt`, so one rule and one write-time re-read cover

package/dist/cli/commands/cron-commands-actions.js

@@ -17,7 +17,6 @@
  * throw, exit code, or emitted byte — and a new sibling must be clean outright.
  *
  * ONE thing has since been restructured, and it is not the verbatim move above:
- * rid `2026-10-01-cron-last-run-at-01` repair cycle 1 replaced `runCronTasks`'s
  * own fold-and-write (a `runTargets` that built the next file from the snapshot
  * read before the runs, stamping every record including killed ones) with the
  * scheduler's `persistLastRunAt`, so one rule and one write-time re-read cover
@@ -100,7 +99,6 @@ function runCronTasks(io, options) {
         return;
     }
     const records = runTargets(projectRoot, targets);
-    // ONE rule, ONE writer (rid `2026-10-01-cron-last-run-at-01`, repair cycle 1).
     // This call is the third site of the `lastRunAt` fold, whose rule and platform
     // costs live in `cron-scheduler-persist.ts`. Two things it replaces: a fold that
     // stamped EVERY record, killed ones included (so the same killed fire went quiet

package/dist/cli/commands/cron-commands-schedule.d.ts

@@ -48,7 +48,6 @@ export type RunRecord = {
     /**
      * Present (and `true`) ONLY when the task was killed for exceeding its exec
      * timeout — i.e. when there is no child exit status behind `exitCode` and the
-     * work may have been mid-flight. Added by rid 2026-10-01-cron-task-tree-kill-01
      * so a killed run cannot be read as a clean `exitCode 1` failure.
      *
      * OPTIONAL on purpose: `appendHistory` is the only writer of
@@ -63,7 +62,6 @@ export declare function readSchedule(projectRoot: string): ScheduleFile;
 /**
  * The one "can this raw JSON entry be represented?" predicate. Exported because
  * a writer that must NOT lose an entry needs to know which ones the reader
- * dropped (rid `2026-10-01-cron-last-run-at-01`, repair cycle 1, F5 — see
  * `persistLastRunAt` in `cron-scheduler-persist.ts`).
  */
 export declare function toScheduleEntry(e: unknown): ScheduleEntry | null;
@@ -73,7 +71,6 @@ export declare function toScheduleEntry(e: unknown): ScheduleEntry | null;
  * `entries` is `ReadonlyArray<unknown>`, not `ReadonlyArray<ScheduleEntry>`, for one
  * caller: `persistLastRunAt` re-writes the raw JSON of entries `toScheduleEntry`
  * refused, so that a daemon write cannot delete an operator's hand-edited entry
- * (rid `2026-10-01-cron-last-run-at-01` repair cycle 1, F5). Every other caller
  * passes a `ScheduleFile`, which satisfies this shape.
  */
 export type ScheduleWrite = {

package/dist/cli/commands/cron-commands-schedule.js

@@ -76,7 +76,6 @@ function assertScheduleRoot(parsed) {
 /**
  * The one "can this raw JSON entry be represented?" predicate. Exported because
  * a writer that must NOT lose an entry needs to know which ones the reader
- * dropped (rid `2026-10-01-cron-last-run-at-01`, repair cycle 1, F5 — see
  * `persistLastRunAt` in `cron-scheduler-persist.ts`).
  */
 export function toScheduleEntry(e) {

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

@@ -1,5 +1,4 @@
 /**
- * `peaks cron` — slice 2026-07-29-worktree-l2-extended Part 14.
  *
  * Persistent scheduled-task system. Stores a JSON schedule at
  * `.peaks/cron/schedule.json` and lets the LLM-side runner

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

@@ -1,5 +1,4 @@
 /**
- * `peaks cron` — slice 2026-07-29-worktree-l2-extended Part 14.
  *
  * Persistent scheduled-task system. Stores a JSON schedule at
  * `.peaks/cron/schedule.json` and lets the LLM-side runner
@@ -77,7 +76,6 @@ function truncateStderr(text) {
  * `exitCode 1 / "peaks-loop: internal module not found — the local build is
  * stale or incomplete"` on every fire. Measured in
  * `tests/unit/cli/commands/cron-task-tree-kill.test.ts` (F1, repair cycle 1 of
- * rid 2026-10-01-cron-task-tree-kill-01).
  */
 function isBootableTaskEntry(entry) {
     return existsSync(entry) && existsSync(resolve(dirname(entry), '..', 'dist', 'cli', 'index.js'));

package/dist/cli/commands/cron-scheduler-commands.d.ts

@@ -1,5 +1,4 @@
 /**
- * `peaks cron scheduler start|stop|status|run-once` — slice 2026-07-29 Part 15.
  *
  * Companion CLI to Part 14 (peaks cron init/list/run). The
  * scheduler is a long-running background daemon that wakes up

package/dist/cli/commands/cron-scheduler-commands.js

@@ -1,5 +1,4 @@
 /**
- * `peaks cron scheduler start|stop|status|run-once` — slice 2026-07-29 Part 15.
  *
  * Companion CLI to Part 14 (peaks cron init/list/run). The
  * scheduler is a long-running background daemon that wakes up

package/dist/cli/commands/cron-scheduler-persist.d.ts

@@ -1,5 +1,4 @@
 /**
- * The ONE writer of `lastRunAt` in this repo — rid `2026-10-01-cron-last-run-at-01`
  * (backlog §2.24), repair cycle 1 (review F1/F4/F5). Lives in its own file because
  * `cron-commands.ts` sits at 287 of its 300 raw-line cap and
  * `cron-scheduler-commands.ts` is already over its own; the rule below is small
@@ -23,7 +22,6 @@
  * invocations across 6 ticks** for one entry with `intervalMs` 86,400,000 at the
  * 60,000 ms daemon period — a 1440× rate error against the declared interval, and the
  * rate half of
- * `.peaks/docs/diagnosis-2026-10-01-worktree-list-population.md` §9. The same
  * test observes **1** once the write-back below runs.
  *
  * THE RULE (persist AFTER the run, from the record's `finishedAt`):
@@ -32,8 +30,6 @@
  *      exactly its own `intervalMs` and not one ms longer;
  *   2. a run carrying `killed: true` does NOT advance it, in EITHER entry point.
  *      Work cut off mid-flight is not a day's work, so the task stays due and is
- *      retried. What that costs is NOT uniform across platforms, and F3 of the
- *      review is the reason this paragraph is platform-shaped instead of global:
  *      - win32: the only fire shape that reaches `killed: true` here is the exec
  *        timeout (`cron-commands.ts:178-185`, spawnSync's `error.code ===
  *        'ETIMEDOUT'` branch), and that fire BLOCKS its caller for the whole
@@ -67,7 +63,6 @@
  *      running one…"); and entries `toScheduleEntry`
  *      (`cron-commands-schedule.ts:129-150`) REJECTS — a hand-edited entry missing
  *      `name`, say — are carried through as the raw JSON they were written as,
- *      appended after the parsed ones. F5 of the review: before this they were
  *      silently DELETED by the daemon's first write, which is data loss on a
  *      long-lived process nobody is watching. An unparseable entry with the same `id`
  *      as a parsed one is the one thing still dropped, because two entries under one

package/dist/cli/commands/cron-scheduler-persist.js

@@ -1,5 +1,4 @@
 /**
- * The ONE writer of `lastRunAt` in this repo — rid `2026-10-01-cron-last-run-at-01`
  * (backlog §2.24), repair cycle 1 (review F1/F4/F5). Lives in its own file because
  * `cron-commands.ts` sits at 287 of its 300 raw-line cap and
  * `cron-scheduler-commands.ts` is already over its own; the rule below is small
@@ -23,7 +22,6 @@
  * invocations across 6 ticks** for one entry with `intervalMs` 86,400,000 at the
  * 60,000 ms daemon period — a 1440× rate error against the declared interval, and the
  * rate half of
- * `.peaks/docs/diagnosis-2026-10-01-worktree-list-population.md` §9. The same
  * test observes **1** once the write-back below runs.
  *
  * THE RULE (persist AFTER the run, from the record's `finishedAt`):
@@ -32,8 +30,6 @@
  *      exactly its own `intervalMs` and not one ms longer;
  *   2. a run carrying `killed: true` does NOT advance it, in EITHER entry point.
  *      Work cut off mid-flight is not a day's work, so the task stays due and is
- *      retried. What that costs is NOT uniform across platforms, and F3 of the
- *      review is the reason this paragraph is platform-shaped instead of global:
  *      - win32: the only fire shape that reaches `killed: true` here is the exec
  *        timeout (`cron-commands.ts:178-185`, spawnSync's `error.code ===
  *        'ETIMEDOUT'` branch), and that fire BLOCKS its caller for the whole
@@ -67,7 +63,6 @@
  *      running one…"); and entries `toScheduleEntry`
  *      (`cron-commands-schedule.ts:129-150`) REJECTS — a hand-edited entry missing
  *      `name`, say — are carried through as the raw JSON they were written as,
- *      appended after the parsed ones. F5 of the review: before this they were
  *      silently DELETED by the daemon's first write, which is data loss on a
  *      long-lived process nobody is watching. An unparseable entry with the same `id`
  *      as a parsed one is the one thing still dropped, because two entries under one

package/dist/cli/commands/dashboard-summary.d.ts

@@ -1,5 +1,4 @@
 /**
- * rid-030 F-direction: `peaks dashboard summary --since <duration>`.
  *
  * Read-only 5-metric surface derived from raw observability events
  * (cycle / token / dispatch / compact / monotonic-trigger). Distinct

package/dist/cli/commands/dispatch-command-spec.d.ts

@@ -0,0 +1,2 @@
+import type { Command } from 'commander';
+export declare function buildDispatchCommandSpec(parent: Command): Command;

package/dist/cli/commands/dispatch-command-spec.js

@@ -0,0 +1,62 @@
+import { addJsonOption } from '../cli-helpers.js';
+const DISPATCH_DESCRIPTION = 'Build an IDE-specific tool-call descriptor for a sub-agent dispatch. ' +
+    'Dry-run by design; the LLM executes the returned toolCall in its own ' +
+    'environment. Flags: --write-artifact (G7), ' +
+    '--force (G9 CLI 兜底). ' +
+    'See skills/peaks-code/references/sub-agent-dispatch.md for the ' +
+    'orchestrator contract.';
+function buildDispatchCommandBase(parent) {
+    return parent
+        .command('dispatch')
+        .description(DISPATCH_DESCRIPTION)
+        .argument('<role>', 'sub-agent role (e.g. rd | qa | ui | txt | qa-business | qa-business-api)');
+}
+function applyDispatchInputOptions(command) {
+    return (command
+        // 2.7.0 slice-dag-dispatcher MVP: --prompt is required ONLY when --from-dag is NOT
+        // supplied. Previously this was `.requiredOption('--prompt')`, which blocked
+        // `dispatch --from-dag <file>` calls because commander.js validates
+        // `.requiredOption` before the action handler runs. The mutual-exclusion
+        // check is enforced below in the action body (--prompt XOR --from-dag).
+        .option('--prompt <text>', 'the prompt to send to the sub-agent (required unless --from-dag is provided)')
+        .option('--prompt-length <bytes>', 'DOGFOOD ONLY: synthesize a prompt of this size (overrides --prompt content for size only; content is "x" repeated)')
+        .option('--request-id <rid>', 'the same <rid> used by peaks request init')
+        .option('--session-id <sid>', 'override active session id (default: resolve from .peaks/_runtime/session.json; falls back to PEAKS_SESSION_ID env var; final fallback "unknown-sid")')
+        .option('--project <path>', 'target project root (defaults to cwd)')
+        .option('--batch-id <uuid>', 'batch id for the dispatch (default: auto-generated UUID)')
+        .option('--write-artifact <path>', 'G7: register an artifact file at <path>; CLI computes sha256 + size + writes ArtifactMeta to the dispatch record')
+        .option('--force', 'G9: override the 80% hard reject threshold at CLI (NOT allowed at hook layer per RL-30 strict)')
+        .option('--from-dag <file>', '2.7.0 slice-dag-dispatcher MVP: read a SliceDag JSON file, dispatch one sub-agent per node in topological order; --batch-id overrides the auto-generated batch id (mutually exclusive with <role>)')
+        .option('--isolation <mode>', 'slice 2026-07-29-worktree-l2-extended Part 2.C: isolation mode for the sub-agent. Accepts "worktree" (Part 2.C + Part 12 L2 surface), "container" (Part 8 contract + Part 12 L4 docker runtime), or "vm" (Part 25 contract; the VM runtime is a follow-up rid and fail-fasts with ISOLATION_VM_NOT_YET_IMPLEMENTED). Auto-spawns a lease + injects PEAKS_<MODE>_LEASE_ID into the dispatch envelope so the sub-agent can write to the isolated surface without a separate auth grant.')
+        // Slice 4.0.8 RD §4 made this a `.requiredOption`. It is optional now:
+        // the requirement was enforced but never validated — nothing downstream
+        // reads the node, and the record writer's graph transition is
+        // best-effort — so its only observable effect was to block dispatch in
+        // every project without graph infrastructure. See
+        // `provisionDispatchNode`.
+        .option('--graph-node <id>', 'graph node id this dispatch binds to (default: a node is provisioned on demand)')
+        .option('--workflow-id <id>', 'workflow id the graph node belongs to (defaults to derived from session)'));
+}
+function applyDispatchExecutionOptions(command) {
+    return (command
+        .option('--graph-ref <ref>', 'graphRef (defaults to graphs/<workflow-id>.json)')
+        // mode is `in-process` so the 106+ existing dispatch call sites
+        // keep their path byte-identical. The detached branch below
+        // fires only when --mode detached is explicitly passed.
+        .option('--mode <mode>', 'dispatch execution mode: in-process (default, dry-run envelope only) | detached (shell out to peaks-loop-internal-runtime/dispatch.dispatchDetached for real vendor CLI execution).')
+        .option('--vendor <vendor>', 'target vendor CLI for --mode detached (claude | codex | copilot). Ignored in the default in-process path.')
+        .option('--no-throttle', 'rid-001 detached: user-overrides ResourceBudgetGuard when concurrent fan-out exceeds max-concurrent (user accepts risk; surfaces as warning)')
+        .option('--max-concurrent <n>', 'rid-001 detached: override the per-tenant max concurrent budget (default 8). Effective in both detached and in-process paths.')
+        // §Lesson 1): the RD sub-agent's fake-green failure mode was that it
+        // claimed "5/5 reachability tests PASS" while the files were never
+        // on disk. `--must-ls-files <glob>` is the anti-fake-green gate:
+        // the CLI runs `git ls-files <glob>` upfront, reports the result in
+        // the envelope (`data.mustLsFilesVerification`), and prepends a
+        // `## must_ls_files enforcement` block to the sub-agent prompt so
+        // the LLM's first action MUST re-verify file existence before any
+        // "completed" claim. Absent → old behavior is preserved.
+        .option('--must-ls-files <glob>', 'F5: anti-fake-green gate. Run `git ls-files <glob>` upfront; surface the result in the envelope as `mustLsFilesVerification: { path, exists, files }`; prepend a must_ls_files enforcement block to the sub-agent prompt. Absent → unchanged behavior.'));
+}
+export function buildDispatchCommandSpec(parent) {
+    return addJsonOption(applyDispatchExecutionOptions(applyDispatchInputOptions(buildDispatchCommandBase(parent))));
+}

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

@@ -3,7 +3,6 @@ import { type ProgramIO } from '../cli-helpers.js';
 export declare function registerDispatchCommand(parent: Command, io: ProgramIO): void;
 /**
  * 2.7.0 slice-dag-dispatcher MVP — see `dispatch-from-dag.ts`.
- * The function was pulled out of this file in slice 2026-06-23-audit-3rd
  * #7 to honor the 800-line file cap and isolate the three heavy
  * module loads (slice-dag / dag-orchestrator / contract-store) to the
  * --from-dag codepath only.