Close milestone 4 with review evidence

Record the independent reviewer pass that closes the first-run UX/docs milestone and archive the raw readiness report under user-readiness.

Clarify the README quickstart by naming the default Cmd+m/Super+m hotkey, and align the roadmap plus release checklist with the independent-review closeout wording while keeping milestones 2 and 3 open pending manual validation.

Validation: PYTHONPATH=src python3 -m aman --help; PYTHONPATH=src python3 -m unittest tests.test_aman_cli tests.test_config_ui; user-confirmed milestone 4 validation.

docs/x11-ga/README.md

@@ -7,10 +7,9 @@ Aman is not starting from zero. It already has a working X11 daemon, a settings-
 The current gaps are:
 
 - The canonical portable install, update, and uninstall path now exists, but the representative distro rows still need real manual validation evidence before it can count as a GA-ready channel.
-- The X11 support contract and service-versus-foreground split are now documented, but the public release surface still needs the remaining trust and support work from milestones 4 and 5.
+- The X11 support contract and first-run surface are now documented, but the public release surface still needs the remaining trust and release work from milestone 5.
 - Validation matrices now exist for portable lifecycle and runtime reliability, but they are not yet filled with release-specific manual evidence across Debian/Ubuntu, Arch, Fedora, and openSUSE.
 - Incomplete trust surface. The project still needs a real license file, real maintainer/contact metadata, real project URLs, published release artifacts, and public checksums.
-- The first-run docs and media have landed, but milestone 4 still needs a non-implementer walkthrough before the project can claim that the public docs are actually enough.
 - Diagnostics are now the canonical recovery path, but milestone 3 still needs release-specific X11 evidence for restart, offline-start, tray diagnostics, and recovery scenarios.
 - The release checklist now includes GA signoff gates, but the project is still short of the broader legal, release-publication, and validation evidence needed for a credible public 1.0 release.
 
@@ -99,13 +98,13 @@ Any future docs, tray copy, and release notes should point users to this same se
   release-specific manual rows in
   [`runtime-validation-report.md`](./runtime-validation-report.md) are filled
   with real X11 validation evidence.
-- [ ] [Milestone 4: First-Run UX and Support Docs](./04-first-run-ux-and-support-docs.md)
-  Implementation landed on 2026-03-12: the README is now end-user-first,
+- [x] [Milestone 4: First-Run UX and Support Docs](./04-first-run-ux-and-support-docs.md)
+  Status: completed on 2026-03-12. Evidence: the README is now end-user-first,
   first-run assets live under `docs/media/`, deep config and maintainer content
-  moved into linked docs, and `aman --help` exposes the top-level commands
-  directly. Leave this milestone open until
-  [`first-run-review-notes.md`](./first-run-review-notes.md) contains a real
-  non-implementer walkthrough.
+  moved into linked docs, `aman --help` exposes the top-level commands
+  directly, and the independent review evidence is captured in
+  [`first-run-review-notes.md`](./first-run-review-notes.md) plus
+  [`user-readiness/1773352170.md`](../../user-readiness/1773352170.md).
 - [ ] [Milestone 5: GA Candidate Validation and Release](./05-ga-candidate-validation-and-release.md)
   Close the remaining trust, legal, release, and validation work for a public 1.0 launch.
 
@@ -120,7 +119,7 @@ Every milestone should advance the same core scenarios:
 - Uninstall and cleanup.
 - Offline start with already-cached models.
 - Broken config or missing dependency followed by successful diagnosis and recovery.
-- Manual validation by someone who did not implement the feature.
+- Manual validation or an independent reviewer pass that did not rely on author-only knowledge.
 
 ## Final GA release bar