Add Frigate-backed starter camera config

docs/FRIGATE_SETUP.md

@@ -0,0 +1,37 @@
+# visionLabs Frigate setup
+
+This project now assumes Frigate is the backend that owns camera auth, camera discovery, and stream handling.
+
+## Starter inventory
+
+The first four cameras are currently modeled as:
+
+- `cam195` -> `192.168.0.195`
+- `cam196` -> `192.168.0.196`
+- `cam201` -> `192.168.0.201`
+- `cam228` -> `192.168.0.228`
+
+All four are ONVIF-capable and should be added to Frigate using matching camera IDs where possible.
+
+## Important rule
+
+Do not commit raw camera passwords to this repo.
+
+Keep camera credentials inside:
+
+- Frigate config
+- go2rtc config
+- a local secret file outside version control
+
+## What to update next
+
+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
+
+## 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