Lanes
One lane at a time — the goal, the critical path, and the current wave of blockers.
Android — Settings, Analytics & tools build
Remaining build work across Settings, Analytics, QR editor, NFC, and the AI agent. CORRECTED 2026-08-06 — THE SHOP CLAIM IN THIS GOAL WAS FALSE and is removed. It previously read: "Shop is the standout risk: unlike iOS (where Shop is entirely dead code), Android's Shop is LIVE and reachable from the Dashboard with a fully fabricated catalog, fake reviews, and a no-op checkout button — needs a product decision before any build work." There is no Shop in the Android app. Verified by code audit: no file anywhere under apps/android/ matches *shop* (case-insensitive); no ShopScreen, ShopViewModel, Storefront, addToCart or cart symbol exists in apps/android/app/src/; no product catalog, no hardcoded products, no reviews, no ratings, no checkout button; and no MainTab for it — ui/shell/MainTab.kt:26-31 is Dashboard, Assets, Analytics, Account, Ai, with nothing in MainShell.kt rendering a Shop. The only "Shop" string in the whole Android tree is ui/destinations/create/builders/menu/MenuAddSheet.kt:60,118, where it is a MENU-SECTION CATEGORY NAME in the menu builder's starter catalog ("New Arrivals", "Apparel", "Accessories", "Gifts", "Sale") — template content for a menu the USER builds, not a store. iOS likewise has no Shop: four hits across 558 Swift files, all menu-template content, including a template literally named "Coffee Shop". So there is no product decision pending here and no fake-catalog risk. If a Shop was expected, it was never built in this repo on either platform. WHAT THE SAME AUDIT DID FIND IN THIS WAVE'S AREA, and which is real: - ui/analytics/AnalyticsScreen.kt:103 — the Analytics gear was a real button with an accessibility label and a completely empty handler, so tapping it did nothing at all. FIXED in PR #225: onGearTap is now nullable and the button renders only when a handler exists. - ui/settings/SettingsDetail.kt:984,1005 — GA4/Meta forwarding rows labelled "Coming soon". Non-interactive and clearly labelled, so disclosure rather than a dead control. Left as-is; low risk. - Dead code safe to delete, which keeps getting re-filed as unbuilt work by successive audits: AiAgentStubScreen, ui/nfc/NfcLaunchpadScreen.kt, TriggerLinkerScreen, and ComingSoonBody in AnalyticsScreen.kt. All orphaned.