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/UI/Board/NewCardTarget.swift

@@ -53,10 +53,28 @@ enum NewCardTarget {
         lastActiveLaneID: ItemID?,
         snapshot: BoardModel
     ) -> Resolution? {
-        let lanes = snapshot.lanes
+        // **Collapsed lanes are not creation targets** (03-board-ui.md § Lane ▸ Collapsed lanes:
+        // "⌘N new-card targeting skips collapsed lanes"): the placeholder is a pseudo-card drawn in the
+        // lane's masonry (`LaneSlot.placeholder`), and a folded lane draws none — so a card created
+        // there would be a focused text field rendered nowhere, with no way to type a title into it and
+        // no way out but Escape. Skipping is therefore not a preference but the only coherent answer,
+        // and it is applied to every branch below by narrowing the lane list once.
+        //
+        // **A board whose every lane is folded has no target at all**, which is exactly the zero-lane
+        // board's answer and reaches the same place: `nil` is New Card's `disabled` condition as well
+        // as its refusal, so the item greys out rather than doing nothing when pressed.
+        let lanes = snapshot.lanes.filter { !LaneLayoutMath.isCollapsed($0) }
         guard !lanes.isEmpty else { return nil }
 
-        if let anchor = flattenAnchor(selection: selection, snapshot: snapshot) {
+        // **A selection inside a folded lane falls through rather than refusing** — the stale
+        // selection's rule verbatim, for its reason: the user pressed ⌘N and the board has lanes it
+        // can create into. So collapsing a lane with one of its cards selected leaves ⌘N working, at
+        // the last-active lane below. `flattenAnchor` itself is deliberately untouched: it is
+        // **shared with paste** ("the same anchor serves paste"), and a paste into a folded lane is
+        // perfectly coherent — it writes a rank, it renders nothing, and the card is there when the
+        // lane unfolds.
+        if let anchor = flattenAnchor(selection: selection, snapshot: snapshot),
+           lanes.contains(where: { $0.id == anchor.laneID }) {
             return anchor
         }
         // Nothing selected, a trash selection, or a stale one — the ids name nothing the board