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

Adapt Dashboard for tablet

DoneOwner · Vivt_9cd8b1a3

Waiting on 1 · all clearAudit every screen at tablet sizes and record what breaks

Unlocks 1Approve: Android tablet support

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

**Adapt Dashboard for tablet** · done

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

## Waiting on 1

- Audit every screen at tablet sizes and record what breaks — done

## Unlocks 1

- Approve: Android tablet support

## The brief on file

DONE — PR #303, merged a3735bd5. The Dashboard width cap is now measured.

Three assertions added to ContentWidthBoundsTest at @Config(qualifiers="w1280dp-h800dp"): content bounded to ContentWidth.standard, content centred, and the page box not itself capped.

Making it measurable required rewiring DashboardViewModel. It took the CONCRETE TriggersRepository, SessionDestinationsStore and SessionStore, which drag in SupabaseClient and the whole auth graph — the exact dependency AssetsSources.kt says a ViewModel test has no business building. It now takes the three narrow interfaces those types already implement and AssetsSourceModule already binds. No new interface, no new Hilt provides.

destinationsStore.current is not on DestinationsSource, so its four call sites became destinations.value — option (a), behaviourally identical (SessionDestinationsStore.kt:54 defines current AS _destinations.value). Option (b) was declined: widening the interface contradicts its own kdoc and would force an override onto FakeDestinations.

Also added: DashboardTestTags (the screen had ZERO testTags), and an `analytics` accessor on OfflineApis — it exposed only repositories, and DashboardViewModel takes the raw AnalyticsApi.

MUTATIONS, both red on the intended assertion, neither a compile error:
- M1 .fillMaxHeight() -> .fillMaxSize() with widthIn left in place (the historical broken shape) -> "dashboard.content is 1280.0.dp wide; the cap is 600.0.dp ... A width equal to the window means the cap never applied."
- M2 drop contentAlignment = Alignment.TopCenter -> "dashboard.content is pinned to the start edge (left = 0.0.dp)"

CEILING, stated plainly: this guards TWO of the three no-op shapes, not three. Bounds cannot see a background painted inside the cap, and on the Dashboard the gap is wider than elsewhere — the page colour is the Scaffold's containerColor (DashboardScreen.kt:121) and the node measured here paints nothing, so the full-bleed assertion proves only that the cap is on the content rather than the page box. See t_a6987e98 for the attempt to close that with pixel capture.

## 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

Adapt Dashboard for tablet