Optional_Focused subset on this entry — the agent's focusIds write-side. Drives the dim/highlight
affordance on _module and feeds focusedFeatures(entryId) for stepping through.
Optional_Per-entry incident-details module. Each entry owns its own module so two areas can be
rendered on the map at the same time without sharing a single source. Lazy-initialised
via TrafficIncidentsState.getEntryModule — undefined until first show. Subscribe to
clicks via module.events.on('click', ...) once retrieved.
Optional_Per-entry polling loop. Lazy-created on first TrafficIncidentsState.startMonitoring call; reused across stop/start cycles. Owns timer, status, error, captured area.
Optional_True while this entry is currently rendered on the map.
Optional_Monotonic counter incremented on every TrafficIncidentsState.replaceEntryData
call. Used to detect out-of-order ticks: if a slow module.show() from an earlier
tick resolves after a newer tick has already overwritten data, the late path bails
before reapplying focus.
The captured query that produced this entry. Replayed by the monitor on each tick so
polling stays in the same slice the entry was loaded with. Reuses the loader's own
params shape; the entry stores a resolved BBox tuple in bbox (the loader
normalises any GeoJSON value before handing the params off).
A single traffic-incidents history entry: the captured query, its incidents, and the per-entry rendering / monitoring state owned by TrafficIncidentsState.
analyseDataanalyses are NOT held here — they live in the session-levelstate.analysesregistry. Clustering IS dedicated incidents state, kept in the slice'sclustersmap keyed by entry id (see ClustersRecord).