Validation: UI Responsiveness

[ucguy4u]

UI Verification

Verify

• Orientation changes
• Split screen
• Foldables
• Tablets
• Dynamic font scaling
• Dark mode
• Accessibility
• Keyboard handling
• Offline state
• Empty state
• Error state
• Loading state

[ucguy4u]

Critical Agent Gate

Problem: Airo lists UI responsiveness requirements, but the repository does not yet provide a deterministic validation path for adaptive layout behavior, dynamic font scaling, keyboard-safe dialogs, and the manual states that still require device QA.
User / actor: Mobile UI, QA automation, and release maintainers validating Android/iPad/foldable style layouts.
Framework or application layer: Mixed, centered on shared Mobile UI framework widgets and release/QA validation docs.
Owning agent: Mobile UI Agent.
Reviewing agents: QA Automation Agent, Release and DevEx Agent.
Impacted modules/files: app/lib/shared/widgets/*, app/test/shared/*, docs/release/*, Makefile.
Base branch/worktree: confirmed from latest origin/main: yes.
Open questions: Which manual states remain out of scope for widget tests and must stay in a release/device checklist?
Decision: Ready.

Cross-Agent Contract

Provider agent: Mobile UI Agent.
Consumer agent: QA Automation Agent and release maintainers.
Interface/API: shared adaptive widget behavior plus a deterministic validation runbook.
Input shape: viewport width, text scale, theme, keyboard insets.
Output shape: widget test assertions and a documented manual verification matrix.
State changes: docs and tests only unless a shared widget defect is found.
Errors: layout overflow, inaccessible navigation, keyboard-obscured content, incorrect desktop/mobile adaptation.
Permissions: none beyond normal local test execution.
Privacy/redaction: no user data involved.
Persistence: release docs only.
Versioning/migration: none.
Tests required: shared widget tests and a local command that runs the responsiveness suite.

Deterministic Use Cases / Automation Flow

1. Run a single local command for shared UI responsiveness coverage.
2. Verify compact vs. wide navigation behavior.
3. Verify adaptive dialogs respond correctly to mobile width and keyboard insets.
4. Record the remaining manual/device-only checks for orientation, split screen, foldables, dark mode, offline, empty, error, and loading states.

[ucguy4u]

Opened follow-up PR: #533

What this PR adds:

• shared widget tests for adaptive navigation width changes, large text scaling, and adaptive dialog presentation
• make test-ui-responsive as a deterministic local validation command
• docs/release/UI_RESPONSIVENESS_VALIDATION.md to separate automated checks from device-only manual verification
• release checklist hooks so the runbook is part of release validation

What remains before #519 can close:

• run the documented manual/device matrix against the feature areas touched in the release candidate
• verify orientation, split-screen, foldables, dark mode, accessibility, offline, empty, error, and loading states on real device or approved emulator paths