Lanes
One lane at a time — the goal, the critical path, and the current wave of blockers.
Web — Destination editing
No destination editing exists on either web app today. apps/web has zero editing (creation is also being built from scratch in a separate wave); apps/web-mobile has creation for 7 of 14 types but no re-edit path for any of them. Neither web app has an authenticated in-app destination detail/preview page distinct from the public /t/[hash] scan page either — apps/web has no /destinations route of any kind (confirmed: zero list, detail, or edit surface in app/(app)/), and apps/web-mobile's DestinationDetailPage only shows a type badge, date, and trigger-link management, not the destination's actual rendered content. Folding the detail/preview gap in here since one screen (mirroring iOS's DestinationLaunchpad: preview + connected triggers + edit entry + delete) naturally serves both.
Add family creation to Assets on both web surfaces
Viv — Neither apps/web nor apps/web-mobile can create a new family today (both can only edit/delete existing ones). Add a create action reusing the existing FamilyLaunchpadPage edit-form fields. Done when: a new family can be created from apps/web/features/assets/pages/AssetsPage.tsx and from apps/web-mobile's FamiliesTab, and is immediately editable via the existing Launchpad flow. File: apps/web/features/assets/pages/AssetsPage.tsx, apps/web-mobile/features/assets/FamiliesTab.tsx.