fix: worker truncation recovery and launch time wave anchor (0.0.32)

[okisdev]

summary

• async claude workers no longer vanish mid run: agent frontmatter turn caps rise to the doubled large sizing values (120, 60, 24) so the harness cap can never undercut the lifecycle budgets, and a notification completed worker whose transcript ends without final text now classifies as incomplete with turn_limit instead of done and collected
• notification driven collection now delivers a readable artifact: the completed path extracts the final assistant text from a bounded transcript tail, writes the bounded final.txt, points outputFile at it, and parses the rescue wrapper footer so engine job id settlements propagate to the wrapper ledger row
• fleet wave width measures launches instead of completions: the guard records dispatches at PreToolUse launch time and confirms at PostToolUse, counts confirmed entries only, expires phantom launches after fifteen minutes, recovers a missing launch in place with a warn audit event, and re advises narrow streaks at every even milestone
• settlement observability: codex acceptance records carry acceptanceSource and acceptanceRecordedAt with the accept-failed-transport gate enforced on every writeback path and --source threaded through the fusion-stats companion argv, collectionMethod folds to one canonical enum across writers and readers, and stats gains an --unsettled view
• grok turn_limit survives into history output, the review runner accepts an empty raw request as the default managed review, both rescue agents relay companion stdout verbatim, and the orchestration rules describe the async wire shape (launch receipt is not delivery) without weakening any collection or settlement obligation

test plan

already verified

• npm test -> 896 tests, 895 pass, 0 fail, 1 known skip on the full merged result
• node --test tests/plugin-versions.test.mjs tests/verified-versions.test.mjs -> 4/4 with the 0.0.32 bump across all seven version fields and the changelog heading
• per package suites green in the main environment after each worktree merge (guard 55, lifecycle plus stop gate 90, codex 112, stats 114, grok history plus acceptance 12, rules sync plus model table plus routing 23)

reviewer should verify

• four platform CI matrix settles green (linux and macos, node 22 and 24)
• node plugins/fusion/scripts/fusion-stats.mjs --raw-args-token ritual still round trips a strict --record settlement against a live store after the --source argv change

notes

• the fixes land in the repo only; installed plugin caches keep vanilla 0.0.31 behavior until the marketplace refresh and a session restart, so live sessions will not show the new collection or wave semantics before then
• a machine local companion cache repair (regenerating ~/.codex/models_cache.json) rode alongside this wave and is intentionally not part of the diff