Install from source
The frozen candidate is 0.0.2-rc.12. Its supported source matrix passed 3,554 unique tests, its exact runtime archive is authenticated, and all six fresh fuzz targets passed five minutes plus corpus replay. See the source evidence summary.
Release qualification remains open: macOS 26 payload reproducibility failed, and complete sanitizer coverage and signed installation/recovery checks remain required. The earlier RC.11 signed package installed over dev.11 but failed rollback; its failure record remains retained. No supported RC or GA channel has been published. Follow the October 15 readiness snapshot.
Signed development package
Section titled “Signed development package”brew install hostwright/tap/hostwrighthostwright --versionThe vendor tap installs the immutable dev.12 qualification prerelease. It uses Manifest v2 and SQLite schema v7, and cannot run the current-source quickstart. The intended GA launch requires an accepted official Homebrew cask. brew install hostwright remains unavailable until acceptance and a fresh no-tap installation are verified. See the Homebrew distribution plan.
The preserved upgrade baselines are:
| Release | Source commit |
|---|---|
| dev.11 | 7d97d6c9ff878ec567c88e6993d4543ab8f0ad95 |
| dev.12 | 71414005104933d8ee3591e8c91bc831bce2e2a2 |
A current signed candidate must pass the release process before publication. Qualification covers the actual CLI, daemon, desktop app, helpers, archive, and package.
Build current source
Section titled “Build current source”Use Apple silicon, macOS 26 or later, and a Swift 6.2-compatible toolchain. Network access is needed for source and dependencies. Apple container is required for live operations through the CLI provider.
git clone https://github.com/hostwright/hostwright.gitcd hostwrightswift build --jobs 1scripts/test.sh prswift run hostwright --versionLocate the executables with swift build --show-bin-path. Source builds do not establish installed trust. Authenticated operations require a coherent signed CLI, daemon, and companion payload; follow daemon setup.
Current source uses Manifest v3, Control API 2.2, Runtime Provider API v2, and SQLite schema v24. See compatibility for the provider matrix.
State and package maintenance
Section titled “State and package maintenance”The default state database is ~/Library/Application Support/Hostwright/state/state.sqlite. After identity bootstrap and daemon startup, inspect selected paths with hostwright paths --json from that signed installation. Use the same state selection for the CLI and daemon.
Before an upgrade, create a verified state backup. State backups do not include workload data or Keychain items. Package upgrades also require a prepared, exact state binding. Follow the installed lifecycle reference for upgrade, rollback, repair, and uninstall, and the recovery runbook after interruption.
Installers act only on verified owned payloads. They preserve unrelated or modified files and do not install or start a LaunchAgent automatically. hostwright daemon install separately manages the current-user service. Deleting a source checkout does not uninstall the application or remove state or workloads.
Release verification
Section titled “Release verification”hostwright-dist verify-release checks the signed release inventory. Checksums establish byte identity; signatures, notarization, and retained source evidence establish separate parts of distribution trust. Local unsigned build and assemble output cannot satisfy the signed release gate.
The release verification reference describes staging, candidate acceptance, and immutable publication. Historical dev.11/dev.12 qualification does not qualify current-source artifacts.
