fix: satisfiable collection demands and reaped probe redirect (0.0.33)

[okisdev]

summary

• notification-driven collection now reads the transcript the notification itself names: wrapper records arrived with null transcriptPath in production, so every clean consult wrapper was mislabeled turn_limit, demanded a manual raw-transcript read, and lost peer footer seeding; the reconciler stamps the path from the notification's output-file element, no-text completions classify missing_final_text unless real turn evidence exists, and peer identity seeds on incomplete branches too
• the collection demand is always satisfiable: any Read of the record's outputFile or transcriptPath counts (offset, limit, or a size-refused response included), the demand wording drops the impossible no-offset-no-limit requirement (a live transcript measured 29045 tokens against the Read tool's 25000 cap and wedged a session for an hour), and final text caps shrink to 72KB so one read always fits
• stray TaskOutput/TaskStop probes against reaped workers are redirected by the guard to the record's output file and settlement command, ending the "No task found" error class
• workers receive a wind-down instruction two turns before their budget instead of overshooting to 62-64 of 60, and multi-record stop output consolidates into one block with a settle-only: prefix for verdict-only rows

test plan

already verified

• npm test -> 907 tests, 906 pass, 0 fail, 1 known skip over the merged wave
• the fix verified itself in live traffic: after hot-deploy, the wave's own final package auto-collected via task_notification with final.txt, honest classification, and a fusion-id settlement that propagated to the linked codex job through the seeded peerJobId
• two production-wedged records unlocked via bounded Reads under the new matcher

reviewer should verify

• four platform CI matrix settles green (linux and macos, node 22 and 24)

notes

• the changed fusion scripts were hot-deployed into the installed 0.0.32 cache during verification; the marketplace refresh to a real 0.0.33 directory formalizes it, and the new TaskOutput/TaskStop hook registration reaches sessions started after that refresh