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/Storage/FrontmatterFields.swift

@@ -101,6 +101,7 @@ extension FrontmatterDocument {
         }
         record(FrontmatterKeys.title, title)
         record(FrontmatterKeys.width, width)
+        record(FrontmatterKeys.collapsed, collapsed)
         record(FrontmatterKeys.created, created)
         record(FrontmatterKeys.modified, modified)
         record(FrontmatterKeys.modifiedBy, modifiedBy)
@@ -215,6 +216,31 @@ extension FrontmatterDocument {
         }
     }
 
+    /// **Whether the lane is folded to a slim strip** (03-board-ui.md § Lane ▸ Collapsed lanes) —
+    /// `width`'s reading one type over, and lenient in exactly its way.
+    ///
+    /// A `true`/`false` scalar reads as itself, and so does any of YAML 1.1's other boolean spellings
+    /// (`yes`/`no`, `on`/`off`, `y`/`n`) written **quoted**: unquoted, the parser has already resolved
+    /// them to `.bool` for us, and a quoted one is the same word the author meant — the numeric string
+    /// `width: "2"` coercing to `2` is the precedent, and it is the one thing lenient reading means.
+    /// Everything else — a number, a sequence, a mapping, `collapsed: maybe` — has no boolean reading
+    /// at all and is malformed, **which renders as expanded**: the default is the absent key's, so an
+    /// unreadable value can only ever fold a lane by accident, and it never does.
+    ///
+    /// Read-side only, like every other coercion here: the bytes stay exactly as the author wrote them
+    /// until the user (or an agent) changes the key, and `collapsed: false` is a perfectly good way to
+    /// write "expanded" by hand even though the app removes the key instead
+    /// (`FrontmatterKeys.collapsed`).
+    public var collapsed: FieldValue<Bool> {
+        read(FrontmatterKeys.collapsed) { value, _ in
+            switch value {
+            case let .bool(value): value
+            case let .string(text): Self.boolWord(text)
+            default: nil
+            }
+        }
+    }
+
     public var created: FieldValue<Date> { read(FrontmatterKeys.created) { value, _ in Self.date(value) } }
     public var modified: FieldValue<Date> { read(FrontmatterKeys.modified) { value, _ in Self.date(value) } }
     public var deleted: FieldValue<Date> { read(FrontmatterKeys.deleted) { value, _ in Self.date(value) } }
@@ -300,6 +326,17 @@ extension FrontmatterDocument {
         return value >= 1 ? Int(value) : 1
     }
 
+    /// YAML 1.1's boolean words, for a **quoted** scalar that spells one — the coercion `collapsed`
+    /// needs and no other field wants. Case-insensitive, because the grammar itself is (`True`, `ON`,
+    /// `Yes` are all booleans unquoted); anything else has no boolean reading.
+    private static func boolWord(_ text: String) -> Bool? {
+        switch text.lowercased() {
+        case "true", "yes", "on", "y": true
+        case "false", "no", "off", "n": false
+        default: nil
+        }
+    }
+
     /// A quoted timestamp reads the same as an unquoted one — same YAML 1.1 timestamp grammar,
     /// a superset of ISO-8601. Anything that isn't a valid timestamp either way has no sensible
     /// date reading and is malformed; per the tombstone rule (`Lane`/`Card.isDeleted`), a