max / quasi

Rename Field::changes to Field::writes and say what it is not for The doc carried its own open question inline: whether a control that writes with no submit and no indication should exist at all. That question was settled elsewhere, so the comment was telling every reader the member was unsettled while the member shipped. It now states what the member is for, what it is not for, and why its name carries the whole statement. Not for: applying a value to a selection, which wants a commit affordance per wiki `explicit-commit-affordance`, and anything that does not write. The second one is the invisible failure: a filter said with `writes` still fires and still updates the screen, so nothing surfaces the lie. Why the name suffices: this is the only member on Field carrying an Action of its own, so a field without it is written by its form's submit. The presence of the member is the statement, and no member is needed to say a field does not write. quasi-notifs' pane took `writes: &Action` as its route parameter, which read as `.writes(writes.clone())` after the rename. It is `route` now. quasi 0.76.0. Consumers are forward-fixed in the same pass.