Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›DevOps›DevOps Launch Readiness·20 in this wave

Wave

DevOps Launch Readiness

Gated by the surfaces existing. Android is the long pole — it has no release automation and no UI tests, while iOS already has working Fastlane.

TacTile › Launch TacTile › DevOps › DevOps Launch Readiness

4/20 done16 open1 open blocker

Selected taskclear

Approve: DevOps Launch Readiness

To doOwner · met_2ee4de1bBlocker

Waiting on 18 · 15 still openRun iOS unit tests in CI Run Android unit tests in CI Wire iOS release to CI Add Android instrumented/UI tests Build Android release automation Build Playwright billing.spec.ts Build Playwright onboarding.spec.ts Build Playwright destinations.spec.ts Add RLS policy tests Add custom domain tests Add coverage reporting in CI Run a load test against staging Add Web Vitals + RUM Add synthetic monitoring on key flows Add a sensitive-operations audit log Add NFC + QR encoding tests Add AI agent tests Add Contacts & Leads tests

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

**Approve: DevOps Launch Readiness** · to do · blocker

Where it sits: TacTile › Launch TacTile › DevOps › DevOps Launch Readiness

## Waiting on 18

- Run iOS unit tests in CI — to do
- Run Android unit tests in CI — done
- Wire iOS release to CI — to do
- Add Android instrumented/UI tests — to do
- Build Android release automation — done
- Build Playwright billing.spec.ts — to do
- Build Playwright onboarding.spec.ts — to do
- Build Playwright destinations.spec.ts — to do
- Add RLS policy tests — done
- Add custom domain tests — to do
- Add coverage reporting in CI — to do
- Run a load test against staging — to do
- Add Web Vitals + RUM — to do
- Add synthetic monitoring on key flows — to do
- Add a sensitive-operations audit log — to do
- Add NFC + QR encoding tests — to do
- Add AI agent tests — to do
- Add Contacts & Leads tests — to do

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

## The brief on file

Matthew's go/no-go gate for DevOps Launch Readiness. Done when: every surface (iOS, Android, Web/API) is tested, monitored, and releasable per the tasks in this wave.

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

DevOps Launch Readiness

Approve: DevOps Launch Readiness