1 commit

Author	SHA1	Message	Date
K7ZVX	c111211850	feat(notifications): Phase 2.11 NIFC fires adapter pipeline integration ... Adds NICFFiresAdapter.to_event(), wiring the NIFC/WFIGS wildfire perimeter adapter into the notification EventBus, following the Phase 2.7 traffic / 2.9 USGS / 2.10 avalanche pattern. to_event() design: - Category: every active perimeter with a reported size maps to a single wildfire_incident category (the adapter's WFIGS query already filters to active WF incidents in the configured state). - Severity: PASSED THROUGH unchanged. The adapter computes severity by proximity to region anchors (< 25 km -> priority, else routine), which is a richer, more actionable signal for a mesh-notification use case than raw acreage. I deliberately did NOT invent acreage breakpoints -- pass-through matches the 2.9/2.10 pattern and defers tiering to the pipeline Inhibitor. (Flagged for review: if acreage-based or containment-based severity is preferred, it belongs in the adapter's _fetch severity logic, not to_event.) - Summary: incident name + acreage + % contained + distance to nearest anchor. - group_key/inhibit_keys: the adapter's stable "nifc_{name}_{state}" event_id as both. Re-polls of the same incident coalesce; single inhibit key lets the Inhibitor suppress lower-severity re-emissions. - Defensive: missing centroid (lat/lon), missing event_id, or missing/zero acreage returns None; try/except-guarded. No store.py change: the Phase 2.9 _emit_event None-guard already handles to_event() returning None, and store gates emission on hasattr(adapter, "to_event"). Rule 17: no new tunable. fires enabled / state / tick_seconds already exist in env_feeds.yaml (GUI-editable). Rule 18 N/A -- the WFIGS Interagency Perimeters ArcGIS FeatureServer is keyless (no .env entry; the .ref credentials store has no NIFC/ArcGIS/wildfire key, confirming none is needed). Rule 16: standalone fetch path validated in-container. FIRMS side-investigation (flagged in the 2.10 report): firms is disabled because it needs a NASA FIRMS map key that is not provisioned -- env_feeds.yaml has firms.enabled=false with map_key='' (not even a ${FIRMS_MAP_KEY} reference), and /data/secrets/.env has no FIRMS key. Intentional/blocked-on-key, not a bug. No action this phase. Config note: fires was already enabled (state US-ID) and already one of the 7 live adapters (store key "nifc"), so this phase keeps the count at 7 (no 7->8 change) and required no env_feeds.yaml edit. No seasonal short-circuit, so no temp config wiggling was needed (unlike 2.10). Tests: tests/test_adapter_fires.py (12 tests) mirrors test_adapter_usgs / test_adapter_avalanche -- category (always wildfire_incident, independent of severity), severity pass-through, group_key/inhibit_keys, distinct-incident keys, field population, summary content, and the defensive cases (zero acreage -> None, missing centroid/event_id -> None, corrupted -> None). Full suite: 200 passed. Live smoke test (prod container, Phase 2.11 code rebuilt in): clean startup, 7 env adapters loaded, no traceback. There IS an active Idaho incident today, so this produced a real end-to-end emission rather than the empty-result cases of 2.9/2.10: the running store logged "NIFC fires updated: 1 active in US-ID" and "Emitted nifc event cc4bd340be7fd57e (wildfire_incident) to pipeline bus". An in-container standalone fetch confirmed health is_loaded=true, last_error=null, consecutive_errors=0, event_count=1 -- the WFIGS ArcGIS endpoint was reached with no DNS/auth errors (Phase 2.6.6 DNS fix). The Summit Creek incident (1,500 ac, 0% contained, ~72 km from the Twin Falls anchor) mapped to wildfire_incident / routine as designed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 23:33:48 +00:00