max / quasi

Add Sought::Save, and answer one ask with every file picked Two findings from the audiofiles picker conversion, both ruled by Max on 2026-08-25 as vocabulary rather than host-side work. They are separate questions: one is about the ask, the other about the answer. `7fda7ae3`. `Sought` had three read pickers and no way to say the reader is naming a file that does not exist yet, so the classifier export, which opens a save dialog seeded with `{export_name}.afcl`, had nowhere to put its suggested name. `Sought::Save` carries the name and an accept list, using `Accepted` the way `File` and `Files` do. The note that said a save dialog was `Outcome::File`'s is corrected in place: that member is a payload that exists when the route answers, this is a destination chosen before there is anything to put in it. `8a246c02`. `Locating::answered` took one handle, so a `Sought::Files` ask was answered once per file and every host half wrote the loop. It now takes every `Picked` and builds one request, with the handles repeating under `under` and their labels beside them, which is what `Params` is a list of pairs for. There is deliberately no single-handle method left: the door is what produced the loop. Answering with no picks is no call, which is what a cancelled dialog is. The cascade: quasi-http refuses each shape by name now rather than the class, so a browser and a Tauri window say which dialog they cannot open; quasi-tui states the terminal's fallback for a save, which is the working directory joined to `safe_file_name` of the suggestion, said out loud; quasi-immediate states the native save dialog and the fallback for a host without one. Tests at the router, http, tui and immediate levels. Breaking, so 0.62.0 to 0.63.0 across the workspace and in the template's pins. The consumers (goingson, audiofiles, MNW server) are still on 0.62 and are the next pass; a push is blocked by the internal-deps gate until they move.