Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android QA — Sign-off·61 in this wave

Wave

Android QA — Sign-off

Page-by-page human sign-off on PHONE ONLY. Owner Caitlin, gate Matthew. Tablet verification is a separate later wave (Android QA — Tablet), because phone must prove the backend and feature logic before any tablet effort. All 16 checks were rewritten to phone-only on 2026-07-26.

TacTile › Launch TacTile › Android › Android QA — Sign-off

4/61 done57 open2 open blockers

Selected taskclear

Decide how QA runs against a prod-only database before Caitlin's phone pass

To doOwner · ait_68803c02Blocker

The Android debug build writes to the production database, which has no backups. Needs a decision on how the QA pass runs, not an engineering fix.

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 how QA runs against a prod-only database before Caitlin's phone pass** · to do · blocker

The Android debug build writes to the production database, which has no backups. Needs a decision on how the QA pass runs, not an engineering fix.

Where it sits: TacTile › Launch TacTile › Android › Android QA — Sign-off

## The brief on file

STILL UNANSWERED since round 4, and it now blocks THREE things rather than one. Raising it again with what changed.

THE QUESTION IS UNCHANGED: QA and demo data would be written to the production database, which has pitr_enabled: false and zero stored backups (verified against the Supabase Management API 2026-07-28). There is no staging DB — branching needs a paid plan (t_a2ccb527) and staging-api.tactile.to's Supabase secrets come from the same 1Password item as prod (wrangler.toml:216-218).

WHAT NOW DEPENDS ON IT:
1. Caitlin's QA pass (w_4e1d3ad0) — 58 tasks, untouched since 2026-07-27.
2. Play screenshots (t_640bb552) — the account is empty, so captures show "No triggers yet" and a flat chart. Unshippable.
3. Any external beta.

WHAT ROUND 7 FIXED so this is no longer ALSO a silent-default problem: scripts/android/wire-local-config.sh:19 used to default SUPABASE_REST_URL to the production project ref, so anyone running it the documented way got a prod-writing build without being told. That default is gone — the variable is required, and pointing at prod now needs an explicit ALLOW_PROD_DB. CI has the same guard. The tooling can no longer choose prod FOR you; it can only make you choose.

So the remaining decision is purely yours: (a) accept prod for QA/demo on a clearly-labelled account, (b) resolve t_a2ccb527 first, or (c) something narrower.

Recommendation unchanged: (a) now, (b) before any external beta.

## 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 QA — Sign-off

Decide how QA runs against a prod-only database before Caitlin's phone pass