cool-workflow 0.1.84 → 0.1.86

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "cool-workflow",
   "description": "A workflow control plane and run-time you are able to check: it sends out jobs in TypeScript, makes certain of work against facts before it goes through, puts state into fixed records, orders jobs by time, runs jobs again and again, gets a group of agents to do their parts together, and talks MCP. It gives the doing of the work to outside agents — it never runs the models itself.",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "author": {
     "name": "COOLWHITE LLC"
   },

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "cool-workflow",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "description": "A workflow control plane and run-time you are able to check: it sends out jobs in TypeScript, makes certain of work against facts before it goes through, puts state into fixed records, orders jobs by time, runs jobs again and again, gets a group of agents to do their parts together, and talks MCP. It gives the doing of the work to outside agents — it never runs the models itself.",
   "author": {
     "name": "COOLWHITE LLC"

package/README.md

@@ -15,7 +15,7 @@
 ![MCP](https://img.shields.io/badge/MCP-native-8A2BE2?style=flat-square)
 ![runtime](https://img.shields.io/badge/runtime-TypeScript%20%C2%B7%20Node-3178C6?style=flat-square)
 
-**[Structure](#structure)** · [Commands](#commands) · [Result Envelope](#result-envelope) · [Scheduled Tasks](#scheduled-tasks) · [License](#license)
+**[Start Here](#start-here)** · [Quickstart](#quickstart) · [Developer Loop](#developer-loop) · [Commands](#commands) · [Release History](docs/release-history.md)
 
 Cool Workflow, or CW, is a free-standing agent workflow control-plane put up as a
 TypeScript runtime. It gives a COL-Architecture: Router / Orchestrator,
@@ -43,225 +43,34 @@ CW keeps to a small set of Unix-based workflow rules: small kernel,
 clear state, pipes that join, workers kept apart, and verifier-gated commits.
 See [docs/unix-principles.md](docs/unix-principles.md).
 
-CW v0.1.32 adds Team Collaboration: a host-attested actor, append-only
-approvals/rejections/comments/handoffs provenance-linked to a durable target
-(`run|task|candidate|selection|commit|node`), and a review gate that STACKS ON the
-verifier gate. Identity is ATTESTED provenance, never authenticated — a missing
-identity is the clear `unattributed` actor, never a made-up one. The review
-gate is POLICY put on top of the verifier MECHANISM: it runs inside `resolveCommitGate`
-AFTER the verifier checks and can only ADD a required-approvals rule, never
-take away the verifier's — so an approval can never turn an unverified result into a
-committed one. It FAILS CLOSED on quorum, authority, self-approval, and
-unattributed actors, writing down just which approvals are not there, and a
-gate-satisfied commit is marked with WHO approved the very artifact that went out.
-Required approvals, authorized roles, and the self-approval rule are POLICY as data
-(`review policy`), off to start with (pre-v0.1.32 behavior unchanged). Each verb is
-declared once in the capability registry so `cw <cmd> --json` is the same as
-`cw_<tool>`; the v0.1.30 Workbench shows the review timeline read-only and the
-v0.1.31 metrics report adds derived approval-rate/time-to-approval/handoff-count.
-See [docs/team-collaboration.7.md](docs/team-collaboration.7.md).
-
-CW v0.1.29 adds Execution Backends: the execution layer is lifted OUT of the
-kernel into drivers you can plug in and swap — `node`, `bun`, `shell`, `container`,
-`remote`, and `ci` — behind ONE small `ExecutionBackend` contract
-(`src/execution-backend.ts`). Built on the lines of a BSD VFS / device-driver layer, the
-kernel (orchestrator/dispatch/pipeline-runner) never learns which backend ran a
-task: WHAT to run and which evidence to record is kernel policy; HOW and WHERE it
-runs is the driver's business. The sandbox profile is the contract — every backend
-makes good or attests each requested read/write/command/network/env dimension, or
-FAILS CLOSED instead of quietly running unsandboxed. The result/evidence
-envelope is schema-identical across backends (CW's own self-verify makes
-byte-stable evidence on `node`, `shell`, and `bun`); the backend id + sandbox
-attestation are recorded AS provenance, so eval/replay, the verifier gates, and
-the v0.1.28 run registry stay backend-agnostic. The container/remote/ci drivers
-DELEGATE and record a handle + attestation + result — CW does not become the
-executor. Selection is like `--sandbox` with a parallel `--backend` flag and
-`backend list|show|probe`, declared once in the capability registry so
-`cw <cmd> --json` is schema-identical to `cw_<tool>`. The default (`node`) backend
-gives pre-v0.1.29 behavior just the same. See
-[docs/execution-backends.7.md](docs/execution-backends.7.md).
-
-CW v0.1.31 adds Observability + Cost Accounting: time/duration, failure rate,
-verifier pass rate, candidate acceptance rate, and token/cost — all DERIVED from
-the run state CW already keeps (timestamps → durations; verifier nodes → pass
-rate; candidates → acceptance; failed workers/feedback → failure rate). There is
-NO metrics database, NO collector daemon, NO secret counter. A rate over zero
-samples is `n/a`, never a made-up 0%/100%. Cost is ATTESTED, never measured:
-CW does not call the model, so token usage is recorded as host-attested
-provenance on the existing result/worker intake (absent ⇒ `unreported`, never 0),
-and a money figure is `attested` only from attested usage × a recorded pricing
-policy — guessed pricing is a SEPARATE `estimated` figure, never mixed in.
-Pricing is POLICY as data (`--pricing <path>|default`), out of the kernel.
-`metrics show`/`metrics summary` are declared once in the capability registry so
-`cw <cmd> --json` is byte-identical to `cw_<tool>`, and the v0.1.30 Workbench
-shows a read-only metrics panel from the same payload. See
-[docs/observability-cost-accounting.7.md](docs/observability-cost-accounting.7.md).
-
-CW v0.1.30 adds the Web / Desktop Workbench: a console for people that shows a
-run's run graph, blackboard, worker logs, candidate compare, and audit timeline,
-plus a cross-run way in over the v0.1.28 Run Registry. It is a THIRD FRONT
-DOOR next to the CLI (human speed) and MCP (machine context) — all three are
-presentation policy over ONE mechanism. Keeping CW's "no hidden dashboard
-database" promise, the Workbench holds ZERO authoritative state: it is a
-stateless, READ-ONLY renderer over the durable `.cw/` files and the existing
-capability payloads, so each panel is the same as its `cw <cmd> --json` payload
-byte-for-byte (parity-gated) and refresh works it all out again from disk — delete
-the host and nothing is lost. The optional localhost host (`cw workbench serve`)
-binds `127.0.0.1` only, is read-only (writes refused `405`), says no to non-localhost
-`Host` headers and path traversal, and fails closed on unreadable state. It is an
-OPTIONAL surface: the committed `dist/` and a plain `node` runtime keep working
-with the Workbench (and its dependency-light static UI) gone. See
-[docs/web-desktop-workbench.7.md](docs/web-desktop-workbench.7.md).
-
-CW v0.1.28 adds the Run Registry / Control Plane: a layer that looks after MANY
-workflow runs across repositories — `run search`, `run resume`, `run archive`, a
-durable `queue`, cross-repo `history`, and failed-run `run rerun` — over the
-per-run `.cw/runs/<id>/state.json`, which stays the one true source. The
-registry (`src/run-registry.ts`) is a DERIVED, rebuildable, fingerprinted index:
-it sorts a documented lifecycle (`queued → running → blocked → completed →
-failed → archived`), finds runs cross-repo through a plain-file home registry
-(`CW_HOME`/XDG), and fails closed — tampered or missing source comes up as
-`stale`/`missing` and starts a rebuild, never a made-up status. Resume
-goes on with a run, rerun makes a NEW run tied to the first one by provenance, and
-archive marks it without deleting source. Every verb is declared once in the
-capability registry, so `cw <cmd> --json` is schema-identical to `cw_<tool>`. See
-[docs/run-registry-control-plane.7.md](docs/run-registry-control-plane.7.md).
-
-CW v0.1.27 adds CLI ↔ MCP Parity: the command-line surface and the MCP surface
-are now two views of ONE data source, declared in a single capability
-registry (`src/capability-registry.ts`) and kept fail-closed. Each capability
-names one shared core `entry`; `cw <cmd> --json` is payload-identical to the
-matching `cw_<tool>` MCP result, the CLI stays short for people while MCP stays
-full for machines, and `npm run parity:check` (wired into `release:check`)
-stops any drift — a capability on only one surface, an undeclared tool or
-command, or a payload that does not match. See
-[docs/cli-mcp-parity.7.md](docs/cli-mcp-parity.7.md).
-
-CW v0.1.26 adds the Evidence Adoption Reasoning Chain: a derived, fingerprinted,
-fail-closed view that makes clear *why* each evidence item was adopted, rejected,
-superseded, or conflicting. For every gate (`fanin`, `candidate-score`,
-`selection`, `verifier`, `commit`) it records the decision, basis (evidence +
-provenance + trust source), authority (role/membership/worker + role policy),
-rationale (using existing reason fields again), and counterfactual (the other choices
-that lost). A "why" that cannot be traced to a real record comes up as
-`unexplained` rather than a made-up rationale. New surfaces: `multi-agent
-reasoning <run-id> [--evidence <id>] [--refresh]`, the MCP tools
-`cw_evidence_reasoning` and `cw_evidence_reasoning_refresh`, and an added
-`rationaleStatus` on `multi-agent evidence`. The chain is derived, never
-the top authority over raw state, and kept under `.cw/runs/<run-id>/reasoning/`.
-See
-[docs/evidence-adoption-reasoning-chain.7.md](docs/evidence-adoption-reasoning-chain.7.md).
-
-CW v0.1.25 adds State Explosion Management: durable, versioned,
-provenance-backed summary records (`MultiAgentSummaryIndex`,
-`BlackboardSummaryRecord`, `GraphSummaryRecord`, `OperatorDigest`,
-`StateExplosionReport`), small and pointed graph views with built-up summary
-nodes, blackboard digests, and eval/replay-gated freshness checks. Summaries are
-derived userland indexes that never delete raw blackboard, graph, audit, or
-evidence records and fail closed when stale. New surfaces: `summary refresh`,
-`summary show`, `blackboard summarize`, `multi-agent summarize`, and
-`multi-agent graph --view`. See
-[docs/state-explosion-management.7.md](docs/state-explosion-management.7.md).
-
-CW v0.1.24 makes harder state loading, migrations, MCP tool calls, multi-agent and
-blackboard persistence, and eval/replay artifact validation with fail-closed
-operator diagnostics.
-
-CW v0.1.23 adds Multi-Agent Eval & Replay Harness: deterministic snapshots,
-isolated replays, normalized comparisons, replay scoring, release gates, human
-reports, and MCP parity for topology-backed multi-agent runs. See
-[docs/multi-agent-eval-replay-harness.7.md](docs/multi-agent-eval-replay-harness.7.md).
-
-CW v0.1.22 adds Multi-Agent Trust / Policy / Audit: role policies, permission
-decisions, provenance-rich blackboard messages, blackboard write audit, judge
-rationale, panel decisions, and policy violations in the existing trust-audit
-log. See
-[docs/multi-agent-trust-policy-audit.7.md](docs/multi-agent-trust-policy-audit.7.md).
-
-CW v0.1.21 adds Multi-Agent Operator UX: small graph, dependencies,
-failures, and evidence adoption views for topology-backed multi-agent runs.
-Operators can trace agent -> dependency -> evidence -> fanin -> score ->
-selection -> verifier-gated commit with no separate dashboard state. See
-[docs/multi-agent-operator-ux.7.md](docs/multi-agent-operator-ux.7.md).
-
-CW v0.1.20 adds Multi-Agent CLI + MCP Surface: the host loop to go for, for
-`multi-agent run`, `multi-agent status`, `multi-agent step`,
-`multi-agent blackboard`, `multi-agent score`, and `multi-agent select`.
-The matching MCP tools are `cw_multi_agent_run`, `cw_multi_agent_status`,
-`cw_multi_agent_step`, `cw_multi_agent_blackboard`, `cw_multi_agent_score`,
-and `cw_multi_agent_select`. See
-[docs/multi-agent-cli-mcp-surface.7.md](docs/multi-agent-cli-mcp-surface.7.md).
-
-CW v0.1.19 adds Multi-Agent Topologies: official `map-reduce`, `debate`, and
-`judge-panel` coordination definitions with validation, apply-time
-materialization, topology run state, topology graphs, Operator UX panels, trust
-audit provenance, CLI commands, and MCP parity. Applying a topology makes the
-linked MultiAgentRun, roles, groups, fanout, blackboard topics, coordinator
-decisions, and deterministic next actions that the agent host can do.
-See [docs/multi-agent-topologies.7.md](docs/multi-agent-topologies.7.md).
-
-CW v0.1.18 adds Coordinator / Blackboard: first-class shared topics,
-messages, context frames, artifact refs, snapshots, and coordinator decisions.
-The blackboard is the coordination filesystem used by topology runs to index
-evidence, conflicts, fanin readiness, and synthesis decisions. See
-[docs/coordinator-blackboard.7.md](docs/coordinator-blackboard.7.md).
-
-CW v0.1.17 added Multi-Agent Runtime Core: first-class `MultiAgentRun`,
-`AgentRole`, `AgentGroup`, `AgentMembership`, `AgentFanout`, and `AgentFanin`
-state with lifecycle validation, dispatch attachment, worker manifest metadata,
-fanin evidence coverage, Operator UX panels, trust audit events, CLI commands,
-and MCP parity. See
-[docs/multi-agent-runtime-core.7.md](docs/multi-agent-runtime-core.7.md).
-
-CW v0.1.16 adds Dogfood One Real Repo: a dry-run release proof that runs the
-canonical `release-cut` app against this repository, records real command
-evidence, scores/selects a release candidate, makes a verifier-gated CW state
-commit, and makes trust clear through audit provenance. See
-[docs/dogfood-one-real-repo.7.md](docs/dogfood-one-real-repo.7.md).
-
-CW v0.1.15 adds Security / Trust Hardening: durable trust audit records,
-worker sandbox decision history, evidence provenance, acceptance rationale,
-and CLI/MCP audit inspection. See
-[docs/security-trust-hardening.7.md](docs/security-trust-hardening.7.md).
-
-CW v0.1.14 added Release & Migration Discipline: clear run-state schema
-migration policy, fixture-based backward compatibility tests, version
-synchronization checks, and a dry-run release gate. See
-[docs/release-and-migration.7.md](docs/release-and-migration.7.md).
-
-CW v0.1.13 completes the MCP / App Surface so agent hosts can take CW as a
-runtime in place of a CLI wrapper. MCP now covers app runs, worker inspection and
-output recording, candidate scoring/selection, sandbox profile resolution,
-verifier-gated commits, and structured operator summaries while keeping old
-tool names. See [docs/mcp-app-surface.7.md](docs/mcp-app-surface.7.md).
-
-CW v0.1.12 added Operator UX: human-readable status, graph, report summaries,
-resource summaries, commit/feedback/worker/candidate panels, and deterministic
-next-step suggestions. JSON is still there with `--json` or
-`--format json`. See [docs/operator-ux.7.md](docs/operator-ux.7.md).
-
-CW v0.1.11 added Canonical Workflow Apps: official app-directory userland for
-`architecture-review`, `pr-review-fix-ci`, `release-cut`, and
-`research-synthesis`. They validate and plan through `npm run canonical-apps`
-and are the app matrix used to judge if the framework is nice to use, steady, and
-able to say much. See
-[docs/canonical-workflow-apps.7.md](docs/canonical-workflow-apps.7.md).
-
-CW v0.1.10 added the End-to-End Golden Path: a deterministic regression command
-that validates a first-class app, plans a run, dispatches a readonly isolated
-worker, records a simulated worker result, scores/selects a candidate, makes a
-verifier-gated commit, and renders a report. See
-[docs/end-to-end-golden-path.7.md](docs/end-to-end-golden-path.7.md).
-
-CW v0.1.9 added the Workflow App framework: first-class app metadata, validation,
-deterministic app discovery, app CLI/MCP tools, app templates, and run
-state/report metadata. See
-[docs/workflow-app-framework.7.md](docs/workflow-app-framework.7.md).
-
-CW v0.1.8 added Sandbox Profiles: named worker policy contracts for read paths,
-write paths, command execution, network access, and environment exposure. CW
-keeps and validates the policy, while the agent host makes good the OS/process
-runtime controls. See [docs/sandbox-profiles.7.md](docs/sandbox-profiles.7.md).
+## Start Here
+
+Use the short path first. The long notes below are history and deep reference,
+not the first run.
+
+```bash
+cw demo tamper
+cw doctor --onramp
+cw quickstart architecture-review --check --repo /path/to/repo \
+  --question "What are the main risks?" --agent-command builtin:claude
+cw quickstart architecture-review --repo /path/to/repo \
+  --question "What are the main risks?" --agent-command builtin:claude --bundle
+cw report verify-bundle report.cwrun.json
+```
+
+For source work, keep the loop small:
+
+```bash
+npm run build
+node test/<nearest-smoke>.js
+npm run test:fast
+```
+
+Run `npm run release:check` only when the batch is ready for the full gate. Start
+with `quickstart` and `report` before the multi-agent pages.
+
+For the full capability and release history, see [docs/release-history.md](docs/release-history.md).
+This README tracks CW v0.1.85.
 
 ## Quickstart
 
@@ -280,6 +89,9 @@ npx cool-workflow quickstart architecture-review --repo /path/to/repo \
   --question "Is this architecture sound?" --agent-command builtin:claude
 ```
 
+Add `--bundle` when the report has to go to someone else; then check the file
+offline with `cw report verify-bundle report.cwrun.json`.
+
 CW DELEGATES worker execution to your own agent. With no `--agent-command` (or
 `CW_AGENT_COMMAND`) the drive fails closed (status `blocked`) — it never makes up a
 result. `--agent-command builtin:claude` points to a bundled read-only `claude -p`
@@ -297,6 +109,20 @@ More: `cw quickstart <app> --preview` (read-only dry run), `cw run resume <run-i
 (go on with a run that was stopped), `cw run inspect-archive <archive>` (integrity-check a
 portable run archive without bringing it in).
 
+## Developer Loop
+
+Use the shortest check that fits the change:
+
+```bash
+npm run build
+node test/<nearest-smoke>.js
+npm run test:fast
+```
+
+For a source checkout, `cw doctor --onramp --changed-from origin/main` gives the
+nearest smoke tests and release gate commands for the current change. Before a
+release, run `npm run release:check`.
+
 ## Structure
 
 ```text
@@ -599,114 +425,4 @@ Verification and synthesis tasks need a structured result block:
 ```
 ````
 
-## Release Tooling (v0.1.33)
-
-the per-tag mechanical surfaces (version bump across 17 surfaces, feature scaffold, and the forward-reference docs) become deterministic scripts, with a release gate that has no copies. See release-tooling(7).
-
-## Real Execution Backend Integrations (v0.1.34)
-
-container/remote/ci backends really do the work (docker/podman run, remote/CI POST-and-poll) under the sandbox contract, with byte-stable evidence vs node and fail-closed refusal when a runtime/endpoint is not there to use. See real-execution-backends(7).
-
-## Node Snapshot / Diff / Replay (v0.1.35)
-
-per-node snapshot, structural diff, and isolated deterministic replay over StateNode, using the v0.1.23 eval harness again; fail-closed on source drift (valid|stale|absent). See node-snapshot-diff-replay(7).
-
-## Contract Migration Tooling (v0.1.36)
-
-first-class declared migration registry (run-state + workflow-app) with per-edge compatibility proofs, fail-closed reachability, and a round-trip/non-destruction prover. See contract-migration-tooling(7).
-
-## Control-Plane Scheduling (v0.1.37)
-
-priority + concurrency limits + lease lifecycle + retry/backoff + fail-closed park over the v0.1.28 Run Registry queue; policy-as-data, deterministic. See control-plane-scheduling(7).
-
-## Agent Delegation Drive (v0.1.38)
-
-start up an outside agent process per worker, catch result.md + attestation, auto-drive plan->dispatch->fulfill->accept->commit
-
-## Run Retention & Provable Reclamation (v0.1.39)
-
-tiered, append-only, cryptographically-verifiable disk reclamation: `gc plan|run|verify` close up the audit skeleton, free the reconstructable/scratch bulk, and prove it by way of a hash-chained tombstone. Write-ahead + fail-closed (skeleton -> tombstone -> fsync -> free); clear capability downgrade (verify-only / re-runnable-by-reconstruction); CW never reclaims to start with.
-
-## Durable State & Locking (v0.1.40)
-
-every authoritative write is now atomic (temp -> rename, so a crash can never cut short state.json) with fsync-durability for the audit-essential stores; the cross-process read-modify-write stores (home queue, archive overlay, reclamation chain) are serialized by a portable stale-stealing file lock. Closes the architecture self-audit's non-atomic/unlocked P1 and pulls reclamation's result-node re-point inside the write-ahead boundary (durable persist + dangling-ref proof before any free) with a content-validated skeleton.
-
-## Self-Audit Hardening & Pure-Router Decomposition (v0.1.41)
-
-closes the v0.1.41 architecture self-audit's real findings and pays down its top maintainability debt. Hardening: evidence-gated commits now need GROUNDED locators (path/URL/namespace:value), not just presence, with opt-in `CW_REQUIRE_RESOLVABLE_EVIDENCE` on-disk resolution; the trust-audit event log is appended with fsync (durable like state.json); path containment is symlink-hardened (realpath of the deepest existing ancestor) across sandbox checks and reclamation proofs; worker ids are deterministic; coordinator secret redaction recurses. Maintainability: the `descriptor.id ===` switches in the execution backend are gone — drivers self-describe through a `registerBackend` registry — and the ~2100-line CoolWorkflowRunner god-object is broken up into per-domain operation modules under `src/orchestrator/`, leaving the runner a pure `loadRun -> delegate` router. Behavior-preserving (verified by adversarial review + full release:check).
-
-## Robust Result Ingest (v0.1.42)
-
-catch findings/evidence from any agent shape that makes sense (alt keys + prose), CW works out grounded evidence itself, warn on empty capture — closes the v0.1.41 live-drive 'accepted with 0 captured' failure
-
-## No-False-Green Gate & Launch Prep (v0.1.43)
-
-Hard gate stopping empty-capture verifier-gated commits, plus quickstart and launch-prep docs.
-
-## Release-Gate Determinism & Agents Vendor (v0.1.44)
-
-Release-readiness checks now validate the committed blob (`git show HEAD:<path>`) in place of the mutable working tree — doing away with false-red/false-green from concurrent working-tree writes (iCloud/Spotlight/editor). Adds the `agents` vendor manifest target: a generated `.agents/plugins/cool-workflow/` adapter that gives any non-Claude AI agent one shared way in to CW.
-
-## Migration DAG (v0.1.45)
-
-Puts in place of the linear migration chain a BFS graph path resolver (`findMigrationPath()`) over directed migration edges. Each `StateMigrationStep` carries an optional `reverse()` function, which makes rollback/downgrade paths possible by way of `reverseRunState()`.
-
-## Capability Auto-Discovery (v0.1.46)
-
-`registerCapability()` builder pattern takes the place of by-hand registry entries. Capabilities self-register at implementation sites by way of Map-based dedup; no need to touch `capability-registry.ts`. New capabilities call `registerCapability()` next to their entry function.
-
-## Vendor-Adapter Registry (v0.1.47)
-
-Data-driven manifest generation: vendor JSON shapes taken out of `gen-manifests.js` into declarative templates in `plugin.manifest.json`. A `_resolveTemplate()` engine works out `{{path.to.field}}` markers. Adding a new AI platform is pure data. Cross-vendor is proven by boot, not just by generation: `npm run manifest:load-check` (`node test/vendor-manifest-load-smoke.js`) loads every generated manifest (claude, codex, agents, gemini, opencode) and makes sure each shows the full tool surface (184 tools).
-
-## P2 Fixes (v0.1.48)
-
-State auto-compaction by way of `setPostSaveCallback()` hook — after every `saveCheckpoint()`, the orchestrator checks `computeStateSize()` and auto-starts compaction. Agent dedup docs, npm `ci` aggregate script.
-
-## CI Content-Surface Fix (v0.1.49)
-
-CHANGELOG.md and RELEASE.md are content surfaces checked by the dogfood-release gate. The bump-version script covers structured surfaces only; content surface updates are now written down as a release step.
-
-## Auto-Compaction Fix (v0.1.50, v0.1.51)
-
-Auto-compaction hook moved from `saveCheckpoint()` to clear `maybeCompactRun()` calls after big lifecycle mutations. Fixes test fixture fingerprint instability. Also fixes the dogfood-release version-sync pipeline: always use `npm run bump:version`, never hand-edit version.ts alone.
-
-## Control-plane naming (v0.1.76)
-
-Positioning consistency: every self-describing surface names CW an auditable workflow control-plane / Workflow App framework, not an "SDK" (which lives on only in the red-line disclaimer "embeds no model SDK").
-
-## Workflow orchestration: Tracks 1–3 (v0.1.77)
-
-The orchestration vision came in one release, all reviewer-gated:
-
-- **Track 1 — telemetry attestation**: each agent's reported token usage is checked against an operator ed25519 trust key (`attested`/`unattested`/`absent`, shown loudly), recorded in a tamper-evident hash-chained ledger; opt-in `require-attested-telemetry` fails closed on usage it cannot check.
-- **Track 2 — concurrent failure semantics**: a `parallel()` phase runs its agents at the same time with declared collapse rules — **collect-all** (a failing hop never stops siblings) and **kill-on-timeout** (a hung agent is killed at its deadline and counted as one failure). 16 agents with a forced hang + crash + dirty-return finish with no deadlock and a replay-complete record.
-- **Track 3 — boundary contract**: per-task output `schema` validation (dependency-free, parks on mismatch), `limits.tokenBudget` made good against recorded usage, and the one-way executor boundary welded into the type layer (a callable crossing it fails `npm run build`).
-
-## Working onboarding + npm distribution (v0.1.78)
-
-`--agent-command builtin:claude` points to a bundled read-only claude wrapper that finishes workers with a real agent; the cross-directory quickstart crash is fixed; missing optional inputs no longer let `{{name}}` slip into prompts. Published to npm (`cool-workflow`, bins `cw`/`cool-workflow`) with LICENSE and metadata. Live dogfood proof committed under `docs/dogfood/`.
-
-## Tamper-evidence demo (v0.1.79)
-
-`cw demo tamper` — a hermetic, one-command proof that a recorded telemetry verdict cannot be faked without being caught: it builds a real ed25519-signed ledger, fakes it at the ledger layer (verdict flip + recomputed local hash → the chain still breaks) and the signature layer (inflated tokens, reused signature → ed25519 rejects), all checked offline with only the public key. `cw telemetry verify <run>` (`cw_telemetry_verify` on MCP) is the operator-facing re-proof: by default it recomputes the hash chain on disk so any later edit to a recorded verdict or usage digest is caught; add `--pubkey <pem-or-path>` to re-run each `attested` hop's ed25519 signature check against the stored raw usage too. What this does and does **not** prove — taking in the single-keyholder ceiling — is set down in a true way in [Trust Model & Limitations](docs/trust-model.md); read it before you put trust in a green verdict.
-
-## Opt-in live agent output during a drive (on main, ships next)
-
-Set `CW_AGENT_STREAM=1` to see each worker's live agent trace. The bundled claude wrapper (`builtin:claude` / `scripts/agents/claude-p-agent.js`) keeps the legacy `--output-format json` path by default; only the opt-in path runs claude in `--output-format stream-json` and renders a short human trace (tool uses, assistant text, per-turn summaries) to **stderr**. CW core sends that stderr on to the operator's terminal only when `CW_AGENT_STREAM=1`, CW's own stderr is a TTY, and `CW_NO_STREAM` is not set; piped/CI runs stay quiet (Rule of Silence). Core only sends the stream on, never reads it — vendor-specific rendering is the wrapper's business (policy), not the kernel's (mechanism).
-
-v0.1.79
-
-## Fast Architecture Review (v0.1.80)
-
-Adds the opt-in fast architecture-review lane: scoped JSONL source contexts, diff-aware exports, Map and Assess results you can use again, wrapper metrics you can measure, a background full-review handoff you can act on, and userland model policy flags for routing fast/strong workers without changing the full review contract.
-
-_This documentation tracks Cool Workflow v0.1.82. See [CHANGELOG](../../CHANGELOG.md) for the release notes._
-
-## Hardening and Onboarding (v0.1.83)
-
-Loaders fail closed on corrupt state; store writes are made safe under more than one writer; a new cw doctor checks your setup; help lists every command; and the docs are put into Basic English.
-
-## Privacy Release (v0.1.84)
-
-This release removes local user path text from saved release review input and adds a scan that keeps those words out of tracked files.
+v0.1.86

package/apps/architecture-review/app.json

@@ -3,7 +3,7 @@
   "id": "architecture-review",
   "title": "Architecture Review",
   "summary": "Map a repository architecture, assess risks, verify important findings, and synthesize an evidence-backed verdict.",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "author": "COOLWHITE LLC",
   "inputs": [
     {

package/apps/architecture-review-fast/app.json

@@ -3,7 +3,7 @@
   "id": "architecture-review-fast",
   "title": "Architecture Review Fast",
   "summary": "Run a shorter architecture review with parallel map and assess phases for faster first results.",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "author": "COOLWHITE LLC",
   "inputs": [
     {

package/apps/architecture-review-fast/workflow.js

@@ -96,6 +96,7 @@ module.exports = ({ workflow, phase, parallel, agent, artifact, input }) => {
           "verify:p0-p2-risks",
           [
             "Re-open evidence for every candidate P0/P1/P2 risk from the fast assessment.",
+            contextInstruction(),
             "Confirm real risks, downgrade unsupported claims, and list exact file paths, commands, logs, or unknowns.",
             "The cw:result evidence array must cite durable locators."
           ].join(" "),
@@ -107,6 +108,7 @@ module.exports = ({ workflow, phase, parallel, agent, artifact, input }) => {
           "verdict:fast-synthesis",
           [
             "Synthesize a fast architecture verdict for {{question}}.",
+            contextInstruction(),
             "Include a short answer, compact architecture map, ranked risks, speed recommendations, non-issues, and evidence links.",
             "State when the full architecture-review app should be scheduled as a background routine.",
             "The cw:result evidence array must support the final verdict."

package/apps/end-to-end-golden-path/app.json

@@ -3,7 +3,7 @@
   "id": "end-to-end-golden-path",
   "title": "End-to-End Golden Path",
   "summary": "Deterministic one-worker workflow app for proving the CW integration chain.",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "author": "COOLWHITE LLC",
   "inputs": [
     {

package/apps/pr-review-fix-ci/app.json

@@ -3,7 +3,7 @@
   "id": "pr-review-fix-ci",
   "title": "PR Review Fix CI",
   "summary": "Review a pull request or branch, inspect CI failures, diagnose actionable issues, optionally patch, verify, and summarize with evidence.",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "author": "COOLWHITE LLC",
   "inputs": [
     {

package/apps/release-cut/app.json

@@ -3,7 +3,7 @@
   "id": "release-cut",
   "title": "Release Cut",
   "summary": "Prepare a release with checklist discipline: version checks, changelog, tests, packaging, release notes, and final verification.",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "author": "COOLWHITE LLC",
   "inputs": [
     {

package/apps/research-synthesis/app.json

@@ -3,7 +3,7 @@
   "id": "research-synthesis",
   "title": "Research Synthesis",
   "summary": "Split a research question into claims, investigate sources, cross-check evidence, verify claims, and synthesize a concise answer.",
-  "version": "0.1.84",
+  "version": "0.1.86",
   "author": "COOLWHITE LLC",
   "inputs": [
     {