* feat(web): add clearAnswer + submit re-entry guard to useClarificationGroup
clearAnswer removes a stored answer so emptying a clarification draft can
revert the stepper to "unanswered". A small inflight ref in submitCollected
/ skipAll prevents duplicate POSTs when multiple submit paths race (e.g.
Cmd+Enter inside the custom input commits the draft and also asks the
parent to finalize the batch).
* feat(web): show selected state and Cmd+Enter submit on clarification custom input
The "Or type a custom answer…" input previously had no selected styling and
needed an Enter keypress before the carousel stepper marked the question as
answered, which made it easy to lose track of which path was the active
answer. Now:
- Typing into the custom input live-records the draft, so the stepper and
group progress update immediately and the input picks up the same blue
ring + check icon used by selected options. When custom is active, any
previously picked option visually deselects (they are mutually exclusive
at commit time).
- Picking an option after typing wipes that question's draft so the visible
input and committed answer stay in sync.
- Cmd/Ctrl+Enter submits the bundle when every question is answered — from
inside the custom input (commits the draft then finalises) and from
anywhere else in the overlay. Inside the input is handled locally so
submitCollected does not fire twice.
* test(web): cover live-record + Cmd+Enter clarification UX
Adds four cases over the existing clarification-multi mock scenario:
typing auto-selects custom and deselects the option, emptying the draft
reverts the stepper, Cmd+Enter from the last-step custom input submits
the bundle, and Cmd+Enter from outside the input submits when all answered.
Adds a session-page locator for the new custom-input container so the
data-active attribute can be asserted.
* fix(web): address bot review feedback on clarification UX
- Cmd/Ctrl+Enter inside the custom-text input no longer calls the
per-question commit path. The draft is already live-recorded via
onChange, so calling onSubmit here only added a stale advance-to-next
step before the bundle was submitted. Now Cmd+Enter just finalises.
- handleSubmit depends on group.submitCollected (which the hook memoises)
rather than the whole group object, so it no longer re-creates on every
keystroke through the live-record path.
- Add a unit test that fires submitCollected twice concurrently and
asserts the inflight ref keeps the wire count at 1 — direct coverage
for the guard introduced in the previous commit instead of relying on
the 409 round-trip test.
José Almeida
af9d3547a6