Realign code with the 2026-07-31 rulings

The trash sorts by modified descending — the arrival rank mint retires
(Ranks.isOrderedForTrash one comparator, loader + merged order agree;
the legacy deleted: migration stamps modified from the tombstone
timestamp where parseable; delete undo steps validate existence-only;
agent guide v8). Trash selection goes kind-blind — ranges, marquee,
Select All, and the successor walk sweep both kinds; the guard moves to
the exits (mixed-payload drop refusal, copy/cut validation). The copy
stamping preflight widens back to comment depth (load-scoped posture —
the board always loads, the gesture refuses whole). Fixes a latent
no-op: trashed-lane drag restore never fired (DragSession.beginLanes
hard-coded the board container).

2403 tests in 413 suites green.

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

Kanban/LiveStore/TrashModel.swift

@@ -11,9 +11,9 @@ import Foundation
 /// returning-card count, a deterministic `deleted`-timestamp sort, and a paths function that had to
 /// restate which items were addressable. All of it is gone. A trashed card is "an ordinary card in a
 /// special place", so the trash's contents *are* `snapshot.trash` and `snapshot.trashedLanes` —
-/// already parsed by the loader, already in `order` display order, already newest-first because
-/// every arrival mints a rank above the current top. There is nothing to derive, and no second
-/// definition to keep in step with the loader's.
+/// already parsed by the loader, already in the column's own order, already newest-first because
+/// every arrival stamps `modified` and the container sorts by it descending (re-ruled 2026-07-31).
+/// There is nothing to derive, and no second definition to keep in step with the loader's.
 ///
 /// What genuinely remains is what the *commands* need and no view can answer: the two purge
 /// confirmations' phrasing — which since lanes rejoined the trash (2026-07-29) has to **count the