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

Kanban/History/HistoryPhrase.swift

@@ -56,6 +56,14 @@ public enum HistoryPhrase {
         case rename = "Rename"
         case restyle = "Restyle"
         case resize = "Resize"
+        /// A lane folded to its slim strip (03-board-ui.md § Lane ▸ Collapsed lanes).
+        ///
+        /// **Two verbs rather than one**, unlike `resize`, which covers growing and shrinking alike:
+        /// the row has to read back the gesture it undoes, and "Undo Resize Lane" after *Collapse
+        /// Lane* would name a control the user never touched. The trash pair's Delete/Restore split is
+        /// the precedent one level up.
+        case collapse = "Collapse"
+        case expand = "Expand"
         /// An Edit session's body save — one step at the Edit→Preview flip (13 ▸ Rules).
         case edit = "Edit"
     }

Kanban/History/HistoryStaleness.swift

@@ -27,6 +27,13 @@ public enum ExpectedField: Sendable, Equatable {
     /// `width` — the lane resize. `nil` is the one-unit default, whose key the write removes.
     case width(Int?)
 
+    /// `collapsed` — the lane fold (03-board-ui.md § Lane ▸ Collapsed lanes). `nil` is the expanded
+    /// default, whose key the write removes, so the pair of after-values a collapse and its inverse
+    /// declare is exactly `true` and `nil` — the app never writes `false`
+    /// (`FrontmatterKeys.collapsed`), and a hand-written one therefore stales the step, which is the
+    /// same reading a malformed value gets: somebody else edited the key.
+    case collapsed(Bool?)
+
     /// `background` — the styling gesture's colour dimension.
     case background(String?)
 
@@ -59,6 +66,7 @@ public enum ExpectedField: Sendable, Equatable {
         case .title: .title
         case .order: .order
         case .width: .width
+        case .collapsed: .collapsed
         case .background: .background
         case .backgroundImage: .backgroundImage
         case .icon: .icon
@@ -73,6 +81,7 @@ public enum ExpectedField: Sendable, Equatable {
         case title
         case order
         case width
+        case collapsed
         case background
         case backgroundImage
         case icon
@@ -336,6 +345,7 @@ public enum HistoryStaleness {
         case let .title(expected): equal(document.title, expected)
         case let .order(expected): document.order.value == expected
         case let .width(expected): equal(document.width, expected)
+        case let .collapsed(expected): equal(document.collapsed, expected)
         case let .background(expected): equal(document.background, expected)
         case let .backgroundImage(expected): equal(document.backgroundImage, expected)
         case let .icon(expected): equal(document.icon, expected)