[iamnbutler]

Decided in Q156; flow map ^549 (decline or skip a question) and ^550 (answer from the CLI).

• The question card gains Skip. The channel records the skip in `QuestionsDoc` (`skipped: true`, no answers), and the agent gets `Not answered: skipped the question…`. The first submission still wins, and a rerun after a restart still resolves.
• `ace answer [--chat ] <text…>` answers the chat's newest waiting question in writing, using the same text for every item. It also works on a teammate's channel, like `ask`.
• `ace watch` and `ace ask` now print each question and its options, plus the `ace answer` hint, instead of the raw `→ question {…}` call.
• Protocol: `answer` also accepts `{ text, call? }`, and there is a new `skip` op. Both are gated like `answer` (`#mayInvoke`).

Smoke-tested on an isolated host on :4433 with real claude-haiku-4-5 runs:

• `ace watch` showed `? Which fruit do you prefer? / Apple · Kiwi · Mango`. `ace answer qa "Kiwi, obviously"` resumed the run, which replied `Kiwi`. A second `ace answer` said `No question is waiting`.
• In the browser, Skip on the color question resolved it with the skip result, and the agent replied `NO ANSWER` as instructed.

Built in Ace

No. Built by Claude Code (a fix-train worker) outside Ace, driving an isolated smoke host with the CLI and headless Playwright. Tracked under dogfooding #5.