WorkForge v0.2.0

WorkForge v0.2.0

This release turns WorkForge into an upgradeable workstation runtime while preserving the v0.1.0 installation and user-owned state.

Highlights

• Transactional WorkForge updater in WorkForge Control for future stable releases.
• Side-by-side staging, full immutable-runtime integrity validation, tunnel runtime rebinding, Doctor verification, and automatic rollback on failure.
• Existing workspace files, profile registry, tunnel credential, and prior engine version are preserved during upgrade.
• Windows path canonicalization fixes for project_resume on CI and path aliases.
• Centralized runtime profile contract and a smaller Windows profile/tunnel runtime architecture.
• macOS workstation support with dedicated macOS CI coverage.

Upgrading from v0.1.0

Because v0.1.0 predates the updater UI, this transition requires one manual bridge:

1. Download WorkForge-v0.2.0-win-x64.zip and its .sha256 file.
2. Verify the checksum and extract the ZIP into a new local folder.
3. Run Setup.cmd from the v0.2.0 folder.
4. Do not uninstall v0.1.0 first. WorkForge stages v0.2.0 side-by-side and keeps v0.1.0 as the rollback target.

Starting with v0.2.0, future stable updates can be checked and applied from WorkForge Control → Update WorkForge.

Assets

• WorkForge-v0.2.0-win-x64.zip — Windows x64 portable release
• WorkForge-v0.2.0-win-x64.zip.sha256 — SHA-256 checksum

The published portable artifact is Windows x64. macOS support is covered by the repository's macOS setup/runtime workflow and CI rather than this Windows ZIP.