docs: Campaign LA gate round 1 record — #398 closed, #399 merged-closed, bake co-deploy

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/plans/2026-08-14-launcher-campaign.md

@@ -717,6 +717,30 @@ in ledger. Reviews name blast radius explicitly
 retail-fidelity lens against named-retail symbols cited in the slice body;
 LA6 adds CH-regression scrutiny; LA0 adds guard-integrity scrutiny.
 
+## Gate round 1 — 2026-08-15 (first live launch by the user)
+
+The user's first hands-on launch found the launcher exiting on every click.
+Root cause (`d54b8a78`): `MainWindow`'s constructor called
+`AvaloniaXamlLoader.Load(this)` instead of the generated
+`InitializeComponent()`, so every `x:Name` backing field was null and any
+modal open/close threw out of the dispatcher into `Program`'s exit-74
+guard. It reached the gate because NO test constructed `MainWindow` —
+filed and closed as **#399** (`2b439cc1`, merged): `Avalonia.Headless.XUnit`
+view tests with falsification evidence (12/12 fail against the old code,
+12/12 pass against the fix; launcher suite 66/66 Windows + native Ubuntu;
+xunit→xunit.v3 in that test project). Same round (`e1e94697`): **#398**
+closed — fatal exceptions now write a full-stack crash report under the
+data root (isolated-roots-safe; the first cut leaked to the real data root
+when parsing failed, caught live and fixed) — and `acdream-bake.exe` is now
+co-deployed on plain Build, not just Publish, so a developer-built launcher
+can actually run its first-run wizard (79.6 MB single file beside the
+launcher, incremental, `--help` verified). One transient 65/66 on the first
+post-merge test run did not reproduce across a clean rebuild + six repeats —
+consistent with stale-artifact mixing, but if it EVER recurs, capture the
+failing test name before anything else. Merged slice worktrees/branches
+(la2/la3/la7a/la-uitest) removed. The §A–I connected script remains the
+open user gate.
+
 ## Ledger
 
 | Slice | Status | Commits | Review | Notes |