thaloco/aman
1
Fork 0
Code Pull requests Releases Packages Activity Actions

Close milestones 2 and 3 on Arch evidence
Some checks failed
ci / test-and-build (push) Has been cancelled
Details

Browse source 
Record the user-reported Arch X11 validation pass and thread it through the portable and runtime validation matrices.

Adjust the milestone 2 and 3 closeout wording so one fully validated representative distro family is enough for now, while keeping Debian/Ubuntu, Fedora, and openSUSE coverage as an explicit milestone 5 GA signoff requirement.

Update the roadmap and GA validation rollup to mark milestones 2 and 3 complete for now rather than fully GA-complete, and archive the raw Arch evidence in user-readiness/1773357669.md.

Validation: documentation consistency review only; no code or behavior changes were made.
This commit is contained in:
Thales Maciel 2026-03-12 20:29:42 -03:00
parent 31a1e069b3
commit b4a3d446fa
No known key found for this signature in database
GPG key ID: 33112E6833C34679
7 changed files with 102 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

17
docs/x11-ga/03-runtime-reliability-and-diagnostics.md
View file

@ -24,7 +24,9 @@ Once Aman is installed, the next GA risk is not feature depth. It is whether the
- X11 injection failure
- model download or cache failure
- service startup failure
- Add repeated-run validation, restart validation, and offline-start validation to release gates.
- Add repeated-run validation, restart validation, and offline-start validation
to release gates, and manually validate them on at least one representative
distro family for milestone closeout.
- Treat `journalctl --user -u aman` and `aman run --verbose` as the default support escalations after diagnostics.
## Out of scope
@ -44,8 +46,12 @@ Once Aman is installed, the next GA risk is not feature depth. It is whether the
- `doctor` and `self-check` have distinct documented roles.
- The main end-user failure modes each produce an actionable diagnostic result or service-log message.
- No supported happy-path failure is known to fail silently.
- Restart after reboot and restart after service crash are part of the validation matrix.
- Offline start with already-cached models is part of the validation matrix.
- Restart after reboot and restart after service crash are part of the
validation matrix and are manually validated on at least one representative
distro family for milestone closeout.
- Offline start with already-cached models is part of the validation matrix and
is manually validated on at least one representative distro family for
milestone closeout.
- Release gates include repeated-run and recovery scenarios, not only unit tests.
- Support docs map each common failure class to a matching diagnostic command or log path.
@ -59,5 +65,8 @@ Once Aman is installed, the next GA risk is not feature depth. It is whether the
- Updated command help and docs for `doctor` and `self-check`, including a public runtime recovery guide.
- Diagnostic output examples for success, warning, and failure cases.
- A release validation report covering restart, offline-start, and representative recovery scenarios.
- A release validation report covering restart, offline-start, and
representative recovery scenarios, with one real distro pass sufficient for
milestone closeout and full four-family coverage deferred to milestone 5 GA
signoff.
- Manual support runbooks that use diagnostics first and verbose foreground mode second.