Materialize the trash — faces, menus, and grammar

Phase 3 finishes the pivot at the surface. One card face serves two
containers: CardFaceView extracted with a role — board or trash — so
stripe, tint, chip, selection stroke, cut dim, marquee registration,
and drag are shared by construction, the trash side differing only in
its absences: no Open, no rename, no Style, no file-hover highlight,
and a Delete that goes through the confirmation host. The column
rewrote around the lanes' own single-column masonry so drag reflow
reads as positional slides; chrome stays the hatched header, symbol,
and count — 11 gives Empty Trash to the File menu alone. Two real
grammar bugs die here: plain Backspace on a trash selection purged
without the confirmation the menu raises, and the context menu's
Delete resolved against the standing selection, so right-clicking a
trash card under a board selection silently did nothing — it now
stages the clicked set explicitly. Open, Rename, Style, and Empty
Trash validation became testable store seams; the column is one named
accessibility container of ordinary card elements. The tombstone era
is swept: deleteItem, restoreItem, stripTombstonedChildren — dead
since lane copies stopped nesting trash — the restore verb, the
unreachable put-back banner row, and every quasi-lane doc comment.

Claude-Session: https://claude.ai/code/session_01SR4XGjmBE16ZUYWpfFHXwY

Kanban/UI/Card/CardSidebarSections.swift

@@ -65,20 +65,20 @@ struct CardStyleSection: View {
 // MARK: - Actions
 
 /// The sidebar's **Actions** section, at the bottom of the stack (05-card-window.md ▸ Actions):
-/// **Delete** — tombstones the card — and **Reveal in Finder** — the card's folder.
+/// **Delete** — moves the card to the trash — and **Reveal in Finder** — the card's folder.
 ///
 /// ### Delete writes; the window's dismissal is not its business
 ///
-/// The button calls `BoardStore.deleteCard`, which is the ⌫ tombstone exactly (same write op, same
-/// bracket, same stamps). It does not close this window: the card's tombstone rounds back through
+/// The button calls `BoardStore.deleteCard`, which is the ⌫ delete exactly (same write op, same
+/// bracket, same stamps). It does not close this window: the card's move into `.trash/` rounds back through
 /// the watcher and `CardWindowHost.cardWindowFate` takes the window down, which is the same path a
 /// delete from the board — or from an agent — already takes. Dismissing from here as well would be a
 /// second rule able to disagree with the first, and 05's own wording is a sequence rather than a
-/// pair ("tombstones the card; the window then dismisses itself").
+/// pair ("moves the card to the trash; the window then dismisses itself").
 ///
-/// Recovery is the board's trash quasi-lane, which is why this needs no confirmation: the row is
-/// still there to Put Back, and 03-board-ui.md reserves the alert for the purge that isn't
-/// recoverable.
+/// Recovery is the board's trash column, which is why this needs no confirmation: the card is still
+/// there to drag out or cut and paste back (03-board-ui.md § Trash — there is no Put Back), and 03
+/// reserves the alert for the purge that isn't recoverable.
 ///
 /// ### Reveal is not edit-shaped
 ///