Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Backend & Infrastructure›Backend API·33 in this wave

Approve: Backend APITo do · blocker Implement /api/profile or remove routeDone Implement /api/uploadDone Implement destination analyticsDone Add upload size limits and file validationDone Define the API versioning strategyDone Verify all 14 destination content read endpointsDone Verify the five existing destination update endpoints workIn progress Fix the stale SENTRY_RELEASE on tactile-apiDone iOS decodes payment_destinations as an array — a latent whole-list decode failureTo do Add staging.tactile.to to the API CORS allowlistDone Emit CardSchema (not bare ActionPreview) from the 12 non-QR tool preview generatorsDone pnpm verify is red on main, and CI hides 9 more failures by excluding three test filesDone EMIT LEG: send method:\"link\" from the clients, or the Link bucket stays at zeroTo do POST /api/events/open is documented public+unauth but 401s anonymouslyDone Staging has no RATE_LIMIT_DO binding — both rate limiters fail open thereDone Mask the Wi-Fi password before it reaches agent proposal cards (blocks WifiCard)Done link_hub.ts has the identical partial-drop hole contact.ts just hadDone Add /health endpointDone Replace link-click placeholder zeroDone Verify documents/gallery/audio routes completeDone Add structured logging via pino-compatible APIIn progress Add request-id middlewareDone Add Sentry to WorkersDone Verify the four completed Backend API items in productionIn progress Build update endpoint for menu destinationsDone Build update endpoint for link_hub destinationsDone Build update endpoint for payment destinationsDone Build update endpoint for wifi destinationsDone Build update endpoint for bluetooth destinationsDone Build update endpoint for action destinationsDone Build the webhook MCP module (tools/webhook.ts) — Matthew chose SHIP over cutDone Derive per-type opIds for destination.create/edit so Website + Gallery cards can renderDone

Wave

Backend API

The long pole — Auth, Billing, Email, Custom Domains and Edge Functions all wait on this gate.

TacTile › Launch TacTile › Backend & Infrastructure › Backend API

27/33 done6 open1 open blocker

Selected taskclear

Fix the stale SENTRY_RELEASE on tactile-api

DoneOwner · Vivt_08dde153

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

**Fix the stale SENTRY_RELEASE on tactile-api** · done

Where it sits: TacTile › Launch TacTile › Backend &amp; Infrastructure › Backend API

## The brief on file

BUILT 2026-08-06 on branch feature/backend-api, commit 27b2ce0a. Code complete, NOT deployed.

FIX SHAPE — the SHA goes INSIDE the deploy command, not around it:
  apps/api/tactile-api/package.json
    deploy:         wrangler deploy --var "SENTRY_RELEASE:$(git rev-parse HEAD || echo unknown)"
    deploy:staging: wrangler deploy --env staging --var "SENTRY_RELEASE:$(...)"
Computed by the same command that uploads, so no caller can forget it. Wiring it
into deploy.sh alone would have left `pnpm --filter tactile-api run deploy` as a
silent drift path.

Then scripts/deploy/deploy.sh PROVES it: the api unit sets VERSION_MUST=1 and the
smoke test asserts the live /api/health body echoes that exact 40-char SHA. That
assertion is the real guarantee — the value drifted for three months precisely
because nothing ever compared what the worker reported against what was shipped.

health.ts: `??` → `||`. A failed `git rev-parse` makes --var land as an EMPTY
STRING, which `??` passes through, serving `"version":""` — worse than "unknown"
because it reads like a value. Test covers it.

VERIFIED WITHOUT DEPLOYING: `wrangler deploy --env staging --dry-run` on the
pinned wrangler lists `env.SENTRY_RELEASE ("(hidden)")` as a binding — the flag
parses, the bundle builds, and wrangler will not echo the value into deploy logs.
bash -n clean, tsc clean, 4 new tests pass.

⚠️ ONE MANUAL STEP BEFORE THE FIRST PROD DEPLOY. A stale wrangler SECRET named
SENTRY_RELEASE exists on the prod worker and will SHADOW the var:
  cd apps/api/tactile-api && pnpm wrangler secret delete SENTRY_RELEASE
Staging never had it (docs/runbooks/setup-staging.md notes staging reports
"unknown"), so staging exercises the clean path and is the safe first test. The
new smoke assertion catches this if it is forgotten — the deploy fails loudly
rather than silently keeping the April SHA.

DELIBERATELY NOT IN SCOPE
- deploy:sentry / deploy:sentry:staging are unreachable from deploy.sh (line 114
  can only select deploy/deploy:staging) and their `./dist` target has never
  existed — there is no build script. Sourcemaps are a separate broken thing.
  Sentry keys regression detection off the event's release tag, which is what
  this fixes; sourcemaps only affect stack-trace readability.
- Surfacing Cloudflare's own version_metadata id alongside `version` would make
  /api/health self-diagnosing (Cloudflare knows it independently of anything we
  set). Left out because it cannot be validated without a real deploy.
- apps/web has the identical defect at apps/web/app/api/health/route.ts:10 —
  reads process.env.SENTRY_RELEASE ?? process.env.VERCEL_GIT_COMMIT_SHA, and
  VERCEL_GIT_COMMIT_SHA does not exist outside Vercel. Belongs to the web session.

REMAINING: staging deploy, confirm /api/health reports the deployed SHA, then
prod (needs the secret delete + Matthew's approval). Backfill is impossible —
note in Sentry that releases before this are unreliable.

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

Backend API

Fix the stale SENTRY_RELEASE on tactile-api