max / quasi

Say the initial caret, a screen's feed, and a header band Three vocabulary members answered together, because all three land in quasi-router and three separate breaking bumps would forward-fix the same consumers three times. `Screen::opens_at` names the field the caret starts in, as a screen-level statement beside `place` and `selection` rather than a flag on a field: a fact that cannot be said twice beats one that can. The webview emits `autofocus` and only in a whole document, because a browser answers most interactions with a fragment and a swap that moves the caret takes it out of whatever is being typed into. A terminal places its caret on arrival, and egui is asked for focus on the first frame of a screen. `Discovery::feed` says a screen offers a syndication feed, singular and enum-typed: `application/rss+xml` written by hand at three sites is three chances to write `application/rss` and have a reader skip it. A renderer with no autodiscovery ignores it, said in the doc rather than left to each renderer's author to guess. `Chrome::band` says the header is one element. The nav stays where it is and the band contains it, because an app with places and no band still has places. Named slots rather than a body of nodes, so a renderer can tell a brand from a heading; `Brand` says a name and which run of it is the mark, which is what `Makenot.work` needed and nothing could say. Two corrections fell out of building it. `action_attrs` named its `href` shortcut by exclusion, so every gesture that was not a click got an `href` and, because that branch returns, no transport at all -- a band's search box is exactly that shape and did nothing. It names the one gesture now. And `Outcome`'s `large_enum_variant` expectation came off: `Screen` grew, the spread closed to 184 bytes, and an unfulfilled expectation is itself a warning. `Place::key` rides out as `data-place`, so a host script can find a place without keying off its label.