[witbrock]

Opening mobile composer options kept the same “+”/“More actions” cue and offered no outside-tap dismissal. The toggle now becomes a close icon with a “Close actions” accessible name. Outside clicks and Send dismiss the options, Escape restores toggle focus, and browsers supporting CloseWatcher can handle device Back through their native close-request stack. Drafts and existing submission handlers remain intact.

Dismissal deliberately waits until click activation: collapsing on pointer-down or focus can move Send before a touch click reaches it. No history entries, prompt policy, backend changes or deployment are included.

Validation (Tier 1):

• 31 tests passed across compactComposer, chatTabSpeechPlanning and chatConversationLayout.
• Production-template/CSS/module Chromium fixture passed at 360×640, 412×915, 360×360 and 1024×900 with touch, plus 900×900 and 1440×900 desktop.
• Browser coverage includes repeated touch toggles, accessible close naming, outside tap, Escape/focus, exactly one Send click with the original draft, unchanged compact height, dictation and desktop placement. The baseline failed the new close-name check. Final mobile draft composer heights recover to 62–76px.
• Static frontend lint and git diff --check passed. Screenshots retained in the worker worktree at .run/composer-dismissal/.

Merge decision: ready; the touch submission regression caught during implementation is repaired and the bounded acceptance checks pass. Browser evidence uses a local production-component fixture, not an authenticated Von server or physically installed PWA. CloseWatcher lifecycle is unit-tested; physical device Back is not claimed. Existing authenticated host bridges target other checkouts and were not repurposed.

Von task: #V#task_agent_55d860ee72cf8465000f59286dbb5db7