Chief: coordinator tools and a configurable point of contact
Chief owner turns can now contact coordinator sessions through six folded acpmux tools: send, ls, last, info, inbox_read and inbox_reply. A per-Chief contact setting, unset by default, names the coordinator for fleet, PR and lane work after the next Chief host restart; the prompt treats its relays as information, never the owner's approval.
Leo: "i also want you to be able to be like a point of contact for chief if possible" and "chief should be able to look like you/have the same level of capabilities as you".
Context: https://github.com/manaflow-ai/cmuxterm-hq/issues/5774 (b+c). This is one Rust change; the presentation pieces are separate.
Risk: a Chief owner turn can now prompt other sessions. Turns carrying another person's text still run ask and refuse these tools. approval::CHIEF_TOOLS and turn_allowed_tools are unchanged; background task tools remain excluded. A standalone acpmux server is denied when cmux folding is unavailable, so it cannot expose background or team tools. Prior art #25615's GUI chat tools and #22866/#22909's approval boundary are preserved.
Validation: fleet tests pending at the published head. Coverage includes all six tools refused in ask turns, an owner-policy acpmux_send allow, preset server folding and tool filters, and contact settings/prompt goldens.
Risk: Chief code (mostly teammates’). A Chief owner turn can now prompt other acpmux sessions, which may run approve-all or bypass. Turns that carry another person’s text run ask and refuse all six tools (tested). The standalone mcp__acpmux server stays denied, so bg_* and team_* never reach a turn when the cmux fold is off.
Review (subagent claude-opus-5-5): SHIP at 1dd6f61459cf4718b1738f1f10be3dbd6bd8dab9, and of the 1dd6f614..328b82891f40058b28946a747107c17f042e9fe1 delta.
Agent session: agent session