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

Viv — Wire up QR design editing from the Launchpad (prefill existing design into the editor).

DoneOwner · Vivt_8ebf0742

Done when: 'Edit design' on QR Launchpad opens the QR editor pre-filled with the saved design (?edit prefill via qr.get(hash) → editor state) instead of static 'coming to web' text. File: apps/web-mobile/features/qr/pages/QRLaunchpadPage.tsx:224-232 (TODO: wire ?edit prefill).

Unlocks 2Approve: Surface build Caitlin — Verify QR create, scan, and Launchpad view/manage flows end-to-end.

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

**Viv — Wire up QR design editing from the Launchpad (prefill existing design into the editor).** · done

Done when: 'Edit design' on QR Launchpad opens the QR editor pre-filled with the saved design (?edit prefill via qr.get(hash) → editor state) instead of static 'coming to web' text. File: apps/web-mobile/features/qr/pages/QRLaunchpadPage.tsx:224-232 (TODO: wire ?edit prefill).

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

## Unlocks 2

- Approve: Surface build
- Caitlin — Verify QR create, scan, and Launchpad view/manage flows end-to-end.

## The brief on file

DONE — PR #253, merged to main as 5770b8e3.

web-mobile can edit a saved QR's design. Route app/create/qr/[hash]/edit, loader features/qr/pages/QREditDesignPage.tsx, bridge features/qr/lib/record-design.ts, and the launchpad's "Edit design" row is now a link instead of a "not available on web yet" note.

MUCH SMALLER THAN THE TODO IMPLIED. QREditorPage already knew how to mount a full-fidelity carried design (the PendingDesign path used for cross-device hand-off) — it just had no way to be handed a SAVED one. useQREditor already accepted an initial state. So edit mode is: map the row to the same {snapshot, center, editorInitial} shape, pass an edit context, and switch save from qr.create to qr.update.

THE PRECEDENCE IN record-design.ts IS THE LOAD-BEARING PART. A row carries both a full `design` snapshot and flat module/eye/colour columns. The blob wins, because it is the only record of gradients, per-eye colour, stickers and the randomised palette. Reading the columns first would FLATTEN a studio-built design the moment someone opened it on a phone, and the next save would persist the flattening. Mirrors apps/web/features/qr/lib/snapshot.ts deliberately (apps/A→apps/B is a HARD depcruise rule).

EDITING IS DESIGN-ONLY, ON PURPOSE. `payload` is carried through untouched and UpdateQRInput leaves it optional, so an edit restyles without re-encoding — a saved dynamic code's payload is the trigger link already printed on something. Program-mode and destination controls are hidden in edit mode for the same reason; switching dynamic↔static regenerates the code, which is the separate flow the locked decision names. No new trigger hash is minted when editing.

Shapes are guarded against the RENDERER's canonical whitelist, not the picker's list: a stored value the picker has no button for keeps its real value in the snapshot and simply shows unhighlighted. Guarding on the picker's list would discard the customer's shape on save.

tests/unit/qr-record-design.test.ts pins the precedence (blob beats columns, rich fields survive, payload comes from the ROW not the stale blob), the fallbacks, and that an unknown shape is left unset rather than substituted.

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

Viv — Wire up QR design editing from the Launchpad (prefill existing design into the editor).