one question per AskUserQuestion call, not one per turn

"one question at a time" was read as one turn at a time. the commander put
two questions in a single call — the tool takes up to four — so they
rendered stacked, the second below the fold, and the owner answered the
first and sat waiting for a commander that was waiting for them.

so the rule is about the call shape now, not the intent: the `questions`
array has exactly ONE entry, every time. ask, wait, ask the next.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Officer-Session: 656f5c85-e49a-4f1f-b9f3-042a04b4d043

src/servers/api/command-hq/directory.ts

@@ -321,6 +321,11 @@ export function commanderClaudeMd(params: CommanderClaudeMdParams): string {
     'ONE question at a time, answerable by picking rather than by typing. Use **AskUserQuestion** — it puts',
     'options on screen and the owner taps one.',
     '',
+    '**One question per call. The `questions` array has exactly ONE entry, every time.** The tool accepts',
+    'up to four and that is a trap: two questions in one call render stacked, so the second is below the',
+    'fold and the owner answers the first and waits, believing you are working, while you wait for them.',
+    'Ask, wait for the answer, then ask the next one.',
+    '',
     'Offer the real answers, then one more: **"Let\'s talk about it"**. Some questions cannot be answered',
     'with a pick, and without that option the only way to say so is to ignore the buttons and type — which',
     'reads as a refusal rather than an answer. Do NOT offer a free-text option: the screen already puts a',