Draft responses — a blank Clara left cannot be sent
The blank is highlighted in the editor, the card says what to do, and Send stays off until it is filled.
4 Nov 2026 · branch draft-blank-guard · captured against propflow-stage · at 598955ae3ba+local
Data note. Every name and balance below comes from propflow-stage, which is anonymized by construction (ADR-0097/0110 — phones in the impossible +1000 NPA, emails @example.test). The identical capture against prod would carry real tenants' names and balances and is not safe to attach anywhere, which is why the generator refuses to run against one.
1 · Clara's draft with a blank (the component's gallery variants, branch build)
The variant Clara's draft left a blank: the bracketed part is highlighted in place inside the editor (amber, behind the words), the line under the editor says to fill it in, and Send is off. Clara still writes the blank instead of guessing the rent; the teammate fills it in the same box, and Send turns on.
Asserted in the captured DOM — SEND STAYS OFF UNTIL IT IS FILLED · Fill in the highlighted part before sending.. The variant's label (rendered upper-case) and the note under the editor.
Sections 2–2 and notes
2 · Phone width
Same card at 390px: the highlight follows the wrapped line.
Asserted in the captured DOM — Fill in the highlighted part before sending.
What this does not show
Captured from this branch's own dev server on stage data, rendering the component gallery's variants on a local-only page: the gallery itself now lives in the dev-tools zone, whose gate does not extend the smoke login's MFA exemption. The server refusal (a stale client or a direct call) is pinned by tests on the staff-draft Send and the send-instead door. The live panel on the motivating thread is checked read-only after deploy; nothing is pressed there.