Build the end-to-end UI test pass

The golden-path XCUITest suite, adapted to current rulings where the
card body had gone stale: trash flows follow the materialized-trash
grammar (no Put Back, restore is drag or cut/paste out), git flows are
pro-m1 scope and skipped, and fixtures extend m11's in-container
--ui-test-fixture-board mechanism (the sandbox forbids the card's
--open-board path handoff) with exact-match variant flags: standard
(the three-lane audit board), large (8 lanes x 40 cards for
masonry/reflow), malformed (BoardWriter-built board with one card's
index.md overwritten to unterminated YAML, opened through the ORDINARY
path so the failure is the loader's own).

EndToEndFlowTests: create card/lane, inline rename, coordinate drag
across lanes, cut/paste, undo/redo of a move, delete-to-trash /
show-trash / restore-by-cut-paste / Empty Trash confirm - all asserting
on lane accessibility labels. FailFastLaunchTests: welcome appears, no
board window ever, a welcome row carries the loader's sentence naming
the file; byte-fidelity of the malformed board pinned unconditionally
in KanbanTests plus an identically-refused relaunch. Performance:
launch metric plus explicit wall-clock gates (30s launch / 5s Show
Trash on 320 cards) since XCTest baselines don't travel. Powerbox
panels (template save panel, Duplicate fallback, Open) are documented
as manual in EndToEndVerification.md, not faked.

The smoke test now launches on the standard fixture (it launched bare
before, opening the developer's real boards); README's everyday test
command scopes to -only-testing:KanbanTests.

Suite compiles on both schemes (build-for-testing verified); flows
await a real display + automation permission to execute - run
instructions in KanbanUITests/EndToEndVerification.md. +8 unit tests;
1669 green both schemes.

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

KanbanUITests/KanbanUITests.swift

@@ -1,11 +1,20 @@
 import XCTest
 
+/// The bundle's smoke test: the app launches and puts a window on screen.
+///
+/// It launches on the **standard fixture** rather than bare, which is a deliberate narrowing of what
+/// it used to prove. A bare launch consults the registry's restore flags, so on a developer's machine
+/// it opens that developer's real boards — real watchers over real documents, and a recents list
+/// stamped by a test run. Every other test in this bundle goes out of its way to avoid exactly that
+/// (`UITestLaunch` redirects the registry into a scratch directory for the same reason), and one test
+/// quietly opting out would make "a UI run never touches your real boards" false.
+///
+/// What is given up is the launch-to-*welcome* path, which no longer has a UI test. It is not
+/// untested: `LaunchPlanTests` pins the decision that produces it, and it is the path a developer
+/// exercises every time they run the app from Xcode.
 final class KanbanUITests: XCTestCase {
     @MainActor
     func testAppLaunches() throws {
-        let app = XCUIApplication()
-        app.launch()
-        XCTAssertTrue(app.wait(for: .runningForeground, timeout: 30))
-        XCTAssertTrue(app.windows.firstMatch.waitForExistence(timeout: 30))
+        _ = XCUIApplication.launchedWithFixtureBoard()
     }
 }