[witbrock]

Merge decision: ready — the pinned composer keeps the jump-to-latest control visible, with matching circular Send and microphone controls.

User outcome

The blue jump control follows the actual top of the composer as drafts and More actions expand. Both main buttons are 44 px circles. Click/tap the microphone to dictate into an editable draft; Shift-click or touch long-press toggles a voice conversation. Start/End voice also remains in More actions, with hover and accessible explanations.

Native Von task: #V#task_keep_jumptolatest_above_the_composer_ae849987.

Material changes

Anchor jump-to-latest to the sticky composer. Preserve icon SVGs while updating accessible action labels. Route alternate microphone gestures through the existing voice lifecycle; cancel touch holds on movement, cancellation and disposal, and suppress the trailing tap. No speech backend or model-routing change.

Evidence

• 18 dictation and voice controller tests pass, including gesture cancellation and icon/state preservation; 13 focused chat scroll/send/queue tests pass; changed JavaScript lint and diff checks pass.
• Chrome production-template/controller fixture at http://127.0.0.1:8777, 11 September 2026: 9 px jump clearance above normal and expanded composer, matching 44 x 44 buttons, and no horizontal overflow at 390 x 844. Clicking jump reaches the end and hides the control.
• Broader chat/speech run: 304 pass, two existing conversation-title expectation failures. Unchanged main reproduces both (286 chat tests pass, two fail). Merge decision does not change; these do not concern composer behaviour.

Ship boundary

The minimum criteria are visible, reachable controls and preserved send/dictation state handling across desktop and narrow layout. Gesture behaviour is controller-tested; no live microphone/model request was made. Cloudflare entry diagnosis and speech quality changes are outside scope. Michael explicitly authorised deployment to DGX after completion.