@delegance/claude-autopilot 5.5.2 → 7.2.0

package/dist/src/cli/json-mode.js

@@ -0,0 +1,201 @@
+// src/cli/json-mode.ts
+//
+// v6 Phase 5 — strict --json channel discipline.
+//
+// When --json is set, the spec mandates:
+//   - stdout: exactly one JSON envelope per command invocation.
+//   - stderr: only NDJSON event lines. No human-readable warnings, no color.
+//   - All warnings / prompts / human diagnostics route to typed events.
+//   - Interactive prompts hard-fail with exit:78.
+//
+// Many existing CLI handlers call `console.log` / `console.error` /
+// `console.warn` / `process.stdout.write` / `process.stderr.write` directly
+// for human output. Migrating each one to thread a json flag and switch
+// behavior would be a multi-thousand-line patch. Instead, we install a
+// channel-discipline shim BEFORE the handler runs that captures every
+// non-NDJSON-shaped write and reroutes it:
+//
+//   - stdout writes that aren't valid JSON       → captured into messages[]
+//                                                   (will be attached to the
+//                                                   final envelope by the
+//                                                   dispatcher).
+//   - stdout writes that ARE valid JSON          → captured raw (the dispatcher
+//                                                   will pick the LAST one as
+//                                                   the envelope, on the
+//                                                   assumption that handlers
+//                                                   that already emit a JSON
+//                                                   envelope want it to win).
+//   - stderr writes that are NDJSON              → passed through as-is.
+//   - stderr writes that aren't NDJSON           → wrapped in a synthetic
+//                                                   run.warning event and
+//                                                   re-emitted as NDJSON.
+//
+// Console wrappers route through the same shim:
+//   console.log -> stdout shim
+//   console.error / console.warn -> stderr shim (with level metadata)
+//
+// All ANSI color codes are stripped on the way out.
+//
+// The shim is restorable — the dispatcher calls `restore()` after the
+// handler completes so test runs (which spawn many handlers in-process) get
+// a clean slate.
+import { __getChannelTestSink, stripAnsi, syntheticRunWarning } from "./json-envelope.js";
+/** Try to JSON.parse a chunk. Returns the parsed value on success, undefined
+ *  on failure. We strip a trailing newline before parsing so handlers writing
+ *  one envelope per line are accepted. */
+function tryParse(chunk) {
+    const trimmed = chunk.trim();
+    if (trimmed.length === 0)
+        return undefined;
+    try {
+        return JSON.parse(trimmed);
+    }
+    catch {
+        return undefined;
+    }
+}
+/** Coerce an unknown buffer/string into a string. Mirrors Node's stream
+ *  semantics where writes accept either. */
+function toText(chunk) {
+    if (typeof chunk === 'string')
+        return chunk;
+    if (chunk instanceof Uint8Array)
+        return Buffer.from(chunk).toString('utf8');
+    return String(chunk);
+}
+/** Install the channel-discipline shim. Returns a handle the caller uses to
+ *  collect captured output and to restore the original state.
+ *
+ *  Safe to call when --json is OFF — the function is a no-op in that case
+ *  (returns a handle whose restore() does nothing and whose buffers stay
+ *  empty). Callers should still respect the active flag and skip the
+ *  envelope emission in text mode. */
+export function installJsonModeChannelDiscipline(opts = { active: true }) {
+    const capturedMessages = [];
+    const capturedJsonStdout = [];
+    if (!opts.active) {
+        return {
+            restore: () => { },
+            capturedMessages,
+            capturedJsonStdout,
+        };
+    }
+    const sink = __getChannelTestSink();
+    const origStdoutWrite = process.stdout.write.bind(process.stdout);
+    const origStderrWrite = process.stderr.write.bind(process.stderr);
+    // When a test sink is installed, the shim still wraps process streams so
+    // user code goes through capture, but pass-through writes (NDJSON we want
+    // to surface as-is) go to the sink so tests can read them deterministically
+    // without interleaving with the test runner's own TAP output on the real
+    // streams.
+    const writeStderr = (line) => {
+        if (sink)
+            sink.stderr(line);
+        else
+            origStderrWrite(line);
+    };
+    const origConsoleLog = console.log;
+    const origConsoleError = console.error;
+    const origConsoleWarn = console.warn;
+    const origConsoleInfo = console.info;
+    const origConsoleDebug = console.debug;
+    /** Splits a chunk on newlines, tries to JSON.parse each non-empty line.
+     *  Lines that parse as JSON are recorded as JSON envelopes; the rest are
+     *  recorded as captured text messages with the given level. */
+    function captureStdout(chunk, level) {
+        const cleaned = stripAnsi(chunk);
+        // Stdout chunks may contain multiple JSON envelopes back-to-back; split
+        // on newlines and parse each line. We treat the WHOLE chunk as a single
+        // text message if no line parses (preserves multi-line formatted text).
+        const lines = cleaned.split('\n');
+        let anyParsed = false;
+        for (const line of lines) {
+            const parsed = tryParse(line);
+            if (parsed !== undefined) {
+                capturedJsonStdout.push(parsed);
+                anyParsed = true;
+            }
+        }
+        if (!anyParsed && cleaned.trim().length > 0) {
+            capturedMessages.push({ level, text: cleaned.replace(/\n+$/, '') });
+        }
+    }
+    /** Splits a chunk on newlines for stderr. NDJSON lines pass through to the
+     *  real stderr; non-NDJSON lines are wrapped in synthetic run.warning
+     *  events and re-emitted. */
+    function captureStderr(chunk, level) {
+        const cleaned = stripAnsi(chunk);
+        const lines = cleaned.split('\n');
+        for (const line of lines) {
+            if (line.length === 0)
+                continue;
+            const parsed = tryParse(line);
+            if (parsed !== undefined) {
+                // Pass through as-is (with trailing newline) — already NDJSON.
+                writeStderr(line + '\n');
+            }
+            else {
+                const ev = syntheticRunWarning(line, { level });
+                writeStderr(JSON.stringify(ev) + '\n');
+            }
+        }
+    }
+    // Wrap process.stdout.write. Note: returning true keeps the stream
+    // signature truthy; we drop the original write entirely under JSON mode
+    // because every byte is captured and re-routed via the envelope.
+    process.stdout.write = ((chunk, ...rest) => {
+        captureStdout(toText(chunk), 'log');
+        // Honor the optional callback signature so caller code that passes one
+        // (rare in our handlers but possible) doesn't hang.
+        const cb = rest.find(r => typeof r === 'function');
+        if (cb)
+            cb();
+        return true;
+    });
+    process.stderr.write = ((chunk, ...rest) => {
+        captureStderr(toText(chunk), 'warn');
+        const cb = rest.find(r => typeof r === 'function');
+        if (cb)
+            cb();
+        return true;
+    });
+    console.log = (...args) => {
+        captureStdout(args.map(toText).join(' ') + '\n', 'log');
+    };
+    console.info = (...args) => {
+        captureStdout(args.map(toText).join(' ') + '\n', 'info');
+    };
+    console.debug = (...args) => {
+        captureStdout(args.map(toText).join(' ') + '\n', 'debug');
+    };
+    console.warn = (...args) => {
+        captureStderr(args.map(toText).join(' ') + '\n', 'warn');
+    };
+    console.error = (...args) => {
+        captureStderr(args.map(toText).join(' ') + '\n', 'error');
+    };
+    let restored = false;
+    function restore() {
+        if (restored)
+            return;
+        restored = true;
+        process.stdout.write = origStdoutWrite;
+        process.stderr.write = origStderrWrite;
+        console.log = origConsoleLog;
+        console.error = origConsoleError;
+        console.warn = origConsoleWarn;
+        console.info = origConsoleInfo;
+        console.debug = origConsoleDebug;
+    }
+    return { restore, capturedMessages, capturedJsonStdout };
+}
+/** Build a ChannelOptions value from the parsed --json flag plus
+ *  process.stdin TTY-ness. The caller (dispatcher) usually wants the
+ *  computed nonInteractive flag for prompt-or-hard-fail decisions. */
+export function computeChannelOptions(json) {
+    return {
+        json,
+        nonInteractive: json || !process.stdin.isTTY,
+    };
+}
+//# sourceMappingURL=json-mode.js.map

package/dist/src/cli/migrate.d.ts

@@ -0,0 +1,111 @@
+import type { GuardrailConfig } from '../core/config/types.ts';
+import { type RunPhase } from '../core/run-state/phase-runner.ts';
+import type { ResultArtifact } from '../core/migrate/types.ts';
+export interface MigrateCommandOptions {
+    cwd?: string;
+    configPath?: string;
+    /** Target environment from `.autopilot/stack.md`. Defaults to `dev`. */
+    env?: string;
+    /** When true, the dispatcher passes `dryRun: true` through the envelope so
+     *  the skill executes a no-side-effect plan rather than applying. */
+    dryRun?: boolean;
+    /** `--yes` — required to apply prod migrations in CI per policy. */
+    yesFlag?: boolean;
+    /** `--non-interactive` / `--json` / not-a-TTY equivalent. */
+    nonInteractive?: boolean;
+    /**
+     * v6.0.8 — engine knob inputs. Same precedence as scan / costs / fix /
+     * plan / review / validate (CLI > env > config > built-in default off).
+     */
+    cliEngine?: boolean;
+    envEngine?: string;
+    /**
+     * Test-only seam — replaces the real dispatcher with a fake so smoke
+     * tests can exercise the engine-wrap path without spawning a child
+     * process or hitting a real database. Production callers MUST NOT
+     * pass this; the CLI dispatcher in `src/cli/index.ts` does not expose
+     * a flag that sets it. Underscore-prefixed for grep-ability.
+     */
+    __testDispatch?: (input: MigrateInput) => Promise<ResultArtifact>;
+}
+/**
+ * Phase input — captured as a struct so the engine path's phase body matches
+ * the engine-off path's call signature.
+ *
+ * Exported so the v6.2.1 orchestrator's phase registry can carry the typed
+ * I/O shape on its `PhaseRegistration<MigrateInput, MigrateOutput>` slot.
+ */
+export interface MigrateInput {
+    cwd: string;
+    env: string;
+    dryRun: boolean;
+    yesFlag: boolean;
+    nonInteractive: boolean;
+    /** Runtime version string (from package.json) — required by the
+     *  dispatcher's manifest handshake. Resolved in the outer scope so the
+     *  phase body stays a pure await on `dispatch()`. */
+    runtimeVersion: string;
+    /** v6.2.1 — dispatcher seam plumbed into the phase body so the wrap can
+     *  emit the pre-effect breadcrumb BEFORE invoking the dispatcher. The
+     *  outer scope assembles either the real `runMigrateDispatch` or the
+     *  test-only `__testDispatch`; the phase body just calls `dispatchFn`. */
+    dispatchFn: (input: MigrateInput) => Promise<ResultArtifact>;
+}
+/**
+ * Phase output — JSON-serializable summary suitable for persistence as
+ * `result` on phases/migrate.json. A future skip-already-applied (Phase 6)
+ * could reconstruct the dispatch outcome without re-running by reading the
+ * persisted externalRefs + this result.
+ *
+ * Exported alongside `MigrateInput` for the registry's typed I/O slot.
+ */
+export interface MigrateOutput {
+    /** Status from the result artifact (applied | skipped | error | ...). */
+    status: ResultArtifact['status'];
+    /** Reason code from the result artifact (migration-applied,
+     *  migration-disabled, env-not-configured, etc.). */
+    reasonCode: string;
+    /** List of migrations applied this run (empty on `skipped` / `error`). */
+    appliedMigrations: string[];
+    /** Operator-facing next-action hints surfaced by the skill. */
+    nextActions: string[];
+    /** Echoed env so the render layer / skip-already-applied has it. */
+    env: string;
+}
+/** v6.2.1 — early-exit / build-result discriminants (parity with the v6.2.0
+ *  builders in scan / spec / plan / implement). `migrate` has no early-exit
+ *  branches today but the discriminant is included for shape parity. */
+export interface BuildMigratePhaseEarlyExit {
+    kind: 'early-exit';
+    exitCode: number;
+}
+export interface BuildMigratePhaseResult {
+    kind: 'phase';
+    phase: RunPhase<MigrateInput, MigrateOutput>;
+    input: MigrateInput;
+    config: GuardrailConfig;
+    renderResult: (output: MigrateOutput) => number;
+}
+/**
+ * v6.2.1 — extract the `RunPhase<MigrateInput, MigrateOutput>` construction
+ * out of `runMigrate(options)` so the new top-level `autopilot` orchestrator
+ * can drive `runPhase` itself with a shared `phaseIdx` against the same run
+ * dir. Mirrors the v6.2.0 builder pattern in scan / spec / plan / implement.
+ *
+ * This builder ALSO closes the v6.2.1 idempotency contract gap on `migrate`:
+ * the phase body now emits a `migration-batch` externalRef BEFORE invoking
+ * the dispatcher. See the long rationale on `executeMigratePhase` below.
+ *
+ * The `lastResultArtifact` ref is the seam through which `runMigrate` gets
+ * the full `ResultArtifact` for its --json envelope (the JSON-serializable
+ * `MigrateOutput` is a compact subset; the full artifact has nonce,
+ * contractVersion, sideEffectsPerformed, etc.). Builder callers that don't
+ * need the artifact can ignore it.
+ */
+export declare function buildMigratePhase(options: MigrateCommandOptions): Promise<BuildMigratePhaseResult | BuildMigratePhaseEarlyExit>;
+export declare function runMigrate(options?: MigrateCommandOptions): Promise<{
+    exitCode: number;
+    /** Surfaced for the CLI dispatcher's `--json` payload callback. */
+    result: ResultArtifact | null;
+}>;
+//# sourceMappingURL=migrate.d.ts.map

package/dist/src/cli/migrate.js

@@ -0,0 +1,305 @@
+// src/cli/migrate.ts
+//
+// v6.0.8 — engine-wrap shell for the `migrate` pipeline phase. Runs the
+// stack-aware migrate dispatcher (`src/core/migrate/dispatcher.ts`) inside
+// a `RunPhase<MigrateInput, MigrateOutput>` so v6 pipeline runs check-
+// point a `migrate` phase entry alongside `plan`, `review`, and
+// `validate`.
+//
+// migrate is the FIRST side-effecting phase to land under
+// `runPhaseWithLifecycle` (followed by `implement` and `pr` in v6.0.7 +
+// v6.0.9 — see the rebase contract in PR #102 / #103). The wrap declares:
+//
+//   idempotent:     false   (per spec table at docs/specs/v6-run-state-engine.md)
+//   hasSideEffects: true    (applies migrations against a database)
+//   externalRefs:   migration-version (one per applied migration / per env)
+//
+// Why `idempotent: false` even though the underlying skill is ledger-
+// guarded:
+//   The Delegance migrate skill (and all conforming `migrate@1` skills)
+//   tracks applied migrations in a ledger table — re-running the verb
+//   against a database that already has a given migration applied is a
+//   no-op (the dispatcher returns `status: 'skipped'`, `reasonCode:
+//   migration-disabled` or skill-specific equivalent). So at the
+//   *outcome* layer, replay is safe.
+//
+//   At the *engine semantics* layer, however, `idempotent: true` means
+//   "re-running the phase against the same input produces equivalent
+//   output." A dispatch invocation that previously applied N migrations
+//   on attempt 1 and applies 0 on attempt 2 (everything already in the
+//   ledger) DOES produce different output (different `appliedMigrations`
+//   list, different `status`). The spec table's `idempotent: false` is
+//   the right declaration.
+//
+//   The practical consequence: when a prior `phase.success` exists for
+//   `migrate` and the engine is asked to retry, it consults the
+//   persisted `externalRefs` (`migration-version` entries) to decide
+//   whether to skip-already-applied or retry. Phase 6 will wire the
+//   read-back to live `migration_state` queries; until then, retries on
+//   side-effecting phases require `--force-replay`. Documented in
+//   docs/v6/migration-guide.md "Idempotency + replay rules".
+//
+// Why `hasSideEffects: true`:
+//   Migrations mutate database schema / seed data. The dispatcher writes
+//   audit log entries, schema cache refreshes, types regeneration. The
+//   engine's "no replay without read-back" gate is exactly what we want.
+//
+// `migration-version` externalRefs:
+//   For every migration name in `result.appliedMigrations`, we emit a
+//   `phase.externalRef` event with `kind: 'migration-version'` and `id`
+//   shaped as `<env>:<migration_name>`. The `<env>:` prefix scopes the
+//   ref by target environment (dev / qa / prod) so multi-env pipelines
+//   can read back per-env state. Phase 6's read-back rule will compare
+//   the persisted set to the live ledger to decide skip-already-applied
+//   vs retry vs needs-human.
+//
+// Engine-off path (default through v6.0.x): byte-for-byte identical to
+// the pre-v6.0.8 inline dispatch case in `src/cli/index.ts`. The
+// `runEngineOff` callback supplied to `runPhaseWithLifecycle` invokes
+// the same dispatch + render shape that the legacy code path used. CI /
+// scripts that don't pass `--engine` are unaffected.
+import * as path from 'node:path';
+import * as fs from 'node:fs';
+import * as crypto from 'node:crypto';
+import { loadConfig } from "../core/config/loader.js";
+import { runPhaseWithLifecycle } from "../core/run-state/run-phase-with-lifecycle.js";
+import { dispatch as runMigrateDispatch } from "../core/migrate/dispatcher.js";
+import { findPackageRoot } from "./_pkg-root.js";
+const C = {
+    reset: '\x1b[0m', bold: '\x1b[1m', dim: '\x1b[2m',
+    green: '\x1b[32m', red: '\x1b[31m', cyan: '\x1b[36m',
+};
+const fmt = (c, t) => `${C[c]}${t}${C.reset}`;
+/**
+ * v6.2.1 — extract the `RunPhase<MigrateInput, MigrateOutput>` construction
+ * out of `runMigrate(options)` so the new top-level `autopilot` orchestrator
+ * can drive `runPhase` itself with a shared `phaseIdx` against the same run
+ * dir. Mirrors the v6.2.0 builder pattern in scan / spec / plan / implement.
+ *
+ * This builder ALSO closes the v6.2.1 idempotency contract gap on `migrate`:
+ * the phase body now emits a `migration-batch` externalRef BEFORE invoking
+ * the dispatcher. See the long rationale on `executeMigratePhase` below.
+ *
+ * The `lastResultArtifact` ref is the seam through which `runMigrate` gets
+ * the full `ResultArtifact` for its --json envelope (the JSON-serializable
+ * `MigrateOutput` is a compact subset; the full artifact has nonce,
+ * contractVersion, sideEffectsPerformed, etc.). Builder callers that don't
+ * need the artifact can ignore it.
+ */
+export async function buildMigratePhase(options) {
+    const cwd = options.cwd ?? process.cwd();
+    const configPath = options.configPath ?? path.join(cwd, 'guardrail.config.yaml');
+    let config = { configVersion: 1 };
+    if (fs.existsSync(configPath)) {
+        const loaded = await loadConfig(configPath);
+        if (loaded)
+            config = loaded;
+    }
+    const envName = options.env ?? 'dev';
+    const dryRun = options.dryRun ?? false;
+    const yesFlag = options.yesFlag ?? false;
+    const nonInteractive = options.nonInteractive ?? !process.stdin.isTTY;
+    // Read package version for the runtime handshake. The CLI dispatcher used
+    // to do this inline; we keep the same lookup shape so the engine-off path
+    // is byte-for-byte identical to v6.0.7.
+    const root = findPackageRoot(import.meta.url);
+    let runtimeVersion = 'unknown';
+    if (root) {
+        try {
+            const pkg = JSON.parse(fs.readFileSync(path.join(root, 'package.json'), 'utf8'));
+            runtimeVersion = pkg.version;
+        }
+        catch {
+            /* fall through with 'unknown' — handshake will fail closed */
+        }
+    }
+    const dispatchFn = options.__testDispatch
+        ?? (async (input) => {
+            return runMigrateDispatch({
+                repoRoot: input.cwd,
+                env: input.env,
+                yesFlag: input.yesFlag,
+                nonInteractive: input.nonInteractive,
+                currentRuntimeVersion: input.runtimeVersion,
+                dryRun: input.dryRun,
+            });
+        });
+    const migrateInput = {
+        cwd,
+        env: envName,
+        dryRun,
+        yesFlag,
+        nonInteractive,
+        runtimeVersion,
+        dispatchFn,
+    };
+    const phase = {
+        name: 'migrate',
+        // See top-of-file rationale. The spec table at line 162 of
+        // docs/specs/v6-run-state-engine.md declares idempotent: false
+        // because dispatch output varies by ledger state — the v6.0.8
+        // wrap matches that declaration. The underlying skill IS
+        // ledger-guarded against double-apply; that's a property of the
+        // skill, not of the phase contract. With `hasSideEffects: true`
+        // and persisted `migration-batch` (pre-effect) + `migration-version`
+        // (post-effect) externalRefs, Phase 6's resume gate reads back the
+        // live migration_state to decide skip-already-applied vs retry vs
+        // needs-human.
+        idempotent: false,
+        hasSideEffects: true,
+        run: async (input, ctx) => executeMigratePhase(input, ctx),
+    };
+    return {
+        kind: 'phase',
+        phase,
+        input: migrateInput,
+        config,
+        renderResult: (output) => renderMigrateOutput(output),
+    };
+}
+export async function runMigrate(options = {}) {
+    const built = await buildMigratePhase(options);
+    if (built.kind === 'early-exit') {
+        return { exitCode: built.exitCode, result: null };
+    }
+    const { phase, input: migrateInput, config, renderResult } = built;
+    // Outer ref so the render path + the wrapper's --json envelope can
+    // surface the full ResultArtifact. Updated by `executeMigratePhase` on
+    // every dispatch (engine-on and engine-off paths share the same body).
+    let resultArtifact = null;
+    const captureInput = {
+        ...migrateInput,
+        dispatchFn: async (inp) => {
+            const artifact = await migrateInput.dispatchFn(inp);
+            resultArtifact = artifact;
+            return artifact;
+        },
+    };
+    // v6.0.6+ — lifecycle wiring lives in `runPhaseWithLifecycle`. The
+    // helper owns engine resolution, createRun, run.complete, state.json
+    // refresh, and lock release. The caller just supplies the phase, the
+    // input, the loaded config, and an engine-off escape hatch.
+    let output;
+    try {
+        const lifecycleResult = await runPhaseWithLifecycle({
+            cwd: migrateInput.cwd,
+            phase,
+            input: captureInput,
+            config,
+            cliEngine: options.cliEngine,
+            envEngine: options.envEngine,
+            // Engine-off escape hatch — re-uses the same dispatchFn. We do
+            // NOT thread a real ctx through here because the engine-off path
+            // has no event ledger to write into; externalRefs only matter on
+            // the engine path. The artifact still lands on `resultArtifact`
+            // for the --json payload callback in the CLI dispatcher.
+            runEngineOff: () => executeMigratePhase(captureInput, null),
+        });
+        output = lifecycleResult.output;
+    }
+    catch {
+        // Helper already printed `[migrate] engine: phase failed — <msg>`
+        // + the inspect hint, emitted run.complete failed, refreshed
+        // state.json, released the lock. Surface the legacy non-zero exit.
+        return { exitCode: 1, result: resultArtifact };
+    }
+    return {
+        exitCode: renderResult(output),
+        result: resultArtifact,
+    };
+}
+// ---------------------------------------------------------------------------
+// Phase body — emit the pre-effect `migration-batch` breadcrumb, dispatch,
+// then emit one post-effect `migration-version` ref per applied migration.
+//
+// v6.2.1 idempotency contract (per docs/specs/v6.2.1-side-effect-idempotency.md):
+//   1. PRE-effect breadcrumb: a `migration-batch` ref BEFORE `dispatchFn` so
+//      a partial crash leaves a resume target. The orchestrator's resume
+//      preflight reads this back to distinguish "we started this batch" from
+//      "we never started any batch."
+//   2. POST-effect reconciliation: one `migration-version` ref per applied
+//      migration AFTER dispatch returns successfully. These are authoritative
+//      for the readback's skip-already-applied decision.
+//
+// On the deterministic-id question: the spec prescribes
+//   `${env}:${sha256Hex(env + ':' + plannedMigrations.sort().join(','))}`
+// which would let two runs of the same batch share an id (better resume
+// semantics). That requires extracting `planMigrations(input)` from the
+// dispatcher to surface the planned set without applying. The current
+// dispatcher doesn't expose that pre-dispatch — every supported migrate skill
+// (Delegance Supabase, Rails, Alembic, …) discovers its planned set inside
+// the skill subprocess after the manifest handshake + envelope build, so a
+// pre-dispatch list would require an across-the-board skill protocol change
+// (a new "plan" verb that runs without side effects). That's out of scope
+// for v6.2.1 — the spec explicitly approves the fallback breadcrumb form
+// `${env}:pre-dispatch:${Date.now()}` ("less idempotent but still
+// recoverable"). The post-effect `migration-version` refs ARE deterministic
+// (`${env}:${migration}`) and remain authoritative for the readback's
+// skip-already-applied decision; the batch ref's role is purely "did we
+// start this work?" — non-deterministic ids don't break that contract.
+//
+// Cross-run dedup of the batch ref (e.g. recognizing two pre-dispatch
+// breadcrumbs as the same operation) is gated on the deterministic id form
+// and explicitly listed under v6.2.1 "out of scope."
+// ---------------------------------------------------------------------------
+async function executeMigratePhase(input, ctx) {
+    // PRE-effect breadcrumb. Recorded BEFORE the dispatcher so that even a
+    // partial crash leaves a resume target. Engine-off path has no ctx; the
+    // breadcrumb is then a no-op (same precedent as pr.ts and every other
+    // wrapped verb's engine-off path).
+    if (ctx) {
+        // Fallback id form per the v6.2.1 spec — see the long rationale comment
+        // above. `crypto` is imported even though only the timestamp variant is
+        // used today; it's reserved for the deterministic-id upgrade once a
+        // `planMigrations()` extraction lands.
+        void crypto;
+        ctx.emitExternalRef({
+            kind: 'migration-batch',
+            id: `${input.env}:pre-dispatch:${Date.now()}`,
+        });
+    }
+    const artifact = await input.dispatchFn(input);
+    // POST-effect reconciliation refs — one per applied migration. The id is
+    // shaped `<env>:<migration_name>` so multi-env pipelines (dev → qa → prod)
+    // can disambiguate the same migration across targets. Phase 6's read-back
+    // rule compares this set to the live ledger.
+    if (ctx) {
+        for (const migration of artifact.appliedMigrations) {
+            ctx.emitExternalRef({
+                kind: 'migration-version',
+                id: `${input.env}:${migration}`,
+            });
+        }
+    }
+    return {
+        status: artifact.status,
+        reasonCode: artifact.reasonCode,
+        appliedMigrations: artifact.appliedMigrations,
+        nextActions: artifact.nextActions,
+        env: input.env,
+    };
+}
+// ---------------------------------------------------------------------------
+// Render — translate MigrateOutput back to the legacy stdout banner + exit
+// code. Lives outside the wrapped phase because it's pure presentation; doing
+// rendering inside the phase body would couple the engine path's idempotency
+// to console output.
+// ---------------------------------------------------------------------------
+function renderMigrateOutput(output) {
+    const ok = output.status === 'applied' || output.status === 'skipped';
+    const color = ok ? C.green : C.red;
+    console.log(`${color}[migrate] status=${output.status} reason=${output.reasonCode}${C.reset}`);
+    if (output.appliedMigrations.length > 0) {
+        console.log(`  applied: ${output.appliedMigrations.join(', ')}`);
+    }
+    if (output.nextActions.length > 0) {
+        console.log(`  next: ${output.nextActions.join('; ')}`);
+    }
+    // Suppress unused-helper TS warning when fmt isn't called above (the dim /
+    // bold / cyan helpers are reserved for future render paths — keeping the
+    // import + fmt() reference parallel with other wrapped verbs makes
+    // bin-mods easier to read).
+    void fmt;
+    return ok ? 0 : 1;
+}
+//# sourceMappingURL=migrate.js.map