feat: upstream cli adaptation and settlement rework (0.0.35)

.claude-plugin/marketplace.json

@@ -6,14 +6,14 @@
     "email": "hi@okis.dev"
   },
   "description": "Multi-model orchestration marketplace for Claude Code.",
-  "version": "0.0.34",
+  "version": "0.0.35",
   "plugins": [
     {
       "name": "grok",
       "source": "./plugins/grok",
       "displayName": "Grok Companion",
       "description": "Local Grok CLI delegation: task, review, resumable history, best-of-n tournaments, background jobs, stats, and setup health checks.",
-      "version": "0.0.34",
+      "version": "0.0.35",
       "author": {
         "name": "Harry Yep"
       },
@@ -34,7 +34,7 @@
       "source": "./plugins/codex",
       "displayName": "Codex Companion",
       "description": "First party local Codex CLI delegation for tasks, reviews, resumable threads, and durable background jobs.",
-      "version": "0.0.34",
+      "version": "0.0.35",
       "author": {
         "name": "Harry Yep"
       },
@@ -55,7 +55,7 @@
       "source": "./plugins/fusion",
       "displayName": "Fusion Orchestrator",
       "description": "Multi-model orchestration: tier agents, routing rules, blind panel, ultra fleet, model config, and drift doctor.",
-      "version": "0.0.34",
+      "version": "0.0.35",
       "author": {
         "name": "Harry Yep"
       },

CHANGELOG.md

@@ -1,5 +1,16 @@
 # changelog
 
+## 0.0.35
+
+- codex adapts to cli 0.145.0: task runs forward `--output-schema <path>` end to end (rescue raw args, exec argv, structured output capture, and a `structured: parsed/invalid/unavailable` footer in the render), adversarial review gains a json schema verdict contract at `plugins/codex/schemas/adversarial-review-verdict.schema.json`, native `review` rejects `--output-schema` because tested versions silently ignore it there, and the 0.144.4 models cache schema drift workaround is deleted with the tested interval moving to 0.145.0 to 0.146.0
+- grok adapts to cli 0.2.110: setup probes the new `grok doctor` capability and surfaces it as a setup advisory line, and ordinary managed runs now require `--no-wait-for-background` unconditionally, dropping the `--background-wait-timeout` compatibility fallback and its capability probe
+- best-of-n is retired: the tournament skill is deleted and grok's protected roles shrink to four (burst, independence, live-web, large-context) across rules, skills, agents, docs, and tests
+- settlement is centralized: engine acceptance writers move to a shared `engine-acceptance.mjs`, `/fusion:stats` records every verdict through the one `--record <id>=<verdict>` form (`--record-acceptance` and `--record-worker-acceptance` are gone), and a verdict recorded before a worker's record turns terminal queues instead of failing, settling automatically when the record lands
+- the worker lifecycle settles queued verdicts on terminal transitions with the engine cascade, backfills peer identity from rescue wrapper stops (the SubagentStop matcher now also covers `codex:codex-rescue`, `grok:grok-rescue`, and `grok:grok-review-runner`), and guards terminal writers against reprocessing already settled records
+- legacy codex plugin state support is dropped: the `codex-openai-codex` compatibility root, `FUSION_CODEX_INCLUDE_LEGACY`, legacy `completed`/`failed` terminal statuses, and log tail failure kind recovery are removed from stats, breaker, and monitor
+- the inline delegation guard always normalizes persisted dispatch counters instead of branching on a legacy period counter
+- verified engine pins move to codex-cli 0.145.0 and grok 0.2.110
+
 ## 0.0.34
 
 - the settle-only advisory stops repeating itself: when settlement is legitimately deferred (a package's verification waiting on a sibling landing), the pending-verdict block re-emitted identically at every stop boundary with no new information; it now dedupes by a persisted pending-set signature, the same mechanism the in-flight advisory has used since 0.0.31, emitting once per distinct set and again only when a record enters or leaves; blocking collection demands are unaffected and refresh the signature when they emit combined

CONTRIBUTING.md

@@ -11,7 +11,7 @@ Any change to `plugins/fusion/rules/orchestration.md` or `plugins/fusion/rules/t
 1. Diff every changed sentence against the previous release and justify each deletion or softening in the PR or release notes. Wording changes are behavior changes; a softer phrase can stop a lane from being chosen even when the surrounding code is untouched.
 2. Check that the load bearing invariants survived the edit:
    - The main Claude session is the only control plane and final judge. It owns ambiguity resolution, decomposition, integration, semantic acceptance, and user communication, while work packages execute in delegated lanes.
-   - Codex owns ordinary implementation by default. Grok remains implementation capable only through its five protected roles (`burst`, `independence`, `live-web`, `large-context`, `best-of-n`) or an explicit user choice; it is not a generic alternative merely because it is idle.
+   - Codex owns ordinary implementation by default. Grok remains implementation capable only through its four protected roles (`burst`, `independence`, `live-web`, `large-context`) or an explicit user choice; it is not a generic alternative merely because it is idle.
    - Codex admission order is the current workspace, an isolated worktree for an independent eligible package, then Grok under `burst`, then the matching Claude fallback. Packages with overlapping files, shared generated state, or ordering dependencies are consolidated or sequenced instead of parallel overflow.
    - Claude worker and Grok dispatches are background Agents. Codex is the foreground Agent exception: its rescue Agent and companion Bash call stay foreground regardless of complexity or expected duration unless the incoming user request already contains `--background`.
    - A Codex package that cannot fit the foreground cap is split or routed elsewhere. Complexity and duration never silently detach it.