team answer

Presses the one recorded key of a folder-trust dialog, and only that key. Every check has to pass on two fresh reads of the pane, and the folder must be the lobby on three readings at once: the path the screen shows, the folder the pane itself reports working in, and the lobby's parent directory, where no name may sit that differs from the lobby's by whitespace alone. A row's trailing padding is stripped, so the screen's last byte alone is never proof. Anything else sends nothing.

Synopsis

team answer <seat> trust [--session <name>] [--file <path>] [--json]

<seat> names one configured live seat. trust is the only dialog word. No option takes a key, a text, or another dialog.

What it reads and writes

Reads the team file, this machine's approval and the approved copy the trust entries are read from, the seat's state, the installed CLI's version, and the pane — the screen's own lines, the folder herdr reports the pane working in, and the lobby's parent directory. The version must match a record whose own capture is registered (src/profiles/trust-answer.ts); Codex's record also needs a registered capture of its folder layout in the real lobby and none exists, so Codex answers nothing today. The command holds the seat's lock (<state dir>/seat-locks/<session>/<seat>) for its whole run, so a launch of the same seat cannot act beside it.

On success it writes trust-sent-recovery into the seat's state and reads it back before sending the key: a crash between the two leaves a recovery a retry only observes, never a dialog answered twice. Under the seat lock, on both of its fresh reads of the pane, and immediately before every terminal input — the trust key, the typed rules line, and Enter — if the seat's state holds a launched record (a seat stopped at a dialog has one: its launch records the identity in the same write as the waiting record; a launch from before the field existed, or one whose process herdr could not read when it stopped, has none and keeps today's check), the pane's process identity must match the recorded process (same); if herdr cannot read the process or it is gone or replaced, the command refuses without sending that input. Refusals before the recovery write — caller, policy, state, version, screen, label, folder and action, and both inspections — write nothing. The one refusal between the write and the key, this process check, puts the record back to exactly what it was (waiting-owner), written and read back under the same lock: a later team answer can still answer the seat, and only a crash in that window leaves trust-sent-recovery for a retry to observe. After the key — a send that failed, an idle prompt that did not come, rules not delivered — a refusal leaves trust-sent-recovery as well. If refusal happens between typing and Enter, the line notes that rules were typed and not sent. It then sends one key, waits for the idle prompt, delivers the ordinary rules, and writes the seat ready.

Who may run it

The owner, from outside herdr, or the coordinator from its own seat — the seat of that name in a session this project's state records, the file's session first and then a session the state records the caller's pane in (any session key the state holds is a session the check will try), on the pane the state records for it: a seat of another session, or a pane merely renamed to the coordinator's name, is refused — and so is a seat the state records no pane for, or records on another pane than this call is on; those two refusals name the seat and the repair. What that proves is placement, and no more: the state file is in the project, and a process of the same user that writes its own pane there under the coordinator's name, and renames its pane, passes. The check guards a mistaken agent, not a hostile process running as the same user. --file and --session are the owner's alone, from a terminal outside herdr: a non-owner aiming either is refused before the flagged file or session is read at all. With dialogs.trust: owner (the value when dialogs is omitted) nobody sends a key, the owner included.

Flags

What it prints

Human output is one line: refusals and recovery on stderr, success on stdout. Under --json, the same outcomes print one object on stdout and stderr stays empty.

The JSON objects, by status:

The recovery reasons are its key could not be sent, its idle prompt did not come, and its rules were not delivered. The usage message is a seat and trust are required, unknown dialog "<word>", or the argument parser's own message. The configuration message is the file's problem list (line <n>: <problem>, joined with ; ) or the team file cannot be read.

Refusals

Every refusal line is <seat>: <reason> except an unplaced caller's, which is its reason alone and names no seat, and the four team answer: lines that speak to the caller rather than about the seat: team answer: --file is the owner's, from a terminal outside herdr; this call is <caller>, team answer: --session is the owner's, from a terminal outside herdr; this call is <caller>, team answer: no pane is recorded for seat <name> in this session: the owner stops that seat and runs `team up` , and team answer: the state records pane <pane> for seat <name> in this session, not the pane this call is on: the owner stops the team and starts it again (`team down`, then `team up`) . The classes are the log line's own (refused trust: <class>):

action is a well-formedness defence: it is reached only when a profile records a key byte the host does not send, which the shipped profiles (0d, 31, 61) do not.

Exit codes

Log lines

Every transition writes one line to team.log: <ISO timestamp> answer [<who>] <seat>: <message>. <who> is the class the caller check returned — owner, coordinator, seat, or unplaced — never the owner for a caller that is not the owner. No line holds pane text, a pane id, a folder, or an unplaced reason.

Examples

$ team answer
team answer: a seat and trust are required
Usage: team answer <seat> trust [--session <name>] [--file <path>] [--json]

Known limits

A process can still change between that last read and the input itself (two herdr calls), as for every read-then-act in team.