Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›web-mobile — Surface build·31 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 web-mobile production build sets no NEXT_PUBLIC_API_URL — six call sites fall back to same-origin and 404To do web-mobile /auth/callback redirects to an unsanitized ?redirect param (open redirect)Done Viv — Fix the 'forms' vs 'form' naming mismatch between web-mobile's disabled-category type and the backend destination type.Done Viv — Add 'action' and 'form' to the shared DestinationType union in the SDK.Done 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.Done Viv — Wire the AI Insights tab to the real analytics insights endpoint once the SDK exposes it.Done Viv — Remove the unreachable 'Group-level analytics are in development' stub banner from Deep Dive, or wire it up if group-scope analytics ships.Done 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.Done Add loading.tsx route skeletons to web-mobileDone Pin test: web-mobile Deep Dive must not offer 'group' scope while useEntitySummary has no real group endpoint (follow-up to #712, t_288daf95)To do Viv — Pin the three unguarded delete paths on the web-mobile QR Launchpad (cache repair, double-submit, sheet while deleting)Done 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.Done Kaitlynn — 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.Done Kaitlynn — Verify the 6 working destination builders (website, notes, gallery, document, link_hub, contact-via-card) end-to-end.Done Kaitlynn — Verify QR create, scan, and Launchpad view/manage flows end-to-end.Done Kaitlynn — Verify ConnectCard editor (create and edit) end-to-end.Done Kaitlynn — Verify all 6 Settings pages (profile, security, subscription, notifications, appearance, plus the settings hub) end-to-end.To do Kaitlynn — Verify Analytics tabs (all 7) render real data with correct empty/error states, confirming no fabricated data anywhere.Done Kaitlynn — Verify Assets browser (Triggers / Destinations / QR / Groups / Families tabs) end-to-end.Done

Wave

web-mobile — Surface build

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

26/31 done5 open1 open blocker

Selected taskclear

Add loading.tsx route skeletons to web-mobile

DoneOwner · Vivt_acd9ac2d

Unlocks 1Approve: Surface build

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

**Add loading.tsx route skeletons to web-mobile** · done

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

## Unlocks 1

- Approve: Surface build

## The brief on file

[2026-10-15 · Viv] DONE: web-mobile now has route skeletons: five loading.tsx (analytics, assets, create, destinations, settings) plus the boundary for / that refuted 236f094a lacked. HomePage in app/page.tsx awaits only getUser and renders AuthenticatedHome inside Suspense with the new DashboardSkeleton; there is deliberately no app/loading.tsx because it would wrap /signin, /signup and /auth/handoff, and a test pins that. Draft PR https://github.com/TacTile-dev/TacTile/pull/756, commit 16c339ae on r31/web-mobile-qr-loading (independent of the two QR commits). Not merged, not deployed. Tests: tests/unit/web-mobile-route-loading.test.ts 18 passed, apps/web-mobile/features/dashboard/__tests__/route-loading-render.test.ts 14 passed; verify:unit 237 files/4761 tests; pnpm run build:web-mobile exit 0. Local stub with a 3 s dashboard fetch: before, the response began at 3038 ms and a tab tap from /assets left it frozen; after, 33 to 45 ms, skeleton on screen at 0.5, 1.5 and 2.5 s, real dashboard at 3.6 s. The reviewer reproduced it on a fresh stub: 61 ms, same timeline, and putting main's page.tsx back gave 3048 ms with no skeleton. Mutations, all restored: builder's five (remove the / boundary 2 red, getSession above the boundary 1, 'use client' 1, frame drift 1, delete settings/loading.tsx 4), reviewer's (fallback null) 1 red. Gate run 1 of 3, exit 0: gate: passing with known-red: verify:secrets-rotation (55 of 56, the sanctioned red). CI on #756 at head 16c339ae (verify run 38808116252): one failed step, Secrets rotation audit (sanctioned); playwright, semgrep, dep-scan and static-firewall green; the two steps CI skipped after that failure, console ratchet and trigger-hash tests, passed in the local gate on the same head. Reviewers: acceptance CONFIRMED, safety CONFIRMED. Limits carried: /settings and /assets boundaries are proven by tests and the build, not a timeline (they fetch client-side); /analytics prerenders static so its boundary may never show; DashboardSkeleton deep-imports across features against the AGENTS.md isolation row (depcruise does not cover web-mobile). QA card t_e7338619 (Kaitlynn), blocked until the PR is merged and deployed.

[2026-10-15 · Viv] BUILT, not gated, not pushed: r31/web-mobile-qr-loading 16c339ae. 236f094a's five loading.tsx plus the missing boundary for /: app/page.tsx awaits only getUser and renders AuthenticatedHome inside Suspense with a new DashboardSkeleton (no app/loading.tsx: it would wrap /signin). Local stub, dashboard fetch 3s: before, response began at 3038ms and a tab tap left /assets on screen; after, 33 to 45ms and the skeleton shows until 3.6s. web-mobile-route-loading 18 and route-loading-render 14 green; 5 mutations red, restored; next build exits 0. Not merged, not deployed.

[2026-10-09 · Viv] TODO: attempted on r30/web-mobile-r1 but an adversarial review refuted it (The hub task names the key routes as 'dashboard, assets, analytics, destinations, settings' and the dashboard is the first of them; the commit ships no boundary for it (it substitutes /create) and says so itself: 'the dashboard at / has no boundary'. The dashboard is the one route where a skeleton matters most: apps/web-mobile/app/page.tsx is an async server component that awaits getUser(), getSession() and fetchDashboardData(tactile, analytics) (page.tsx:~35-75) with no Suspense and no skeleton); not shipped. Next session starts from that reason.

Viv — add route-level loading.tsx skeletons to apps/web-mobile for key routes (dashboard, assets, analytics, destinations, settings), matching the pattern being built for apps/web in "Add route-level loading.tsx skeletons for key authenticated routes" (t_6bee88fd). apps/web-mobile has zero loading.tsx anywhere in its route tree — confirmed by full glob search. Note: the companion task "Add app-wide error.tsx and not-found.tsx boundaries to web-mobile" (t_7c97a876) covers the error/404 boundaries but its Done-when criteria only commits to error.tsx and not-found.tsx, not loading.tsx — this task closes that remaining gap. Done when: navigating into key authenticated routes on web-mobile shows a Suspense-driven skeleton at the route boundary during slow data fetches. File: apps/web-mobile/app/ (zero loading.tsx anywhere in the tree).

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

Add loading.tsx route skeletons to web-mobile