You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a reusable clean-install qualification flow. The flow consumes an immutable candidate artifact set and a compatible target, installs the candidate through that target's documented package mechanism, verifies the installation, invokes the selected test suites, and cleans up.
The flow must contain no Fedora-, Podman-, architecture-, or suite-specific behavior.
Clean installation is P0 across the initial release qualification matrix. Fedora rootless Podman is the first target, but the same flow must be reusable for other RPM, DEB, Helm, macOS, and Windows targets as their package operations become available.
Definition of Done
The flow accepts an immutable candidate artifact manifest and a separately defined target.
It installs the exact candidate artifacts through the target's documented package mechanism without using floating dev artifacts.
It verifies the installed OpenShell version and candidate identity before running suites.
It starts or discovers the installed gateway and verifies gateway health.
It invokes independently selected suites and propagates their pass/fail result.
It emits machine-readable step results and retains target-provided diagnostics on failure.
It always invokes target cleanup after success, failure, or interruption.
The Fedora Podman target requires no flow-specific fork or copied implementation.
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.
The reusable clean-install capability is complete on main through the tmachine install layer and conformance workflow. PR #3419 makes the native installation profile explicit without changing that outcome. Package-manager qualification is separate follow-up work in #3454.
Activity
github-actions commentedon Sep 10, 2026
This issue has had no activity for 14 days and is now marked stale. It may be closed in 7 days if there is no further activity. Comment or remove the state:stale label to keep it open.
SDAChess commentedon Sep 18, 2026
The reusable clean-install capability is complete on main through the tmachine install layer and conformance workflow. PR #3419 makes the native installation profile explicit without changing that outcome. Package-manager qualification is separate follow-up work in #3454.