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 workBlocked Fix the stale SENTRY_RELEASE on tactile-apiDone iOS decodes payment_destinations as an array — a latent whole-list decode failureDone 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 APITo do Add request-id middlewareDone Add Sentry to WorkersDone Verify the four completed Backend API items in productionDone 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

29/33 done4 open1 open blocker

Selected taskclear

EMIT LEG: send method:\"link\" from the clients, or the Link bucket stays at zero

To doOwner · met_28110653

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

**EMIT LEG: send method:\"link\" from the clients, or the Link bucket stays at zero** · to do

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

## The brief on file

NEEDS MATTHEW — the display half is DONE; the emit leg is blocked on three unapplied migrations and nothing else.

RECEIVE SIDE COMPLETE 2026-09-21 (Viv). Branch feature/link-channel-clients, commit a8c8fd60. Not merged, not pushed. Every client can now receive and label a `link` bucket, so the day the migrations land nothing drops data or changes shape unannounced.

=== THE STOP-NOTE: WHAT IS NEEDED AND FROM WHOM ===
Apply supabase/migrations/202608060900, 0901 and 0902, which add `link` to the analytics method enum. `ALTER TYPE ... ADD VALUE` is irreversible and the database has pitr_enabled:false with zero stored backups, so this has always been Matthew's. Until it is applied, the Link bucket reads zero no matter what any client sends, and sending the value from a client would have nowhere to land. That is why the emit half was deliberately NOT built today.
AFTER IT IS APPLIED: decide the web discriminator (item 1 of the original brief — an HTTP Referer is the obvious signal but a bare pasted URL has none, so referer-only undercounts), then verify with `GET /api/analytics/scans/channel-mix` and confirm the Link bucket is non-zero and the four percentages sum to 100.

=== ONE ITEM OF THIS BRIEF WAS NOT A FUTURE PROBLEM. IT WAS ALREADY BROKEN. ===
Item 3b warned that DDTriggerMixWidget "starts drawing a third arc the moment link carries a real count — silently, on a deploy, with no iOS commit." That understates it. routes/analytics/scans.ts:277-281 ALREADY emits four buckets in the order [nfc, qr, link, direct], and the widget did `buckets.prefix(3).enumerated()` — so it was already selecting link as its third channel and had NEVER rendered `direct` at all. It only looked right because link is a placeholder zero and the `pct == 0` guard skipped it.
FIXED: mapChannelSegments now selects BY KEY on ["nfc","qr"]. This widget is the trigger-method split; direct and link are non-trigger opens and are now excluded by name rather than by array position. Today's rendering is byte-identical — which is the point. Removed the consequently-unreachable brand100 colour and the `hairlineDot: (i == 2)` branch, and corrected a struct doc that described a three-bucket layout the code never drew. Pinned by a new DDTriggerMixWidgetTests.swift: four buckets in wire order yield exactly NFC and QR, the same holds when bucket ORDER changes, key matching is case-insensitive, and the zero-pct skip still works.

=== TWO CORRECTIONS TO THIS BRIEF ===
1. Item 2 pointed at a three-value whitelist in apps/web-mobile/features/analytics/hooks/useLiveFeed.ts:182-184. STALE — that file is 88 lines and has no method/nfc/qr handling at all. The real MethodBadge whitelist lives in RealtimeFeed.tsx and is fixed. (Separately: apps/web's own useLiveFeed.ts has ZERO importers and is a confirmed orphan tracked in the web dead-code wave — do not "fix" it.)
2. Item 3a's line numbers were right; item 2's and CampaignWidgets' were not. CampaignWidgets.swift already handles `link` — at :448-451 and :587-590, not :398 as written.

=== WHAT LANDED, PER SURFACE ===
· iOS — `link` added to ScanSummaryTotals.Methods and TimelineResponse.MethodSeries; LiveActivityFeedCard gave link AND direct real labelled pills instead of the generic unlabeled dot (direct had been lumped in too).
· Android — Methods.link with a default so old payloads still decode, plus a decode assertion in the existing test.
· web / web-mobile — RealtimeFeed's MethodBadge, TimelineChart and OverviewPage all label Link distinctly from Direct.

=== A LESSON THAT COST TWO PASSES, worth keeping ===
Adding a field to a Swift struct is a BREAKING CHANGE. `link` broke five existing memberwise-init call sites in `#if DEBUG` sample data. No static scan sees that; the first agent's xcodebuild failed only because the worktree lacked the gitignored SupabaseConfig.plist and it read that as pre-existing noise, and the reviewer then declined to re-run the build because both edited files "type-check cleanly". Only a compiler answers this.
And the tempting one-line fix is a trap: defaulting the field fixes all five sites at once, but in Swift a `let` with an initial value is EXCLUDED from synthesized decoding, so `link` would have decoded as permanently zero — exactly the bug this task exists to prevent, passing every check including the build. The five call sites were fixed explicitly instead.

VERIFIED: xcodebuild Debug BUILD SUCCEEDED, zero errors · ios-wire-key-strategy, swift-source-coverage, swift-test-coverage all exit 0 · verify:web-check exit 0 · verify:web-mobile-unit 121/121.

[2026-09-27 restart audit] Blocker stale: the 3 migrations are live in prod (open_method enum includes 'link'; analytics_rollups_daily.link_scans exists; verified read-only 2026-09-27). Remaining work is client-side: no client sends method:link yet.

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

EMIT LEG: send method:\"link\" from the clients, or the Link bucket stays at zero