Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Web›Web — App shell & dashboard·9 in this wave

Approve: Web app shell & dashboardTo do · blocker Replace the fake dashboard with real dataDone Add destination editing to webDone Fix mobile hamburger menu — wire onClick in apps/web AppShellDone Add a custom 404 pageDone Finish the analytics inline-lock badgeTo do Add error boundaries to web-mobileDone Wire the analytics insights endpointTo do Wire the QR launchpad destination pickerDone

Wave

Web — App shell & dashboard

The dashboard is decorative — hardcoded fake metrics and dead buttons. Editing does not exist for any type on web.

TacTile › Launch TacTile › Web › Web — App shell & dashboard

6/9 done3 open1 open blocker

Selected taskclear

Add error boundaries to web-mobile

DoneOwner · Vivt_e47b2776

Unlocks 1Approve: Web app shell & dashboard

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 error boundaries to web-mobile** · done

Where it sits: TacTile › Launch TacTile › Web › Web — App shell & dashboard

## Unlocks 1

- Approve: Web app shell & dashboard

## The brief on file

Viv — add error boundaries to apps/web-mobile. CLOSED AS DONE (round 17); the work already shipped.

The stated premise was false. This task said apps/web-mobile has neither error.tsx nor not-found.tsx. Verified at 48f9f67c: `ls apps/web-mobile/app/` lists error.tsx, global-error.tsx AND not-found.tsx. All three landed in PR #307.

What is there:
  error.tsx        — the in-tree boundary, with a reset() path. Matters more in a PWA than on desktop: an installed app has no browser chrome, no address bar and no reload button, so Next's default is a dead end.
  global-error.tsx — catches the root layout itself failing, which error.tsx cannot because it renders INSIDE that layout. Inline-styled on purpose: a rescue screen that needs the stylesheet it is rescuing you from is not one.
  not-found.tsx    — branded 404, pinned by apps/web-mobile/playwright/not-found.spec.ts.

The only genuinely missing file is loading.tsx, which Next does not require and which is separately tracked. Not reopening this for it.

## 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 — App shell & dashboard

Add error boundaries to web-mobile