max / quasi

0.7.0: describe a board's columns as peers RegionKind::Columns, over makeover-layout 0.25.0's Region::Columns. Peer regions across, all equals, which is the shape Split is not: a split's two panes stand in master-detail where the left chooses what the right shows. Measured against goingson's tasks-kanban.js before it was added. Every card fact was already sayable -- title, project, due, the blocked and unblocks badges, subtask progress, the open action and the context menu are Row's existing parts, and a column is a heading, a count and a list. The one thing nothing could say was that the columns are peers. A board described as list-detail is a lie about the screen, and list-detail and sidebar-content were the only arrangements there were. Dragging a card between columns never entered into it. A drop's effect is "set status", a discrete action Row's menu already carries; the drag is affordance and stays the host's, the same answer the day view got. quasi-webview emits the class and nothing else, because regions are laid out by the consumer's stylesheet the way band, sidebar and pane already are. A test asserts no share, no count and no order index reach the markup: every one of those would be a renderer deciding something peers settle by being peers. A second test holds columns and split apart, since the one place their difference is visible is the class name. quasi-tui needs no arm. It matches Band, Sidebar and Modal and lets everything else stack, so a board reads as its columns one after another -- which is the terminal honouring this member rather than degrading it.