First-run UX: fix six defects and surface motion history

[Sbussiso]

Ran Command Center in AUTH_PROVIDER=local — the exact path a first self-hosted install takes — and drove every page in a real browser. Everything here was found that way, not by reading code.

Six defects, all visible in the first minute

1. A self-hosted install's root redirected to our marketing site. RedirectToStandalone fired unconditionally, so an operator visiting http://their-host/ was bounced to sentinel-command.com. The root of their own deployment was unusable. Now skipped when IS_LOCAL_AUTH.

2. Every new org displayed the wrong timezone. Intl.supportedValuesOf("timeZone") returns 418 IANA zones and does not include a bare "UTC" — which is exactly what the backend defaults a new org to. <select value="UTC"> matched no option, so the browser silently rendered the first one: Africa/Abidjan. The stored value was correct; only the display lied, which is worse than an error.

3. A brand-new install reported "Offline" in amber. systemOk was total > 0, so zero cameras — the state every install starts in — rendered as a warning. Now reads "No cameras yet" in neutral; "Offline" means what it says.

4. Self-hosted showed 0.0 / 999999h. 999999 is plans.py's sentinel for unlimited, exactly as 999 is for cameras/nodes — and those already render as ∞ three lines away in the same component. The sidebar contradicted the Settings page, which said "Unlimited" for the same plan.

5. Two of three notification settings had no control. GET /api/settings has always returned camera_transition_notifications and node_transition_notifications, and POST /settings/notifications has always persisted them — only the motion toggle was rendered. An operator flooded with node-transition notifications had no way to stop them.

6. The camera icon was malformed on every CameraCard. Path read h16c0 1.1-.9-2-2V6, which the SVG parser rejects outright — logged attribute d: Expected number on every render and dropped the rest of the path, drawing clipped. Only found because the new panel's browser pass surfaced the console error. Swept src/ for the same damage — none else.

Motion history was recorded but unreadable

GET /api/motion/events and /events/stats have shipped since motion ingestion landed — paginated, camera-filterable, require_view — and nothing in the SPA ever called them. The only motion surface was the live SSE toast, so "what triggered overnight?" was unanswerable.

Adds a Motion tab to Admin, mirroring the existing tabs' shape. Per-camera rollup answers "which camera saw the most movement" before you read a row; scores carry colour because that's the number operators scan for.

Verified against 140 seeded events across two cameras: 3 pages, correct counts and peak scores, camera-name resolution, zero console errors.

Also

.gitignore covered only bare .env, missing .env.local — the file Vite's own docs designate for secrets, and the one AGENTS.md tells self-hosted operators to create. Nothing has leaked (the only tracked env file holds a publishable pk_test_ key), but it was one git add -A away.

Verified

99 frontend tests pass, production bundle builds, all six fixes confirmed in-browser after the change.

Noted, not fixed: CI doesn't lint the frontend (audit + test + build only), which is why 5 eslint errors have been sitting unnoticed — the backend gates on ruff. Wants its own change.

🤖 Generated with Claude Code