Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android — Tablet support·14 in this wave

Approve: Android tablet supportTo do · blocker Unlock orientation and add adaptive dependenciesDone Audit every screen at tablet sizes and record what breaksDone Adapt Dashboard for tabletDone Adapt Assets tabs for tabletDone Adapt Analytics for tabletTo do Adapt Canvas for tabletDone Adapt destination creation flow for tabletTo do Rotation-survival pass — remaining screens (shell done; create flow, canvas, QR editor outstanding)In progress Android QR editor destroys a code's marker gradient on any save (6 fields nulled by one decode default)Done Adapt Settings for tabletDone Adapt QR editor for tabletTo do Adapt AI agent screen for tabletTo do Decide whether the instrumented paint tier becomes a required gate (needs an emulator CI job)To do

Wave

Android — Tablet support

Starting from zero, and worse than zero — the manifest hard-locks portrait orientation, so the app cannot even rotate. 0 of ~53 screens are size-aware. This is a from-scratch initiative, not a tuning pass.

TacTile › Launch TacTile › Android › Android — Tablet support

7/14 done7 open1 open blocker

Selected taskclear

Decide whether the instrumented paint tier becomes a required gate (needs an emulator CI job)

To doOwner · met_7dff6480

No dependencies in this wave — nothing gates it, and nothing waits on it.

Show the prompt

You are Viv, the agent for the TacTile lane of Command.

Open the lane and work there:

```bash
cd ~/Command/tactile && claude
```

Read that lane's CLAUDE.md and lane.json before you touch anything — they
carry your identity, your scope, and the hazards specific to this lane.
Read state from the hub (https://internal.tactile.to) or ask. Never guess at it.

## The task

**Decide whether the instrumented paint tier becomes a required gate (needs an emulator CI job)** · to do

Where it sits: TacTile › Launch TacTile › Android › Android — Tablet support

## The brief on file

MATTHEW'S CALL — a spend decision, not a code one. Filed because round 14 found there was no row for the runner/strict-mode work (an earlier brief mis-filed it under t_a6987e98, which is actually "Adapt Analytics for tablet").

The runner half is DONE — PR #320 (merged 8a06d862): scripts/android/run-paint-tier.sh sets density 160, resets it in a trap, passes -Ptactile.paint.strict, and parses the result XML so zero-tests / any-skip / any-failure is a non-zero exit.

THE DECISION: should `bash scripts/android/run-paint-tier.sh` become a required gate?

What makes it a spend decision:
- gate.sh delegates to run-all.sh, whose 18 checks are all node/vitest/bash. Zero Android. Adding a gradle+emulator step there would make every TS-only PR boot an emulator locally.
- .github/workflows/android.yml has no connectedAndroidTest job and is dead anyway behind the GitHub Actions billing wall (t_43e311d2). A CI emulator job costs runner minutes on top of clearing that wall.
- verify:android is `./gradlew :app:assembleDebug -q` — it runs ZERO tests, so wiring THAT into the root chain would not run this or any other Kotlin test.

Why it matters: ContentWidthPaintTest is the only test in the repo that can see width-cap no-op shape 3 (a page background painted inside the cap). Bounds assertions provably cannot — verified by mutation. Today nothing runs it, and the bare Gradle command is green-by-omission: measured on the dev AVD, `./gradlew :app:connectedDebugAndroidTest` at 411dp exits 0 while its XML records skipped=1.

Options: (a) leave it developer-run and documented (status quo, zero cost, relies on someone remembering); (b) add a local pre-push hook step for PRs touching apps/android/**; (c) clear the billing wall and add an emulator CI job.

Recommendation: (a) until the billing wall is resolved, then reconsider (c). Do NOT wire it into gate.sh — that would make an emulator a prerequisite for every TS change in the monorepo.

## How to work this

- Do the work, don't just plan it. If the fix is obvious and safe, make it.
- Surface anything needing Matthew's sign-off instead of deciding it yourself.
- Short replies. Lead with the answer, then stop.
- Finish by saying what changed, what you verified, and what you'd do next.

To doIn progressDoneBlockedPick a wave on the left · tap a task to expand it

Lanes

Android — Tablet support

Decide whether the instrumented paint tier becomes a required gate (needs an emulator CI job)