feat: fleet default signal and notification driven collection (0.0.31)

[okisdev]

summary

• the fleet default now has a per turn signal: a new fleet-posture.mjs UserPromptSubmit hook injects one advisory line naming the three package threshold, /fusion:ultra, and the fleet-decline: <reason> protocol (disable with FUSION_FLEET_MODE=off or a fleet-mode state file), and the compact recovery echo restates the fleet default instead of a fleet less posture model
• worker records reach terminal from delivered task notifications alone: handleStop scans the parent transcript's notification delta (persisted per session offset, bounded per pass, fail open) before cancellation classification, which removes the deliberately failing TaskOutput probe from the normal collection path and stops TaskStop demands for tasks that already finished
• the in flight stop advisory dedupes by the sorted task id signature (one armed notice per dispatch wave instead of one per turn end, each of which cost an extra model request), and the inline guard appends a one line advisory after a second consecutive dispatch wave of width two or less
• the orchestration policy and ultra skill are restructured so one trigger has one action: the fleet default is hoisted into the operating model with a posture versus execution width split, the three manual fan out sites name /fusion:ultra, the skill's when_to_use leads with task shape, facet counts floor at three, and the convening ceremony of checkpoint, worktrees, and sibling declarations runs inside the skill

test plan

already verified

• node --test "tests/*.test.mjs" -> 878 tests, 877 pass, 0 fail, 1 pre existing skip (the suite grew by 12 new tests across the three touched surfaces)
• a live stop event against a real stuck pending_async record flipped it to task_notification collection with no TaskOutput probe and it settled through a plain --record
• piping a UserPromptSubmit event into plugins/fusion/scripts/fleet-posture.mjs emits the single advisory JSON line when enabled and stays silent with FUSION_FLEET_MODE=off

reviewer should verify

• start a fresh session against this plugin version and confirm each user prompt carries the one line fleet default reminder and that FUSION_FLEET_MODE=off silences it
• dispatch two consecutive narrow agent waves and confirm the guard's advisory line appears once and that a wave of width three resets the counter

notes

• installed 0.0.30 cache dirs already carry these files as hot deploys for live sessions; the next plugin refresh to 0.0.31 reconciles the cache with the release
• hooks.json registration and the skills listing load at session start, so running sessions gain only the script side fixes; the per turn reminder and the skill framing need a new session