Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›Web — QR management·15 in this wave

Approve: QR managementTo do · blocker BUG: dynamic-QR detection hardcodes tactile.to, so white-label codes render the wrong symbolDone SPEC → backend: move QR render glue into the package, and make program_mode first-classTo do Build the desktop QR creation/design studioTo do Wire desktop 'Edit Design' to the new QR studioDone Make the desktop QR static/dynamic toggle functionalBlocked Bring QR module/eye shape pickers to the full native set on both web surfacesTo do Add gradient design controls to QR codes on both web surfacesDone Add per-eye frame and inner color controls to QR codes on both web surfacesDone Add interactive logo crop to QR logo embedding on both web surfacesDone Add the decorative shape library to QR codes on both web surfacesTo do Add stickers to QR codes on both web surfacesTo do Add QR readability/scannability grading to both web surfacesDone Add pixel randomizer, background image, and lighting effect to QR codes on both web surfacesTo do Sign off: QR management parityTo do

Wave

Web — QR management

New wave, created 2026-07-26 following Matthew's full-parity decision: 'on web, manage all the destinations and QR codes... do everything except physically encode the NFC.' Today apps/web (desktop) has ZERO QR design capability — TriggerLaunchpadPage.tsx explicitly stubs 'Edit Design' with 'QR Studio lives in the mobile apps for now' (line 278) and its Dynamic/Static toggle is decorative, not functional (lines 303-317). apps/web-mobile has a real but shallow QR editor (QREditorPage.tsx) — close to parity on shape picking (19/23 module shapes, 4/5 frames, 14/14 inners) but missing gradients, per-eye color, decorative shapes (58 unused assets), stickers, logo interactive crop, readability/scannability grading, pixel randomizer, lighting, and background image — all of which the native iOS QR studio (QRGeneratorPage.swift, 8,725 lines) has, and all of which the shared @tactile/qr-renderer engine already supports render-side. This wave brings both web surfaces to native QR-management parity.

TacTile › Launch TacTile › Web › Web — QR management

6/15 done9 open1 open blocker

Selected taskclear

Wire desktop 'Edit Design' to the new QR studio

DoneOwner · Vivt_fa12fd55

Viv — Replace the 'QR Studio lives in the mobile apps for now' stub on desktop with a real link into the new QR studio (built in the prior task). Done when: clicking Edit Design on any existing QR trigger on tactile.to opens the desktop studio pre-loaded with that QR's current design, and saves persist back to the same trigger. File: apps/web/features/assets/pages/TriggerLaunchpadPage.tsx:278.

Unlocks 1Approve: QR management

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

**Wire desktop 'Edit Design' to the new QR studio** · done

Viv — Replace the 'QR Studio lives in the mobile apps for now' stub on desktop with a real link into the new QR studio (built in the prior task). Done when: clicking Edit Design on any existing QR trigger on tactile.to opens the desktop studio pre-loaded with that QR's current design, and saves persist back to the same trigger. File: apps/web/features/assets/pages/TriggerLaunchpadPage.tsx:278.

Where it sits: TacTile › Launch TacTile › Web › Web — QR management

## Unlocks 1

- Approve: QR management

## The brief on file

DONE (commit c9c8ffe8, PR #241). Desktop "Edit Design" opens a real studio.

THE STUB IS GONE: TriggerLaunchpadPage's Edit Design button was an error toast ("QR Studio lives in the mobile apps for now"). It existed because apps/web could not render a QR AT ALL — the only full-fidelity pipeline was apps/web-mobile/features/qr/lib/render-carried.ts, and apps/A importing apps/B is a HARD depcruise rule. #239 extracted it to the new package @tactile/qr-studio (renderCarriedDesign, patchSvgSize, CenterElement, LOGO_BOX_SIZES); web-mobile's file is now a re-export shim, so both surfaces render through one implementation and cannot drift.

NOTE FOR ANYONE LOOKING FOR IT: the extraction went into @tactile/qr-studio, NOT into @tactile/qr-renderer as the earlier spec suggested. Grepping qr-renderer for it finds nothing and reads like the work never landed.

SHIPPED at /assets/trigger/[hash]/design (apps/web/features/qr/): live preview, module shape, eye frame, eye centre, module + background colour, save through qr.update with the re-rendered svg_markup and the design snapshot.

SHAPE VOCABULARY comes from @tactile/qr-renderer's canonical enums — 23 module shapes, 5 eye frames, 16 eye centres — deliberately NOT web-mobile's picker list, which binds to a second, divergent vocabulary in @tactile/qr-web containing a non-canonical `fracture` the renderer cannot draw. Sourcing the options from the thing that renders them makes that class of mismatch impossible by construction rather than by review.

THE BUG THIS ALMOST SHIPPED WITH, worth recording: the snapshot's field names invert what the UI calls them. `snapshot.eyeShape` is the FRAME (5 values); `eyeInnerShape` is the CENTRE (16). Wiring the 16-value set into the frame COMPILES, renders a perfectly valid QR, and silently discards the user's pick — resolveEyeShape (qr-renderer/src/snapshot/resolve-options.ts:154) defaults anything unrecognised to "rounded" rather than throwing. Caught it by checking the resolver before wiring, not after.

GATE: tests/unit/qr-studio-shape-coverage.test.ts renders every one of the 44 options and asserts a real symbol comes back (not an empty <svg> shell), pins the 23/5/16 counts, and asserts `fracture` never appears in the canonical set.

MODE STAYS REPORTED, never toggled — locked by context/decisions/2026-08-06-dynamic-default-static-is-a-separate-flow.md. Saving a design re-renders the symbol but leaves the payload untouched, so anything already printed keeps working; the UI says exactly that.

snapshotFromRecord bridges the API's QRCodeSnapshot to the renderer's QRCodeDesignSnapshot, preferring the stored `design` blob over the flat module/eye/colour columns. That precedence is load-bearing: reading the columns first would flatten a studio-built design (gradients, stickers, per-eye colour) down to its lowest-common-denominator fields the first time someone opened the editor.

NOT INCLUDED, each its own task: gradients (t_7e7e875e), per-eye colours (t_3b954edc), crop (t_793bdeda), decoratives (t_ccc3b2df), stickers (t_814edc23), randomizer/bg-image/lighting (t_d6c8ef5c), grading (t_498d2172).

## 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 — QR management

Wire desktop 'Edit Design' to the new QR studio