Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android — Build & release·15 in this wave

Submit Android build for reviewTo do · blocker Approve: Android releaseTo do · blocker Seed a demo account — it blocks BOTH the Play screenshots and Caitlin's QA passBlocked · blocker Produce phone + tablet Play screenshotsBlocked Complete the Play Data Safety formIn progress Full device test pass on a physical Android phoneTo do Full device test pass on a physical Android tabletTo do Play Store review pre-flightIn progress Android CI + release automation (the wave goal had no task for it)Done Play feature graphic (1024x500) — hard submission requirement, nobody has filed itDone Public data-deletion page — Play requires it reachable WITHOUT sign-in (verified 307 today)Done The Android tier can be GREEN on a tree that does not clean-build — Hilt errors hide behind stale codegenTo do Write Play Store listing copyIn progress Play 7"/10" tablet screenshots — after the tablet adaptation landsTo do AssetsViewModelFailureTest flakes ~3% — cause not identified, symptom guarded not fixedTo do

Wave

Android — Build & release

No CI, no Play metadata, no release automation exist today. iOS has working Fastlane; Android has nothing.

TacTile › Launch TacTile › Android › Android — Build & release

3/15 done12 open3 open blockers

Selected taskclear

Play Store review pre-flight

In progressOwner · Vivt_af4a7a28

Waiting on 4 · 4 still openProduce phone + tablet Play screenshots Complete the Play Data Safety form Full device test pass on a physical Android phone Full device test pass on a physical Android tablet

Unlocks 2Submit Android build for review Approve: Android release

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

**Play Store review pre-flight** · in progress

Where it sits: TacTile › Launch TacTile › Android › Android — Build & release

## Waiting on 4

- Produce phone + tablet Play screenshots — blocked
- Complete the Play Data Safety form — in progress
- Full device test pass on a physical Android phone — to do
- Full device test pass on a physical Android tablet — to do

4 of those are still open. If one genuinely blocks this, say so and stop rather than working around it.

## Unlocks 2

- Submit Android build for review
- Approve: Android release

## The brief on file

Viv — pre-flight audit RUN 2026-08-06 against the code. Two of the four stated criteria are already met; the third had two real failures and both are fixed in PR #225; the fourth is blocked.

CRITERION 1 — "account deletion is reachable in-app": ALREADY MET. Not a blocker, contrary to the usual assumption about this app.
  Path, two taps from cold launch: Account tab (MainTab.kt:30, a top-level nav tab) -> AccountHostScreen -> SettingsHost -> SettingsScreen -> AccountActionsSection -> "Delete Account" row (SettingsScreen.kt:417-423, destructive/red) -> DeleteAccountDialog (:160-171) -> SettingsViewModel.confirmDelete (:282) -> AccountDeletionRepository.deleteAccount.
  It hits a REAL endpoint, not a stub: DELETE /api/account with hasBody (AccountApi.kt:47-48), legacy POST fallback on 404/405, and the server handler (apps/api/tactile-api/src/routes/account.ts:287+) does a GDPR Art. 17 confirmation gate, Stripe cancel, R2 purge across three buckets, and rpc/delete_account_cascade.
  Client gate accepts the account email (case-insensitive) or the literal "DELETE".
  PLAY ALSO WANTS A WEB DELETION URL — https://tactile.to/account/delete exists (apps/web/app/(app)/account/delete/page.tsx). CAVEAT WORTH CHECKING BEFORE SUBMITTING: it sits under the authenticated (app) route group. Confirm it does not 404 or redirect-loop for a SIGNED-OUT visitor, since that is who Play tests it as.

CRITERION 2 — "Data Safety complete": see t_3473969b. The inventory is now derived from code.

CRITERION 3 — "no placeholder or dead-end paths in reachable UI": TWO REAL FAILURES, BOTH FIXED IN PR #225.
  a) ui/analytics/AnalyticsScreen.kt:103 — `onGearTap = { /* analytics settings deep-link — later */ }`. A real button with an accessibility label and an EMPTY handler: tapping produced nothing at all. A control that silently does nothing reads as a broken app rather than an unfinished feature, and reviewers open exactly these. Fixed: onGearTap is nullable and the gear renders only when a handler exists.
  b) ui/dashboard/DashboardScreen.kt:177 — recent-destination rows raised a "coming soon" snackbar under a comment claiming DestinationLaunchpad was unbuilt. It was built and wired at MainShell.kt:345, and Assets had been routing to it the whole time. Fixed: the row opens the same launchpad, resolving the row projection back to the real record via the store.

  LEFT DELIBERATELY, and worth a product call rather than a code change: ui/launchpad/TriggerLaunchpadScreen.kt:513, :521, :548 — "Lock tag", "Password protect" and "White label domain" toggles. The audit rated these highest-risk because they appear on every trigger launchpad, but each already states when the feature ships and where to do it today (iOS or web). That is disclosure, not a dead control. If Matthew wants them gone before submission, say so — it is a one-line removal each.

  ALSO SAFE TO DELETE, and worth doing so successive audits stop re-filing them as unbuilt work: AiAgentStubScreen, ui/nfc/NfcLaunchpadScreen.kt, TriggerLinkerScreen, and ComingSoonBody in AnalyticsScreen.kt — all orphaned, all unreachable, all cost nothing at review time but keep generating false findings.

  NO FABRICATED DATA IS REACHABLE. Every data-bearing surface reads from a repository; the dashboard falls back to "—" rather than fake numbers. The three things that look like candidates are a styled form-preview swatch, @Preview-only fixtures, and a canvas placeholder consumed solely by a unit test. Worth noting the reverse is true on iOS: LinkHubCard defaults collectionRows to sampleRows and production never overrides it, so iOS users see fabricated link rows (Website/acme.com, Instagram/@acme). Android is clean; iOS is not — that is an iOS-wave finding.

CRITERION 4 — "release build passes on real hardware": BLOCKED on t_f85c04f8 (local.properties has no Supabase config, so the app cannot reach a backend) and on t_b4b198df / t_8d098ffa, which are Caitlin's device passes.

## 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 — Build & release

Play Store review pre-flight