--- import { screensOf, PHONE } from '../../data/screens.mjs'; /** * The app's screenshot strip. Reserved in phase 5 (D26), filled in phase 9. * * --------------------------------------------------------------------------------------- * WHY THIS COMPONENT EXISTED FOR A PHASE WITH NOTHING IN IT * --------------------------------------------------------------------------------------- * PLAN.md §10 said `/app/` shows "the 14 existing screenshots". They exist — * `docs/android/screenshots/` on the `docs` repository — and they are the wrong fourteen: a * trusted-device and recovery-code smoke test from 2026-07-22, captured against a * development instance with no seeded content, before the theming work that changed how * every screen looks. Five of them are two-factor prompts. The home shot is an empty page. * * Shipping them would have broken D4 and §1 at once, so D26 reserved the slot for the phase * that stands up the review stack anyway. The shape was defined then and the data arrived * now, which is exactly what it was for: filling it was a data change. * * --------------------------------------------------------------------------------------- * WHY IT READS screens.mjs RATHER THAN HOLDING ITS OWN LIST * --------------------------------------------------------------------------------------- * The draft carried its own `shots` array, written before there was anywhere else to put * one. There is now: `src/data/screens.mjs` holds every capture the site ships, web and * phone alike, and `scripts/checkScreens.mjs` proves each one exists at the size the markup * claims. A second list here would be the one nothing checks. * * The phone captures come from an emulator pointed at the same seeded deployment the web * screenshots were taken from, on the same day — which is the property D26 was really * after, since the app takes its colours, type and navigation from the site it connects to. */ const shots = screensOf('phone'); --- { shots.length > 0 && (

What it looks like

Captured against a real deployment with real content, not mocked up. The app takes its colours, type and navigation from the site it is connected to, so these show one community's app rather than a neutral one.

) }