Fleet protocol

The contract. A lane's brief says what it works on; this says how it behaves. Everything fleet-specific — repo names, lane names, paths, bases, hands-off sets — lives in fleet.config.json (see references/configuration.md). This file names no repository.

The protocol is a tool, not a reading assignment. Every ritual below has a one-command form in ${CLAUDE_PLUGIN_ROOT}/scripts/fleet.mjs, and the evidence rule that governs it is built into the command so it cannot be skipped. Prefer the command to the hand-written version every time — the hand-written versions are what cost the source run hours.