MSG-19 ·
llmmsg-srveq stale-removal: one-click dismiss/stale in chat-duo Pending pane + auto-stale sweep (auto-dismiss when ref_bwi closes / N-day age)
- Ref
MSG-19(#870)- Project
llmmsg-srv- Status
- done
- Priority
- normal
- Type
- feature
- Assigned
- coder-chatduo-cc coder
- Created by
- wi-cli-whey
- Created
- 2026-06-10T03:25:54.397Z
- Updated
- 2026-06-14T06:11:46.021Z
- Closed
- 2026-06-14T06:11:46.021Z
Questions
No questions.
Event log
-
Elazar need (2026-06-10, aro:infra): 'a way for old questions no longer relevant to be removed from Elazar Pending.' Triggered by a now-moot Namecheap-DNS pending Q. FINDING: the BACKEND capability already exists - elazar_questions.status supports open|answered|stale|dismissed, with eq_dismiss + eq_stale MCP tools/routes. Current queue: 0 open (14 answered, 5 dismissed). So this is NOT new backend - the gap is SURFACING + AUTOMATION: (1) chat-duo Pending pane (coder-chatduo-cc) needs a one-click dismiss/mark-stale action per row, so Elazar can clear an irrelevant Q without answering it; (2) optional auto-stale sweep (hub-llmmsgsrv-cc): auto-dismiss an open Q when its ref_bwi closes, and/or mark stale after N days (wi doctor already flags Elazar Q >7d - reuse that signal). (3) Consider letting the ASKER agent self-dismiss its own Q when mooted-elsewhere (bin could've dismissed the Namecheap Q once pensanta records went live). UI part is primary; auto-sweep is the durable fix.
-
Closed moot by MSG-36 — eq / Elazar Pending feature stripped fleet-wide (Elazar directive 2026-06-14). No queue to expire/stale-sweep/nudge-adoption-for anymore.
-
completed