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

Approve: Backend API

To doOwner · met_2451cca5Blocker

Waiting on 20 · 3 still openImplement /api/profile or remove route Implement /api/upload Add /health endpoint Replace link-click placeholder zero Implement destination analytics Verify documents/gallery/audio routes complete Add structured logging via pino-compatible API Add request-id middleware Add Sentry to Workers Add upload size limits and file validation Define the API versioning strategy Verify all 14 destination content read endpoints Verify the five existing destination update endpoints work Verify the four completed Backend API items in production Build update endpoint for menu destinations Build update endpoint for link_hub destinations Build update endpoint for payment destinations Build update endpoint for wifi destinations Build update endpoint for bluetooth destinations Build update endpoint for action destinations

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

**Approve: Backend API** · to do · blocker

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

## Waiting on 20

- Implement /api/profile or remove route — done
- Implement /api/upload — done
- Add /health endpoint — done
- Replace link-click placeholder zero — done
- Implement destination analytics — done
- Verify documents/gallery/audio routes complete — done
- Add structured logging via pino-compatible API — in progress
- Add request-id middleware — done
- Add Sentry to Workers — done
- Add upload size limits and file validation — done
- Define the API versioning strategy — done
- Verify all 14 destination content read endpoints — done
- Verify the five existing destination update endpoints work — in progress
- Verify the four completed Backend API items in production — in progress
- Build update endpoint for menu destinations — done
- Build update endpoint for link_hub destinations — done
- Build update endpoint for payment destinations — done
- Build update endpoint for wifi destinations — done
- Build update endpoint for bluetooth destinations — done
- Build update endpoint for action destinations — done

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

## The brief on file

DECIDED BY MATTHEW 2026-08-06: **this gate holds until the WHOLE Backend API wave is genuinely done, destination analytics included.** Closing early on "versioning + the verification sweep, analytics deferred" was offered and rejected. So did closing now on what is already merged.

CONSEQUENCE, STATED PLAINLY: Auth (w_3a300faf), Billing (w_aa343251), Email (w_2c90036d), Custom Domains (w_c325f174) and Supabase Edge Functions (w_3ea67014) stay blocked for as long as the analytics build takes — and that build is a new product surface (a table, an ingest endpoint, a browser SDK, an aggregate), not a gap-fill. That is the accepted trade, not an oversight.

WHAT MUST BE TRUE BEFORE THIS CLOSES:
1. API versioning (t_af5f700a) implemented — /api/v1/* prefix with the unversioned surface permanently aliased, plus ADR 0008 registered in docs/adr/INDEX.md.
2. The four verification tasks proven against a DEPLOYED worker, not a clean compile: t_27b2c3f2 (gallery + video PATCH remain), t_2f021e7b (real-data half), t_081dcf20 (Sentry probe leg), t_e08859cf (one oversized upload per kind expecting 413).
3. SENTRY_RELEASE fixed at the deploy path (t_08dde153) so /api/health stops advertising a April SHA.
4. Structured logging (t_50dbeb17).
5. The "link" channel made real (t_258a2a7c) — definition settled: a link open is a plain-URL open, no tag, no QR.
6. Destination analytics funnel (t_8cad053d) built.

DEFINITION OF DONE for every item above: the behaviour was OBSERVED against a deployed worker. Not that it compiles, not that it is on a branch. This wave has already had several notes corrected because an inference from a 401 was mistaken for evidence — note that PATCH is useless as a probe, since the worker demands a Bearer token BEFORE route dispatch, so PATCH against a family that does not exist also 401s. An unrouted GET returns a route-level `Not found`; a mounted route that performed a real lookup returns a NAMED miss ("Destination not found."). Use GET.

Owner: Matthew. Do not self-approve.

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

Approve: Backend API