max / quasi

Say that one Locate ask is answered with every handle The two doorway docs still described the answer as a single handle and a single label, which is what it was before the batch landed. Response::locate is the constructor a route author reads first and Outcome::Locate owns the mechanism, so those are the two places a reader forms the wrong model.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: Max Johnson <me@maxj.phd> · 2026-08-26 01:43 UTC

Signed with PGP, not checked

Commit: c909002599f52d9501a1b61d8118f14818300faf

Parent: df30e1e

1 file changed, +5 insertions, -3 deletions

M crates/quasi-router/src/response.rs +5 -3

			@@ -308,8 +308,9 @@
308	308		/// A place for the app to write into, chosen by the host.
309	309		///
310	310		/// `ec92f9cb`, ruled 2026-08-25: the route says a place is wanted, the host
311		-	/// performs the picker, and what comes back is an opaque handle plus a label
312		-	/// to show. The description never learns what the host did, which is the
	311	+	/// performs the picker, and what comes back is every opaque handle it chose,
	312	+	/// each with a label to show. **The description never learns what the host
	313	+	/// did**, which is the
313	314		/// same bargain [`File`](Self::File) strikes from the other end: that one
314	315		/// says what the file is and never where it goes, this one asks for a
315	316		/// somewhere and never asks what it is.
			@@ -768,7 +769,8 @@
768	769		}
769	770
770	771		/// Ask the host for a place. Where it asks and what it asks with is the
771		-	/// host's; what comes back is a handle and a label.
	772	+	/// host's; what comes back is every handle it chose, each with a label. One
	773	+	/// ask is answered once, however many things the reader picked.
772	774		///
773	775		/// `ec92f9cb`. See [`Outcome::Locate`] for why this is an answer rather
774	776		/// than a control, and [`Locating`] for where the answer goes.