max / quasi

Add quasi-axum: the first host adapter Turns an HTTP request into a path, a verb and a bag of named values, hands them to the router, and turns the answer back into a response. - Mounts as a fallback, so quasi matches paths and axum does not. One matcher rather than two that have to agree, and real axum routes merged in front keep serving what a description has no word for. - Decodes query strings and form bodies, keeping repeats, because a checkbox group submits one name several times. Body beats query, path capture beats both. - Calls the router on a blocking thread, per decision 6. - A class becomes a status code and a notice becomes the body, from one return value, so an operator's tooling and the user's screen read the same event. A panicking handler is a 500 that reads as ours. - A fragment's region becomes HX-Retarget. It emits no markup. Render is a parameter because the Tauri protocol adapter serves HTML to a webview too, and generating it here would guarantee a second implementation; whole-screen markup is makeover-webview phase B. The htmx module carries the response-handling gap decision 9 opened: htmx 2's default does not swap a 4xx, so a classified error would render nothing. RESPONSE_HANDLING and CONFIG_META are the fix, checked against each other by a test.