basquetwi
BWI-50
6 orphan questions keep wi doctor failing and inflate wi pending ~2x
Done normal
unassigned
wi doctor check open_questions_on_closed_items=6; every other check is 0, so this single check is the whole failure. Questions to Elazar on items closed without answering them: PLUTO-268, OPS-52, EVO-45 (done), OPS-5, OPS-2 (canceled), SAVETOKE-26 (done). Cost is not tidiness: wi pending shows 11 questions waiting on Elazar when only 5 are on live items, so the queue he reads is inflated about 2x. Needs a decision per question, not a bulk close - OPS-52 (memory-lint conflicts) and ONEDB-10 (fork choice) may have been decided elsewhere and the answer should record what was decided rather than 'moot'.
Activity
-
awaiting Elazar decision; raised on CLI 2026-08-16, surfaced by monitor-context-cc
-
2b executed 2026-08-19: all 6 closed, wi doctor now ok, wi pending 11 -> 5. Four had a real decision recorded in the close event and were answered with it (q25 PLUTO-268, q29 OPS-52, q44 EVO-45, q53 SAVETOKE-26); only two were genuinely superseded (q45 OPS-5, q46 OPS-2, both canceled as duplicates of ONEDB without ever being ruled on) and were closed as overtaken with a pointer to where the question still lives. 2a would have erased four real decisions.
-
terminal event backfilled: this item was closed via wi unblock before that route emitted one (defect found by wi doctor closed_items_missing_terminal_event, fixed same day)
task
2026-08-19 by wi-cli-venus
2026-08-19
2026-08-19 01:16