- Ya
- 27 Agosti 2026, 08:50 UTC
- Mwandishi
- kamo
- Ahadi ya
- 44dcfed
app/patients/** was in no vitest include pattern, so a test written beside the clinical console's own kit was collected by nothing and would have passed by never running. That kit is component code that happens not to live under app/components — the shared primitives, and the dialog eight screens route their audit reasons through. Eleven cases on the dialog, all on behaviours whose absence is silent: an empty or whitespace reason cannot be submitted; the reason is trimmed; it is CLEARED on every opening, because a reason typed for one patient arriving on another's record is the failure mode with no visible symptom; the consequence stays on screen while the reason is typed, which a prompt could never do; Ctrl+Enter submits while plain Enter inserts a newline, because these are prose; every exit is refused while the write is in flight; and the dialog is announced by its own heading rather than as "dialog". One of these caught my own wrong assumption rather than a bug: the confirm button stops saying "Stop" and starts saying "Saving…" while busy, which is right — a button still offering the action invites a second click on something already happening.