Animated mic button states (idle glow / recording pulse / transcribing shimmer / success flash)

[Pivii]

Context

The Android mic button is static (icon swap + X/✓ pills). iOS AnimatedMicButton has 4 animated states: idle glow, recording pulse, transcribing shimmer, success flash — strong perceived-quality signal in the keyboard.

What to do

Port the 4 visual states to the Compose MicButtonRow:

• Idle: subtle accent-blue glow
• Recording: red pulse
• Transcribing: shimmer
• Success: brief flash before returning to idle
  Drive from DictationState (Idle/RecordingRequested/Recording/Transcribing/Done/Failed). Keep haptics on touch-down.

Acceptance criteria

• Each DictationState maps to a distinct animated visual
• No jank on low-end device (Pixel 4); animations respect reduced-motion / battery saver where applicable

[Pivii]

Current-code premise audit (2026-08-27)

The issue cannot safely be implemented literally against current develop@bcba9a6 without overturning an approved Android layout:

• Android DictationState has only Idle / Recording / Transcribing, not RecordingRequested / Done / Failed. Engine loading/failure is intentionally separate in SttEngineState + PendingMicGate.
• MicButtonRow is composed only in the idle keyboard. Recording and transcribing deliberately replace the keyboard with the approved WwpNL / XfNKh waveform screens; commit history explicitly removed the recording mic pill.
• The iOS reference also models success as a transient transition, not a persistent Done state; requested is static and failed reuses idle.

A design-safe implementation would preserve those Android screens, animate the idle pill, use the existing recording/processing waveforms as lifecycle motion, and add a one-shot green acknowledgement only after a non-null transcription result. Reduced-motion/battery-saver policy must also gate the existing infinite waveform loops.

This slice is deferred rather than silently reintroducing a mic control that contradicts the approved Android mockups. The campaign is continuing with the concrete, non-ambiguous accelerating-backspace child #53.

[Pivii]

Reduced-motion / battery-saver slice merged (#98)

Child #97 is closed on develop@5c1108e. The four custom synthetic processing-waveform loops now share a live Android policy: animator scale 0 and battery saver freeze at a deterministic phase-zero waveform; restoring either setting resumes motion without process recreation. Live microphone-energy bars remain functional and untouched.

Exact head: 476 JVM tests, lint 0 errors, APK assembly; fresh-context review approved; CodeRabbit passed. Pixel 4 Android 15 frame diffs proved normal→static→resumed for both animator scale and forced battery saver with the same process PID, no crash/ANR, and no sensitive capture.

The remaining #24 visual semantics (idle glow and one-shot success acknowledgement while preserving approved WwpNL/XfNKh replacement screens) remain intentionally unresolved because the issue prose conflicts with current Android state/layout contracts.