Lead-time / time-to-impact display #84
Labels
No labels
area:ai
area:ci-cd
area:notifications
area:observability
area:public-pages
backlog
bug
duplicate
enhancement
help wanted
invalid
question
type:decision
type:feature
type:infra
type:maintenance
type:security
v1.0.1
v1.1.0
v1.2.0
v1.3.0
v2.0.0
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rbrooks/WeatherBot#84
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
onsetis already parsed off NWS alerts (nws.py:238) but only ever shown as a status badge. Surface "arrives in ~40 min" on dashboard cards and in notifications where onset is in the future. Small change, meaningfully better situational awareness. Missed because the badge (WARNING/WATCH/OK) framed alerts as binary state, not a timeline. Effort S, value Medium.Filed from the 2026-07-17 codebase audit (
docs/.internal/report-2026-07-17.md), finding I-14.Done in #113 (merged).
onsetis now persisted onSentAlert(migration 0026) and surfaced as a friendly time-to-impact wherever it's in the future:time_formatting.lead_time_textrenders "in ~40 min" / "in ~1.5 hr" (None when past/absent), added as an "Arrives:" line to all 9 notifiers and a "⏳ arrives in ~40 min" span on the dashboard cards (server-side + live SSE). Output is byte-for-byte unchanged when onset isn't in the future (the common case — most alerts are already in effect). Bulk suite 709 passed; migration 0026 verified on a real-DB copy. Bonus:SentAlert.onsetnow also enables the #75 feeds to expose real onset in a follow-up.