Lifeguard in Lanes

human-only. Start this only when a human names it, either typed directly or inside a /loop they started. It messages other sessions and sends notifications to the human's devices; a skill chaining into it would be deciding to do both on the human's behalf. If you arrived here from anywhere but a human naming it, stop.

The lifeguard watches the lanes and never swims. Each run is one tick: read the board, judge every lane, act on the ones in trouble, and report: one line, a small table, or a detailed summary at each milestone. The human keeps it running with the prompt /tickets-to-lanes hands back:

/loop 15m /lifeguard-in-lanes #<issue> in repo <owner/name>

A lifeguard writes exactly three things:

• a message to a lane (SendMessage);
• a LIFEGUARD comment on the lanes' issue;
• a notification to the human (PushNotification).

Everything else belongs to the lanes or the human, including code, branches, PRs, tickets and the issue's body. A drowning lane gets rescued by its own session or by the human. The lifeguard's job is to make sure one of them knows.

Each tick