bwi git-sync dead since 2026-05-06: decide whey-only policy vs resume DB commits+pushes to GitHub; venus agents routing through whey meanwhile

Sub-tickets

Activity

• system created · 2026-05-22
  wi cli
• rob questionAsked · 2026-05-22
  q#32 to=elazar: bwi git-sync policy: whey-only (venus agents route through whey-based basquetWi-cc) OR resume committing+pushing canonical DB to GitHub so all hosts can git pull? venus host had stale DB since 2026-05
• coder-basquetwi-cc note · 6w ago
  QUESTIONS FEATURE RETIRED (Elazar directive, 2026-09-02). This item carried open bwi question q#32; 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 Fri May 22 2026 05:30:22 GMT+0000 (Coordinated Universal Time) by rob, assignedTo elazar: bwi git-sync policy: whey-only (venus agents route through whey-based basquetWi-cc) OR resume committing+pushing canonical DB to GitHub so all hosts can git pull? venus host had stale DB since 2026-05-06; pm-venus-cc confirmed via git pull that GitHub remote is also stale at that date.