feat: upstream cli adaptation and claude-worker re-form (0.0.43)

[okisdev]

summary

• adapt to codex-cli 0.146.0 and grok 0.2.112: the codex tested interval moves to 0.146.0 up to but excluding 0.147.0 with alpha hotfix version parsing pinned, the grok capability preflight generalizes its acceptance probe to every required flag hidden from --help, hard version policy deaths (0.2.112's soft/hard split that --no-auto-update cannot bypass) classify as setup with remediation matched to the violated bound, and setup gains a [shell_environment_policy] presence advisory
• re-form fusion:fast-worker as fusion:claude-worker: a claude-surface-only seat (hooks, subagent files, MCP, plugin state, privacy boundary, or a structurally stranded package with a claude-fallback: reason header), artifact-first deliverable contract, width one dispatches may run synchronously, and the lifecycle accepts both names so existing records keep settling; mining showed the old lane was the slowest (p50 514s vs terra 236s, luna 77s, grok 107s) with only 6 percent of briefs needing the claude surface
• orchestration ergonomics: settlement grammar binds --reason-for by id from any position with a broadcast --reason and example carrying errors, the stop gate batches settlement demands until the wave drains (FUSION_SETTLE_DEMAND_STALE_MS), a wrapper dying on a harness API error before dispatch auto settles with a redispatch advisory, the narrow wave advisory counts same message pending launches, and grok ordinary task mode accepts the same --json-schema contract as review
• verified pins move to codex-cli 0.146.0 and grok 0.2.112, with stale wording swept (--background-wait-timeout fallback, best-of-n doctor surface, pre split version enforcement prose) and the grok contract recording the 0.2.110 to 0.2.112 audit (silent EndTurn stationarity stops, resume by title, memtrace real home escape, x_search unmappable via --tools under forced tracing)

breaking changes

• the fusion:fast-worker agent id becomes fusion:claude-worker with a narrowed claude-surface-only routing seat; the lifecycle and hooks accept both names so existing ledger records and in flight sessions keep settling

test plan

already verified

• npm test -> 1023 tests, 1022 pass, 0 fail, 1 skip (one known roaming flake, rerun green)
• live probes against the installed CLIs: codex 0.146.0 exec review --output-schema confirmed still accepted and ignored, grok 0.2.110/0.2.111/0.2.112 hidden flag acceptance probes exit 0, --tools x_search confirmed unmappable under forced builder tracing
• node plugins/fusion/scripts/generate-rules-manifest.mjs regenerated for the new rules revisions

reviewer should verify

• after refreshing installed plugin caches to 0.0.43, run /fusion:smoke and confirm version parity plus the three lane probes settle green

notes

• post merge release cadence: refresh plugin caches, run /fusion:setup to sync the live rules copy, and run /fusion:stats --prune-dead --yes to sweep the removed campaign worktrees' dead codex state dirs