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

KanbanTests/KeyboardGrammarTests.swift

@@ -183,6 +183,47 @@ struct NavigationMathTests {
         // From the row itself, ↓ reaches the card below it: navigation crosses back.
         #expect(NavigationMath.nearest(from: row.frame, direction: .down, among: all) == card2)
     }
+
+    /// **A collapsed lane is scanned past by the absolute destinations** (03-board-ui.md § Lane ▸
+    /// Collapsed lanes: "cards inside are not rendered — they are excluded from … keyboard spatial
+    /// navigation"), which is what ⌥←/⌥→ and the empty-selection seed land through.
+    ///
+    /// The *relative* half — a plain or ⇧ arrow — needs nothing: a folded lane registers no card frame,
+    /// so `nearest` has no candidate to reject, exactly as the hidden trash has none.
+    /// `@MainActor` where its neighbours are not, and only because the fixture is: a board on disk is
+    /// the honest way to ask what a *read-side* fold reads as, and `WriterFixture` is main-actor bound.
+    @MainActor
+    @Test("The absolute destinations scan past a folded lane, an empty one, and one the query emptied")
+    func firstCardSkipsFoldedLanes() throws {
+        let fixture = try makeBoard()
+        defer { fixture.tearDown() }
+        // Lane 1 folded, lane 2 open: the first card the *board* is showing is lane 2's.
+        try fixture.item(Ident.lane1, "---\nschema: 1\ntitle: Todo\norder: 1024\ncollapsed: true\n---\n\n")
+        let lanes = try load(fixture).lanes
+
+        #expect(NavigationMath.firstCard(scanning: lanes) == card5)
+        // Reversed — ⌥→'s scan — the last showing lane is lane 2 as well, since lane 3 is empty and
+        // lane 1 is folded.
+        #expect(NavigationMath.firstCard(scanning: lanes.reversed()) == card5)
+
+        // The filter narrows the same scan: "Sixth" is in the open lane, "First" is in the folded one
+        // and stays unreachable however well it matches.
+        #expect(NavigationMath.firstCard(scanning: lanes, filter: SearchFilter(query: "Sixth")) == card6)
+        #expect(NavigationMath.firstCard(scanning: lanes, filter: SearchFilter(query: "First")) == nil)
+
+        // Every lane folded: there is nowhere to land at all, which is the same answer an empty board
+        // gives and leaves the press inert rather than selecting something drawn nowhere.
+        let allFolded = try WriterFixture()
+        defer { allFolded.tearDown() }
+        try allFolded.item("", Item.board)
+        try allFolded.item(Ident.lane1, "---\nschema: 1\ntitle: Todo\norder: 1024\ncollapsed: true\n---\n\n")
+        try allFolded.item("\(Ident.lane1)/\(Ident.card1)", Item.rich(order: "1024", title: "First"))
+        #expect(NavigationMath.firstCard(scanning: try load(allFolded).lanes) == nil)
+
+        // And unfolding restores it, key removal and all — nothing about the cards changed.
+        try fixture.item(Ident.lane1, "---\nschema: 1\ntitle: Todo\norder: 1024\n---\n\n")
+        #expect(NavigationMath.firstCard(scanning: try load(fixture).lanes) == card1)
+    }
 }
 
 // MARK: - The registry the arrows and the band read