#Member lifecycle

The cafleet member CLI group wraps the two-step "register + spawn a pane" recipe behind cafleet member create and persists the member-to-pane mapping in the member_placements table. An ordinary member is an active registry row with a placement row, other than the fleet's root Director: it is spawned by a Director via cafleet member create and linked to a specific multiplexer pane, window, and session. The root Director is instead bootstrapped by cafleet fleet create and keeps its own placement row since it is pane-bound.

Single-Director invariant: A fleet has exactly one Director — the root Director recorded in fleets.director_member_id at fleet create time. Only that root Director may own members: cafleet member create resolves the Director from the fleet row itself, so a member can never be another member's Director by construction. The team model is a single flat tier; there is no team nesting.

#Create flow and compensation

cafleet member create registers a pending placement (no pane id yet), spawns the member pane in the Director's own window, then patches the placement row with the real pane id. It compensates failures across the DB and multiplexer: a known owned pane is killed and the registration is deregistered, removing the placement. A backend run failure is compensated by the backend before the CLI deregisters; a patch failure is compensated by the CLI. Cleanup failures preserve the original error and identify the failed cleanup. If a split response did not reveal a pane id, pane cleanup remains unconfirmed; CAFleet does not guess which pane to close. See the creation failure contract. The pending window is ping-tolerant: cafleet member ping against a member whose placement has no pane yet skips the keystroke and succeeds — the member polls its inbox on spawn, so there is nothing a ping would add. The new pane is created without stealing focus, so the Director's active window is unchanged. Identity reaches the spawned pane as literals rendered into the prompt: cafleet member create runs str.format over the resolved prompt, substituting the four identity placeholders — each one and its label line is in CLI options § Spawn-prompt substitution.

#Delete ordering

cafleet member delete tears down the pane (when one exists) and soft-deletes the member, exiting 0. An already-gone pane is tolerated, not an error.

#Spawn-prompt input modes

The spawn prompt is supplied inline as the positional PROMPT argument or from a file via --file <path> (an absolute or CWD-relative UTF-8 path; - reads the whole prompt from stdin); literal braces in prompt text must be doubled ({{, }}) — see CLI options member create.

#Commands

The lifecycle ops and keystroke interaction all live in the member group:

member create takes no identity flag — the CLI resolves the Director from fleets.director_member_id; every other lifecycle verb targets its member by the positional MEMBER_ID subject (the fleet is derived from the member row). Each subcommand's purpose and argument surface are in CLI options § Subcommand summary, which also carries every flag and the shared resolution rules.

cafleet member prompt keystrokes text into a member's pane: the plain form submits a direct user turn (for slash commands and other magic commands a broker message body cannot trigger), and the --shell form is the shell-dispatch primitive of the bash-via-Director fallback protocol — see CLI options.