feat: guard verification sensor, staleness sweep, footer symmetry (0.0.48)

[okisdev]

summary

• the inline guard's verification recognizer only ever looked at a compound command's final segment, so piped and redirected runner invocations never registered (a 7 day audit showed 1 recognized verification event against 1325 counted writes, which is how the 40 write ceiling fired on a fully verified session); recognition is now any-segment with a quote-aware splitter, and when the runner's exit status is unobservable the reset requires pass evidence in the tool output (fail 0 with no ✖ or not ok lines), with each reset stamping evidence: exit-status|output-summary for /fusion:stats --audit
• absolute paths outside the session workspace (memory files, transport payloads, scratchpads) are logged as exempt writes and no longer burn the unverified window; relative and missing paths keep counting, failing toward the count; the ceiling default stays at forty pending re-observation under the fixed sensor
• a five facet peer fleet staleness audit checked roughly four hundred living prose claims and twelve confirmed groups are corrected across the contract docs, README, and six orchestration rule sentences (removed FUSION_CODEX_INCLUDE_LEGACY references, the codex monitor's lock-repair truth, the sandbox:/job: pairing rule, turn_limit in the grok kinds, grok model capture order and exact cost gate, the codex preflight version floor, ceiling-bounded guard wording, wall clock and stall as the only surviving sizing env overrides, the dual run_in_background exception, advisory-then-block stop gate, epoch scoped to the anomaly report, tool and path agnostic zero dispatch relief, and a new rule that warm thread follow ups restate --model, --effort, and --cwd)
• grok terminal footers become symmetric with codex: sandbox: <cwd> appears exactly where a job: line does, on done, error, cancelled, result re-render, and terminal status paths, while pre-record input rejections carry neither

test plan

already verified

• npm test -> 1087 tests, 1086 pass, 0 fail, 1 pre-existing skip
• ten transcript vectors from the incident session: five compound passing shapes reset the window, five failing or error shapes do not (tests/inline-delegation-guard.test.mjs)
• out-of-workspace exemption: memory and transport paths log exempt without counting, repo paths count, the ceiling still denies at forty in-workspace unverified writes
• grok recorded-job failure and cancelled footers carry sandbox:, pre-record input rejection carries neither (tests/grok-companion.test.mjs, tests/failure-kinds.test.mjs, tests/task-lifecycle.test.mjs, tests/review.test.mjs)

reviewer should verify

• run a verification command through a pipe tail (for example npm test 2>&1 | rg "ℹ") after a few writes in judgment posture and confirm the guard audit records a verification event with evidence: output-summary
• run a grok task that fails after job creation and confirm its footer shows sandbox: <cwd> between job: and state:

notes

• the rules template edits regenerate rules-manifest.json; installed environments pick everything up via a plugin cache refresh plus /fusion:setup