Verify WorldMonitor

WorldMonitor's primary surface is a browser dashboard: a Vite/TypeScript SPA served at /dashboard, with a map, a panel grid, a settings overlay, and a command palette. This skill launches one isolated instance of it, drives a feature the way a user does, and leaves evidence behind.

This skill proves browser behavior. Use the code and check map for backend, desktop, worker, or documentation changes.

Run everything from the repo root of the worktree under test.

Choose the proof

1. Name the user action and expected result. Load the matching feature recipe, including its data path and proof limits.
2. Follow worktree preparation. Run an existing strict test first when it covers the outcome. Country Brief uses npm run test:e2e:country-brief. Playwright owns that test's server; do not also run launch for it.
3. For an interaction the test does not cover, use the manual steps below. Extend an existing test when a lasting regression check is needed.
4. Report the exercised path, controlled responses, evidence, and unmet criteria. Apply the local API proof limits. A successful drive proves only its assertions.

Launch

One long-lived dev server per run; every drive gets a fresh browser context against it.