Thales Maciel
b4a3d446fa
Some checks failed
ci / test-and-build (push) Has been cancelled
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.
36 lines
1.7 KiB
Markdown
36 lines
1.7 KiB
Markdown
# Arch Linux Validation Notes
|
|
|
|
- Date: 2026-03-12
|
|
- Reviewer: User
|
|
- Environment: Arch Linux on X11
|
|
- Release candidate: `1.0.0`
|
|
- Evidence type: user-reported manual validation
|
|
|
|
This note records the Arch Linux validation pass used to close milestones 2 and
|
|
3 for now. It is sufficient for milestone closeout, but it does not replace the
|
|
full Debian/Ubuntu, Fedora, and openSUSE coverage still required for milestone
|
|
5 GA signoff.
|
|
|
|
## Portable lifecycle
|
|
|
|
| Scenario | Result | Notes |
|
|
| --- | --- | --- |
|
|
| Fresh install | Pass | Portable bundle install succeeded on Arch X11 |
|
|
| First service start | Pass | `systemctl --user` service came up successfully |
|
|
| Upgrade | Pass | Upgrade preserved the existing state |
|
|
| Uninstall | Pass | Portable uninstall completed cleanly |
|
|
| Reinstall | Pass | Reinstall succeeded after uninstall |
|
|
| Reboot or service restart | Pass | Service remained usable after restart |
|
|
| Missing dependency recovery | Pass | Dependency failure path was recoverable |
|
|
| Conflict with prior package install | Pass | Conflict handling behaved as documented |
|
|
|
|
## Runtime reliability
|
|
|
|
| Scenario | Result | Notes |
|
|
| --- | --- | --- |
|
|
| Service restart after a successful install | Pass | Service returned to the expected ready state |
|
|
| Reboot followed by successful reuse | Pass | Aman remained usable after restart |
|
|
| Offline startup with an already-cached model | Pass | Cached-model startup worked without network access |
|
|
| Missing runtime dependency recovery | Pass | Diagnostics pointed to the correct recovery path |
|
|
| Tray-triggered diagnostics logging | Pass | `Run Diagnostics` matched the documented log flow |
|
|
| Service-failure escalation path | Pass | `doctor` -> `self-check` -> `journalctl` -> `aman run --verbose` was sufficient |
|