cool-workflow 0.2.2 → 0.2.4

package/docs/operator-ux.7.md

@@ -10,7 +10,7 @@ deterministic summaries for people, while it keeps JSON for scripts and MCP.
 Human status is the default:
 
 ```bash
-node scripts/cw.js status <run-id>
+cw status <run-id>
 ```
 
 The status view gives you run id, workflow/app id and version, loop stage, active
@@ -21,8 +21,8 @@ path, and the next command it puts forward.
 Machine-readable status is still there for you:
 
 ```bash
-node scripts/cw.js status <run-id> --json
-node scripts/cw.js status <run-id> --format json
+cw status <run-id> --json
+cw status <run-id> --format json
 ```
 
 `CoolWorkflowRunner.status()` and MCP `cw_status` still give back structured
@@ -39,19 +39,19 @@ The things it puts forward are deterministic and use only commands that are in
 the CW CLI. Examples:
 
 ```text
-node scripts/cw.js dispatch <run-id> --limit 4
+cw dispatch <run-id> --limit 4
   reason: pending tasks are ready for the active phase
 
-node scripts/cw.js worker manifest <run-id> <worker-id>
+cw worker manifest <run-id> <worker-id>
   reason: running workers need their manifests inspected
 
-node scripts/cw.js feedback show <run-id> <feedback-id>
+cw feedback show <run-id> <feedback-id>
   reason: open feedback should be resolved before more dispatch
 
-node scripts/cw.js candidate register <run-id> --worker <worker-id>
+cw candidate register <run-id> --worker <worker-id>
   reason: a completed worker result has not been registered as a candidate
 
-node scripts/cw.js commit <run-id> --selection <selection-id>
+cw commit <run-id> --selection <selection-id>
   reason: a verified selected candidate is ready for a verifier-gated commit
 ```
 
@@ -63,15 +63,15 @@ work is done, the advisor points to `cw report <run-id> --show`.
 Use the top-level graph command for a small console map:
 
 ```bash
-node scripts/cw.js graph <run-id>
-node scripts/cw.js graph <run-id> --json
+cw graph <run-id>
+cw graph <run-id> --json
 ```
 
 The legacy node command still works:
 
 ```bash
-node scripts/cw.js node graph <run-id>
-node scripts/cw.js node graph <run-id> --json
+cw node graph <run-id>
+cw node graph <run-id> --json
 ```
 
 The human graph puts phases, tasks, dispatches, workers, result nodes,
@@ -90,10 +90,10 @@ v0.1.21 adds clear multi-agent operator views that answer who is dependent on
 whom, who is blocked, and which evidence went into the accepted result:
 
 ```bash
-node scripts/cw.js multi-agent graph <run-id>
-node scripts/cw.js multi-agent dependencies <run-id>
-node scripts/cw.js multi-agent failures <run-id>
-node scripts/cw.js multi-agent evidence <run-id>
+cw multi-agent graph <run-id>
+cw multi-agent dependencies <run-id>
+cw multi-agent failures <run-id>
+cw multi-agent evidence <run-id>
 ```
 
 The same derived model is in `status`, `report --show`, and
@@ -106,14 +106,14 @@ trace from agent membership to verifier-gated commit.
 `cw report` still writes the Markdown report file and prints its path:
 
 ```bash
-node scripts/cw.js report <run-id>
+cw report <run-id>
 ```
 
 Use `--show` or `--summary` when the operator needs a console report that is easy to read:
 
 ```bash
-node scripts/cw.js report <run-id> --show
-node scripts/cw.js report <run-id> --summary
+cw report <run-id> --show
+cw report <run-id> --summary
 ```
 
 The console report gives the same high-value status panels plus active and
@@ -124,25 +124,25 @@ pending tasks, evidence paths and locators, and resource inspection commands.
 The chief run resources have human summaries by default and JSON when you ask for it:
 
 ```bash
-node scripts/cw.js worker summary <run-id>
-node scripts/cw.js worker summary <run-id> --json
+cw worker summary <run-id>
+cw worker summary <run-id> --json
 
-node scripts/cw.js candidate summary <run-id>
-node scripts/cw.js candidate summary <run-id> --json
+cw candidate summary <run-id>
+cw candidate summary <run-id> --json
 
-node scripts/cw.js feedback summary <run-id>
-node scripts/cw.js feedback summary <run-id> --json
+cw feedback summary <run-id>
+cw feedback summary <run-id> --json
 
-node scripts/cw.js commit summary <run-id>
-node scripts/cw.js commit summary <run-id> --json
+cw commit summary <run-id>
+cw commit summary <run-id> --json
 
-node scripts/cw.js multi-agent summary <run-id>
-node scripts/cw.js multi-agent summary <run-id> --json
-node scripts/cw.js multi-agent graph <run-id>
-node scripts/cw.js multi-agent graph <run-id> --json
-node scripts/cw.js multi-agent dependencies <run-id>
-node scripts/cw.js multi-agent failures <run-id>
-node scripts/cw.js multi-agent evidence <run-id>
+cw multi-agent summary <run-id>
+cw multi-agent summary <run-id> --json
+cw multi-agent graph <run-id>
+cw multi-agent graph <run-id> --json
+cw multi-agent dependencies <run-id>
+cw multi-agent failures <run-id>
+cw multi-agent evidence <run-id>
 ```
 
 Worker summaries show allocated/running/verified/failed/rejected counts,

package/docs/pipeline-runner.7.md

@@ -93,10 +93,10 @@ commit stage.
 Commands that look at runs print stable JSON:
 
 ```text
-cw.js contract show <run-id> [contract-id]
-cw.js node list <run-id>
-cw.js node show <run-id> <node-id>
-cw.js node graph <run-id>
+cw contract show <run-id> [contract-id]
+cw node list <run-id>
+cw node show <run-id> <node-id>
+cw node graph <run-id>
 ```
 
 ## EXAMPLES

package/docs/project-index.md

@@ -1,15 +1,15 @@
 # Cool Workflow Project Index
 
-Generated from the current repository code on 2026-07-08 by `npm run sync:project-index`.
+Generated from the current repository code on 2026-07-11 by `npm run sync:project-index`.
 
 ## Snapshot
 
 - Package: `cool-workflow`
-- Version: `0.2.2`
-- Source modules: `145`
+- Version: `0.2.4`
+- Source modules: `149`
 - Workflow apps: `8`
 - Docs: `62`
-- Smoke tests: `181`
+- Smoke tests: `204`
 - Repository: https://github.com/coo1white/cool-workflow
 
 ## Architecture
@@ -84,7 +84,9 @@ multi-agent host -> topology -> blackboard/coordinator
 - [cli/parseargv.ts](../src/cli/parseargv.ts)
 - [core/capability-data.ts](../src/core/capability-data.ts)
 - [core/capability-table.ts](../src/core/capability-table.ts)
+- [core/format/completion.ts](../src/core/format/completion.ts)
 - [core/format/help.ts](../src/core/format/help.ts)
+- [core/format/safe-json.ts](../src/core/format/safe-json.ts)
 - [core/format/state-explosion-text.ts](../src/core/format/state-explosion-text.ts)
 - [core/hash.ts](../src/core/hash.ts)
 - [core/multi-agent/collaboration.ts](../src/core/multi-agent/collaboration.ts)
@@ -116,7 +118,9 @@ multi-agent host -> topology -> blackboard/coordinator
 - [core/types/boundary.ts](../src/core/types/boundary.ts)
 - [core/types/execution-backend.ts](../src/core/types/execution-backend.ts)
 - [core/types/observability.ts](../src/core/types/observability.ts)
+- [core/util/cli-args.ts](../src/core/util/cli-args.ts)
 - [core/util/collate.ts](../src/core/util/collate.ts)
+- [core/util/numeric-flag.ts](../src/core/util/numeric-flag.ts)
 - [mcp/dispatch.ts](../src/mcp/dispatch.ts)
 - [mcp/server.ts](../src/mcp/server.ts)
 - [shell/agent-config.ts](../src/shell/agent-config.ts)
@@ -281,6 +285,7 @@ multi-agent host -> topology -> blackboard/coordinator
 Smoke tests mirror the public contracts. The high-signal suites are:
 
 - [agent-backend-concurrent-user-env-smoke.js](../test/agent-backend-concurrent-user-env-smoke.js)
+- [agent-backend-sandbox-deny-smoke.js](../test/agent-backend-sandbox-deny-smoke.js)
 - [agent-backend-user-env-smoke.js](../test/agent-backend-user-env-smoke.js)
 - [agent-config-atomic-write-smoke.js](../test/agent-config-atomic-write-smoke.js)
 - [agent-delegation-drive-smoke.js](../test/agent-delegation-drive-smoke.js)
@@ -303,6 +308,7 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [claude-p-agent-wrapper-smoke.js](../test/claude-p-agent-wrapper-smoke.js)
 - [cli-arg-parsing-smoke.js](../test/cli-arg-parsing-smoke.js)
 - [cli-command-surface-smoke.js](../test/cli-command-surface-smoke.js)
+- [cli-epipe-smoke.js](../test/cli-epipe-smoke.js)
 - [cli-format-smoke.js](../test/cli-format-smoke.js)
 - [cli-handler-clones-smoke.js](../test/cli-handler-clones-smoke.js)
 - [cli-handler-eval-node-smoke.js](../test/cli-handler-eval-node-smoke.js)
@@ -324,6 +330,7 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [contract-migration-tooling-smoke.js](../test/contract-migration-tooling-smoke.js)
 - [control-plane-scheduling-smoke.js](../test/control-plane-scheduling-smoke.js)
 - [coordinator-blackboard-smoke.js](../test/coordinator-blackboard-smoke.js)
+- [coordinator-topology-persist-dirty-tracking-smoke.js](../test/coordinator-topology-persist-dirty-tracking-smoke.js)
 - [cw-help-per-command-smoke.js](../test/cw-help-per-command-smoke.js)
 - [dead-export-removal-guard-smoke.js](../test/dead-export-removal-guard-smoke.js)
 - [deepseek-agent-wrapper-smoke.js](../test/deepseek-agent-wrapper-smoke.js)
@@ -331,11 +338,15 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [demo-bundle-smoke.js](../test/demo-bundle-smoke.js)
 - [det-ids-b-smoke.js](../test/det-ids-b-smoke.js)
 - [dispatch-legacy-burndown-smoke.js](../test/dispatch-legacy-burndown-smoke.js)
+- [doctor-audit-integrity-repair-smoke.js](../test/doctor-audit-integrity-repair-smoke.js)
 - [doctor-smoke.js](../test/doctor-smoke.js)
 - [dogfood-architecture-review-smoke.js](../test/dogfood-architecture-review-smoke.js)
 - [dogfood-release-smoke.js](../test/dogfood-release-smoke.js)
+- [drive-async-real-signal-smoke.js](../test/drive-async-real-signal-smoke.js)
 - [drive-concurrency-flag-smoke.js](../test/drive-concurrency-flag-smoke.js)
+- [drive-concurrent-round-sigkill-smoke.js](../test/drive-concurrent-round-sigkill-smoke.js)
 - [drive-exhaustion-blocked-smoke.js](../test/drive-exhaustion-blocked-smoke.js)
+- [drive-round-cache-serial-smoke.js](../test/drive-round-cache-serial-smoke.js)
 - [durable-atomic-write-smoke.js](../test/durable-atomic-write-smoke.js)
 - [end-to-end-demo-smoke.js](../test/end-to-end-demo-smoke.js)
 - [end-to-end-golden-path-smoke.js](../test/end-to-end-golden-path-smoke.js)
@@ -348,6 +359,7 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [execution-backends-smoke.js](../test/execution-backends-smoke.js)
 - [feedback-ops-unit-smoke.js](../test/feedback-ops-unit-smoke.js)
 - [freebsd-audit-fixes-smoke.js](../test/freebsd-audit-fixes-smoke.js)
+- [fs-atomic-lock-steal-race-smoke.js](../test/fs-atomic-lock-steal-race-smoke.js)
 - [gemini-agent-wrapper-smoke.js](../test/gemini-agent-wrapper-smoke.js)
 - [gemini-opencode-agent-wrapper-smoke.js](../test/gemini-opencode-agent-wrapper-smoke.js)
 - [h7-custom-profile-persist-smoke.js](../test/h7-custom-profile-persist-smoke.js)
@@ -357,9 +369,11 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [ledger-resolution-smoke.js](../test/ledger-resolution-smoke.js)
 - [ledger-verify-smoke.js](../test/ledger-verify-smoke.js)
 - [loop-bounded-expansion-smoke.js](../test/loop-bounded-expansion-smoke.js)
+- [man-run-registry-traversal-smoke.js](../test/man-run-registry-traversal-smoke.js)
 - [mcp-app-surface-smoke.js](../test/mcp-app-surface-smoke.js)
 - [mcp-surface-registry-smoke.js](../test/mcp-surface-registry-smoke.js)
 - [mcp-tool-call-coverage-smoke.js](../test/mcp-tool-call-coverage-smoke.js)
+- [mcp-untrusted-content-advisory-smoke.js](../test/mcp-untrusted-content-advisory-smoke.js)
 - [metrics-summary-limit-smoke.js](../test/metrics-summary-limit-smoke.js)
 - [multi-agent-cli-mcp-surface-smoke.js](../test/multi-agent-cli-mcp-surface-smoke.js)
 - [multi-agent-eval-determinism-regression-smoke.js](../test/multi-agent-eval-determinism-regression-smoke.js)
@@ -367,6 +381,7 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [multi-agent-eval-replay-smoke.js](../test/multi-agent-eval-replay-smoke.js)
 - [multi-agent-operator-ux-smoke.js](../test/multi-agent-operator-ux-smoke.js)
 - [multi-agent-runtime-core-smoke.js](../test/multi-agent-runtime-core-smoke.js)
+- [multi-agent-state-lock-concurrency-smoke.js](../test/multi-agent-state-lock-concurrency-smoke.js)
 - [multi-agent-topologies-debate-smoke.js](../test/multi-agent-topologies-debate-smoke.js)
 - [multi-agent-topologies-judge-panel-smoke.js](../test/multi-agent-topologies-judge-panel-smoke.js)
 - [multi-agent-topologies-map-reduce-smoke.js](../test/multi-agent-topologies-map-reduce-smoke.js)
@@ -375,6 +390,7 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [node-snapshot-diff-replay-smoke.js](../test/node-snapshot-diff-replay-smoke.js)
 - [npm-global-install-smoke.js](../test/npm-global-install-smoke.js)
 - [npm-trusted-publish-smoke.js](../test/npm-trusted-publish-smoke.js)
+- [numeric-flag-parsing-smoke.js](../test/numeric-flag-parsing-smoke.js)
 - [observability-cost-accounting-smoke.js](../test/observability-cost-accounting-smoke.js)
 - [one-way-boundary-smoke.js](../test/one-way-boundary-smoke.js)
 - [onramp-check-smoke.js](../test/onramp-check-smoke.js)
@@ -401,9 +417,11 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [readme-trust-claim-smoke.js](../test/readme-trust-claim-smoke.js)
 - [real-execution-backends-smoke.js](../test/real-execution-backends-smoke.js)
 - [registry-corrupt-fail-closed-smoke.js](../test/registry-corrupt-fail-closed-smoke.js)
+- [registry-corrupt-state-distinct-error-smoke.js](../test/registry-corrupt-state-distinct-error-smoke.js)
 - [release-check-skip-smoke.js](../test/release-check-skip-smoke.js)
 - [release-flow-smoke.js](../test/release-flow-smoke.js)
 - [release-gate-smoke.js](../test/release-gate-smoke.js)
+- [release-oneclick-smoke.js](../test/release-oneclick-smoke.js)
 - [release-pipeline-hygiene-smoke.js](../test/release-pipeline-hygiene-smoke.js)
 - [release-tooling-smoke.js](../test/release-tooling-smoke.js)
 - [remote-link-archive-smoke.js](../test/remote-link-archive-smoke.js)
@@ -437,10 +455,14 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [schema-validation-smoke.js](../test/schema-validation-smoke.js)
 - [security-trust-hardening-smoke.js](../test/security-trust-hardening-smoke.js)
 - [self-audit-hardening-smoke.js](../test/self-audit-hardening-smoke.js)
+- [sigint-sigterm-drive-loop-smoke.js](../test/sigint-sigterm-drive-loop-smoke.js)
+- [smoke-duration-scheduling-smoke.js](../test/smoke-duration-scheduling-smoke.js)
 - [source-context-batch-smoke.js](../test/source-context-batch-smoke.js)
 - [source-context-profile-smoke.js](../test/source-context-profile-smoke.js)
 - [state-node-smoke.js](../test/state-node-smoke.js)
+- [status-run-flag-smoke.js](../test/status-run-flag-smoke.js)
 - [sub-workflow-nesting-smoke.js](../test/sub-workflow-nesting-smoke.js)
+- [summary-show-no-checkpoint-write-smoke.js](../test/summary-show-no-checkpoint-write-smoke.js)
 - [surface-explicit-cwd-smoke.js](../test/surface-explicit-cwd-smoke.js)
 - [tamper-evidence-demo-smoke.js](../test/tamper-evidence-demo-smoke.js)
 - [team-collaboration-smoke.js](../test/team-collaboration-smoke.js)
@@ -452,11 +474,16 @@ Smoke tests mirror the public contracts. The high-signal suites are:
 - [telemetry-verify-signatures-smoke.js](../test/telemetry-verify-signatures-smoke.js)
 - [token-budget-enforcement-smoke.js](../test/token-budget-enforcement-smoke.js)
 - [trust-audit-anchor-smoke.js](../test/trust-audit-anchor-smoke.js)
+- [trust-audit-append-lock-concurrency-smoke.js](../test/trust-audit-append-lock-concurrency-smoke.js)
+- [trust-audit-append-tail-cache-smoke.js](../test/trust-audit-append-tail-cache-smoke.js)
 - [vendor-manifest-load-smoke.js](../test/vendor-manifest-load-smoke.js)
 - [vendor-preflight-smoke.js](../test/vendor-preflight-smoke.js)
+- [verdict-signing-workflow-smoke.js](../test/verdict-signing-workflow-smoke.js)
 - [verifier-gated-commit-smoke.js](../test/verifier-gated-commit-smoke.js)
+- [verify-bump-reproduction-smoke.js](../test/verify-bump-reproduction-smoke.js)
 - [verify-import-audit-chain-smoke.js](../test/verify-import-audit-chain-smoke.js)
 - [web-desktop-workbench-smoke.js](../test/web-desktop-workbench-smoke.js)
+- [wiring-lazy-shell-imports-smoke.js](../test/wiring-lazy-shell-imports-smoke.js)
 - [worker-accept-path-architecture-smoke.js](../test/worker-accept-path-architecture-smoke.js)
 - [worker-isolation-smoke.js](../test/worker-isolation-smoke.js)
 - [worker-retry-count-smoke.js](../test/worker-retry-count-smoke.js)

package/docs/real-execution-backends.7.md

@@ -195,3 +195,7 @@ _No behavioral change in v0.1.89 (CLI-surface golden-path + help-output fixes on
 0.2.1
 
 0.2.2
+
+0.2.3
+
+0.2.4

package/docs/release-and-migration.7.md

@@ -9,7 +9,7 @@ Maintainers cutting CW releases should use `npm run release:check` from
 files can check compatibility with:
 
 ```bash
-node scripts/cw.js state check <run-id>
+cw state check <run-id>
 ```
 
 Use `--state /path/to/state.json` when checking a state file outside the
@@ -335,3 +335,7 @@ _No behavioral change in v0.1.89 (CLI-surface golden-path + help-output fixes on
 0.2.1
 
 0.2.2
+
+0.2.3
+
+0.2.4

package/docs/release-tooling.7.md

@@ -170,14 +170,32 @@ model you set up does the review. CW starts the agent argv-style (`shell:false`)
 takes on the agent's own credentials, and pulls in no model SDK — the red line.
 
 ```bash
+# the operator's one-command release (scripts/release-oneclick.js — preflight,
+# gated cut, tag-only push, CI wait, npm confirmation, verdict-record PR):
+npm run release -- 0.2.4
 # check only (gate + independent review, no mutation):
 node plugins/cool-workflow/scripts/release-flow.js --check
 # cut a tag once review is green (when --push, also creates the GitHub Release):
 node plugins/cool-workflow/scripts/release-flow.js --cut --version 0.1.77 [--push] [--no-release]
+# run ONLY the cut's fail-fast preflight (seconds; used by release-oneclick.js):
+node plugins/cool-workflow/scripts/release-flow.js --cut --version 0.1.77 --push --preflight-only
 # backfill / re-create the GitHub Release for an already-pushed tag (no gate/cut):
 node plugins/cool-workflow/scripts/release-flow.js --release --version 0.1.77 [--soft]
 ```
 
+A `--cut` starts with a fail-fast **preflight** (added after the v0.2.3 cut,
+where each of these fired only AFTER the gate/vendor/reviewer had already
+spent real time and tokens): the version flag, the signing key (present AND
+matching the committed `verdict-signing.pub` — once that pubkey is in the
+repo, an unsigned cut is refused up front instead of failing later in CI),
+no pre-existing `vX.Y.Z` tag (local or on origin), a `## X.Y.Z` CHANGELOG
+section, a clean tracked tree, and — for `--push` — HEAD equal to the
+`origin/main` tip (`--allow-stale-head` skips that one check for a
+deliberate re-cut). The push at the end moves ONLY `refs/tags/vX.Y.Z`: the
+verdict commit is a one-hop leaf on the reviewed commit, reachable through
+the tag alone, so main's branch protection is never in the path and no
+stray remote branch is created.
+
 The per-platform difference is config, not code — set the reviewer agent here:
 
 | Platform | Reviewer config |
@@ -298,3 +316,7 @@ _No behavioral change in v0.1.89 (CLI-surface golden-path + help-output fixes on
 0.2.1
 
 0.2.2
+
+0.2.3
+
+0.2.4

package/docs/routines.md

@@ -15,7 +15,7 @@ CW keeps routine data in:
 Create an API trigger:
 
 ```bash
-node scripts/cw.js routine create \
+cw routine create \
   --kind api \
   --prompt "Handle this API event."
 ```
@@ -23,7 +23,7 @@ node scripts/cw.js routine create \
 Create a GitHub trigger:
 
 ```bash
-node scripts/cw.js routine create \
+cw routine create \
   --kind github \
   --prompt "Review this GitHub event." \
   --match '{"action":"opened"}'
@@ -32,13 +32,13 @@ node scripts/cw.js routine create \
 Fire a trigger from a payload file:
 
 ```bash
-node scripts/cw.js routine fire github payload.json
+cw routine fire github payload.json
 ```
 
 Inspect events:
 
 ```bash
-node scripts/cw.js routine events
+cw routine events
 ```
 
 ## Long Architecture Reviews

package/docs/run-registry-control-plane.7.md

@@ -251,25 +251,25 @@ freshness, and provenance back to its `.cw/runs/<id>/`. Filter with `--app` and
 ## CLI
 
 ```text
-node scripts/cw.js registry refresh [--scope repo|home] [--json]
-node scripts/cw.js registry show [--scope repo|home] [--json]
-node scripts/cw.js run search [--app ID] [--status STATE] [--text Q] [--repo PATH] [--since ISO] [--until ISO] [--limit N] [--offset N] [--scope repo|home] [--json]
-node scripts/cw.js run list [--scope repo|home] [--json]
-node scripts/cw.js run show <run-id> [--scope repo|home] [--json]
-node scripts/cw.js run resume <run-id> [--limit N] [--drive [--once]] [--json]
-node scripts/cw.js run archive <run-id> [--reason TEXT] [--unarchive]
-node scripts/cw.js run archive --older-than-days N [--state completed --state failed]
-node scripts/cw.js run rerun <run-id> [--reason TEXT]
-node scripts/cw.js run export <run-id> --output PATH
-node scripts/cw.js run import PATH --target DIR
-node scripts/cw.js run verify-import <run-id> [--cwd DIR]
-node scripts/cw.js run inspect-archive PATH [--json]
-node scripts/cw.js run restore PATH --target DIR [--json]
-node scripts/cw.js queue add [--app ID|--workflow ID|--runId ID] [--repo PATH] [--priority N] [--note TEXT]
-node scripts/cw.js queue list [--status STATE] [--repo PATH] [--json]
-node scripts/cw.js queue show <queue-id>
-node scripts/cw.js queue drain [--limit N] [--repo PATH]
-node scripts/cw.js history [--app ID] [--status STATE] [--limit N] [--offset N] [--scope repo|home] [--json]
+cw registry refresh [--scope repo|home] [--json]
+cw registry show [--scope repo|home] [--json]
+cw run search [--app ID] [--status STATE] [--text Q] [--repo PATH] [--since ISO] [--until ISO] [--limit N] [--offset N] [--scope repo|home] [--json]
+cw run list [--scope repo|home] [--json]
+cw run show <run-id> [--scope repo|home] [--json]
+cw run resume <run-id> [--limit N] [--drive [--once]] [--json]
+cw run archive <run-id> [--reason TEXT] [--unarchive]
+cw run archive --older-than-days N [--state completed --state failed]
+cw run rerun <run-id> [--reason TEXT]
+cw run export <run-id> --output PATH
+cw run import PATH --target DIR
+cw run verify-import <run-id> [--cwd DIR]
+cw run inspect-archive PATH [--json]
+cw run restore PATH --target DIR [--json]
+cw queue add [--app ID|--workflow ID|--runId ID] [--repo PATH] [--priority N] [--note TEXT]
+cw queue list [--status STATE] [--repo PATH] [--json]
+cw queue show <queue-id>
+cw queue drain [--limit N] [--repo PATH]
+cw history [--app ID] [--status STATE] [--limit N] [--offset N] [--scope repo|home] [--json]
 ```
 
 Read commands print short human panels by default (lifecycle, freshness, counts,
@@ -478,3 +478,7 @@ _No behavioral change in v0.1.89 (CLI-surface golden-path + help-output fixes on
 0.2.1
 
 0.2.2
+
+0.2.3
+
+0.2.4

package/docs/run-retention-reclamation.7.md

@@ -107,6 +107,22 @@ scratch dir) is **re-pointed** to the retained `results/<task-id>.md` copy, and
 result-node snapshot is shown to stay `valid` (not `absent`) — so no surviving
 node points to a freed path. Opt out with `--keep-scratch`.
 
+## Commit snapshots — never reconstructable, always downgrades to verify-only
+
+`commitState` embeds the FULL run into `commits/<id>.json` on every commit, so
+these grow unbounded in both count and per-file size with no cap. Reclaiming them
+frees the run's superseded, non-`verifierGated` "checkpoint" commit snapshots —
+the run's LATEST commit and every `verifierGated` commit (the actual
+audit-significant milestones) are always kept. `run.commits`' own lightweight
+metadata (id, `verifierGated`, evidence digests, acceptance rationale — everything
+`extractSkeleton` seals) lives in `state.json`, not the snapshot file, so it stays
+fully intact and queryable regardless. Unlike a node snapshot, a commit snapshot is
+a genuine point-in-time capture with no `ReconstructionRecipe` — reclaiming even
+one downgrades capability to `verify-only`, never `re-runnable-by-reconstruction`.
+Each reclaimed commit's own `StateNode` had its `snapshot` artifact stripped (not
+re-pointed — there is no retained alternative) before the free, so `prepareFree`'s
+dangling-reference proof covers this kind too. Opt out with `--keep-commits`.
+
 ## Orphan runs — a second pure-scratch case, OUTSIDE this transaction
 
 A run directory can also be pure scratch a different way: a process killed or
@@ -131,8 +147,8 @@ class of run; it is left `retained` indefinitely rather than guessed at.
 ## CLI
 
 ```
-cw gc plan   [run-id] [--reclaimAfterArchiveDays N] [--keep-scratch] [--keep-snapshots] [--scope repo|home] [--json]
-cw gc run    [run-id] [--reclaimAfterArchiveDays N] [--keep-scratch] [--keep-snapshots] [--limit N] [--actor NAME] [--json]
+cw gc plan   [run-id] [--reclaimAfterArchiveDays N] [--keep-scratch] [--keep-snapshots] [--keep-commits] [--scope repo|home] [--json]
+cw gc run    [run-id] [--reclaimAfterArchiveDays N] [--keep-scratch] [--keep-snapshots] [--keep-commits] [--limit N] [--actor NAME] [--json]
 cw gc verify <run-id> [--scope repo|home] [--json]
 ```
 
@@ -163,7 +179,8 @@ rule: only ISO timestamps may be now-derived.
 
 Retention/reclamation thresholds extend `RunRegistryPolicy` (alongside
 `archiveOlderThanDays`), never a new policy file: `reclaimAfterArchiveDays`,
-`keepSnapshots`, `keepScratch`, `reclaimStates`, `maxReclaimRuns`, `maxReclaimBytes`.
+`keepSnapshots`, `keepScratch`, `keepCommits`, `reclaimStates`, `maxReclaimRuns`,
+`maxReclaimBytes`.
 Back-compatible defaults reclaim nothing; pre-v0.1.39 runs load unchanged.
 
 ## Compatibility
@@ -267,3 +284,7 @@ _No behavioral change in v0.1.89 (CLI-surface golden-path + help-output fixes on
 0.2.1
 
 0.2.2
+
+0.2.3
+
+0.2.4

package/docs/scheduled-tasks.md

@@ -14,7 +14,7 @@ CW keeps schedules in:
 Make a `/loop`-ready schedule:
 
 ```bash
-node scripts/cw.js loop \
+cw loop \
   --intervalMinutes 30 \
   --prompt "Check this workflow and continue if work is due."
 ```
@@ -22,7 +22,7 @@ node scripts/cw.js loop \
 Make a loop:
 
 ```bash
-node scripts/cw.js schedule create \
+cw schedule create \
   --kind loop \
   --intervalMinutes 30 \
   --prompt "Check this workflow and continue if work is due."
@@ -31,7 +31,7 @@ node scripts/cw.js schedule create \
 Make a cron schedule:
 
 ```bash
-node scripts/cw.js schedule create \
+cw schedule create \
   --kind cron \
   --cron "*/15 * * * *" \
   --prompt "Run the due workflow scan."
@@ -40,7 +40,7 @@ node scripts/cw.js schedule create \
 Make a reminder:
 
 ```bash
-node scripts/cw.js schedule create \
+cw schedule create \
   --kind reminder \
   --delayMinutes 60 \
   --prompt "Remind me to inspect the report."
@@ -49,26 +49,26 @@ node scripts/cw.js schedule create \
 List and look through:
 
 ```bash
-node scripts/cw.js schedule list
-node scripts/cw.js schedule due
-node scripts/cw.js schedule complete <schedule-id>
-node scripts/cw.js schedule pause <schedule-id>
-node scripts/cw.js schedule resume <schedule-id>
-node scripts/cw.js schedule run-now <schedule-id>
-node scripts/cw.js schedule history <schedule-id>
-node scripts/cw.js schedule delete <schedule-id>
+cw schedule list
+cw schedule due
+cw schedule complete <schedule-id>
+cw schedule pause <schedule-id>
+cw schedule resume <schedule-id>
+cw schedule run-now <schedule-id>
+cw schedule history <schedule-id>
+cw schedule delete <schedule-id>
 ```
 
 Run the local desktop-like daemon one time:
 
 ```bash
-node scripts/cw.js schedule daemon --once
+cw schedule daemon --once
 ```
 
 Run it without stopping:
 
 ```bash
-node scripts/cw.js schedule daemon --intervalSeconds 60
+cw schedule daemon --intervalSeconds 60
 ```
 
 ## Notes

package/docs/security-trust-hardening.7.md

@@ -82,21 +82,21 @@ With the require flag off (the default), none of this changes: a plain
 ## CLI
 
 ```bash
-node scripts/cw.js audit summary <run-id>
-node scripts/cw.js audit worker <run-id> <worker-id>
-node scripts/cw.js audit provenance <run-id> [--worker ID|--candidate ID|--commit ID]
-node scripts/cw.js audit multi-agent <run-id>
-node scripts/cw.js audit policy <run-id>
-node scripts/cw.js audit role <run-id> <role-id>
-node scripts/cw.js audit blackboard <run-id>
-node scripts/cw.js audit judge <run-id>
-node scripts/cw.js audit attest <run-id> --worker <worker-id> --hostEnforced true
-node scripts/cw.js audit decision <run-id> <worker-id> --path <path>
-node scripts/cw.js audit decision <run-id> <worker-id> --command "npm test"
-node scripts/cw.js audit decision <run-id> <worker-id> --network example.com
-node scripts/cw.js audit decision <run-id> <worker-id> --env SECRET_NAME
-node scripts/cw.js worker output <run-id> <worker-id> <result-file> [--allow-unattested]
-node scripts/cw.js result <run-id> <task-id> <result-file> [--allow-unattested]
+cw audit summary <run-id>
+cw audit worker <run-id> <worker-id>
+cw audit provenance <run-id> [--worker ID|--candidate ID|--commit ID]
+cw audit multi-agent <run-id>
+cw audit policy <run-id>
+cw audit role <run-id> <role-id>
+cw audit blackboard <run-id>
+cw audit judge <run-id>
+cw audit attest <run-id> --worker <worker-id> --hostEnforced true
+cw audit decision <run-id> <worker-id> --path <path>
+cw audit decision <run-id> <worker-id> --command "npm test"
+cw audit decision <run-id> <worker-id> --network example.com
+cw audit decision <run-id> <worker-id> --env SECRET_NAME
+cw worker output <run-id> <worker-id> <result-file> [--allow-unattested]
+cw result <run-id> <task-id> <result-file> [--allow-unattested]
 ```
 
 Denied audit decisions are put into audit files and joined to feedback/error