Necesidades: no se seleccionan de a 1 (multi-select roto)

Sub-tickets

Activity

• system created · 2026-05-11
  wi cli
• coder-ayudarg-cc assigned · 2026-05-12
  assigned to coder-ayudarg-cc
• system statusChanged · 2026-05-12
  PM dispatch (chained after 283)
• system statusChanged · 2026-05-12
  investigating multi-select
• system blocked · 2026-05-12
  code looks correct; need client repro/clarification (multi-select bug vs UX expectation)
• rob questionAsked · 2026-05-12
  q#16 to=elazar: Coder says the multi-select code looks correct (Set+toggle). Two interpretations: (a) real bug where clicking selects all/none, or (b) UX mismatch — client expects single-select (picking comuna 3 shou
• rob blocked · 2026-05-12
  awaiting elazar
• system commented · 2026-05-12
  Auditor independently confirmed code is correct (no Set ref mutation, no type coercion, single handlers, immutable updates). Two reviewers agree: bug doesn't reproduce in code; likely UX expectation mismatch.
• system commented · 2026-05-12
  Client confirmed (pluto fwd 19646): map needs-selection cannot reset to zero. Likely the same single-select-expectation hypothesis — needs UX change to allow clear/reset.
• coder-basquetwi-cc note · 6w ago
  QUESTIONS FEATURE RETIRED (Elazar directive, 2026-09-02). This item carried open bwi question q#16; 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 Tue May 12 2026 02:49:47 GMT+0000 (Coordinated Universal Time) by rob, assignedTo elazar: Coder says the multi-select code looks correct (Set+toggle). Two interpretations: (a) real bug where clicking selects all/none, or (b) UX mismatch — client expects single-select (picking comuna 3 should replace comuna 5, not stack). Which is the actual behavior the client saw? A screenshot/video helps. Same question applies to WI 279 (comunas).