quiet

Quiet supervision mode (kunchenguid/firstmate#2356): the same token-saving daemon tradeoff as /afk, made explicit for a captain who is staying, watching the session, and does not want to exit the mode just by chatting.

Where a daemon runs, this skill is a thin wrapper. The afk skill owns the daemon's injection, busy/composer guards, and reliability properties; quiet mode uses that machinery while the captain remains present. For captain-held rechecks under quiet, see architecture.

What it does

0. First check whether quiet mode needs anything here. On Pi or pi-signed, enter nothing: the attended branch already keeps routine wakes out of this conversation (the afk skill's step 2); tell the captain so. Everywhere else run bin/fm-afk-launch.sh quiet-check; its header's QUIET MODE owns what each result means.
   • Exit 0: enter nothing - no record, no flag, no daemon, and /quiet off then needs nothing either. Tell the captain in AGENTS.md section 9 language that supervision here already works that way: routine fleet events stay off this conversation, while decisions, failures, credentials, and review-ready work still reach them. When its line says the supervision session is paused, say instead that routine updates reach them until it recovers, and when it next retries.
   • Exit 2: an away record is live, so the captain has returned: run the afk skill's return and clear its catch-up gate, then run quiet-check again and follow its new result.
   • Exit 1: go on to step 1; if it printed a line, first tell the captain plainly what keeps supervision from already being quiet here.