/fleet-wrap

Etan, at dawn after gen-10's overnight run (verbatim, red-team verified ✅RT): "Why were you just listing my messages in WhatsApp the whole night? Why didn't you stop?"

Recurring since gen-7 — idle-pane / wasted-money / heartbeat noise (f3231646:[2655], 62517efa:[7956]). gen-10 weave #24, imp10.

When the fleet wraps: ZERO polling crons, ONE final dashboard + ONE message, then SILENT.

If the planned overnight mechanism breaks, choose one of two paths only: delegate real approved work to a live owner, or stand down SILENT. A polling loop with zero workers is the inverted fleet-wrap failure: it burns the night reading status/messages while nothing is actually being driven. Evidence: Etan at dawn, verbatim raw operator turn: "Why were you just listing my messages in WhatsApp the whole night? Why didn't you stop?" (orchestrator 62517efa:[7957]).

When this fires

• All workers are done/idle AND their claims are verified — no queued approved work remains.
• The overnight/sprint queue is exhausted.
• Etan said "wrap the fleet", "stand down", "we're done", or approved the final state.

Disambiguation vs /session-handoff: "wrap up" aimed at YOUR session (context high, session ending, successor needed) routes to /session-handoff — that skill owns single-session continuation. THIS skill fires on FLEET-wide close: all workers done, nothing queued, the channel goes quiet. When both apply, run /session-handoff FIRST — then this protocol governs the outgoing agent's exit.

Retire protocol (outgoing agent — pairs with /session-handoff)

Succession is routine (gen-12 evening: orc → gen-13 path, vl LEAD v1→v2, bl LEAD outgoing→successor — three successions one day). Before you compact or go silent:

1. Hand off completely — live-watch transfer list written (see /session-handoff); successor brief posted; grill answered (monitors still running during transfer).
2. Stop monitors — kill every cron/monitor you own so compaction doesn't fire on stale loops (71a8e3f5 [5418]).
3. Final dashboard (if fleet-wide wrap via this skill).
4. Kill your own pane — do not linger as a zombie orc writing duplicate handoffs.

Order: handoff → stop monitors → final dashboard (if fleet-wide wrap) → close pane.

The protocol (in order)

1. VERIFY done. Per worker: state check + independent claim verification (/never-fabricate R8). A fleet is not wrapped because it looks quiet.
2. KILL ALL POLLING. CronList → CronDelete every monitor/heartbeat/status cron you own; TaskStop background monitors; report the stopped IDs in the wrap-up (orc REF9). Zero exceptions — a "harmless" 5-minute status cron is exactly how the WhatsApp-all-night failure happened.
3. ONE final dashboard (/html-dashboard, cloned template — never from scratch): sprint state, merged PRs, open loops, blockers, money/tokens spent.
4. ONE final message (WhatsApp / the agreed channel): dashboard link + a 2-3 line summary. ONE message. Not one per event.
5. brain_store the wrap — sprint summary, stopped cron/monitor IDs, open loops. Tags: milestone, <project>.
6. SILENT. No further messages, no re-armed loops, no "still quiet" heartbeats — until Etan speaks or new approved work arrives.

What silence does NOT mean

• Blockers found during wrap go ON the dashboard and IN the one message — not as a follow-up stream.
• A real incident (data loss in progress, security) justifies ONE alert. Everything else waits for the next session.
• Silence ≠ abandonment. Open loops are written down (dashboard + collab + brain_store) so the next session picks them up — the channel goes quiet, the state does not evaporate.

Anti-patterns

Integration