cool-workflow 0.2.0 → 0.2.1

package/dist/core/state/state-node.js

@@ -11,7 +11,7 @@
 //
 // Evidence: SPEC/state-core.md "src/state-node.ts — StateNode lifecycle and
 // contract gates", "StateNode transition matrix", "Deterministic id
-// fallback", "Contract gates" (v2/PLAN.md byte-compat item 7 — the double
+// fallback", "Contract gates" (docs/rebuild/PLAN.md byte-compat item 7 — the double
 // commit gate).
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.PipelineContractError = exports.PIPELINE_CONTRACT_SCHEMA_VERSION = exports.STATE_NODE_SCHEMA_VERSION = void 0;
@@ -115,7 +115,7 @@ function validatePipelineContract(contract) {
  *  check against; every real caller (shell/) passes `fs.existsSync` so the
  *  `missing-artifact-path` gate behaves exactly like the old build. Kept as
  *  an explicit parameter (never a top-level `require("node:fs")`) so this
- *  stays a pure core/ module per v2/PLAN.md's core/shell split. */
+ *  stays a pure core/ module per docs/rebuild/PLAN.md's core/shell split. */
 function assertNodeSatisfiesContract(node, contract, stageId, pathExists = () => true) {
     validatePipelineContract(contract);
     const stage = contract.stages.find((candidate) => candidate.id === stageId);

package/dist/core/state/types.js

@@ -1,7 +1,7 @@
 "use strict";
 // core/state/types.ts — the state-kernel's own type set.
 //
-// MILESTONE 3 (v2/PLAN.md build order, step 3). Scoped to exactly what
+// MILESTONE 3 (docs/rebuild/PLAN.md build order, step 3). Scoped to exactly what
 // state-core.md's public surface needs: WorkflowRun and everything it
 // carries, StateNode + its snapshot/replay/diff family, the pipeline
 // contract shape, and the small persisted-record shapes validation.ts

package/dist/core/trust/ledger.js

@@ -1,7 +1,7 @@
 "use strict";
 // core/trust/ledger.ts — the cross-agent handoff ledger kernel.
 //
-// MILESTONE 8 (v2/PLAN.md build order, step 8; SPEC/ledger-trust.md in
+// MILESTONE 8 (docs/rebuild/PLAN.md build order, step 8; SPEC/ledger-trust.md in
 // full). Pure: computeLedgerDigest, buildLedgerProposal/Review,
 // verifyLedgerEntry, applyLedgerProposal. Directory reads
 // (listLedgerEntries/unionLedgerEntries) live in shell/ledger-io.ts, NOT

package/dist/core/trust/telemetry-attestation.js

@@ -6,7 +6,7 @@
 // node:crypto's built-in ed25519 sign/verify (no npm dependency).
 //
 // `crypto.verify`/`crypto.createPublicKey` are allowed here per
-// v2/PLAN.md's lint carve-out for this exact file (Target shape,
+// docs/rebuild/PLAN.md's lint carve-out for this exact file (Target shape,
 // core/trust/telemetry-attestation.ts comment) — this remains otherwise
 // pure (no fs, no process.env, no clock; `resolveTrustPublicKey`'s lazy
 // `require("node:fs")` is the one exception, ported byte-identically
@@ -62,7 +62,7 @@ const crypto = __importStar(require("node:crypto"));
  *  recursively, AND maps a top-level `undefined` input to the literal
  *  string `"null"`. Divergent from `core/hash.ts`'s
  *  `ledgerStableStringify` exactly at the top-level-undefined edge (see
- *  v2/PLAN.md byte-compat item 2). Re-exported under this file's own
+ *  docs/rebuild/PLAN.md byte-compat item 2). Re-exported under this file's own
  *  name (rather than importing `telemetryStableStringify` from
  *  core/hash.ts) because SPEC/ledger-trust.md's "Exported functions"
  *  list names `stableStringify` as a real export of THIS module — the
@@ -118,7 +118,7 @@ function normalizeReportedUsage(usage) {
     };
 }
 /** Verify the agent's signed usage against the operator-provisioned
- *  public key. Two-arm check (v2/PLAN.md byte-compat item 11): try the
+ *  public key. Two-arm check (docs/rebuild/PLAN.md byte-compat item 11): try the
  *  5-field payload (with resultDigest) first; on a miss, retry the
  *  4-field payload (old signers still verify). `coversResult` is set
  *  ONLY on a first-arm match — a 4-field fallback match never covers the

package/dist/core/trust/telemetry-ledger.js

@@ -7,7 +7,7 @@
 //
 // MILESTONE 8. Byte-exact port of the old build's src/telemetry-ledger.ts
 // verify-side logic. Uses core/hash.ts's `sha256`/`telemetryStableStringify`
-// (see v2/PLAN.md byte-compat item 2's key-omission-vs-null rule).
+// (see docs/rebuild/PLAN.md byte-compat item 2's key-omission-vs-null rule).
 //
 // Evidence: SPEC/ledger-trust.md "Telemetry ledger record", byte-compat
 // items 2 and 12; plugins/cool-workflow/src/telemetry-ledger.ts:1-224.
@@ -43,7 +43,7 @@ function genesisPrevHash(runId) {
  *  recordHash itself. `reportedUsage`/`resultDigest` are OMITTED (not
  *  `null`) when absent, so a usage-only record's hash is byte-identical
  *  to a pre-result-coverage one (back-compat with old ledgers) — see
- *  v2/PLAN.md byte-compat item 2. */
+ *  docs/rebuild/PLAN.md byte-compat item 2. */
 function recordHashInput(record) {
     return (0, hash_1.telemetryStableStringify)({
         schemaVersion: record.schemaVersion,

package/dist/core/version.js

@@ -7,7 +7,7 @@ exports.MIN_SUPPORTED_RUN_STATE_SCHEMA_VERSION = exports.LEGACY_RUN_STATE_SCHEMA
 // `cw version` output does not change bytes just because the code under it
 // was rebuilt. See SPEC/cli-surface.md "Exact outputs > Version" and
 // conformance/cases/version-basic.case.js (regex `/^\d+\.\d+\.\d+\n$/`).
-exports.CURRENT_COOL_WORKFLOW_VERSION = "0.2.0";
+exports.CURRENT_COOL_WORKFLOW_VERSION = "0.2.1";
 // State-kernel schema version constants (SPEC/state-core.md "Version
 // constants"). Pinned to the old build's src/version.ts byte-for-byte.
 exports.WORKFLOW_APP_SCHEMA_VERSION = 1;

package/dist/core/workflow-apps/app-schema.js

@@ -4,7 +4,7 @@
 // `agent`, `artifact`, `subWorkflow`, `input`), and full manifest
 // validation (`validateWorkflowApp`).
 //
-// MILESTONE 12 (v2/PLAN.md build order; workflow-apps.md). Milestone 6+7
+// MILESTONE 12 (docs/rebuild/PLAN.md build order; workflow-apps.md). Milestone 6+7
 // built the minimal real subset needed to load ONE app and drive it
 // end to end (see git history / the old header note this replaces).
 // This milestone adds, on top of that, WITHOUT changing any existing

package/dist/mcp/dispatch.js

@@ -2,7 +2,7 @@
 // mcp/dispatch.ts — the generic MCP tool-call reader over
 // core/capability-table.ts.
 //
-// MILESTONE 2 (v2/PLAN.md build order, step 2). Replaces the old build's
+// MILESTONE 2 (docs/rebuild/PLAN.md build order, step 2). Replaces the old build's
 // 196-arm `callTool` switch (src/mcp/tool-call.ts) with a data-driven
 // lookup: resolve the row by tool name, check its declared required-arg
 // groups (SPEC/mcp.md's `McpBinding.requiredArgs`), re-base `cwd` if

package/dist/mcp/server.js

@@ -2,7 +2,7 @@
 // mcp/server.ts — the stdio JSON-RPC loop: initialize / tools/list /
 // tools/call.
 //
-// MILESTONE 2 (v2/PLAN.md build order, step 2). Byte-exact port of the
+// MILESTONE 2 (docs/rebuild/PLAN.md build order, step 2). Byte-exact port of the
 // framing rules in SPEC/mcp.md's "JSON-RPC methods" / "Exact outputs" /
 // "Invariants and error behavior" #9 / "Edge cases" sections:
 //   - transport: stdin/stdout, ONE JSON object per line, no

package/dist/shell/agent-config.js

@@ -2,7 +2,7 @@
 // shell/agent-config.ts — agent delegation config: env/file/flag resolution
 // order, CW_HOME resolution, builtin:<name> expansion, PATH auto-detect.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/agent-config.ts.
 //
 // Resolution order per field: flags > env > a durable

package/dist/shell/doctor.js

@@ -2,7 +2,7 @@
 // shell/doctor.ts — `cw doctor` environment diagnostics, in the spirit of
 // `brew doctor`.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/doctor.ts's checks this milestone needs
 // (node/agent/agent-binary/git/home-registry/repo-state). The `--onramp`
 // section (buildDoctorOnramp) is later-milestone (reporting) territory and
@@ -167,7 +167,20 @@ function runDoctor(args = {}, env = process.env, cwd = process.cwd()) {
                 });
         }
     }
-    // 3. git — only needed for commit provenance; a warn, not a hard fail.
+    // 3. Sandbox enforcement boundary — a fixed architectural fact (see
+    // docs/sandbox-profiles.7.md), not a host-specific problem to fix, so this
+    // is "ok" (informational), never "warn": CW validates sandbox policy and
+    // gates worker-output acceptance, but OS-level read/write/execute/network/
+    // env isolation is the execution host's responsibility, which this doctor
+    // run cannot itself verify. An "ok" check carries no `fix` line by
+    // convention (see the node/git checks above), so the pointer to the docs
+    // lives in `detail` instead.
+    checks.push({
+        name: "sandbox-enforceability",
+        status: "ok",
+        detail: "CW sandbox profiles validate policy and gate worker-output acceptance; OS-level read/write/execute/network/env isolation is the execution host's responsibility (see docs/sandbox-profiles.7.md's ENFORCEMENT section) — this doctor run cannot verify that host enforcement.",
+    });
+    // 4. git — only needed for commit provenance; a warn, not a hard fail.
     const git = (0, node_child_process_1.spawnSync)("git", ["--version"], { encoding: "utf8", timeout: 5000 });
     checks.push(!git.error && git.status === 0
         ? { name: "git", status: "ok", detail: `${String(git.stdout || "git").trim()}.` }
@@ -177,7 +190,7 @@ function runDoctor(args = {}, env = process.env, cwd = process.cwd()) {
             detail: "git is not available — commit provenance (git HEAD) is recorded as absent.",
             fix: "Install git (e.g. `brew install git`) if you want commit provenance.",
         });
-    // 4. Home registry — the cross-repo run index lives here; must be writable.
+    // 5. Home registry — the cross-repo run index lives here; must be writable.
     const home = env.CW_HOME && String(env.CW_HOME).trim() ? path.resolve(String(env.CW_HOME)) : path.join(os.homedir(), ".local", "state", "cool-workflow");
     checks.push(dirWritable(home)
         ? { name: "home-registry", status: "ok", detail: `Home registry location is writable (${home}).` }
@@ -187,7 +200,7 @@ function runDoctor(args = {}, env = process.env, cwd = process.cwd()) {
             detail: `Home registry location is not writable: ${home}`,
             fix: "Set $CW_HOME to a writable directory, or fix the permissions.",
         });
-    // 5. Working-dir state — per-repo runs land under <cwd>/.cw.
+    // 6. Working-dir state — per-repo runs land under <cwd>/.cw.
     const cwState = path.join(path.resolve(cwd), ".cw");
     checks.push(dirWritable(cwState)
         ? { name: "repo-state", status: "ok", detail: `Run state location is writable (${cwState}).` }

package/dist/shell/drive.js

@@ -3,7 +3,7 @@
 // once per step and performs the spawn/commit/cache-write IO the
 // decision names.
 //
-// MILESTONE 6+7 (combined; see v2/PLAN.md Open risk 9/10 — the LARGEST
+// MILESTONE 6+7 (combined; see docs/rebuild/PLAN.md Open risk 9/10 — the LARGEST
 // milestone). Byte-exact port of the old build's src/drive.ts's
 // imperative shell around the pure decision core now in
 // core/pipeline/drive-decide.ts. Sub-workflow nesting and `--incremental`
@@ -76,7 +76,6 @@ const trust_audit_1 = require("./trust-audit");
 const agent_config_1 = require("./agent-config");
 const registry_1 = require("./execution-backend/registry");
 const agent_1 = require("./execution-backend/agent");
-const local_1 = require("./execution-backend/local");
 const hash_1 = require("../core/hash");
 const pipeline_1 = require("./pipeline");
 const reporter_1 = require("./reporter");
@@ -384,6 +383,25 @@ function processSelectedTask(ctx, selectedId, preparedOutcome, deferPersist = fa
     catch (error) {
         return handleHop(ctx, selected, workerId, `result.md rejected: ${errMessage(error)}`, deferPersist, deferPersist ? run : undefined);
     }
+    // Trust visibility (purely additive, no execution-behavior change): when
+    // the agent backend forwarded provider-namespace env vars (CW_/ANTHROPIC_/
+    // etc.) to the delegated child, record the NAMES (never values) as their
+    // own tamper-evident audit event, mirroring the worker.sub-workflow event
+    // pattern above. Only ever populated by execution-backend/agent.ts's
+    // recordedAgentHandle() — a no-op for every other backend.
+    const forwardedEnvVars = handle?.metadata?.forwardedEnvVars || [];
+    if (forwardedEnvVars.length) {
+        (0, trust_audit_1.recordTrustAuditEvent)(run, {
+            kind: "worker.agent-env",
+            decision: "delegated",
+            source: "runtime-derived",
+            workerId,
+            taskId: selected.id,
+            nodeId: selected.resultNodeId,
+            envVars: forwardedEnvVars,
+            metadata: { reason: "provider-namespace env vars forwarded from host process env to the delegated agent child" },
+        });
+    }
     if (cachePath && fs.existsSync(manifest.resultPath)) {
         writeResultCache(cachePath, fs.readFileSync(manifest.resultPath, "utf8"));
     }
@@ -664,13 +682,7 @@ function prepareConcurrentOutcomes(ctx, batch) {
         if (job) {
             const sandboxPolicy = manifest.sandboxPolicy;
             if (sandboxPolicy) {
-                const filteredEnv = (0, local_1.buildChildEnv)(sandboxPolicy);
-                for (const key of Object.keys(process.env)) {
-                    if (/^(CW_|ANTHROPIC_|OPENAI_|GEMINI_|DEEPSEEK_|CODEX_|GOOGLE_|COHERE_|MISTRAL_|OLLAMA_|AZURE_|AWS_)/i.test(key)) {
-                        filteredEnv[key] = process.env[key];
-                    }
-                }
-                job.env = filteredEnv;
+                job.env = (0, agent_1.buildAgentChildEnv)(sandboxPolicy).env;
             }
             jobs.push(job);
             jobTaskIds.push(taskId);

package/dist/shell/execution-backend/agent.js

@@ -2,7 +2,7 @@
 // shell/execution-backend/agent.ts — agent-delegation pure helpers +
 // concurrent batch fulfillment.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/execution-backend/agent.ts. This module holds
 // the PURE data-transform helpers (invocation resolution, arg substitution,
 // secret redaction, report parsing) plus the batch delegate-child spawn.
@@ -49,6 +49,7 @@ var __importStar = (this && this.__importStar) || (function () {
     };
 })();
 Object.defineProperty(exports, "__esModule", { value: true });
+exports.buildAgentChildEnv = buildAgentChildEnv;
 exports.resolveAgentInvocation = resolveAgentInvocation;
 exports.stripSecretArgs = stripSecretArgs;
 exports.parseAgentReport = parseAgentReport;
@@ -70,6 +71,35 @@ const envelopes_1 = require("./envelopes");
 function messageOf(error) {
     return error instanceof Error ? error.message : String(error);
 }
+const AGENT_PROVIDER_KEY_ENV_RE = /^(CW_|ANTHROPIC_|OPENAI_|GEMINI_|DEEPSEEK_|CODEX_|GOOGLE_|COHERE_|MISTRAL_|OLLAMA_|AZURE_|AWS_)/i;
+/** Build the env for a REAL spawned agent child under a sandbox policy: the
+ *  policy's own PATH+HOME+expose/deny base (buildChildEnv), plus provider-key
+ *  vars (the CW_, ANTHROPIC_, etc. prefixes), plus USER. USER is not a provider key, but a
+ *  real vendor CLI (claude, at least) reads it to resolve its own OS-level
+ *  login/keychain credential in headless mode -- buildChildEnv alone keeps
+ *  only PATH+HOME under the readonly policy, so a spawned agent that IS
+ *  logged in interactively reported "Not logged in" here. Found live: PATH+
+ *  HOME alone reproduces it, adding USER back fixes it, LOGNAME alone does
+ *  not. This is the ONE place that builds this env -- the single-request
+ *  (runAgentProcess) and concurrent-batch (shell/drive.ts) spawn paths both
+ *  call it, so the allowlist cannot drift into a second silent copy again.
+ *  Returns the forwarded var NAMES too (never values) for the
+ *  worker.agent-env trust-audit event. */
+function buildAgentChildEnv(policy, baseEnv = process.env) {
+    const env = (0, local_1.buildChildEnv)(policy, baseEnv);
+    const forwarded = [];
+    for (const key of Object.keys(baseEnv)) {
+        if (AGENT_PROVIDER_KEY_ENV_RE.test(key)) {
+            env[key] = baseEnv[key];
+            forwarded.push(key);
+        }
+    }
+    if (baseEnv.USER !== undefined && env.USER === undefined) {
+        env.USER = baseEnv.USER;
+        forwarded.push("USER");
+    }
+    return { env, forwarded };
+}
 /** Resolve the agent invocation from the request delegation > env.
  *  Vendor-neutral; the durable file config is folded in by the drive layer
  *  before this point (see shell/agent-config.ts's resolveAgentConfig). */
@@ -203,7 +233,7 @@ function substituteAgentArg(arg, subst) {
 /** Build the recorded process handle for the envelope — secret-stripped +
  *  the agent-reported model. Same SHAPE that lands in provenance, never in
  *  evidence. */
-function recordedAgentHandle(binary, endpoint, recordedArgs, model, reportedModel, reportedUsage, usageSignature) {
+function recordedAgentHandle(binary, endpoint, recordedArgs, model, reportedModel, reportedUsage, usageSignature, forwardedEnvVars) {
     const ref = binary ? [binary, ...recordedArgs].join(" ") : endpoint || "";
     return {
         kind: "process",
@@ -217,6 +247,7 @@ function recordedAgentHandle(binary, endpoint, recordedArgs, model, reportedMode
             reportedModel,
             ...(reportedUsage ? { reportedUsage } : {}),
             ...(usageSignature ? { usageSignature } : {}),
+            ...(forwardedEnvVars && forwardedEnvVars.length ? { forwardedEnvVars } : {}),
         },
     };
 }
@@ -365,17 +396,18 @@ function runAgentProcess(descriptor, policy, request, label, attestation) {
         const realArgs = resolved.rawArgs.map((arg) => substituteAgentArg(arg, subst));
         const recordedArgs = stripSecretArgs(realArgs);
         let outcome;
+        // Names only, never values — for the worker.agent-env trust-audit event
+        // below. Stays empty for a preparedAgentOutcome (a batch-delegated child
+        // that already ran elsewhere; this code path forwards nothing itself).
+        let forwardedEnvVars = [];
         if (request.preparedAgentOutcome) {
             outcome = request.preparedAgentOutcome;
         }
         else {
             const streamStderr = shouldStreamAgentStderr(process.env, Boolean(process.stderr.isTTY));
-            const childEnv = (0, local_1.buildChildEnv)(policy);
-            for (const key of Object.keys(process.env)) {
-                if (/^(CW_|ANTHROPIC_|OPENAI_|GEMINI_|DEEPSEEK_|CODEX_|GOOGLE_|COHERE_|MISTRAL_|OLLAMA_|AZURE_|AWS_)/i.test(key)) {
-                    childEnv[key] = process.env[key];
-                }
-            }
+            const built = buildAgentChildEnv(policy);
+            const childEnv = built.env;
+            forwardedEnvVars = built.forwarded;
             const child = (0, node_child_process_1.spawnSync)(resolved.binary, realArgs, {
                 cwd: request.cwd,
                 env: childEnv,
@@ -392,7 +424,7 @@ function runAgentProcess(descriptor, policy, request, label, attestation) {
             };
         }
         if (outcome.spawnError) {
-            const handleOut = recordedAgentHandle(resolved.binary, undefined, recordedArgs, resolved.model, "unreported");
+            const handleOut = recordedAgentHandle(resolved.binary, undefined, recordedArgs, resolved.model, "unreported", undefined, undefined, forwardedEnvVars);
             return (0, envelopes_1.refusedEnvelope)(descriptor, policy, label, "delegation-failed", `agent process failed to spawn: ${outcome.spawnError}`, {
                 ...attestation,
                 handle: handleOut,
@@ -402,7 +434,7 @@ function runAgentProcess(descriptor, policy, request, label, attestation) {
         const stdout = outcome.stdout;
         const report = parseAgentReport(stdout);
         const reportedModel = report.model && report.model.trim() ? report.model.trim() : "unreported";
-        const handleOut = recordedAgentHandle(resolved.binary, undefined, recordedArgs, resolved.model, reportedModel, report.usage, report.usageSignature);
+        const handleOut = recordedAgentHandle(resolved.binary, undefined, recordedArgs, resolved.model, reportedModel, report.usage, report.usageSignature, forwardedEnvVars);
         if (exitCode === null) {
             return (0, envelopes_1.refusedEnvelope)(descriptor, policy, label, "delegation-failed", `agent process returned no exit code (timed out or killed)`, { ...attestation, handle: handleOut });
         }

package/dist/shell/execution-backend/ci.js

@@ -1,7 +1,7 @@
 "use strict";
 // shell/execution-backend/ci.ts — the ci delegating driver.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). The ci driver shares its
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). The ci driver shares its
 // entire HTTP-delegation body with the remote driver (byte-exact port of
 // plugins/cool-workflow/src/execution-backend.ts, which also shares
 // `runHttpDelegation` between the two); this file just re-exports the ci

package/dist/shell/execution-backend/container.js

@@ -1,7 +1,7 @@
 "use strict";
 // shell/execution-backend/container.ts — the container delegating driver.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/execution-backend.ts's container handle builder
 // (:1068-1075) and `runContainer` (:720-792).
 //

package/dist/shell/execution-backend/envelopes.js

@@ -3,7 +3,7 @@
 // every delegating driver (container/remote/ci/agent) plus the registry's
 // own refusal path.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of the
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of the
 // `delegatedEnvelope` (src/execution-backend.ts:680-713) and
 // `refusedEnvelope` (:1095-1126) helpers, factored into one shared module
 // since every delegating driver builds the identical shape (byte-stable

package/dist/shell/execution-backend/local.js

@@ -2,7 +2,7 @@
 // shell/execution-backend/local.ts — the local-execution driver body
 // (executeLocal) shared by the node/bun/shell built-in drivers.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/execution-backend.ts's `executeLocal` (lines
 // 547-626) plus the leaf helpers it needs (sha256/hasExecutable/messageOf).
 //

package/dist/shell/execution-backend/probes.js

@@ -1,7 +1,7 @@
 "use strict";
 // shell/execution-backend/probes.ts — per-backend readiness probe bodies.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/execution-backend/probes.ts. Each probe is a
 // pure free function of the host (PATH + configured env); the registry's
 // `probeBackend` wraps these with the descriptor-derived envelope.

package/dist/shell/execution-backend/registry.js

@@ -3,7 +3,7 @@
 // registerBackend, resolveBackendSelection, attestSandbox, probeBackend,
 // runBackend, and the CLI-facing inspection payloads.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/execution-backend.ts (the parts not carved into
 // local.ts/container.ts/remote.ts/ci.ts/agent.ts/probes.ts).
 //

package/dist/shell/execution-backend/remote.js

@@ -2,7 +2,7 @@
 // shell/execution-backend/remote.ts — remote/ci delegating drivers (shared
 // HTTP-delegation body) + handle builders.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/execution-backend.ts's `runHttpDelegation`
 // (:821-876), `remoteHandle` (:1077-1084), `ciHandle` (:1086-1093), and
 // `delegateChildScript` (:801-811).

package/dist/shell/execution-backend/types.js

@@ -1,7 +1,7 @@
 "use strict";
 // shell/execution-backend/types.ts — plain data shapes for the driver layer.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of the shapes
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of the shapes
 // in the old build's src/types/execution-backend.ts and the sandbox slice of
 // src/types/sandbox.ts that this subsystem needs. Types only — no logic — so
 // this file is safe to import from both shell/ (impure) and any future core/

package/dist/shell/fs-atomic.js

@@ -5,7 +5,7 @@
 // `writeJson` here, so the write bytes stay exactly one place.
 //
 // Evidence: SPEC/state-core.md "Write ordering and atomic rules", "Lock
-// protocol"; v2/PLAN.md byte-compat items 1 and 6.
+// protocol"; docs/rebuild/PLAN.md byte-compat items 1 and 6.
 var __createBinding = (this && this.__createBinding) || (Object.create ? (function(o, m, k, k2) {
     if (k2 === undefined) k2 = k;
     var desc = Object.getOwnPropertyDescriptor(m, k);

package/dist/shell/ledger-io.js

@@ -5,7 +5,7 @@
 //
 // MILESTONE 8. Byte-exact port of the old build's src/ledger.ts stage-2
 // git-transport functions (listLedgerEntries, unionLedgerEntries), split
-// out per v2/PLAN.md's core/shell rule since these two functions are the
+// out per docs/rebuild/PLAN.md's core/shell rule since these two functions are the
 // ONLY impure ones in the old ledger.ts module.
 //
 // Evidence: SPEC/ledger-trust.md "Handoff ledger entry" (listLedgerEntries/

package/dist/shell/metrics-cli.js

@@ -72,12 +72,14 @@ function metricsShowCli(runId, args) {
     const policy = (0, observability_1.loadCostPolicy)(args, pluginRoot());
     return (0, observability_1.showMetricsReport)(run, { now: nowOf(args), policy });
 }
-/** `cw metrics summary [--scope repo|home] [--pricing ...] [--now ISO]`. */
+/** `cw metrics summary [--scope repo|home] [--pricing ...] [--now ISO] [--limit N]`.
+ *  `--limit` defaults to RunRegistry.list()'s own 50-record floor when omitted. */
 function metricsSummaryCli(args) {
     const cwd = invocationCwd(args);
     const scope = args.scope === "home" ? "home" : "repo";
     const registry = new run_registry_io_1.RunRegistry(cwd);
-    const listing = registry.list({ scope, includeArchived: true });
+    const limit = args.limit === undefined ? undefined : Number(args.limit);
+    const listing = registry.list({ scope, includeArchived: true, limit });
     const inputs = [];
     let unreadableRuns = 0;
     for (const record of listing.records) {

package/dist/shell/multi-agent-host.js

@@ -9,7 +9,7 @@
 // deterministic step order), hostBlackboard's action dispatch. The
 // `summaries.workers/candidates/feedback/commits/operator` blocks are
 // simplified real projections (not the full operator-ux/multi-agent-
-// operator-ux module — out of this milestone's scope per v2/PLAN.md's
+// operator-ux module — out of this milestone's scope per docs/rebuild/PLAN.md's
 // build-order list) — every FIELD the conformance cases actually assert
 // on (`summaries.topologies.officialTopologies`, the envelope's fixed key
 // set, `ids.*`) is still byte-exact; the parts no case reaches are

package/dist/shell/reclamation-io.js

@@ -2,7 +2,7 @@
 // shell/reclamation-io.ts — gc plan/run/verify's write-ahead reclamation
 // transaction, plus the orphan-run sweep and the clone cache gc.
 //
-// MILESTONE 10 (v2/PLAN.md build order, step 10). Byte-exact port of the
+// MILESTONE 10 (docs/rebuild/PLAN.md build order, step 10). Byte-exact port of the
 // old build's src/reclamation.ts + src/reclamation/hash.ts +
 // src/run-registry/{gc,orphans}.ts + src/clones.ts. Reuses
 // shell/fs-atomic.ts's `withFileLock` directly (no reimplementation, per

package/dist/shell/registry-cli.js

@@ -58,6 +58,7 @@ exports.routineCreateCli = routineCreateCli;
 exports.routineListCli = routineListCli;
 exports.routineDeleteCli = routineDeleteCli;
 exports.routineFireCli = routineFireCli;
+exports.resolveRoutineFirePayload = resolveRoutineFirePayload;
 exports.routineEventsCli = routineEventsCli;
 exports.registryRefreshCli = registryRefreshCli;
 exports.registryShowCli = registryShowCli;
@@ -79,6 +80,7 @@ exports.orphansListCli = orphansListCli;
 exports.orphansGcCli = orphansGcCli;
 exports.clonesListCli = clonesListCli;
 exports.clonesGcCli = clonesGcCli;
+const fs = __importStar(require("node:fs"));
 const path = __importStar(require("node:path"));
 const run_registry_io_1 = require("./run-registry-io");
 const pipeline_1 = require("./pipeline");
@@ -149,6 +151,19 @@ function routineDeleteCli(id, options = {}) {
 function routineFireCli(kind, payload, options = {}) {
     return new scheduler_io_1.RoutineTriggerBridge(resolveCwd(options)).fire(kind, payload);
 }
+/** Resolves a `routine fire` payload: a `--payload-path`/positional file wins
+ *  (parsed as JSON) over the raw CLI/MCP options bag. The file read lives
+ *  here, in the shell layer, not in core/capability-table.ts. */
+function resolveRoutineFirePayload(payloadPath, options) {
+    if (!payloadPath)
+        return options;
+    try {
+        return JSON.parse(fs.readFileSync(payloadPath, "utf8"));
+    }
+    catch (e) {
+        throw new Error(`Failed to parse payload file "${payloadPath}": ${String((e && e.message) || e)}`);
+    }
+}
 function routineEventsCli(id, options = {}) {
     return new scheduler_io_1.RoutineTriggerBridge(resolveCwd(options)).events(id);
 }

package/dist/shell/run-registry-io.js

@@ -2,7 +2,7 @@
 // shell/run-registry-io.ts — the on-disk run registry: index/queue/history
 // persistence, lifecycle derivation, search/resume/archive/rerun.
 //
-// MILESTONE 10 (v2/PLAN.md build order, step 10). Byte-exact port of the
+// MILESTONE 10 (docs/rebuild/PLAN.md build order, step 10). Byte-exact port of the
 // old build's src/run-registry.ts + src/run-registry/{derive,policy,
 // queue}.ts. The registry is a DERIVED, rebuildable index over each repo's
 // `.cw/runs/<id>/state.json` (the single source of truth, never mutated

package/dist/shell/sandbox-profile.js

@@ -2,7 +2,7 @@
 // shell/sandbox-profile.ts — the 4 bundled sandbox profiles, resolution,
 // validation, and the runtime read/write/command/network checks.
 //
-// MILESTONE 5 (v2/PLAN.md build order, step 5). Byte-exact port of
+// MILESTONE 5 (docs/rebuild/PLAN.md build order, step 5). Byte-exact port of
 // plugins/cool-workflow/src/sandbox-profile.ts.
 //
 // Evidence: SPEC/execution-backend.md "Sandbox profiles".