chore(monitor): refresh data — replay June 12–15 (10 orgs)

[Chouffe]

Summary

Data-only refresh of the monitor/ store and replay artifacts, covering June 12–15, 2026. No code changes — only the DVC pointers (monitor/data/01_raw/sequences.dvc, monitor/dvc.lock); the data lives on the s3remote DVC remote.

• Imported 478 sequences across 10 organizations (--all-orgs --exclude-org pyroadmins): June 12 (179), June 13 (133), June 14 (130), June 15 (36, partial). New since the merged June‑12 snapshot: full June 13–15, June‑12 evening traffic, the grown sdis-12 (3 → 9) and a new engine org.
• Replayed the 380 sequences carrying a temporal_api_version (all 0.3.1; 98 unscored dropped as no_temporal_version): 161 exact + 219 window-drift = 380, 0 unexplained. All 380 trigger-enriched with 0 score disagreements.
• Production verdicts: 186 keep / 194 discard.

Review / load the data

git checkout arthur/monitor-data-june15
cd monitor && make install && uv run dvc pull
cd ../viewer && npm ci && DATA_ROOT=../monitor npm run dev   # http://localhost:3000

The alert-api source shows all three days (sort by started); organizations are a column + filter, with kept/discarded stats per org in the left rail.

Notes

• Purely operational; safe to merge or close once reviewed. The reporting tree is reproducible from the store via dvc repro (Docker + the pinned pyronear/temporal-model-api:0.3.1 and local temporal-model-api:dev trigger image).
• Follow-ups still open from the feature PR: a per-sequence replay cache (so dvc repro is incremental instead of re-running the whole store, as it did here) and a scheduled import → repro to keep this current without a manual hour-long cycle.