Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›DevOps›DevOps Foundation·35 in this wave

Approve: DevOps FoundationTo do · blocker NEEDS MATTHEW: staging STRIPE_WEBHOOK_SIGNING_SECRETBlocked · blocker main is RED — 8 unit tests failing on origin/main, so pnpm verify cannot gate any PRDone · blocker The production account's data is 42 days stale — Analytics renders empty at any default windowBlocked · blocker MATTHEW: add db_url to the 1Password Supabase item — two RLS audits have never been runnableDone · blocker Wire apps/api test suite into CIDone Wire Playwright specs into CIDone Wire verify:swift-parity into CIDone Enable branch protection on mainBlocked Verify the staging environment is actually liveDone Web deploy workflow (manual trigger only)To do API deploy workflow (manual trigger only)To do Add post-deploy smoke test to the deploy workflowsTo do Write the rollback procedureTo do Add Sentry to iOSTo do Add Sentry to AndroidTo do Configure uptime monitoringTo do Set the three missing staging secrets on tactile-api-stagingDone Playwright is failing on main and producing no report — every run that gets a runner failsTo do Playwright job must free port 3000 BEFORE its first suite — a watchdog-killed job leaks its server and fails every later runDone Add CHANGELOG.mdTo do Automate release tagging on mainTo do Fix stale Vercel references in the observability runbookDone Add apps/api typecheck to CIDone Clean the SAST baselineTo do Flip SAST to blockingTo do Edge function deploy workflow (manual trigger only)To do Supabase migration check in CITo do Write the release procedureTo do Configure Supabase log drainTo do Centralize Cloudflare Workers logsTo do Replace console.* with structured logging in apps/apiTo do Two runners share one ~/.gradle — scope it per runner without losing the warm cacheTo do MATTHEW: CI capacity — one Mac, two runners, and a full Xcode build now runs on every pushTo do Auto-cancel queued CI runs whose head branch was deletedTo do

Wave

DevOps Foundation

Unblocked now — nothing waits on the surfaces. Wiring existing tests into CI, deploy automation, base observability.

TacTile › Launch TacTile › DevOps › DevOps Foundation

10/35 done25 open3 open blockers

Selected taskclear

Enable branch protection on main

BlockedOwner · met_ba67f30b

Waiting on 5 · 1 still openWire apps/api test suite into CI Wire Playwright specs into CI Wire verify:swift-parity into CI Add apps/api typecheck to CI Flip SAST to blocking

Unlocks 1Approve: DevOps Foundation

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

**Enable branch protection on main** · blocked

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

## Waiting on 5

- Wire apps/api test suite into CI — done
- Wire Playwright specs into CI — done
- Wire verify:swift-parity into CI — done
- Add apps/api typecheck to CI — done
- Flip SAST to blocking — to do

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

## Unlocks 1

- Approve: DevOps Foundation

## The brief on file

BLOCKED ON t_412e17f7 — do not action this until the GitHub Actions billing wall is cleared. Flagged 2026-08-02 by Viv.

WHY. Branch protection works by requiring named status checks to report success. Since ~04:40 UTC on 2026-08-02 no job on this repo starts at all — every one is annotated "The job was not started because recent account payments have failed or your spending limit needs to be increased." Turning on required checks now would make every PR permanently unmergeable, including the PR that fixes it. Wait for t_412e17f7.

ORIGINAL BRIEF (still accurate, and its prerequisite is now met):
me — in GitHub repo settings, enable branch protection on main requiring verify.yml and sast to pass, blocking direct pushes and force-pushes. Done when: main requires verify.yml + sast as required status checks, no direct pushes, no force-push allowed. Must be done after the CI checks (apps/api tests, Playwright, swift-parity, apps/api typecheck, SAST blocking) exist so there are required checks to select in the GitHub UI.

PREREQUISITE STATUS: met. t_8e519d94 (Playwright into CI) closed 2026-08-02 — the `playwright` job is blocking and was green on 12 real runs. When you open the branch-protection UI, the check names to select are: `verify`, `playwright`, `swift-parity` (all three are separate jobs in verify.yml, so they appear as three separate required checks, not one), plus `SAST (Semgrep)`.

CAUTION ON `verify`: that job is currently RED on main for reasons unrelated to Playwright. Making it required will block all merges until it is fixed. Either fix it first or add it as a required check in a second pass after `playwright` and `swift-parity`.

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

Enable branch protection on main