max / quasi

Give a region's label to the thing that draws it A label is the name of the control that reveals a member: a tab's text, a disclosure's summary. Only a region that discloses or steps through its members draws one, and until now any region could carry one. Max ruled that a label nothing will draw should not be representable. It cannot be a check. A member is built before it is placed, so nothing about the member knows whether its label will be drawn, and the parent that decides may be in another declare! entirely. That is how MNW's /use-cases lost the titles of nine cards for weeks with a green suite. So Slot has no label. A selective region's body is its own arm carrying frames, each with the name of the control that reveals it, and body, showing and shown collapse into it. That retires the neighbouring trap in the same move: shown was meaningless under Showing::All and ignored there. Picks is the two selective variants only, so a selective body cannot say it shows everything. Slot::frame(label, node) is the only thing that takes a name, and it places the member in the same call. layout::Showing is untouched: it carries no data, so it stays the vocabulary's word and is derived. The declare! syntax is unchanged where it can be. `label` stays written inside the child, which is where it reads, and the macro hoists it onto the placement. A `framed <label> <emission>` modifier covers what a hoist cannot reach: a shape in another invocation answers a Slot, which now carries no label, so goingson's summary_body is placed by its parent as `framed "Time tracked" include summary_body(panel)`. Found and fixed while landing it: three test fixtures labelling screen-level slots, and MNW's shortcuts modal, whose label had never reached markup. A dialog does want an accessible name, so that one became `named`, which is the field that writes one. Span placement is a repair again rather than a re-placement, and the walk is a stack. Choosing every span afresh moved spans that were already right -- a loop nested inside a branch has a range reaching back past the branch that holds it -- which broke quasi-bench under the previous commit. Comparing neighbours is not enough either: the two spans in a straddle are often not adjacent once sorted, since a third can nest inside the first and sort between them, which is /fan-plus. Breaking, so every pin moves in the same pass: the family to 0.104, and quasi-declare to 0.1.13 for `framed`.