docs: Campaign LU is code-complete; record the gate limitation

All six slices are committed locally with the full solution green at 14,370
tests. Records the one thing a gate tester will hit that is NOT a Campaign LU
defect: the installed client predates the #420 character-select crash fix, so
Play still dies until a release carrying it is published.

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

docs/plans/2026-08-19-launcher-usability-campaign.md

@@ -1,6 +1,26 @@
 # Campaign LU — launcher usability
 
-**Status:** PLANNED 2026-08-19. Not started; awaiting the goal being set.
+**Status:** CODE-COMPLETE 2026-08-19. All six slices implemented, tested, and
+committed locally (not pushed — the user asked for local verification first).
+The connected user gate is the remaining boundary.
+
+| slice | commit | tests |
+|---|---|---|
+| (blocker) #420 client crash | `a34e8f2a` | reverting test reproduces the live stack |
+| LU1 instant startup | `00d12782` | 10 cache tests + 2 view-model tests |
+| LU2/LU3 one update question | `a01ff426` | 8 rewritten update tests |
+| LU4 Setup complete | `0a2defb6` | 2 tests (success + failure never claims success) |
+| LU5/LU6 Play + sessions | `09305be6` | 16 session-row tests |
+
+Full solution under the release-gate filter: **14,370 passed, 0 failed,
+0 skipped.**
+
+**Known gate limitation.** The client installed under
+`%LOCALAPPDATA%\acdream\app\` is the pre-#420 build, so pressing **Play** still
+crashes on the character-select screen until a release carrying the fix is
+published and the launcher installs it. That is itself the natural next test:
+push → CI publishes → the new startup prompt offers the update → taking it
+exercises LU2 end to end and replaces the crashing client.
 
 **Goal**