Command

PePersonal JEJust Electrolyte RTRelease Timer TtTacTile CSClearSource AtAthletic

TacTile›Launch TacTile›Foundations›Shared Packages·5 in this wave

Wave

Shared Packages

@tactile/ui primitives every surface depends on. First-mover work — iOS, Android, and Web are all blocked on these.

TacTile › Launch TacTile › Foundations › Shared Packages

4/5 done1 open1 open blocker

Selected taskclear

Add Toast / Notification system

DoneOwner · Vivt_62db2d15

App-wide toast/notification primitive.

Unlocks 1Approve: Shared Packages

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 Toast / Notification system** · done

App-wide toast/notification primitive.

Where it sits: TacTile › Launch TacTile › Foundations › Shared Packages

## Unlocks 1

- Approve: Shared Packages

## The brief on file

Viv — add the app-wide Toast/Notification primitive.

--- DONE 2026-07-27 (Viv) · commit a6d056cc ---
Shipped on @radix-ui/react-toast with a stories file. Verified: tsc clean, build:web compiles, all gates at pre-existing counts. This commit also lands the src/index.ts barrel covering all four primitives from this wave — one shared file, so it went in the last of the four rather than being split.

TWO LAYERS: the Radix presentational parts, plus a ToastProvider + useToast() imperative API — because what callers actually want is `toast({ title })` from an event handler, not JSX they render and manage open-state for.

Radix handles what's easy to get wrong: swipe-to-dismiss, pause on hover and on focus loss, the aria-live region, and the F8 hotkey that moves focus to the toasts. Announcement matters — a toast nobody can hear is a toast that didn't happen.

Four tones (default/success/warning/error) each with an icon, optional action button, and duration: Infinity for toasts that must be dismissed.

IMPLEMENTATION DETAILS THAT WILL MATTER LATER:
- Toast ids come from a counter, not Math.random or Date.now, so they're stable across SSR and hydration.
- Records are dropped only after the close animation ends, otherwise the toast vanishes with a visible jump.
- useToast THROWS outside its provider rather than no-oping. A silently swallowed toast surfaces as "the save button does nothing" — far more expensive to find than a clear error at mount.

ACTION NEEDED WHEN A SURFACE ADOPTS THIS: <ToastProvider> must be mounted once near the app root, inside any theme provider. It is not wired into apps/web yet — that belongs to whichever surface task first needs a toast, not to this primitive task.

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

Shared Packages

Add Toast / Notification system