Collapsible lanes — frontmatter-backed slim strips outside the width division

A lane folds to a fixed slim vertical strip carrying its glyph, its card-count
badge and its title turned on its side, and the strip is deliberately not part
of the window's division: the expanded lanes' units divide what is left once
each folded strip's fixed width has come off the top, so folding a lane is a
re-divide trigger of the Show/Hide Trash family — the window never moves and
the siblings grow into what the lane gave up.

The state is a first-class lane frontmatter key, `collapsed: true`, and
document state exactly as `width` is: the files are the board, so an agent
folds a lane by writing one key. Absent means expanded, expanding removes the
key rather than writing `false` (the remove-at-default family beside a
one-unit `width`, the empty rename's `title` and the None well's
`background`), and the lane's `width` rides along untouched so expanding
restores the lane the user had. The read is `width`'s leniency one type over —
a boolean scalar or a quoted boolean word reads as itself, everything else has
no reading at all and renders as expanded, bytes preserved either way.

Toggling is the header's always-visible collapse chevron, the lane context
menu's single Collapse Lane / Expand Lane row, and a plain click anywhere on
the strip; a modified click on the strip stays the ordinary selection grammar,
so a folded lane is still selectable by pointer. The title reads bottom-up and
is justified to the top of the room below the strip's chrome (owner ruling
2026-08-08), truncating against the strip's own height.

While folded the lane draws no cards at all, which is what makes every
exclusion true by construction rather than by a guard per gesture: no card
face means no marquee target and no navigation frame, and no registered grid
means the masonry's drop zones have nothing to resolve against. What did need
code is the half that names absolute destinations — the option-arrow jumps and
the arrow seed scan past a folded lane, the lane domain's down-arrow is inert
on one, and New Card skips it (a selection inside one falls through to the
last-active lane, the stale selection's rule). A drop on the strip appends at
the lane's end, cards and Finder files alike, with an accent edge standing in
for the shadow the strip has no masonry to open; there is no hover-to-auto-
expand yet. Lane reorder works on the strip, and a dragged folded lane carries
its fold, so its shadow and its replica are the strip rather than its units.

The write is `writeLaneWidths` clause for clause — one `updateIndex` bracket,
the same stamp behaviour, the same three do-nothing paths — with two new
`WriteOperation` cases and two new undo verbs rather than one of each, because
a banner or an Edit-menu row that said "resize" after Collapse Lane would name
a control the user never touched.

Claude-Session: https://claude.ai/code/session_014PtZdPwqZuqEDLc6wZMtEy
This commit is contained in:
2026-08-08 22:53:10 -04:00
parent 57542177c1
commit bab456c08d
33 changed files with 1811 additions and 133 deletions
+19 -2
View File
@@ -87,8 +87,17 @@ enum AccessibilityPhrases {
/// search filter like the visible badge", so `LaneView` hands the very collection its badge
/// counts (`renderedCards`) and the two can no more disagree than the badge can disagree with
/// the masonry.
static func laneLabel(title: String?, cards count: Int) -> String {
"\(displayTitle(title)), lane, \(cardCount(count))"
/// **A folded lane says so** (03-board-ui.md § Lane Collapsed lanes; 10-accessibility.md's
/// never-colour-alone family, read one rung out: a state a sighted user reads off the strip's
/// shape has to be a word for everyone else). It sits between the level and the count, which is
/// where the container's own qualifier belongs "Doing, lane, collapsed, 5 cards" and the count
/// stays the lane's *held* cards, since a collapsed lane renders none and "0 cards" would say the
/// lane was empty when it is merely shut.
///
/// Defaulted, so every caller that has no fold to report reads exactly as it did before.
static func laneLabel(title: String?, cards count: Int, collapsed: Bool = false) -> String {
let state = collapsed ? "collapsed, " : ""
return "\(displayTitle(title)), lane, \(state)\(cardCount(count))"
}
/// The lane header's new-card button "New card in lane", the one labeled child
@@ -97,6 +106,14 @@ enum AccessibilityPhrases {
"New card in \(displayTitle(title))"
}
/// The lane header's **collapse chevron** "Collapse lane" (03-board-ui.md § Lane Collapsed
/// lanes), the header's second labeled child and the new-card button's twin in every respect: a
/// glyph-only control needs a word, and the word names the lane so the label stands on its own out
/// of context.
static func collapseLaneLabel(lane title: String?) -> String {
"Collapse \(displayTitle(title))"
}
// MARK: - Cards
/// A card's label: its title, or the untitled placeholder. Named rather than inlined so the