The flows run a real browser against the built dashboard, the fixture API,
and the real event stream: the feed and its figures, filtering, a call's
published record, the map and the narrow-screen switch between them, the
empty-period offer of a longer range, and calls published while the reader
watches, both live and while updates are paused.
The fixture harness publishes and retracts those calls, so each flow starts
from the same dataset whichever order they run in. The build gets a blank
tile so the suite never asks a public tile server for map tiles.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
JMR-devandClaude Opus 5
df0bd9415d