max / quasi

0.51.0: a suggestion carries a second line, and picking is local by default Two rulings, one cascade, both by Max 2026-08-21. `1fcf2e9b`: `Outcome::Suggestions` carries `Candidate` rather than `Choice`. The two are near-identical and the mitigation is written on the type: an option and a candidate are submitted the same way and read differently. An option is picked out of a set the user can see whole; a candidate is offered out of a set nobody can see, so it carries what tells it from a row that reads alike. Both measured sites draw that string today by hand, in a second span, and MNW's tag box computes it as the parent path because "Format" is a leaf under audio, software, writing and video. This reverses what response.rs argued at 0.45.0 -- "a candidate is submitted under one string and read under another, which is what an option is". True, and never the half that differed. That paragraph is rewritten rather than left standing; a doc that argues against the shipped design is how the next session re-derives the rejected option. The "picking is local, by definition" paragraph on `Field::suggests` goes the same way. `ed1fa86f`: `Candidate::picks` carries an action, and absent one picking writes the value. Local stays the default, so every site that exists today is unchanged. It lands on `Candidate` rather than `Choice`, which is what makes it affordable: a per-row action on the most-consumed struct in the vocabulary would have reached every option list in the tree. `Candidate` is `#[non_exhaustive]` from birth and carries no `unavailable` -- a suggestion that cannot be picked is a row a route should not have offered. It also carries no `Hash`, unlike `Choice`, because an `Action` is not hashable. `picks` does not survive `as_layout`: the description layer has no `Action`, exactly as it has no `suggests`. Three renderers, three answers to the same description. The terminal draws the detail as the rest of the row, egui appends it dimmed in the same button, the webview gives it its own element because it is styled apart and is not part of what the typed value matches. Each renderer's pick path grows one branch, and the webview's acting row keeps the closing half of the hyperscript program and none of the writing half, with htmx emitting what the click does. Performed with no payload rule invented for this one place: an action already carries its own params and the view it was offered under. MNW's search box is what decides it -- its candidates are `Action::get(url)` to a project, item or creator page, and appending the typed value would be a description saying something the route never asked for. Also here: the template's quasi pins move to 0.51, its `makeover-build` pin off a stale 0.47.0 onto 0.49.0, and its `makeover-tui` off 0.30.0 onto 0.33.0.