v1.3.0 Phase A: AI context enrichment #104
No reviewers
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!104
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/v1.3.0-phaseA-aicontext"
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?
Enriches the structured context handed to the AI summarizer — input-only, no prompt/validator changes.
_freshness_statusnow emits a distinctstalestatus when a feed has no failures but itslast_success_atis older than the category threshold (previously always"ok"), so a silently-stalled feed is reported as stale to the model instead of fresh. Reaches both local and cloud prompts (thefreshnessfield is already whitelisted).normalize_timestamp, and the new fields are localized viaformat_location_datetime(no rawZ).AI_CONTEXT_INCLUDE_SEVERE_STATEMENTS(default off, since it adds a per-summary NWS fetch).Note
The new SPS/SVS and radar fields reach local providers only (dropped by
_filter_structured_context_for_cloud's whitelist) — consistent with the existing cloud-privacy posture (SPS/SVS carries geographic detail). The staleness change reaches cloud too.Testing
Full suite green on the dev server: 644 passed (9 new tests covering staleness boundaries, local-time formatting, and SPS/SVS + radar bounding).
Closes #17, #18, #20, #61
🤖 Generated with Claude Code