smoke

Verify the update landed, then prove the dispatch chain end to end with four tiny probes before real packages ride it.

1. Version parity: read ~/.claude/plugins/installed_plugins.json and compare the fusion, codex, grok, and cursor entries against .claude-plugin/marketplace.json in this repository when present. Report each version pair; a mismatch is a FAIL naming the stale plugin.
2. Fan out four probes as parallel foreground Agent calls in one message. The three engine probes name no model, so the routing table's lane default fills it and the probe exercises that path too:
   • a codex:codex-rescue task whose direct prompt passes --effort low --cwd "<absolute repository root>" -- followed by a brief whose header line is lane: codex volume | effort low | acceptance: exact marker line and whose body asks for exactly the line FUSION-SMOKE-CODEX-OK;
   • a grok:grok-rescue task whose direct prompt passes --effort low --cwd "<absolute repository root>" -- followed by a brief whose header line is grok-role: burst | effort low | acceptance: exact marker line and whose body asks for exactly the line FUSION-SMOKE-GROK-OK;
   • a cursor:cursor-rescue task whose direct prompt passes --cwd "<absolute repository root>" -- followed by a brief whose header line is cursor-role: diversity | acceptance: exact marker line and whose body asks for exactly the line FUSION-SMOKE-CURSOR-OK;
   • a fusion:trivial-worker brief in the fusion-brief: v1 envelope with context-mode: isolated, a goal of returning exactly the line FUSION-SMOKE-WORKER-OK, a scope of no file access, and an acceptance of the exact marker line.
3. Collect all four, then settle them in one /fusion:stats call carrying one --record <id>=<verdict> flag per probe: accepted only when the exact marker line came back, rejected otherwise.
4. Report one PASS or FAIL line per gate: version parity, codex dispatch and envelope, grok dispatch and sandbox handshake, cursor dispatch and private home, worker dispatch and deliverable, settlement write. The codex, grok, and cursor gates also require the lane default notice naming the filled model, and the cursor gate also requires that the job record's homeDir sits under the Cursor plugin's runs/ directory. A FAIL names the failing surface and advises holding real dispatches on that lane until repaired.

The wave is a probe, not work: never attach real packages to it, and never skip the settlement step, because the settlement write is itself one of the gates under test.