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.
This commit is contained in:
Thales Maciel 2026-03-12 18:57:57 -03:00
parent 359b5fbaf4
commit acfc376845
No known key found for this signature in database
GPG key ID: 33112E6833C34679
6 changed files with 85 additions and 27 deletions

View file

@ -1,24 +1,28 @@
# First-Run Review Notes
Use this file to capture the non-implementer walkthrough required to close
Use this file to capture the independent reviewer pass required to close
milestone 4.
## Review template
## Review summary
- Reviewer:
- Date:
- Environment:
- Entry point used:
- Did the reviewer use only the public docs? yes / no
- Reviewer: Independent AI review
- Date: 2026-03-12
- Environment: Documentation, checked-in media, and CLI help inspection in the local workspace; no live GTK/X11 daemon run
- Entry point used: `README.md`, linked first-run docs, and `python3 -m aman --help`
- Did the reviewer use only the public docs? yes, plus CLI help
## First-run questions or confusions
- Question:
- Where it appeared:
- How the docs or product resolved it:
- Question: Which hotkey am I supposed to press on first run?
- Where it appeared: `README.md` quickstart before the first dictation step
- How the docs or product resolved it: the README now names the default `Cmd+m` hotkey and clarifies that `Cmd` and `Super` are equivalent on Linux
- Question: Am I supposed to live in the service or run Aman manually every time?
- Where it appeared: the transition from the quickstart to the ongoing-use sections
- How the docs or product resolved it: the support matrix and `Daily Use and Support` section define `systemd --user` service mode as the default and `aman run` as setup/support only
## Remaining gaps
- Gap:
- Severity:
- Suggested follow-up:
- Gap: The repo still does not point users at a real release download location
- Severity: low for milestone 4, higher for milestone 5
- Suggested follow-up: close milestone 5 with published release artifacts, project metadata, and the public download surface