max / quasi

0.10.0: Node takes #[non_exhaustive], and the third renderer stops panicking Node's next member was a breaking minor across three renderers, which is what makeover-layout took the attribute for on RowPart, Readiness and Region. The trade is the same: a node added upstream no longer stops a renderer compiling, and in exchange landing one is not a lockstep release. Each renderer's catch-all draws a muted line saying it does not know this node yet rather than drawing nothing, because a blank is indistinguishable from a screen that never carried the part. quasi-tui contributes no reach for one: a Reach says where a key press goes and this cannot know, so drawn-and-unreachable is the honest pair. quasi-immediate's leaf walk was a loaded panic. Its draw match was fixed yesterday for exactly this class -- Node::Image and Node::Timeline reached container's unreachable! and killed the frame -- but leaf's catch-all is also an unreachable! and a table cell ends its own match with other => leaf(..), so the third instance was already waiting. leaf now names its addressed members, keeping that assertion for the routing bug it is there to catch, and sends only unknown members to undrawn. Consumers forward-fixed in the same pass. MNW server and goingson were pinned 0.8, audiofiles and the scaffolder's own template 0.2 -- so every generated app shipped a pin that could not resolve.