Block a user
New "Deploy Firestore rules & indexes" CI job fails every run — FIREBASE_TOKEN secret not set
place_verifier.verify() has the same no-anchor gap #159 fixed in intelligence.py's geocoder — never ported over
Citywide/large systems (e.g. NYPD Citywide) never get a location anchor, so location_proximity never fires and duplicate incidents get created for the same event at nearby addresses
fast/thin correlation path never uses srcaddr for disambiguation, even though every call already carries it
Second SDR: ADS-B (dump1090) / AIS (AIS-catcher) support
Second SDR: ADS-B/AIS telemetry ingestion + live map overlay (server side)
Second SDR support: ADS-B (dump1090) / AIS (AIS-catcher) / dual-OP25, configurable client+server
ADS-B and AIS are now wired end to end (both node-side and server-side), decision made to also push to the map, not just node-local:
node-26 commits: 523a948 (plumbing), e880d50 (ADS-B/dump1090…
LLM-orphan gate's "type" veto fires on visibly content-free chatter (18/22 this window)
Fixed this session, commit 3f69879 (deployed, confirmed via /health). intelligence.py's incident_type rule now checks for real event content before applying the channel default — content-free/admi…
Second SDR support: ADS-B (dump1090) / AIS (AIS-catcher) / dual-OP25, configurable client+server
deploy.yml: /opt/drb/.last_good_tag reads empty (not missing), so PREV_TAG is blank and every deploy's Main Deploy step fails — rollback safety net has been dead since at least run #602
Incidents never actually clear — units_cleared almost never populates, 90-min idle sweep does the resolving instead
Same call_id linked into 2 incident records with identical extracted data (~2% of linked calls)
Fix confirmed working — window #5 measurement (CORRELATION_REVIEW_0914.md).
Zero duplicate-links among calls that started after this window began (i.e., processed entirely under the fixed…