Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›NFC/QR Core Pipeline·36 in this wave

Approve: NFC/QR Core PipelineTo do · blocker Real scans are never recorded: nothing calls POST /api/events/openBlocked · blocker Verify end-to-end scan path for all 14 destination typesTo do Build the unassigned/orphaned tag landing pageDone Suppress analytics event writes for free-tier accountsDone Unify the four conflicting hash validation patternsDone Assess hash entropy against enumeration and PII scrapingDone Decide and implement Free-tier destination revitalizationDone Rate-limit and cache the public scan resolverTo do Triage the "couldn't connect to the server" preview clusterDone Android NdefUriDecoder accepts any host: anchor it to tactile.to / *.tactile.to or decide custom-domain tagsDone Public scan landing page polishTo do Replace the duplicate web hash-shape copies with one shared import once #658 or #681 landsTo do Android NdefMessageBuilder.build always writes the Text record; spec omits it when the hash is blankDone iOS Program NFC Tag read path rejects 7 and 8 character hashes; spec says accept 7-9Done ndef-format.md is stale: deleted symbols, wrong line cites, duplicate messageIsEmpty, no URI decode tableTo do CI gives no per-suite proof for the NDEF suites: iOS prints totals only, Android's newest main run was a Gradle cache hitTo do Fix tap_count hardcoded to 0 in NFC metadata endpointDone Add hash exhaustion alertingDone Run end-to-end NFC hardware soak testTo do Document NDEF record formatDone Confirm whitelabel.tactile.to DNS + routingDone Add hash-format validation on /t/[hash] scan landingDone Load-test QR/NFC scan resolution at scale (1M+ events)To do Decide: is missing camera QR scanning in iOS/Android intentional?To do Reconcile the three divergent hash generatorsDone Close the check-then-insert race on hash claimingDone Enforce chip compatibility in code, not just docsTo do Handle partially-written and orphaned physical tagsTo do Sign off: NDEF spec and the 111 encoding unit testsDone Free-tier inactivity: R2 media purge job (follow-up to t_9008dc76)To do API: make the visibility gate's fail-closed 404 carry a machine-readable reason, so /d /n /v /a and /t can say "unavailable" for a Supabase failureTo do API: validate the hash shape in the four /content handlers (documents, notes, videos, audio) like destinationsPublic.ts doesTo do Android NfcWriter has no post-write read-back verify (spec 4a step 5)Done NDEF parity corpus: iOS asserts 1 of 5 vectors and no https://www. vector exists; generator and Kotlin disagree on wwwTo do ndef-format.md section 5 contradicts itself on empty + read-only; NFCTagClassifier.classify and diagnose order them oppositelyTo do

Wave

NFC/QR Core Pipeline

The core of the product — encoding tags and resolving scans. Everything else is a surface on top of this.

TacTile › Launch TacTile › NFC/QR Core Pipeline

18/36 done18 open2 open blockers

Selected taskclear

Fix tap_count hardcoded to 0 in NFC metadata endpoint

DoneOwner · Vivt_bb962577

Unlocks 2Approve: NFC/QR Core Pipeline Verify end-to-end scan path for all 14 destination types

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 tap_count hardcoded to 0 in NFC metadata endpoint** · done

Where it sits: TacTile › Launch TacTile › NFC/QR Core Pipeline

## Unlocks 2

- Approve: NFC/QR Core Pipeline
- Verify end-to-end scan path for all 14 destination types

## The brief on file

Viv — fix tap_count hardcoded to 0 in the NFC metadata endpoint. Done when: GET /api/nfc/:hash returns a real tap count computed from actual scan/tap events, not the literal 0. File: apps/api/tactile-api/src/routes/nfc.ts:204.

[overnight 29→30 Sep] DONE — already on origin/main (1d960865); the hub was lagging the code.
EVIDENCE: apps/api/tactile-api/src/routes/nfc.ts:234-262 computes tap_count through fetchScanCounts (utils/scanCounts.ts:34, counts analytics_events by trigger_id). It returns null when the lookup fails and a genuine 0 only when the lookup succeeded with no rows. Landed in b4938b5f (#444). Pinned by apps/api/tactile-api/tests/routes/nfc.test.ts: (d) real count 41, (d2) never-tapped = 0, (e) failed lookup = null and nothing else changes, (h) legacy 7-char tag still resolves with its count. `pnpm verify:api-test` on origin/main: 950 pass / 0 fail.
CAVEAT (what Matthew will actually SEE): the number is only as good as analytics_events. (1) free accounts record nothing by design (t_f8ec9c72); (2) server-side scan recording is not shipped until PR #653; (3) prod's live log_analytics_event body (md5 3532aceb…, read-only pg_proc SELECT 2026-09-29) still names campaign_triggers, so a trigger scan raises 42P01 and stores nothing until the DRAFT migration 202609261245_log_analytics_event_families_lookup.sql is applied (Matthew applies by hand). Counts will read 0 in prod until those land — that is the pipeline, not this endpoint.

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

NFC/QR Core Pipeline

Fix tap_count hardcoded to 0 in NFC metadata endpoint