Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Android›Android — Pre-submission blockers·11 in this wave

Approve: Android pre-submission blockersTo do · blocker Provision apps/android/local.properties so the Android app can reach a backendTo do · blocker GitHub Actions is off for the whole repo — billing wall fails every job in 2sDone · blocker Add launcher icon setDone Bump compileSdk and targetSdk to Play's current floorDone Produce and validate a real signed release AABDone Confirm Supabase session tokens are encrypted at restDone verify:one-contact-address is red on main — design/card-creation-flow.html publishes kaitlynn@tactile.to 14 timesDone Automate versionCode and versionNameDone Un-pin security-crypto from alphaDone Replace deprecated security-crypto with Android Keystore + migrate enrolled devicesBlocked

Wave

Android — Pre-submission blockers

Short, hard list that blocks any Play Store submission. Do these first — they are cheap and absolute.

TacTile › Launch TacTile › Android › Android — Pre-submission blockers

8/11 done3 open2 open blockers

Selected taskclear

GitHub Actions is off for the whole repo — billing wall fails every job in 2s

DoneOwner · met_43e311d2Blocker

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

**GitHub Actions is off for the whole repo — billing wall fails every job in 2s** · done · blocker

Where it sits: TacTile › Launch TacTile › Android › Android — Pre-submission blockers

## The brief on file

CLOSED 2026-09-21 (Viv) AS STALE — this condition ended on 2026-08-15 and the row has been sitting in Matthew's queue as a live blocker ever since, telling him to go fix a billing problem that no longer exists.

WHAT THIS SAID: every GitHub Actions job fails in ~2 seconds having executed ZERO steps, with the check-run annotation "The job was not started because recent account payments have failed or your spending limit needs to be increased." It asked Matthew to fix Billing & plans for the org.

WHY IT IS NO LONGER TRUE: the fleet moved to SELF-HOSTED runners on Matthew's Mac on 2026-08-15 (tactile-m1max, tactile-m1max-2, launchd LaunchAgents with RunAtLoad+KeepAlive). Self-hosted consumes zero Actions minutes on any plan, so the wall is structurally unable to recur — it is bypassed, not paid down. Jobs execute for real with real durations: iOS build & test 17.4 min, verify 10.3 min, playwright 8.2 min, measured 2026-08-16. Hosted runners remain walled, which is precisely why the self-hosted ones exist. Recorded on t_412e17f7, which is closed.

TWO THINGS THIS ROW SAID THAT ARE ALSO NOW WRONG, corrected so nobody inherits them:
  · "pnpm verify cannot complete on this machine either (segfaults on exit under Node 24; the repo pins node >=20 <21 and no Node 20 is installed). Run the 18 checks individually." — the full chain completes here today. Measured on three separate branches: 50 of 51 green on each. The chain is 51 checks now, not 18. Node segfaults DO still occur on bare `node scripts/verify/*.mjs` invocations, which is why the repo wraps them in scripts/verify/retry-on-segv.sh — use the pnpm scripts, not bare node.
  · ".github/workflows/verify.yml deliberately enumerates all 18 verify checks ... that design is worth nothing while the runner never starts" — the design is now load-bearing again, and entry 25 (verify:ci-step-coverage) enforces both directions of the parity.

WHAT REPLACED IT AS THE REAL CONSTRAINT, and it is a different problem with a different fix: RUNNER CAPACITY, tracked as t_361002e9. Two runners on one Mac, and queue WAIT now exceeds compute — verify waits 28.6 min, playwright 33.7 min, and static-firewall waits 19.6 minutes to do 12 SECONDS of work. Host saturation also produces FALSE REDS: of the 25 most recent verify.yml runs, 15 never reached a single verify:* step. Entry 51 (verify:contention-stamps) now makes every self-hosted job label its own failure regime, so read that stamp before believing a red.

STILL TRUE AND UNRELATED: branch protection needs a paid plan (t_ba67f30b), so scripts/verify/gate.sh via .githooks/pre-push remains the only real merge gate.

The one item from this row's own "what to do" list that survives is the hub check it suggested: apps/tactile-hub auto-deploys on any push to main touching its path. Its push trigger was removed on 2026-08-15 and RESTORED the same day after the workflow's restore checklist was followed, with the first-ever D1 migration apply run by hand first (run 31911424523) and idempotence measured on a re-run (31912173144). So that is settled too.

## 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 — Pre-submission blockers

GitHub Actions is off for the whole repo — billing wall fails every job in 2s