feat: timeout salvage, quick tier sizing, observability denominators (0.0.42)

[okisdev]

summary

• the codex rescue wrapper now salvages foreground timeouts itself: one scripted wind down resume when a result ends state: error with failure: timeout and carries the companion's Resume Codex job line, relayed verbatim, never chained; 15 of 20 recorded timeout deaths had previously needed a manual resume round to end accepted
• quick tier briefs get a 570 second sizing contract in the routing rules (narrow suites in the brief, full list at collection rerun, second timeout is a sizing error), and the trivial row names the light middle band for gpt-5.6-luna
• telemetry stops lying about salvage and proportion: codex records persist timeoutMs (the near cap counter had been reading a field no writer set) and all three record families persist companionVersion; fusion stats reads engine semanticStatus (engine records were invisible to acceptance views), adds a salvaged n/m per SKU column, and the breaker advisory renders failure counts against terminal job counts so singletons read as singletons
• stop gate demand and reverify share extracted predicates (runtimeTaskMissing, needsCancellation, settleReapedIfActive), round two of the 0.0.39 gate symmetry class, and /fusion:smoke ships as a post update live smoke wave over version parity, the three dispatch lanes, and the settlement write

test plan

already verified

• npm test over the merged tree -> 1006 tests, 1005 pass, 0 fail, 1 known skip
• per package suite reruns in the full environment: codex-state + codex-companion 119/119, breaker-check 26/26, fusion-stats 100/100, fusion-worker-lifecycle + fusion-worker-state 133/133, rules-sync + routing-policy green, plugin-versions lockstep green
• claude plugin validate plugins/fusion and rules manifest regenerated (33 hashes)

reviewer should verify

• node --test tests/fusion-stats.test.mjs and confirm the by SKU trend renders the trailing salvaged column as n/m
• read the new bullet in plugins/codex/agents/codex-rescue.md and confirm the resume trigger names all three conditions (error state, timeout failure kind, Resume Codex job line) and the single use bound

notes

• live sessions keep the old behavior until plugin caches refresh to 0.0.42 plus a fusion:setup rules sync; the contributing checklist now runs /fusion:smoke right after that refresh
• the stop gate collection matching pair (demand instruction vs handlePostToolUse arms) is deliberately deferred; it is acceptance wider than demand today, which is the safe direction