max / quasi

0.29.1: a waiting form locks its button, not itself Task 930947c3, found starting mnw-server's Shape 7 adoption (0da6a218). An Action carrying awaiting emitted hx-disabled-elt="this" wherever it landed, and on a Node::Form that lands on the <form>. htmx sets the disabled attribute on whatever the selector resolves to; <form> has no such attribute and it does not reach the controls inside the way <fieldset disabled> does. So a form marked as waiting emitted a double-submit guard that permits a double submit, which is worse than none: a consumer adopts the mark by deleting a hand-rolled guard that works. Fires::Submit says what a form fires on, which htmx already defaulted to and the markup never stated, and Fires::guards answers what a wait on that trigger locks. Everything gesture-shaped stays "this". A form names its button. The button and not every control inside it: the button is what has to stop answering, and locking the fields would take the text away from a reader still correcting it. The existing coverage only ever built an Act, which is how a button-shaped assumption reached a form. The new test builds a Form and asserts the button it names is really there, spelled the way the selector spells it.