max / quasi

0.32.0: a call the host makes, and the renderer does not `a81384d4`, ruled by Max 2026-08-18 as option (a). Found starting mnw-server's audio upload, which is the first description in the tree whose destination a renderer cannot call. `f7261a5a` settled the four axes of an upload and this is none of them. The accept list, the multiplicity, the destination and the progress were all expressible; who performs the destination was not. An MNW upload is three requests, not one -- ask the server to sign a URL, PUT the file to storage with it, tell the server it landed -- and thirteen files across `static/` and `frontend/src/` run that chain against three route families. A renderer posting the field to the first of those is wrong about the response shape and about where the bytes go. `Action::by_host` says so, and it is `Action::saves`' shape rather than a new principle: a named attribute the host acts on, because there are calls a renderer cannot make and the alternative to saying so is a host reaching around the description to a control the description owns. quasi-webview emits `data-sends` with the address and no transport at all -- no verb, no trigger, no href. `data-sends` and not `data-action`: what is named is where the thing goes, which is the half the description knows. Two things that would have been silent if they were wrong, so both have a test. The payload travels as `data-vals`, since `hx-vals` is htmx's and htmx is not involved here; dropping it would be the description saying something the markup did not carry. And the wait survives while the lock does not -- `data-awaiting` is a fact about the call, `hx-disabled-elt` is htmx locking a control on a request it is making, and this is not one. That split the old block in two, so `awaiting_attrs` is now its own function. quasi-tui refuses one rather than making it wrongly. Pressing a control marked this way says "this app cannot do that here" and calls nothing: the address is a signing endpoint that answers JSON, and a terminal asking it for a screen would swap the signature it got back. Announced on the spot, because no navigation is coming to carry the message later. The cost is written onto the member rather than left to be discovered: a call marked this way is not portable, and that is permanent. A terminal meeting a described upload learns the accept list, the multiplicity and that it waits, and has nothing to perform. That is what the ruling bought for keeping the file going browser-to-storage instead of through the production box, which would otherwise proxy half-gigabyte bodies it does not proxy today.