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

Fix stale Vercel references in the observability runbook

DoneOwner · Vivt_9a2f291e

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

**Fix stale Vercel references in the observability runbook** · done

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

## Unlocks 1

- Approve: DevOps Foundation

## The brief on file

Viv — fix docs/runbooks/observability.md, which still references Vercel for web deploys. Done when: the doc describes the real Cloudflare/OpenNext deploy path instead of Vercel.

--- DONE 2026-07-27 (Viv) · commit a8ab87e8 ---
Every Vercel command in the runbook would have failed if someone ran it, and the runbook is what you reach for mid-incident. Three fixes, each checked against real config rather than assumed:

1. Triage step 2 said "Cloudflare wrangler tail or Vercel logs". Both surfaces are Cloudflare Workers, so it now names them: `wrangler tail --name tactile-web` and `--name tactile-api` (confirmed at apps/web/wrangler.jsonc:3 and apps/api/tactile-api/wrangler.toml:1).

2. The kill-switch block ran `vercel env add SENTRY_KILL_SWITCH production` + `vercel deploy --prod`. Replaced with `wrangler secret put` + `pnpm --filter @tactile/web deploy` (the repo's real script: opennextjs-cloudflare build && wrangler deploy), plus the staging variant — staging is a SEPARATE worker named `tactile-staging`, which the old doc didn't mention at all.

3. WORST OF THE THREE: the source-maps section told CI to export SENTRY_RELEASE=$VERCEL_GIT_COMMIT_SHA. That variable only exists on Vercel, so on Cloudflare it expands to empty and web releases go to Sentry UNTAGGED — meaning stack traces can't be tied to a deploy. Replaced with `git rev-parse HEAD` (and ${{ github.sha }} for Actions). Noted that apps/api's deploy:sentry already does this correctly, so the API side was fine.

One Vercel mention remains deliberately — a line stating the variable does not exist here, so nobody re-adds it.

RELATED, NOT FIXED (out of scope, worth a task): seven other docs still mention Vercel — docs/DEV_ENVIRONMENT.md, docs/SANDBOX.md, docs/STAGING_SETUP.md, docs/secrets/runbook.md, docs/analytics/FRONTEND_ARCHITECTURE.md, and two proposals. DEV_ENVIRONMENT.md and SANDBOX.md matter most: both describe Vercel Preview/Production env scoping for the NEXT_PUBLIC_ENABLE_SANDBOX gate. The gate itself works regardless (it keys off NODE_ENV, verified in t_ff96f955), but the guidance names the wrong platform.

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

Fix stale Vercel references in the observability runbook