max / quasi

Add Action::navigates: performing this replaces the whole document `00ee7af5`, ruled 2026-08-25: a member on `Action`, not a fourth `Destination`. Nothing in the vocabulary said "performing this replaces the whole document": `Action::replaces` names a region and a document is not one. The ruling went knowingly against `f35aafee`, which put the sibling fact on the destination. What differs between a navigation and a fragment swap is what happens to the document, and the document is the action's business; where it goes is the same place either way. `quasi-webview` narrows rather than adds. A read of a route already emits an `href` beside the verb, for middle-click, copy-link, crawlers and JS off; a navigating act keeps that anchor and drops the verb, the trigger and the swap, which would otherwise morph a whole screen into the page it was meant to leave. Guarded on the same conditions that anchor is, plus two the anchor cannot carry the meaning of: an `hx-confirm` is htmx gating the request, and `saves` says the answer is a file. Either one and the transport is emitted as it was. `quasi-tui` pushes a screen and `quasi-immediate` swaps its view, which in both is the same sentence: the call is made and whatever is open over the place being left is put away before it goes out, rather than left floating over wherever the answer lands. `hx-target` is still emitted for `Action::replaces` and nothing else. Breaking, so 0.58.0, with the consumer pins moved in the same pass.