BWI-10 ·
basquetwiwi ask: drop hardcoded assignedTo='elazar' default + retire stale_elazar_questions_gt_7d doctor check (OPS-16 code part)
- Ref
BWI-10(#1056)- Project
basquetwi- Status
- todo
- Priority
- normal
- Type
- chore
- Assigned
- coder-basquetwi-cc coder
- Created by
- wi-cli-whey
- Created
- 2026-06-14T06:40:24.721Z
- Updated
- 2026-06-14T06:40:40.219Z
Questions
No questions.
Event log
-
MSG-36/2026-06-14: Elazar Qs go by direct DM now; 'wi ask' is agent/PM-audience only. Docs already scrubbed (ee66b40). Code (your lane): 1. cli-scripts/wi:312 & :628 — change default assignee from 'elazar' to: the WI's current assignedAgent; if that's NULL, ERROR requiring explicit --to (don't silently fall back to elazar). 2. cli-scripts/wi-http-server.mjs:411 — same: replace `b.to || 'elazar'` with b.to ?? row.assignedAgent, and 400 if both null. 3. cli-scripts/wi:740-748 and wi-http-server.mjs:502-504 — remove stale_elazar_questions_gt_7d; replace with a generic audience-agnostic 'open_questions_gt_7d' (any assignedTo) so we keep a stale-Q drift signal without the elazar special-case. 4. cli-scripts/wi:95 help text — update '(assignedTo=elazar)' to reflect new default. Keep wi + wi-http behavior in lockstep. No PG schema change (assignedTo column stays; only the app default logic changes). Ping me with the diff before push.
-
Spec'd + assigned coder-basquetwi-cc; ready to start