mulmoterminal-bug-report

# MulmoTerminal — is it a bug? **The goal is that the user ends up unblocked, not that an issue gets filed.** An issue is what's left after the other three steps fail to explain the behaviour. Work the steps in order. Stop the moment the user is unblocked. ## Rules that hold in every step - **Never assert "that's by design" from memory.** Say it only with a reason attached: a config key, an implementation file, a guide page. `faq.md` is an index of where to look — it deliberately contains no values. - **Read the real thing.** Current and default values come from the user's actual config file, the schema in the source, or the running server — never from this file, and never from recollection. - **"I don't know" is an allowed answer.** If a step cannot decide, say so and go to the next one. Never close the conversation by guessing. - **Nothing leaves the machine before the user has seen it in full** and said yes. - Reply in the language the user writes in. ## Step 1 — Hear the symptom (collect nothing yet) Ask with `AskUserQuestion`, options first — a user who is already frustrated should be picking, not composing. Up to 4 questions per call; two calls cover this comfortably. - **What kind** — display looks wrong / input doesn't work / a session died or won't connect / won't start at all / phone features / something else - **Where** — a grid cell / the zoomed view / the single view / the file browser / settings / phone - **Which agent** — claude / codex / shell...