# Android question-card proof

Environment for each run: Android API 36, Pixel 9, 1080 x 2424, portrait, default text size, light app theme, Gboard software keyboard. Each commit runs its own server and Metro from its own checkout with a fresh home and dev seeding disabled. The native-client fingerprints match. Synthetic projects and threads are created through the normal CLI; the replay transcript supplies two long questions and five long options per question.

## Primary: three-button navigation

1. Enable Settings > Navigation mode > 3-button navigation.
2. Open the paired app and Release decisions thread; expand the pending question card.
3. Start a recording. Select the first option in Decision 1.
4. Scroll inside the question card and select the first option in Decision 2.
5. Tap the center of Submit answers through its accessibility label.
6. Base: button overlaps the Android navigation bar; tapping opens Android Home and leaves the answers pending. Head: button remains fully above the bar and tapping submits both answers, showing the replay completion message.

## Keyboard and floating queue

Use keyboard-transcript.ndjson, which adds optional free-text companion fields to the same two questions, and a new Keyboard decisions thread on each server. Queue the same follow-up with `thread send`: “After these answers, summarize the release plan.” Record scrolling to the first custom-answer field and tapping it to open Gboard. On base the bottom of Submit is clipped at the keyboard edge; on head its entire button stays above Gboard. The 1 queued floating control remains below the header on both sides in this viewport. No answer submission is claimed for this keyboard-only check.

## Gesture navigation

Switch Settings > Navigation mode > Gesture navigation. Open a fresh Gesture decisions thread on each server, select the first option of each question, and tap Submit answers. Both sides submit successfully. Base places the button lower, near the gesture area; head provides the bottom clearance. Do not claim a Home activation in gesture mode.

Recordings are whole app interactions; the primary base video intentionally ends on Android Home because that is the observed failure. Capture review used decoded contact sheets and terminal frames. No tests stand in for these observations.

## Tablet

Pixel Tablet, Android API 36, 2560 x 1600 landscape, gesture navigation, light theme. Use the same keyboard-capable two-question transcript in a fresh Tablet decisions thread on each server; select the first option in both questions and tap Submit answers. Both commits submit successfully; base places Submit at the bottom gesture area, while head keeps the full button clear. The navigation rail and content pane use the same widths; the second run's thread list also includes the first paired environment. Tablet three-button navigation and tablet keyboard were not checked.