♻️ Split server events behavior

[Robdel12]

Why

The events route is the live-update path for report/dashboard behavior. It is also one of the easiest places for hidden tech debt to pile up because failures often show up as stale UI, missed updates, or watchers that behave differently across environments.

This PR keeps event behavior separate from baseline/screenshot route work. That makes the review about one thing: whether local server events and adjacent dashboard/server smoke paths behave predictably.

What Changed

• Tightened event-router behavior and related test coverage.
• Updated dashboard filter behavior that depends on event/report state.
• Refreshed adjacent router smoke tests so the server surface stays consistent across assets, auth, cloud proxy, config, dashboard, and health routes.

Verification

• npm run build
• node --test tests/server/routers/events.test.js tests/server/routers/assets.test.js tests/server/routers/auth.test.js tests/server/routers/cloud-proxy.test.js tests/server/routers/config.test.js tests/server/routers/dashboard.test.js tests/server/routers/health.test.js

Stack

6/10 in the CLI audit stack.

Base: rd/cli-audit-server-baselines
Head: rd/cli-audit-server-events

[vizzly-testing]

Vizzly - Visual Test Results

CLI Reporter - Approved

19 comparisons, no changes detected.

View build

CLI TUI - Approved

5 comparisons, no changes detected.

View build

---

_{rd/cli-audit-server-events · 90740551}