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 2sTo do · 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 devicesTo do

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

7/11 done4 open3 open blockers

Selected taskclear

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

To doOwner · 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** · to do · blocker

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

## The brief on file

Matthew — this is a billing action, so it is yours. It blocks nothing from being WRITTEN but blocks everything from being merged with confidence.

STATE, verified 2026-08-05 against PR #225: every workflow job fails in about 2 seconds having executed ZERO steps. The check-run annotation reads:

  "The job was not started because recent account payments have failed or your spending limit needs to be increased. Please check the 'Billing & plans' section in your settings"

Confirmed via: gh api repos/TacTile-dev/TacTile/check-runs/<id>/annotations

This is not specific to one branch. verify, playwright, semgrep, static-firewall and swift-parity all fail identically, which means NO CI HAS RUN ON ANYTHING for as long as this has been true — including anything merged to main in that window. Every green-looking merge in that period was green because nothing ran, not because it passed.

WHAT TO DO: GitHub → Settings → Billing & plans for the TacTile-dev org. Either a failed payment method needs replacing or the Actions spending limit needs raising. Then re-run the failed workflows on any open PR to confirm.

WHY IT MATTERS BEYOND THE RED MARKS: .github/workflows/verify.yml deliberately enumerates all 18 verify checks as separate steps so one red gate cannot hide later failures — that design is worth nothing while the runner never starts. And per the root AGENTS.md, apps/tactile-hub AUTO-DEPLOYS on any push to main touching its path, applying D1 migrations before wrangler deploy. That workflow is presumably also dead right now, so hub changes merged during this window may not actually be deployed. Worth checking the hub's live state against main once billing is restored.

INTERIM: local gates are the only real signal. For Android that is, from apps/android with JAVA_HOME pointed at Android Studio's JBR:
  ./gradlew :app:assembleDebug :app:testDebugUnitTest :app:lintDebug
For the repo, `pnpm verify` — but note it 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 until that is fixed.

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