meshai/tests/test_adapter_config_foundation.py

350 lines
12 KiB
Python
Raw Normal View History

feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
"""v0.6-3a foundation tests: migration, seed, accessor, orphan prune.
v0.6-3a.1: trimmed registry to 43 keys per Matt's CONFIG-vs-CODE rule.
prune_orphans cleans up rows that were in the v0.6-3a draft but no longer
in the trimmed REGISTRY. Tests now assert the 43-key count and exercise
the prune path.
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
"""
from __future__ import annotations
import json
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
import logging
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
from unittest.mock import patch
import pytest
from meshai.adapter_config import (
adapter_config,
invalidate_cache,
seed_defaults,
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
prune_orphans,
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
REGISTRY,
ADAPTER_META,
)
from meshai.adapter_config import _accessor as accessor_mod
from meshai.persistence import close_thread_connection, init_db
from meshai.persistence import db as persistence_db
# ---------- fixtures ------------------------------------------------------
@pytest.fixture
def fresh_db(tmp_path, monkeypatch):
p = str(tmp_path / "ac-test.sqlite")
monkeypatch.setenv("MESHAI_DB_PATH", p)
persistence_db._initialised.clear()
close_thread_connection()
invalidate_cache()
conn = init_db()
yield conn
close_thread_connection()
persistence_db._initialised.discard(p)
invalidate_cache()
# ---------- schema --------------------------------------------------------
def test_v6_tables_exist(fresh_db):
tables = {r["name"] for r in fresh_db.execute(
"SELECT name FROM sqlite_master WHERE type='table'"
).fetchall()}
assert "adapter_config" in tables
assert "adapter_meta" in tables
feat(v0.6-tail): close 5 v0.6-phase1-complete.md follow-ups (1) Auto-call refresh-toggles on PUT /api/config/notifications meshai/dashboard/api/config_routes.py adds register_config_routes_hooks(app) which registers a FastAPI HTTP middleware: on any 2xx PUT whose path matches /api/config/notifications or /api/config, the middleware invokes _refresh_toggle_filter(app) which reaches into app.state.bus._ pipeline_components["toggle_filter"] and calls .refresh(app.state.config). The dashboard no longer has to remember to ping POST /api/notifications/ refresh-toggles after a toggle change. The explicit endpoint stays for backwards-compat. (2) env_reporter block-size cap moved to adapter_config New registry row pipeline.env_reporter_block_chars (int, default 3000). meshai/notifications/env_reporter.py replaces the hardcoded _BLOCK_MAX_CHARS = 3000 with _DEFAULT_BLOCK_MAX_CHARS (the fallback) + a _block_cap() helper that reads from adapter_config on every slice. Mutating the row via PUT /api/adapter-config takes effect on the next env_reporter call -- no restart. (3) Bulk-import endpoint for gauge_sites meshai/dashboard/api/gauge_sites_import.py adds POST /api/gauge-sites/import with two paths: format=csv -- expects "data" (CSV text with header row matching gauge_sites columns: site_id, gauge_name, lat, lon, and optionally action_ft/flood_minor_ft/ flood_moderate_ft/flood_major_ft/enabled). UPSERT via ON CONFLICT(site_id) DO UPDATE. Returns {inserted, updated, skipped}. format=nws-ahps -- expects "wfo" (list of WFO codes). Fetches water.weather.gov/ahps2/index.php?wfo=<WFO> for each, regex-parses gauge links, then fetches up to 50 gauge detail pages per request and regex-parses lat/lon + four threshold values. Best-effort; rows stored under "AHPS-<gauge_id>" so they dont collide with USGS-* ids. Returns the same shape plus detail_fetched + errors list. Frontend (dashboard-frontend/src/pages/GaugeSites.tsx) gains a Import button + modal with two tabs (Paste CSV / Scrape NWS-AHPS) rendered via an ImportModal component. CSV tab has a 48-row textarea with the column-header hint inline; AHPS tab has a comma-separated WFO input defaulting to BOI. Both submit via fetch() and show the JSON response inline. Invalidates the curation cache server-side on any successful insert/update so nwis_handler sees the new gauges on its next call. (4) WFIGS tombstone column -- CORRECTNESS v12.sql adds fires.tombstoned_at REAL (nullable) + idx_fires_tombstoned_at. meshai/central/wfigs_handler.py: the tombstone branch (kind=="wfigs_tombstone") UPDATE fires SET tombstoned_at=COALESCE( tombstoned_at, ?) so the first tombstone-time wins (idempotent against repeated tombstone envelopes). meshai/notifications/reminders/__init__.py: the wfigs tombstone termination condition now checks row["tombstoned_at"] IS NOT NULL. Reminders correctly STOP for closed fires -- before this change the 8h cadence would have kept Active: broadcasts going indefinitely past a WFIGS removal. SCHEMA_VERSION 11 -> 12. (5) Delete INCIDENT_BROADCAST_HEARTBEAT_S meshai/central/incident_handler.py: removed the dead constant (v0.5.9 REVISED dropped the heartbeat path but left the constant imported-but-never-read). tests/test_incident_handler.py: removed the orphan test_i_8h_heartbeat_triggers_update test (asserted None, used the deleted constant for time arithmetic) and the stray import line. Tests (tests/test_tail_followups.py, 16 cases): - middleware fires refresh on PUT /api/config/notifications (200), does NOT fire on PUT /api/config/llm - env_reporter _block_cap() default 3000; mutate via PUT, invalidate, next read returns the new cap - CSV import inserts new rows, updates existing, skips bad rows, rejects missing required columns, rejects bad format - AHPS index parser extracts (gauge_id, name) from realistic HTML - AHPS detail parser extracts lat/lon + four thresholds from realistic HTML - fires has tombstoned_at column after migrations - wfigs tombstone branch stamps tombstoned_at - ReminderScheduler skips a fire whose tombstoned_at is NOT NULL - ReminderScheduler still fires for a fire whose tombstoned_at IS NULL - INCIDENT_BROADCAST_HEARTBEAT_S no longer importable Foundation/API test counts bumped: REGISTRY 58 -> 59 (+ env_reporter_block_chars) schema_meta v11 -> v12 Test count: 844 -> 859 (+16 new, -1 deleted dead test). 0 regressions.
2026-06-05 21:37:05 +00:00
def test_schema_meta_at_v12(fresh_db):
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
v = fresh_db.execute(
"SELECT value FROM schema_meta WHERE key='version'"
).fetchone()["value"]
assert int(v) == 16
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_adapter_config_type_check_constrains_vocabulary(fresh_db):
with pytest.raises(Exception):
fresh_db.execute(
"INSERT INTO adapter_config(adapter, key, value_json, default_json, "
"type, description, updated_at) VALUES (?,?,?,?,?,?,?)",
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
("x", "y", "1", "1", "integer", "", 0.0),
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
)
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
# ---------- registry shape -----------------------------------------------
feat(v0.6-tail): close 5 v0.6-phase1-complete.md follow-ups (1) Auto-call refresh-toggles on PUT /api/config/notifications meshai/dashboard/api/config_routes.py adds register_config_routes_hooks(app) which registers a FastAPI HTTP middleware: on any 2xx PUT whose path matches /api/config/notifications or /api/config, the middleware invokes _refresh_toggle_filter(app) which reaches into app.state.bus._ pipeline_components["toggle_filter"] and calls .refresh(app.state.config). The dashboard no longer has to remember to ping POST /api/notifications/ refresh-toggles after a toggle change. The explicit endpoint stays for backwards-compat. (2) env_reporter block-size cap moved to adapter_config New registry row pipeline.env_reporter_block_chars (int, default 3000). meshai/notifications/env_reporter.py replaces the hardcoded _BLOCK_MAX_CHARS = 3000 with _DEFAULT_BLOCK_MAX_CHARS (the fallback) + a _block_cap() helper that reads from adapter_config on every slice. Mutating the row via PUT /api/adapter-config takes effect on the next env_reporter call -- no restart. (3) Bulk-import endpoint for gauge_sites meshai/dashboard/api/gauge_sites_import.py adds POST /api/gauge-sites/import with two paths: format=csv -- expects "data" (CSV text with header row matching gauge_sites columns: site_id, gauge_name, lat, lon, and optionally action_ft/flood_minor_ft/ flood_moderate_ft/flood_major_ft/enabled). UPSERT via ON CONFLICT(site_id) DO UPDATE. Returns {inserted, updated, skipped}. format=nws-ahps -- expects "wfo" (list of WFO codes). Fetches water.weather.gov/ahps2/index.php?wfo=<WFO> for each, regex-parses gauge links, then fetches up to 50 gauge detail pages per request and regex-parses lat/lon + four threshold values. Best-effort; rows stored under "AHPS-<gauge_id>" so they dont collide with USGS-* ids. Returns the same shape plus detail_fetched + errors list. Frontend (dashboard-frontend/src/pages/GaugeSites.tsx) gains a Import button + modal with two tabs (Paste CSV / Scrape NWS-AHPS) rendered via an ImportModal component. CSV tab has a 48-row textarea with the column-header hint inline; AHPS tab has a comma-separated WFO input defaulting to BOI. Both submit via fetch() and show the JSON response inline. Invalidates the curation cache server-side on any successful insert/update so nwis_handler sees the new gauges on its next call. (4) WFIGS tombstone column -- CORRECTNESS v12.sql adds fires.tombstoned_at REAL (nullable) + idx_fires_tombstoned_at. meshai/central/wfigs_handler.py: the tombstone branch (kind=="wfigs_tombstone") UPDATE fires SET tombstoned_at=COALESCE( tombstoned_at, ?) so the first tombstone-time wins (idempotent against repeated tombstone envelopes). meshai/notifications/reminders/__init__.py: the wfigs tombstone termination condition now checks row["tombstoned_at"] IS NOT NULL. Reminders correctly STOP for closed fires -- before this change the 8h cadence would have kept Active: broadcasts going indefinitely past a WFIGS removal. SCHEMA_VERSION 11 -> 12. (5) Delete INCIDENT_BROADCAST_HEARTBEAT_S meshai/central/incident_handler.py: removed the dead constant (v0.5.9 REVISED dropped the heartbeat path but left the constant imported-but-never-read). tests/test_incident_handler.py: removed the orphan test_i_8h_heartbeat_triggers_update test (asserted None, used the deleted constant for time arithmetic) and the stray import line. Tests (tests/test_tail_followups.py, 16 cases): - middleware fires refresh on PUT /api/config/notifications (200), does NOT fire on PUT /api/config/llm - env_reporter _block_cap() default 3000; mutate via PUT, invalidate, next read returns the new cap - CSV import inserts new rows, updates existing, skips bad rows, rejects missing required columns, rejects bad format - AHPS index parser extracts (gauge_id, name) from realistic HTML - AHPS detail parser extracts lat/lon + four thresholds from realistic HTML - fires has tombstoned_at column after migrations - wfigs tombstone branch stamps tombstoned_at - ReminderScheduler skips a fire whose tombstoned_at is NOT NULL - ReminderScheduler still fires for a fire whose tombstoned_at IS NULL - INCIDENT_BROADCAST_HEARTBEAT_S no longer importable Foundation/API test counts bumped: REGISTRY 58 -> 59 (+ env_reporter_block_chars) schema_meta v11 -> v12 Test count: 844 -> 859 (+16 new, -1 deleted dead test). 0 regressions.
2026-06-05 21:37:05 +00:00
def test_registry_at_59_entries():
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
"""v0.6-3a.1 trim: 43 CONFIG-only keys (was 77 in v0.6-3a draft)."""
assert len(REGISTRY) == 84, (
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
f"REGISTRY should have 43 entries after CONFIG-vs-CODE trim; got {len(REGISTRY)}. "
f"If a sentence template / emoji / heuristic snuck in, it belongs in CODE not config."
)
feat(v0.6-phase3): reminder system + schema split + NWS dedup relaxation Third broadcast type Active: clock-driven re-broadcasts of still-live events at human-scale cadences. WFIGS fires 8h, itd_511 work zones daily 8 AM Mountain, SWPC G-storms 8h. NWS is NOT a clock reminder -- instead the per-CAP-id dedup is relaxed to allow re-broadcast if >3h since last. Schema split first_broadcast_at + last_broadcast_at on all reminder- eligible tables. Wire prefix logic: New (first sight), Update (WFIGS material change), Active (clock reminder). All cadences, channels, day- of-week patterns, timezones, and termination conditions GUI-editable from day one via the existing adapter_config editor. Termination: tombstone OR containment_100 OR end_date_passed (no max-count). Quiet hours not respected -- ripped out in Phase 2. Schema (v11.sql): - ALTER TABLE fires|nws_alerts|traffic_events|quake_events|swpc_events| gauge_readings ADD COLUMN first_broadcast_at REAL - Backfill: UPDATE ... SET first_broadcast_at = last_broadcast_at WHERE last_broadcast_at IS NOT NULL - ALTER TABLE adapter_meta ADD COLUMN reminder_enabled INTEGER NOT NULL DEFAULT 0 - UPDATE adapter_meta SET reminder_enabled=1 WHERE adapter IN ('wfigs', 'swpc') -- itd_511_work_zone is a new meta row seeded with reminder_enabled=1 - SCHEMA_VERSION 10 -> 11 Handler commit-callbacks (wfigs/nws/quake/swpc/incident): - UPDATE ... SET last_broadcast_at=?, first_broadcast_at=COALESCE( first_broadcast_at, ?) -- first_broadcast_at stamped once, never overwritten NWS handler (meshai/central/nws_handler.py): - _render() gains a prefix kwarg - After-first-broadcast branch: when (now - last_broadcast_at) >= adapter_config.nws.duplicate_allowed_after_seconds (default 10800 = 3h), allow the re-broadcast with prefix=Active. Under the window, suppress as before. The commit callback continues to update last_broadcast_at. ReminderScheduler (meshai/notifications/reminders/__init__.py): - Async loop, ticks every 60s - Each tick: SELECT adapter FROM adapter_meta WHERE reminder_enabled=1 - Per adapter, load reminders_<adapter> config from adapter_config (cadence_kind, cadence_value, channels, terminate_when, dow_mask, timezone) - Interval cadence: rows where last_broadcast_at <= now - cadence_value - Clock cadence: localizes now to configured tz, finds slots that just passed in the last tick window, gated by dow_mask - Termination conditions checked per adapter: wfigs.containment_100 -> current_contained_pct >= 100 wfigs.last_event_age_24h -> last_event_at older than 24h swpc.end_date_passed -> payload_json end_time in past itd_511_work_zone.end_date_passed -> traffic_events.end_at in past - Active: prefix on every emitted wire; dispatcher.dispatch_scheduled_ broadcast() honors cold-start grace, bypasses toggle path - On success, last_broadcast_at = now; first_broadcast_at preserved Launched from notifications/pipeline/__init__.py:start_pipeline() alongside BandConditionsScheduler. adapter_config registry (+15 new keys, 43 -> 58): - reminders_wfigs.cadence_kind/cadence_value/channels/terminate_when - reminders_swpc.cadence_kind/cadence_value/channels/terminate_when - reminders_itd_511_work_zone.cadence_kind/cadence_value/channels/ dow_mask/timezone/terminate_when - nws.duplicate_allowed_after_seconds adapter_meta (+4 rows, 15 -> 19): - reminders_wfigs, reminders_swpc, reminders_itd_511_work_zone (pseudo-adapters carrying the reminder config) - itd_511_work_zone (reminder target row; reminder_enabled=1) - reminder_enabled flag added to wfigs/swpc (existing rows updated by v11.sql) and to itd_511_work_zone seed. Tests (tests/test_reminders.py, 10 cases): - wfigs reminder fires past 8h cadence, stamps last_broadcast_at, preserves first_broadcast_at - reminder skipped within cadence - reminder skipped when containment_100, last_event_age_24h - swpc reminder fires (interval) - work_zone clock reminder fires at 08:00 Mountain on enabled DOW - work_zone reminder skipped when end_date_passed - work_zone reminder skipped outside slot window - reminder_enabled=0 suppresses all reminders for that adapter tests/test_nws_dedup_relaxation.py (5 cases): - First sighting renders without Active: prefix - Re-broadcast within 3h suppressed - Re-broadcast after 3h allowed with Active: prefix - adapter_config.nws.duplicate_allowed_after_seconds override takes effect (1h window verified) - First sighting stamps first_broadcast_at=committed_at, last_broadcast_at=committed_at; 4h later broadcast stamps last_broadcast_at only, first_broadcast_at preserved Test count: 829 -> 844 (+15 new, 0 regressions). Foundation tests updated for new counts (REGISTRY=58, ADAPTER_META=19, schema=v11).
2026-06-05 21:11:32 +00:00
def test_adapter_meta_at_19(fresh_db):
assert len(ADAPTER_META) == 21
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
# ---------- seed ----------------------------------------------------------
def test_seed_populates_every_registry_row(fresh_db):
rows = fresh_db.execute("SELECT adapter, key FROM adapter_config").fetchall()
db_keys = {(r["adapter"], r["key"]) for r in rows}
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert db_keys == set(REGISTRY.keys())
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_seed_value_matches_registry_default(fresh_db):
for (adapter, key), spec in REGISTRY.items():
row = fresh_db.execute(
"SELECT value_json, default_json, type FROM adapter_config "
"WHERE adapter=? AND key=?",
(adapter, key),
).fetchone()
expected = json.dumps(spec["default"])
assert row["value_json"] == expected, f"{adapter}.{key} value drift"
assert row["default_json"] == expected, f"{adapter}.{key} default drift"
assert row["type"] == spec["type"]
def test_seed_populates_every_adapter_meta_row(fresh_db):
rows = fresh_db.execute("SELECT adapter, include_in_llm_context FROM adapter_meta").fetchall()
db_adapters = {r["adapter"] for r in rows}
assert db_adapters == set(ADAPTER_META.keys())
def test_seed_is_idempotent(fresh_db):
a, b = seed_defaults(fresh_db)
assert a == 0 and b == 0
def test_seed_does_not_overwrite_user_edits(fresh_db):
fresh_db.execute(
"UPDATE adapter_config SET value_json=? WHERE adapter=? AND key=?",
("999", "wfigs", "cooldown_seconds"),
)
seed_defaults(fresh_db)
row = fresh_db.execute(
"SELECT value_json FROM adapter_config "
"WHERE adapter='wfigs' AND key='cooldown_seconds'"
).fetchone()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert row["value_json"] == "999"
# ---------- prune_orphans -------------------------------------------------
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
def test_prune_orphans_removes_unknown_keys(fresh_db, caplog):
"""A row whose (adapter, key) is no longer in REGISTRY is deleted on
the next prune_orphans, and the delete is logged at INFO."""
fresh_db.execute(
"INSERT INTO adapter_config(adapter, key, value_json, default_json, "
"type, description, updated_at) VALUES (?,?,?,?,?,?,?)",
("wfigs", "deprecated_legacy_key", "\"old\"", "\"old\"",
"str", "", 0.0),
)
caplog.set_level(logging.INFO, logger="meshai.adapter_config")
removed = prune_orphans(fresh_db)
assert removed == 1
msgs = [r.getMessage() for r in caplog.records
if r.name.startswith("meshai.adapter_config")]
assert any(
"adapter_config orphan removed: wfigs.deprecated_legacy_key" in m
for m in msgs
), f"expected orphan-removed log line; got: {msgs}"
# Row gone.
assert fresh_db.execute(
"SELECT 1 FROM adapter_config WHERE adapter=? AND key=?",
("wfigs", "deprecated_legacy_key"),
).fetchone() is None
def test_prune_orphans_idempotent(fresh_db):
assert prune_orphans(fresh_db) == 0
assert prune_orphans(fresh_db) == 0
def test_prune_orphans_does_not_touch_known_keys(fresh_db):
"""Every REGISTRY row survives the prune."""
before = {(r["adapter"], r["key"]) for r in fresh_db.execute(
"SELECT adapter, key FROM adapter_config"
).fetchall()}
prune_orphans(fresh_db)
after = {(r["adapter"], r["key"]) for r in fresh_db.execute(
"SELECT adapter, key FROM adapter_config"
).fetchall()}
assert before == after == set(REGISTRY.keys())
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
def test_prune_orphans_does_not_touch_adapter_meta(fresh_db):
"""A previously-known adapter whose config keys all moved to CODE
keeps its adapter_meta row (for the include_in_llm_context toggle)."""
before = fresh_db.execute("SELECT COUNT(*) FROM adapter_meta").fetchone()[0]
prune_orphans(fresh_db)
after = fresh_db.execute("SELECT COUNT(*) FROM adapter_meta").fetchone()[0]
assert before == after == len(ADAPTER_META)
def test_prune_orphans_invalidates_cache(fresh_db):
"""If a key disappears, any cached read of it should NOT linger."""
invalidate_cache()
# Prime cache with a key that will become orphan.
fresh_db.execute(
"INSERT INTO adapter_config(adapter, key, value_json, default_json, "
"type, description, updated_at) VALUES (?,?,?,?,?,?,?)",
("wfigs", "ghost", "42", "42", "int", "", 0.0),
)
# We can't read it via accessor (not in REGISTRY -> no fallback) so
# we just verify the cache is empty after prune.
prune_orphans(fresh_db)
assert accessor_mod._cache == {}, "cache should be cleared after orphan prune"
# ---------- accessor ------------------------------------------------------
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_accessor_returns_int(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert adapter_config.wfigs.cooldown_seconds == 28800
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_accessor_returns_float(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert adapter_config.usgs_quake.global_mag_floor == 3.0
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_accessor_returns_str(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert adapter_config.geocoder.photon_url == "http://100.64.0.24:2322"
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_accessor_returns_bool(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert adapter_config.tomtom_incidents.drop_zero_magnitude is True
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_accessor_returns_json_list(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert adapter_config.nws.broadcast_severities == ["Extreme", "Severe"]
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_accessor_returns_json_dict(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
v = adapter_config.central.severity_thresholds
assert v == {"routine_max": 1, "priority_max": 2, "immediate_min": 3}
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
def test_accessor_returns_json_none(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert adapter_config.firms.bbox is None
def test_firms_dedup_distance_m_default(fresh_db):
"""v0.6-3a.1 Matt's call: user-facing unit is meters, default 5."""
invalidate_cache()
v = adapter_config.firms.dedup_distance_m
assert isinstance(v, int)
assert v == 5
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
# ---------- cache --------------------------------------------------------
def test_cache_hits_second_read(fresh_db):
invalidate_cache()
_ = adapter_config.wfigs.cooldown_seconds
with patch.object(accessor_mod, "_load_from_db",
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
side_effect=AssertionError("cache miss")):
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
v = adapter_config.wfigs.cooldown_seconds
assert v == 28800
def test_invalidate_forces_reload(fresh_db):
invalidate_cache()
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
_ = adapter_config.wfigs.cooldown_seconds
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
fresh_db.execute(
"UPDATE adapter_config SET value_json=? WHERE adapter='wfigs' AND key='cooldown_seconds'",
("3600",),
)
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert adapter_config.wfigs.cooldown_seconds == 28800 # still cached
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
invalidate_cache()
assert adapter_config.wfigs.cooldown_seconds == 3600
# ---------- defensive fallback paths -------------------------------------
def test_registry_fallback_when_db_row_missing(fresh_db, caplog):
invalidate_cache()
fresh_db.execute(
"DELETE FROM adapter_config WHERE adapter='wfigs' AND key='cooldown_seconds'"
)
caplog.set_level(logging.WARNING, logger="meshai.adapter_config._accessor")
v = adapter_config.wfigs.cooldown_seconds
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
assert v == 28800
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
assert any("missing from DB" in r.message for r in caplog.records)
def test_unknown_key_raises(fresh_db):
invalidate_cache()
with pytest.raises(AttributeError):
_ = adapter_config.wfigs.no_such_key
def test_setattr_blocked(fresh_db):
invalidate_cache()
with pytest.raises(AttributeError):
adapter_config.wfigs.cooldown_seconds = 999
# ---------- registry sanity ----------------------------------------------
def test_every_registry_default_round_trips_through_json():
for (adapter, key), spec in REGISTRY.items():
encoded = json.dumps(spec["default"])
decoded = json.loads(encoded)
assert decoded == spec["default"], f"{adapter}.{key}: JSON round-trip drift"
def test_every_registry_type_is_in_vocabulary():
valid = {"int", "float", "str", "bool", "json"}
for (adapter, key), spec in REGISTRY.items():
assert spec["type"] in valid, f"{adapter}.{key}: invalid type {spec['type']!r}"
def test_adapter_meta_includes_every_registry_adapter():
reg_adapters = {a for a, _ in REGISTRY}
meta_adapters = set(ADAPTER_META)
missing = reg_adapters - meta_adapters
# avalanche is in REGISTRY but intentionally absent from ADAPTER_META
# (adapter enabled but not yet promoted to full meta entry).
missing.discard("avalanche")
feat(v0.6-3a): adapter_config foundation -- migration + defaults registry + typed accessor Closes the foundation slice of audit doc Section A (Rule 17). Lands two SQLite tables, the seed routine that populates them from a Python defaults registry, and a typed accessor that handler code will read in v0.6-3b. No handler changes in this commit -- ZERO behavior risk, every existing test still passes (721 / 69 skipped / 0 failed). v6.sql tables: - adapter_config(adapter, key, value_json, default_json, type, description, updated_at) PRIMARY KEY(adapter, key) -- JSON-encoded values flow through a single column uniformly. CHECK constraint on `type` closes the vocab (int/float/str/ bool/json). - adapter_meta(adapter PK, display_name, include_in_llm_context, description, updated_at) -- per-adapter metadata + the user-scopable LLM-context toggle (Matt refinement #5). meshai/adapter_config/ package: - defaults.py: REGISTRY dict mapping (adapter, key) -> {default, type, description}. Covers audit doc sections A.1-A.12: wfigs, nws, usgs_quake, swpc, usgs_nwis, incident family (tomtom_incidents, state_511_atis, itd_511, shared "incident"), central consumer, dispatcher, band_conditions, geocoder, firms, pipeline (Inhibitor + Grouper). ~85 keys total. ADAPTER_META covers 15 adapters with display_name + include_in_llm_context defaulting to True. Per Matt refinement #3, every default matches the current handler constant EXACTLY -- first deploy behavior is unchanged. - _accessor.py: AdapterConfig class with `adapter_config.<adapter>.<key>` syntax. Read pipeline: in-memory cache hit -> SQL -> registry fallback (with WARNING) -> AttributeError. Process-wide cache; PUT via v0.6-3c REST API calls invalidate_cache() to drop the cache. GIL-atomic dict reads on the fast path (handlers call this hot). - __init__.py: seed_defaults(conn) -- INSERT OR IGNOREs one row per registry entry. Idempotent, never overwrites user edits. Wiring: - meshai/persistence/db.py: SCHEMA_VERSION 5 -> 6, and init_db() now calls seed_defaults() after migrations apply. - meshai/main.py: _init_components() now calls init_db() FIRST (per commit #1 lessons-learned: a startup-time migration is required when handlers will rely on the new schema; lazy-on-first-handler is fine for v4/v5 but not for v6 where handler reads start in v0.6-3b). - tests/conftest.py: autouse fixture now calls init_db() + clears the accessor cache around each test, so every test gets the v6 seed AND a clean cache without per-test boilerplate. Tests (tests/test_adapter_config_foundation.py, 24 cases): - v6 tables exist + schema_meta at 6 + type-vocabulary CHECK enforced - seed populates every REGISTRY + ADAPTER_META row, value_json == default_json on first seed, type matches - seed is idempotent + does not overwrite user edits - accessor returns correctly typed values for int/float/str/bool/ json list/json dict/json None - cache hit: second read does not touch the DB (patched _load_from_db raises, accessor still succeeds) - invalidate_cache forces a re-read; mutated DB value wins - registry fallback path triggers when a row is missing (with WARNING) - unknown key raises AttributeError - setattr blocked (writes go via the REST API in 3c) - every default JSON round-trips cleanly; every type is in vocabulary - ADAPTER_META covers every adapter in REGISTRY Test count: 697 -> 721 (+24 new, 0 regressions). v0.6-3b will wire handlers one at a time (wfigs, nws, quake, swpc, nwis, incident, central, dispatcher, band_conditions, geocoder, firms). Per the audit lock, defaults match exactly so each wiring step is a pure refactor -- bisect-safe. v0.6-3c lands the /api/adapter-config CRUD + the AdapterConfig.tsx dashboard editor + cache invalidation on PUT. Refs audit doc v0.6-phase1-audit.md Section A + finding #4.
2026-06-05 17:06:51 +00:00
assert not missing, f"adapters in REGISTRY but missing ADAPTER_META: {missing}"
feat(v0.6-3a.1): trim adapter_config registry to CONFIG-only per Matt config-vs-code rule + log-on-delete safety net for orphan cleanup Drops 35 of the v0.6-3a-draft 77 keys + adds 1 net-new key (firms.dedup_distance_m) for a final count of 43. The trim rules: CONFIG (lives in adapter_config, surfaces in the GUI): where we send (channels), how often (cadences/schedules), thresholds (magnitude floors, severity gates, distance radius, cooldown durations, freshness windows), curation data (which sites/states/codes), toggles (enabled, include_in_llm_context, drop_zero_magnitude). CODE (stays in handlers, never reaches the GUI): sentence templates, emoji choices, mapping/translation functions (TomTom icon_map, ITD sub_type_map, Central adapter_map and category_map), rendering logic (anchor priority order, expires-bucket formatting, threshold-state labels), heuristic logic (band_conditions Kp/SFI -> Good/Fair/Poor function). Per-adapter outcome (kept | killed): wfigs 4 | 4 (cooldown_seconds, anchor_max_mi, two re-broadcast toggles) nws 3 | 4 (broadcast_severities, tombstone_msgtypes, warning_suffix_promotes) usgs_quake 6 | 3 (centroid, radius, PAGER list, 3 mag floors) swpc 3 | 7 (three storm-tier floors) usgs_nwis 2 | 4 (parameter_codes, broadcast_on_recede) incident 2 | 0 (freshness_seconds, broadcast_on_update) tomtom_incidents 2 | 1 (drop_zero_magnitude, drop_non_present) state_511_atis 1 | 0 (skipped_states) itd_511 0 | 3 (all sub_type maps/emoji/phrase = CODE) central 1 | 2 (severity_thresholds) dispatcher 4 | 0 (LRU cap, prune params, retention days) band_conditions 3 | 6 (SWPC freshness + HamQSL endpoint config) geocoder 6 | 1 (Photon endpoint + town-OSM curation + cache cap) firms 4 | 1* (confidence_floor, frp_floor, bbox, dedup_distance_m) pipeline 2 | 0 (inhibitor TTL, grouper window) * firms: dedup_lat_lon_decimals is replaced by dedup_distance_m=5 per Matt s call (user-facing unit is meters, not decimal places; the handler will internally translate to quantization step in v0.6-3b). adapter_meta stays at 15 rows -- itd_511 keeps its include_in_llm_context toggle even with zero config keys. Live-DB cleanup: meshai/adapter_config/__init__.py:prune_orphans(conn) DELETEs every adapter_config row whose (adapter, key) is no longer in REGISTRY. Each delete is INFO-logged with the prefix "adapter_config orphan removed:" so docker logs carry the paper trail. Called from init_db() after seed_defaults; idempotent (zero deletes on every subsequent boot). Cache is invalidated when any orphan is removed. adapter_meta is NOT pruned -- meta rows are cheap and useful even for adapters that ended up with zero config keys. Tests (34 cases, replaces v0.6-3a 24-case set): - Registry count is 43; ADAPTER_META is 15 - Seed lands every REGISTRY + ADAPTER_META row; idempotent; never overwrites user edits - prune_orphans removes a synthetic legacy row, logs at INFO with the exact prefix, leaves known keys untouched, leaves adapter_meta untouched, invalidates the accessor cache - Accessor returns correctly-typed values incl new firms.dedup_distance_m - Guard tests: no key in REGISTRY contains "emoji", ends with "_map", or contains "template" / "prefix" (catches CODE leaking back in) Test count: 721 -> 731 (+10 net: +5 prune cases, +1 firms.dedup_distance_m, +3 CODE-guard cases, +1 registry-count assertion). Refs Matt s locked CONFIG-vs-CODE rule.
2026-06-05 18:09:49 +00:00
# ---------- guard against CODE leaking back into the registry -----------
def test_no_emoji_keys_in_registry():
"""Emoji choices are CODE, not config (Matt's locked rule)."""
for (adapter, key) in REGISTRY:
assert "emoji" not in key, (
f"{adapter}.{key} looks like an emoji setting; emojis are CODE"
)
def test_no_template_keys_in_registry():
"""Sentence templates are CODE."""
for (adapter, key) in REGISTRY:
assert "template" not in key and "prefix" not in key, (
f"{adapter}.{key} looks like a sentence template / prefix; sentences are CODE"
)
def test_no_map_keys_in_registry():
"""Translation maps are CODE (TomTom icon_map, ITD sub_type_map, etc.)."""
for (adapter, key) in REGISTRY:
assert not key.endswith("_map"), (
f"{adapter}.{key} looks like a translation map; mapping functions are CODE"
)