max / quasi

Node::Notice grows an act, so an undo survives the conversion Settled in quasicoherent bde35298: grow the node, not a per-host holder. Message::undo says a response can offer a way back. A host that keeps a screen turns that message into a Node::Notice, and the node had nowhere to put a control -- quasi-tui's announce said so in a comment and dropped it, and quasi-immediate did the same without saying anything. Every retained- screen host writing its own holder beside the screen was the alternative, and both shapes are the same thing said from two ends. Message::UNDO and Message::undo_act name the control once. The address carries no label deliberately, so somebody has to supply the word, and three renderers supplying it separately is three chances to disagree. Two gaps behind it, both closed here rather than filed. The tui drew the undo and could not reach it: focus::reaches walked the slots and never looked at screen.notices, which was correct while a notice was only a sentence. It walks them now in the order the drawing writes them -- floating, slots, rested, verbs -- under a reserved NOTICE_REGION, and the existing walk-matches-drawing test covers the ordering. And the webview dropped it too, which the task did not expect: the HX-Trigger path hands a message to the client without building a node, so notice_trigger had to carry the undo itself. Additive, so a client written before this reads the object it always read. An external destination is not carried: an undo is this router's own route. 12 Node::Notice struct literals in audiofiles and 3 in goingson became Node::banner / Node::toast rather than growing an act: None.