Add snapshot-first Frigate camera wall

docs/FRIGATE_SETUP.md

@@ -27,11 +27,13 @@ Keep camera credentials inside:
 
 1. Set the real Frigate base URL in `config/cameras.json`
 2. Confirm the Frigate camera IDs match `cam195`, `cam196`, `cam201`, and `cam228`
-3. Decide which Frigate live endpoint format the Roku app should consume first
-4. Add snapshot and live tile loading in the SceneGraph UI
+3. Verify that each camera snapshot is reachable at `/api/<camera>/latest.jpg`
+4. Add snapshot tile loading in the SceneGraph UI
+5. Decide which direct live endpoint format the Roku app should consume after snapshots are working
 
 ## Why this shape works
 
 - Roku does not want to manage ONVIF directly
 - Roku is happier when Frigate handles the camera-side protocol mess
 - This keeps the app focused on layout, browsing, and playback
+- Snapshot-first is the lowest-risk way to prove the app shape before live playback is finalized

docs/ROADMAP.md

@@ -4,12 +4,12 @@
 
 - Static packaged Frigate-backed camera config
 - Simple Roku SceneGraph shell
-- One screen with a fixed camera grid
+- One screen with a fixed snapshot-first camera grid
 - Frigate-managed live feeds in a Roku-friendly format
 
 ## Phase 2
 
-- Config loader and camera tile rendering
+- Config loader and snapshot tile rendering
 - Snapshot fallback if a stream is unavailable
 - Focus movement and remote navigation
 
@@ -30,4 +30,5 @@
 - Roku does not directly fit raw RTSP workflows well
 - Frigate should own camera auth and camera-side protocol details
 - HLS is the safest first-class playback target
+- Snapshot-first is the safest prototype path while live endpoint details are still being verified
 - Packaged JSON is fine for V1 but not enough for runtime editing