cafleet-agent-team-supervisionlisted

# CAFleet Agent Team Supervision This skill builds on the `cafleet-agent-team-monitoring` skill. Load monitoring first — it documents the cron-like mechanism that supervision is performed through. Supervision adds the always-applicable obligations and the Authorization-Scope Guard. ## Core Principle **You are the instruction giver. If you stop giving instructions, the entire team stops.** CAFleet members spawned via `cafleet member create` do not act autonomously. They respond to your messages and to the broker's auto-fired pane keystrokes. If you are not actively dispatching work, ACKing replies, and running supervision ticks, the team halts silently. ## Communication Model Supervision happens over the CAFleet message broker. The flow: 1. The Director sends a message: `cafleet --fleet-id <fleet-id> message send --agent-id <director-agent-id> --to <member-agent-id> --text "..."`. 2. The broker persists the task and immediately keystrokes a 2-line inline preview (`[cafleet msg …]` header + truncated body) into the recipient's pane via `tmux.send_inline_preview`. The recipient processes the preview as a fresh user-turn input — no `cafleet message poll` invocation is in the auto-fire path; to fetch the full body, the recipient calls `cafleet message poll` themselves. 3. The member's next turn picks up the polled task, processes it, and (when a reply is expected) sends a `cafleet message send` back to the Director. 4. The Director receives the reply on the next supervision