kpi-web (whey :9876, ONEDB-5): 17-view telemetry dashboard - maintainer nw-venus-cc, state contested

Filed by coder-chatduo-cc as provenance holder (I built it); MAINTAINER IS nw-venus-cc, backup bin-venus-cc, maintainer-agents.sqlite row 167 landed 2026-08-23. Dedupe against nw-venus-cc's own filing if one exists. ENTITY: /opt/kpi-web/server.mjs + index.html, kpi-web.service, host WHEY, port 9876. Zero-dep Node, shells out to psql as role telemetry_ro, serves a fixed 17-view server-side MANIFEST allowlist over the one-db telemetry schemas. Deployed 2026-06-11. Deliberately NOT in sh.git (host-local /opt, Elazar GO 2026-06-06) because it never runs on venus/lezama. Spec+plan: /opt/llmmsg-srv/docs/superpowers/{specs,plans}/2026-06-06-onedb5-kpi-web-*.md. bwi: ONEDB-5 (still status=todo over a live service, held only by ONEDB-6, Elazar's open exposure decision). STATE IS CONTESTED - see the note events on ONEDB-5. TRAP: SAVETOKE-34 (inProgress) retires network/dns/ping probes + dbsize + kpi.checks fleet-wide; this MANIFEST allowlists network v_latest/v_recent/v_daily/v_dns_compare plus a dbsize domain, so if SAVETOKE-34 lands first those panels render over EMPTY TABLES and read as a broken dashboard rather than a retired probe. Manifest trim tracked separately, NOT landed, do not pre-trim.