v0.0.2 release process

The active target is v0.0.2; the working version is 0.0.2-dev.

Release ladder

1. 0.0.2-dev throughout all 15 implementation phases.
2. v0.0.2-rc.1 only after every phase/workstream reaches verification.
3. A later RC after all defects are fixed and the complete qualification run repeats.
4. v0.0.2 only after two clean complete RC runs.

An RC cannot omit an unimplemented phase or convert a blocker into a known limitation.

Baseline gate

swift build
swift test list || swift test --list-tests
swift test
scripts/integration.sh
scripts/grep-orchard.sh .
scripts/test.sh
scripts/lint.sh

Each owning phase adds real migration, security, resilience, multi-host, interoperability, accessibility, distribution, and hardware evidence. Blocked, skipped, fixture-only, mock-only, dirty, or cleanup-failed results fail the implementation/release gate.

GA qualification

• 167 workstreams and 15 epics complete; zero unresolved P0/P1 defects.
• Exact macOS/runtime/Kubernetes/Docker/client matrices frozen from evidence.
• 10,000 lifecycle cycles and a 72-hour single-host soak.
• Physical three/five-node fault matrices and seven-day cluster soak.
• Independent security assessment, fuzzing, sanitizers, dependency/license/ secret/SAST gates.
• Performance, density, energy, migration, upgrade, rollback, disaster recovery, conformance, docs/quickstart, and accessibility gates.
• Signed/notarized archive and .pkg, vendor tap, SBOM/provenance, clean install/reboot/upgrade/rollback/repair/uninstall.
• Two complete clean release-candidate runs.

brew install hostwright remains subject to Homebrew-core acceptance. The Hostwright-controlled fallback is the vendor tap.

Historical release material

The v0.1.0-alpha.1 page is an immutable historical candidate record. It is not the active target, package policy, or current support boundary.