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

Verify the four completed Backend API items in production

In progressOwner · Vivt_081dcf20

Unlocks 1Approve: Backend API

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

**Verify the four completed Backend API items in production** · in progress

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

## Unlocks 1

- Approve: Backend API

## The brief on file

Viv — confirm the Backend API items marked done are genuinely working in the deployed environment, not just present in code.

⚠️ CORRECTION TO MY OWN NOTE FROM EARLIER TODAY. I previously wrote here that the six destination update endpoints are "deployed, contrary to what their task notes say", on the grounds that PATCH /api/{menu,link-hub,...}/:hash returns 401 in prod. **That inference was wrong and is withdrawn.** The worker requires a Bearer token BEFORE route dispatch on mutating methods: `PATCH /api/notarealtype/ZZZZZZZZZ` — a family that does not exist at all — also returns 401 {"error":"Missing Bearer token."}. So a 401 on PATCH proves nothing about whether a route exists. GET is different (an unrouted GET returns plain-text 404), which is why the GET-based content-endpoint verification in t_2f021e7b still stands.

VERIFIED LIVE 2026-08-03 against https://whitelabel.tactile.to:
  ✅ /health — lives at **/api/health**, not /health (bare /health 404s). Returns 200
     with {"ok":true,"version":…,"uptime_seconds":…}. Working; the task's path was
     written down wrong.
  ✅ request-id middleware — `x-request-id` is stamped on responses including 404s, so
     it is genuinely middleware-level rather than per-route.
  ⬜ Sentry capture — still NOT verified end to end. There IS a purpose-built probe:
     `/api/__test/sentry` (src/index.ts:93) gated by the SENTRY_TEST_TOKEN secret.
     Blocked only because 1Password is returning "authorization timeout" and the token
     cannot be read. Two minutes once that is unlocked.
  ⬜ documents/gallery/audio route completeness — the /content routes are confirmed
     mounted and reaching a real lookup (see t_2f021e7b), but returning usable data for
     a real saved destination is unproven. Same blocker.

DEPLOY FRESHNESS — settled, after a false alarm I want recorded so nobody repeats it.
`/api/health` reports `version: "0990e389…"`, which is a real commit in this repo dated
2026-04-30, 1,425 commits behind main. That looks damning and it is NOT what it seems:
utils/health.ts:61 reads `env.SENTRY_RELEASE ?? "unknown"`, so the field is a
deploy-time SECRET, not the running code's SHA. The actual deploy history from
`wrangler deployments list` shows the worker was uploaded **2026-08-03T16:10:28Z**,
minutes before main's current tip. Production is current, not three months stale.

NEW BUG FOUND WHILE ESTABLISHING THAT — the SENTRY_RELEASE secret is stale, and it
matters. See the separate task; short version: every prod API error has been tagged
with release 0990e389 (2026-04-30) since April, so Sentry's release tracking,
regression detection and "first seen in" are all wrong, and /api/health advertises a
version number that is not the deployed code.

STILL OPEN, and both need the same unblock (1Password): the Sentry probe and the
real-data half of the content endpoints.

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

Verify the four completed Backend API items in production