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)

Sub-tickets

Activity

• wi-cli-whey created · 2026-06-06
• wi-cli-whey parentChanged · 2026-06-06
  parent=#698
• wi-cli-whey questionAsked · 2026-06-06
  ONEDB-10 venus-kpi pg-flip is a fork decision, not a mechanical edit. venus-kpi-collect.sh is a stale BUGGY fork of kpi-enforce.sh (the canonical whey collector that already does keep-sqlite+pg-mirror correctly and fixed the FK/rowid + dead-DM bugs the venus script still has). Pick: (A) port just the mirror pattern into venus-kpi-collect.sh — minimal, but keeps a 2nd buggy script alive (its FK/dead-DM bugs need fixing anyway = scope creep); or (B) make kpi-enforce.sh host-aware (whey: memory_lint+backup_whey / venus: memory_lint+disk+systemd, gated on HOST), RETIRE venus-kpi-collect.sh, venus runs the canonical script. One collector, buggy fork dies, pg-mirror free. Touches whey's live collector. I recommend B. host col namespaces rows so no double-count either way.
• wi-cli-whey blocked · 2026-06-06
  blocked by question #50
• coder-basquetwi-cc note · 6w ago
  QUESTIONS FEATURE RETIRED (Elazar directive, 2026-09-02). This item carried open bwi question q#50; the question row has been DELETED and `wi ask`/`wi answer`/`wi pending` no longer exist. Elazar's reason, verbatim: "the question feature is not working. i dont check it, i just ask each agent in cli." Four of the five open questions were addressed to elazar, who does not read the queue - so the queue was holding items in `blocked` against an answer that was never coming. THE ITEM'S STATUS AND blockedReason ARE UNCHANGED by this: it is another lane's row and only the question row was mine to remove. If it is still blocked on this, ask the person in CLI and unblock it yourself. Preserved verbatim so the text survives the deletion -- asked Sat Jun 06 2026 19:35:52 GMT+0000 (Coordinated Universal Time) by wi-cli-whey, assignedTo elazar: ONEDB-10 venus-kpi pg-flip is a fork decision, not a mechanical edit. venus-kpi-collect.sh is a stale BUGGY fork of kpi-enforce.sh (the canonical whey collector that already does keep-sqlite+pg-mirror correctly and fixed the FK/rowid + dead-DM bugs the venus script still has). Pick: (A) port just the mirror pattern into venus-kpi-collect.sh — minimal, but keeps a 2nd buggy script alive (its FK/dead-DM bugs need fixing anyway = scope creep); or (B) make kpi-enforce.sh host-aware (whey: memory_lint+backup_whey / venus: memory_lint+disk+systemd, gated on HOST), RETIRE venus-kpi-collect.sh, venus runs the canonical script. One collector, buggy fork dies, pg-mirror free. Touches whey's live collector. I recommend B. host col namespaces rows so no double-count either way.