Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›web-mobile — Surface build·27 in this wave

Approve: Surface buildTo do · blocker Viv — Fix Dashboard 'Create → Destination' tile to link to the destination picker instead of the QR page.Done Viv — Build the missing destination picker on QR Launchpad so users can connect a destination to an existing QR code from web.Done Viv — Add app-wide error.tsx and not-found.tsx boundaries to web-mobile.Done SPEC → backend: three dead QR shape values, a sticker key Android and web disagree on, and a grader blind to bothDone QR studio: four remaining silent-substitution hazards before decoratives/stickers shipDone SPEC → backend: collapse the duelling QR enums and make every offered shape render — Matthew decided parity, not documentationDone BLOCKED: logo interactive crop cannot be built on web — all five logo snapshot fields are inert in the TS rendererDone Viv — Fix the 'forms' vs 'form' naming mismatch between web-mobile's disabled-category type and the backend destination type.To do Viv — Add 'action' and 'form' to the shared DestinationType union in the SDK.To do Viv — Wire up QR design editing from the Launchpad (prefill existing design into the editor).Done Viv — Add QR code deletion once a DELETE endpoint/SDK method exists.To do Viv — Wire the AI Insights tab to the real analytics insights endpoint once the SDK exposes it.To do Viv — Remove the unreachable 'Group-level analytics are in development' stub banner from Deep Dive, or wire it up if group-scope analytics ships.To do me — Decide whether to complete the orphaned device-trust / verify-device feature on web-mobile or delete the dead scaffolding.To do Viv — Point 'Help Center' to a real docs/FAQ URL instead of duplicating the 'Contact Support' mailto link.To do Add loading.tsx route skeletons to web-mobileTo do Viv — Either finish the Menu destination builder or mark it disabled/coming-soon in the category picker.Done Viv — Add video, audio, and action to the destination CategoryPicker with an honest disabled/coming-soon state, instead of leaving them silently absent.Done Viv — Add a timeout/failure path to the cross-domain auth handoff when setSession() hangs.To do Caitlin — Verify auth + cross-domain handoff end-to-end: sign in, sign up, forgot/reset password, and the tactile.to → app.tactile-connect.com handoff flow.To do Caitlin — Verify the 6 working destination builders (website, notes, gallery, document, link_hub, contact-via-card) end-to-end.To do Caitlin — Verify QR create, scan, and Launchpad view/manage flows end-to-end.To do Caitlin — Verify ConnectCard editor (create and edit) end-to-end.To do Caitlin — Verify all 6 Settings pages (profile, security, subscription, notifications, appearance, plus the settings hub) end-to-end.To do Caitlin — Verify Analytics tabs (all 7) render real data with correct empty/error states, confirming no fabricated data anywhere.To do Caitlin — Verify Assets browser (Triggers / Destinations / QR / Groups / Families tabs) end-to-end.To do

Wave

web-mobile — Surface build

TacTile › Launch TacTile › Web › web-mobile — Surface build

10/27 done17 open1 open blocker

Selected taskclear

SPEC → backend: collapse the duelling QR enums and make every offered shape render — Matthew decided parity, not documentation

DoneOwner · ait_d5b7c2f2

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

**SPEC → backend: collapse the duelling QR enums and make every offered shape render — Matthew decided parity, not documentation** · done

Where it sits: TacTile › Launch TacTile › Web › web-mobile — Surface build

## The brief on file

DONE — PR #499 (merge 0920f40a), launch round 10. Verified on main after the squash:
each pair is now the SAME BINDING, not two lists that happen to agree —
  enums.ts:330  export const MODULE_SHAPES     = QR_MODULE_SHAPES
  enums.ts:346  export const EYE_SHAPES        = QR_EYE_FRAME_SHAPES
  enums.ts:374  export const EYE_INNER_SHAPES  = QR_EYE_SHAPES
Identity is asserted with toBe rather than deep equality, so they cannot drift back into
two lists that merely look alike.

THE DEFECT WAS WORSE THAN THE DOC RECORDED. The eye frame had FOUR render outcomes, not
five: renderer/eye-shapes.ts:784-787 gave `cross` its own arm emitting
rectShape(origin,7,fill,0) + rectShape(+1,5,background,0) — byte-identical to `square`,
whose radii are both 0 — and on the transparent-gap path it had no arm at all. No public
value could even reach it. apps/web-mobile had already hardcoded the real four locally.

BLAST RADIUS WAS THREE LAYERS WIDER THAN THE DOC LISTED, and this is the part that
mattered: agent-core/systemPrompt.ts:47 fed the enums to the CUSTOMER-FACING model, so the
agent advertised `squircle`; the normalizer emitted `diamond` verbatim; and the agent's
tweak card built its picker from the lexicon — so it offered `squircle` straight to the
customer.

THE MEASUREMENT THAT PREVENTED A SILENT DATA CHANGE: `cross` as a STORED frame renders
ROUNDED, not square — resolveEyeShape has no case for it and takes its default, so the
renderer's cross arm is unreachable. The obvious fix (cross → square) was truer to the
renderer and would have SILENTLY RESTYLED STORED DESIGNS. The alias tables are asserted
against the resolver, which is what caught it.

Dead values became aliases normalising to the outcome they already produce. Deletion was
rejected in the decision doc, and making them render distinctly has the same
appearance-change defect plus it breaks Swift pixel parity — the opposite of the parity
this task asked for. design-plugin-ui's hand-filters became provably dead code and
TypeScript said so. Five goldens moved, all in the right direction. Twelve files.

STILL OPEN, tracked separately — do NOT treat these as covered by this task:
  · t_64f78631 (blocked) — three dead QR shape values plus a sticker key Android sends
    that nothing accepts. Same decision doc.
  · The iOS and Android halves — offering exactly the surviving set, and Android's kebab
    read-shim — belong to those lanes and were not verified here.
  · A possible FOURTH vocabulary: the session reported "@tactile/qr-web" carrying a
    `fracture` module value that tests/unit/qr-studio-shape-coverage.test.ts:82 explicitly
    guards against leaking (`expect(QR_MODULE_SHAPES).not.toContain("fracture")`). NOTE
    there is no packages/qr-web on this tree — only qr-studio and qr-renderer — so
    RESOLVE WHICH PACKAGE IS MEANT before acting on that claim.

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

web-mobile — Surface build

SPEC → backend: collapse the duelling QR enums and make every offered shape render — Matthew decided parity, not documentation