context.v_kpi_compact_7d counts a failed-read sentinel as a real sample, splitting over-cap episodes

ONEDB-19 one-db Backlog high

one-db: 5 telemetry sqlite -> Postgres17 consolidation (umbrella)

ONEDB-1 one-db Backlog high

GATE#1 step v: remote-monitor ingestion — venus/lezama write whey-pg DIRECTLY per-host (NO ssh-pull). Transport: venus=ZeroTier 172.27.178.27 or Tailscale; lezama=ssh -w L3 tunnel only (GCABA blocks ZT+TS), pg client→172.30.0.1. whey: listen_addresses + pg_hba for both + telemetry_rw role. nw co-owns

ONEDB-12 one-db Backlog high ↳ ONEDB-2

DECISION (Elazar): kpi.pensanta.com exposure - Tailscale-only (team rec: bind whey tailnet IP, no TLS/cert ops, no public attack surface) vs public-TLS

ONEDB-6 one-db Backlog high ↳ ONEDB-5

GATE#1 step iii: flip venus-kpi-collect.sh to pg-write (telemetry_rw via metrics_write) — kills kpi.sqlite split-brain co-writer; nw lane (cross-host)

ONEDB-10 one-db Blocked high ↳ ONEDB-2

GATE#1 step i: add reporter-set pg views to schema.sql (network v_history/v_report/v_by_wifi; kpi 3-day window) — distinct from coder's dashboard views; back the 5 sqlite readers

ONEDB-8 one-db Backlog high ↳ ONEDB-2

GATE#1 step ii: repoint 5 sqlite readers to pg telemetry_ro — netreport.sh, testnetwork --report, ccusage-daily-kpi.sh, llmmsg-kpi-report.sh, memory-lint.sh

ONEDB-9 one-db Backlog high ↳ ONEDB-2

Lezama context/token telemetry -> venus canonical store

ONEDB-16 one-db Backlog

collector races DNS at boot: one psql name-resolution failure for venus.pensanta.com

ONEDB-18 one-db Backlog low

cc-context-monitor v3.0 M1 sys.exit(1) aborts MANUAL venus/lezama runs before pg-mirror write when CCM_HUB_URL=127.0.0.1 default. Unattended unaffected (service unit exports LLMMSG_HUB_URL ZT/tunnel). Fix post-ONEDB-12: document manual-run env requirement (export LLMMSG_HUB_URL) over per-host CCM_HUB_URL remap. Bump VERSION.

ONEDB-13 one-db Backlog low