WorkForge v0.2.9

What's Changed

• feat(macos): port WorkForge Control dashboard by @smilejsu82 in #4

Full Changelog: v0.2.8...v0.2.9

WorkForge v0.2.8

Fixes WorkForge Control after a portable update. The dashboard now force-closes lingering local HTTP connections during its normal shutdown path, so a previous engine cannot remain active and return the portable engine-root mismatch.

WorkForge v0.2.7

Full Changelog: v0.2.6...v0.2.7

WorkForge v0.2.6

Full Changelog: v0.2.5...v0.2.6

WorkForge v0.2.5

WorkForge v0.2.5

Fixed

• The Control dashboard now explains when no WorkForge profile registry has been created yet.
• The expected setup-required status no longer exposes a PowerShell stack trace or local path details.

Upgrade guidance

• Already on v0.2.4: use WorkForge Control → Check again → Update WorkForge.
• Fresh install: download the Windows ZIP, extract it to a new folder, and run Setup.cmd.

WorkForge v0.2.4

WorkForge v0.2.4

Hotfix for Windows tunnel process verification during upgrades and Setup.

Fixed

• Retry transient Windows process metadata when Win32_Process.CommandLine is temporarily unavailable.
• Prevent an empty process command line from surfacing as a PowerShell parameter-binding failure.
• Keep process verification fail-closed: if identity metadata remains incomplete after the bounded retry window, WorkForge refuses to act on that PID.

Upgrade guidance

• Already on v0.2.3: use WorkForge Control → Check again → Update WorkForge.
• If a v0.2.3 Setup attempt showed a CommandLine empty-string error but WorkForge is currently healthy, do not uninstall first. Update to v0.2.4.
• Fresh install: download the v0.2.4 Windows ZIP, extract it to a new folder, and run Setup.cmd.

This release also includes the multilingual Control dashboard from v0.2.3: English, Korean, Japanese, and Simplified Chinese.

WorkForge v0.2.3

What's new

• Added a language switch to WorkForge Control: English, Korean, Japanese, and Simplified Chinese.
• The dashboard automatically follows the browser language on first launch and remembers the user's selection locally.
• Tunnel, Doctor, update progress, activity, and uninstall UI are translated together instead of mixing languages.
• Existing transactional update, rollback, security, and local-only dashboard behavior remain unchanged.

Windows update

Existing WorkForge users can update from WorkForge Control → Update WorkForge. The release ZIP is also available for fresh/manual installations.

WorkForge v0.2.2

WorkForge v0.2.2

This release makes WorkForge Control updates visibly trackable instead of feeling like a silent button press.

What changed

• Adds a live update progress bar to WorkForge Control.
• Shows the real transactional stages: check, download, verify, stage, pause tunnels, activate, rebind, Doctor, restart, and finish.
• Reports progress from the actual updater transaction rather than a cosmetic timer.
• Shows rollback state explicitly if post-update validation fails.
• Disables conflicting Control actions while an update or rollback is active.
• Keeps existing CLI/JSON behavior unchanged unless progress events are explicitly requested.

Update paths

• v0.2.1 users can update directly from WorkForge Control → Update WorkForge.
• v0.1.0 users can download this Windows ZIP, extract it to a new folder, and run Setup.cmd. Do not uninstall the existing WorkForge version first.

The Windows portable archive is SHA-256 verified and uses the existing side-by-side transactional update/rollback flow.

WorkForge v0.2.1

Hotfix

• Fixes the v0.1.0 → v0.2.x manual bridge failure where the transactional upgrade succeeded but the follow-up Setup call treated -SkipStart as the positional Mode value.
• Setup-Entry.ps1 now mirrors the Setup.ps1 parameter surface, forwards named parameters through hashtable splatting, and injects SkipStart as a named switch after a portable upgrade.
• Adds regression coverage that fails if the Setup entrypoint parameter surface drifts or positional -SkipStart injection returns.
• Synchronizes WorkForge plugin metadata to v0.2.1.
• Updates upgrade guidance so v0.1.0 users bridge directly to v0.2.1 or a newer stable release.

Upgrade guidance

• Already on v0.2.0: if the earlier Setup error appeared but v0.2.0 is active, do not reinstall or roll back. Open WorkForge Control → Check again → Update WorkForge and upgrade to v0.2.1.
• Still on v0.1.0: download the v0.2.1 Windows ZIP and matching .sha256, verify/extract it to a new folder, and run Setup.cmd. Do not uninstall v0.1.0 first.
• The original v0.2.0 ZIP remains published for history but is not recommended for new v0.1.0 bridge attempts.

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.