v0.2.22

New Features

• Install Open Machine through npm on Apple Silicon Macs with macOS 13+ and Node.js 20+. The package bundles Python, Git, Core and locked dependencies for offline first-run setup, with command execution and workspace writes enabled only by explicit grants. (#171, #179, #180)
• Control login startup with openmachine startup on|off and apply the verified bundled Core with openmachine update. Updating the npm package alone does not replace the running service. Updates preserve deliberate Stop, configuration, history and original operation IDs. (#186)
• Surface advisory notices when a newer official Core release is available. Release checks run asynchronously and do not block ordinary tool calls or automatically download, install or restart Core. (#158)

Bug Fixes

• Distinguish MCP validation failures from errors after a handler starts, with bounded diagnostics and original-result recovery guidance. Expose the server's catalog fingerprint and correctly mark additive Task creation as non-destructive. (#156)
• Return a nonzero exit status when openmachine start cannot verify Core readiness, while retaining its JSON diagnostics. (#184)
• Identify the trusted-review workflow by its immutable ID and verify assignee updates from GitHub's write response. (#166, #170)

Documentation

• Publish release-grounded setup, connection, verification, troubleshooting and update guides on the documentation website, with grouped navigation and direct links from the README. (#159, #161, #163, #169)
• Refresh the public project overview with npm onboarding, a working demo and contributor avatars; simplify contribution and collaboration guidance. (#157, #160, #168, #178, #181, #185, #187, #188)
• Remove private client references from public documentation and pin version-dependent examples and schema links to v0.2.22. (#155, #189)

Chores

• Synchronize the Core and npm package versions at 0.2.22. State contract 21, SSH protocol 7 and worktree receipt format 6 remain unchanged. Configured SSH targets still require matching prepared workers for new requests. (#189)
• Build release packages from the exact published Core tag, include pinned third-party sources and notices, and attest the resulting archives. (#177, #179, #182, #183)
• Move CI to GitHub-hosted runners, require trusted approval for external pull requests, route reviews to Core maintainers, fill missing metadata and keep required checks running after PR edits. (#162, #164, #167, #173, #175, #176)
• Independent clean-GUI-account, logout/relogin and reboot acceptance remains explicitly deferred for this early-development release. Current-login-session tests do not establish those behaviors. The npm package does not configure an MCP tunnel, connect a ChatGPT account, or provide an Apple-signed/notarized installer. (#189)

Changelog

Full Changelog: v0.2.21...v0.2.22

• #155 Scrub private client references from public docs @LuozhuZhang
• #156 Clarify client contract and handler failures @bella-chai
• #158 Surface non-blocking release notices @bella-chai
• #157 Launch public-facing project overview @LuozhuZhang
• #159 Add release-grounded user documentation @bella-chai
• #160 Prepare public contribution workflows @LuozhuZhang
• #161 Build and validate the Core documentation website @bella-chai
• #162 Use GitHub-hosted Ubuntu for all workflows @LuozhuZhang
• #164 Require trusted approval for external PRs @LuozhuZhang
• #163 Group navigation and apply the official logo @bella-chai
• #166 Identify review signal by immutable workflow ID @LuozhuZhang
• #167 Fill missing issue and PR fields @LuozhuZhang
• #168 Keep guidance essential and durable @LuozhuZhang
• #169 Link to the published documentation @bella-chai
• #170 Verify assignees from GitHub write response @LuozhuZhang
• #171 Add Apple Silicon installer and package build @LuozhuZhang
• #175 Make PR title style advisory @LuozhuZhang
• #173 Route reviews to core maintainers @LuozhuZhang
• #176 Run required checks on all PR edits @LuozhuZhang
• #177 Attest manually built Apple Silicon packages @LuozhuZhang
• #178 Show contributor avatars @LuozhuZhang
• #179 Bundle pinned third-party sources @LuozhuZhang
• #180 Align installer version with Core 0.2.21 @LuozhuZhang
• #182 Build from published Core tags @LuozhuZhang
• #183 Build released Core from local checkout @LuozhuZhang
• #181 Simplify collaboration guidance @LuozhuZhang
• #184 Fail start when Core is not ready @LuozhuZhang
• #185 Add concise npm onboarding @LuozhuZhang
• #186 Expose login startup and bundled Core updates @LuozhuZhang
• #187 Showcase the Open Machine action demo @LuozhuZhang
• #188 Show video directly beneath banner @LuozhuZhang
• #189 Prepare Open Machine v0.2.22 @LuozhuZhang

v0.2.21

New Features

• Add native, scoped GitHub Release creation with exact-tag checks, verified readback, and original-operation recovery safeguards. (#149)
• Support deleting top-level Issue and PR comments with verified parent identity, timestamp guards, and confirmed deletion readback. (#150)

Bug Fixes

• Restore bounded original Task receipt observation across local and distinct SSH targets while preserving route checks, original IDs, and non-replay boundaries. (#153)
• Improve native execution workspace-lock conflict diagnostics with the actual launch cwd and lock root without changing existing lock behavior. (#151)

Documentation

• Document squash as the default method for explicitly authorized PR merges unless another method is requested. (#152)
• Clarify that command launch cwd, rather than cd or Git -C within argv, selects the workspace lock. (#151)
• Pin README, setup, managed service, and runtime payload examples to v0.2.21. (#154)

Chores

• Route private repository quality and metadata checks to the repository runner, retaining GitHub-hosted Ubuntu fallback when public or unconfigured. (#148)
• Bump the Open Machine package version to 0.2.21. State contract 21, SSH protocol 7, and worktree receipt format 6 remain unchanged. (#154)

Changelog

Full Changelog: v0.2.20...v0.2.21

• #148 Route private checks to repository runner @LuozhuZhang
• #149 Add verified GitHub Release document creation @LuozhuZhang
• #150 Verify top-level Issue and PR comment deletion @LuozhuZhang
• #151 Clarify native execution cwd and workspace-lock conflicts @LuozhuZhang
• #152 Document squash as default PR merge method @LuozhuZhang
• #153 Verify multi-target Task observer receipts @LuozhuZhang
• #154 Prepare Open Machine v0.2.21 @LuozhuZhang

v0.2.20

New Features

• Add community Feature Request intake through a [REQUEST] Issue template with a dedicated feature-request label. (#143)
• Allow the native GitHub connector to add Pull Requests, as well as Issues, to organization Projects V2 with repository identity checks and verified readback. (#146)

Bug Fixes

• Remove the Open Machine-only requirement to submit a current-HEAD PR review when GitHub does not require one, while preserving GitHub branch rules, CI checks, change requests and unresolved-review-thread guards. (#142)

Documentation

• Update contributor guidance and Issue templates for Feature Request intake and the [BUG] and [ROADMAP] title conventions. (#143, #144, #145)
• Pin README, setup, managed service installation and runtime payload examples to the v0.2.20 tag and wheel. (#147)

Chores

• Standardize Bug Report titles to [BUG] and rename Program intake to [ROADMAP], preserving the existing Bug and Roadmap labels and fields. (#144, #145)
• Bump the Open Machine package version to 0.2.20. State contract 21, SSH protocol 7 and worktree receipt format 6 remain unchanged. (#147)

Changelog

Full Changelog: v0.2.19...v0.2.20

• #142 Make submitted PR reviews optional in the native GitHub merge gate @LuozhuZhang
• #143 Add Feature Request intake @LuozhuZhang
• #144 Standardize Bug Report titles @LuozhuZhang
• #145 Standardize Roadmap titles @LuozhuZhang
• #146 Add Pull Requests to organization Projects @LuozhuZhang
• #147 Prepare Open Machine v0.2.20 @LuozhuZhang

v0.2.19

New Features

• Add GitHub Projects field management and release history reads. (#133)
• Support updating Core from an exact source commit, and expose the selected commit in version, doctor, service status and MCP capabilities. (#137)
• Add scoped runtime context observations with explicit source and coverage boundaries. (#139)
• Observe target runtime environment and bounded hardware, project and network-listener resources without executing project scripts. (#140)

Bug Fixes

• Allow a guarded managed Core cutover for cleanup-only unknown local execution history without rebooting, while retaining original receipts, resource guards and rollback safety checks. (#136)

Documentation

• Update the README, setup guide, service installation and runtime payload examples to reference v0.2.19. (#141)

Chores

• Update the package version to 0.2.19. (#141)

Changelog

Full Changelog: v0.2.18...v0.2.19

• #133 Add GitHub Projects field management and release history @LuozhuZhang
• #136 Allow rebootless Core cutover for cleanup-only history @LuozhuZhang
• #137 Support commit-based Core updates and source provenance @LuozhuZhang
• #139 Expose scoped context observations @LuozhuZhang
• #140 Observe target runtime environment and resources @LuozhuZhang
• #141 Bump the package version and installation examples to v0.2.19 @LuozhuZhang

v0.2.18

New Features

• Add an explicit, audited Task abandonment outcome for eligible unresolved original work after the native leader has exited, preserving immutable receipts and unresolved provider-effect exclusions. State contract 21. (#124)

Bug Fixes

• Correct Task continuation guidance after a previous Chat handoff timeout so a later explicitly authorized continuation can reuse the original guarded claim without bypassing no-replay rules. (#131)

Documentation

• Refresh Task, service, MCP, execution, and workspace guidance for the cleaned-up ownership boundaries and explicit recovery/abandonment lifecycle. (#123, #124, #125, #126, #127, #129, #130, #131)
• Update the README, exact-tag setup instructions, managed service installation wheel path, and packaged runtime build example to v0.2.18. (#132)

Chores

• Remove retired automatic Chat-recovery metadata compatibility from the runtime Task reader. Historical records using the retired fields require the separately authorized offline conversion before selecting this runtime; automatic recovery is not restored, and original receipts and unknown outcomes must be preserved. (#123)

• Consolidate Task receipts and ledger codecs, service subprocess ownership, MCP protocol and tool registrations, and execution/workspace ownership without introducing new public interfaces or changing existing GitHub, Task, and service safety boundaries. (#125, #126, #127, #129, #130)

• Bump Open Machine runtime version to 0.2.18. State contract 21, SSH protocol 7, worktree receipt format 6, and MCP SDK 2.2.0 remain unchanged by this release bump. (#132)

Changelog

Full Changelog: v0.2.17...v0.2.18

• #123 Retire Chat recovery compatibility @LuozhuZhang
• #124 Allow audited abandonment of unknown work @LuozhuZhang
• #125 Share Task receipts and ledger row ownership @LuozhuZhang
• #126 Give bounded service subprocesses a shared owner @LuozhuZhang
• #127 Clarify MCP protocol and integration ownership @LuozhuZhang
• #129 Clarify execution and workspace ownership @LuozhuZhang
• #130 Group MCP protocol and tools in one package @LuozhuZhang
• #131 Clarify Task recovery after a handoff timeout @LuozhuZhang
• #132 Prepare Open Machine v0.2.18 @LuozhuZhang

v0.2.17

Bug Fixes

• Persist and verify original GitHub merge intent across lost acknowledgements, process restarts and later destination-branch advances. Reconciliation retains the original HEAD, target branch and commit-text constraints, and never resends an uncertain merge. State contract 19 introduced the durable binding. (#116)
• Reconcile original native execution and worktree cleanup when the command exited but cleanup observation failed. Add bounded query retries, boot/session identity checks and local-only reconcile_execution with hash-bound supplemental evidence; preserve unknown status when proof is incomplete. State contract 20 validates retained reconciliation evidence. (#118)
• Preserve exact historical contract.recovery_policy and nullable chat_registration values in format-3/4 stored Tasks. Validate the original field pair and byte/hash integrity, reject those fields in new Task input, and retire the obsolete registration on explicit new plans. This fixes the managed v0.2.16-to-v0.2.17 compatibility gate without restoring automatic Chat continuation. (#121)

Documentation

• Update operating guidance for retired automatic Chat recovery and explicit continuation, GitHub merge-result reconciliation, and original native execution recovery. (#115, #116, #118)
• Pin exact-tag installation and runtime-payload examples to v0.2.17, and document state contract 20. (#119)
• Explain safe historical Task metadata reads and why original Task bytes must not be deleted or rewritten to complete a managed update. (#121)

Chores

• Permanently retire automatic Chat recovery, its controller/sidecar and recovery-only MCP/configuration surfaces. User-driven Task continuation and original execution receipts remain supported. Existing format-3/4 Task recovery fields are now preserved as read-only historical authority; managed upgrades must remove the obsolete [chat_recovery] configuration section without deleting or rewriting retained Task history. (#115, #121)
• Update the package version to 0.2.17. SSH protocol 7 and worktree receipt format 6 are unchanged. Managed updates must validate all retained original records before activation. (#119)

Changelog

Full Changelog: v0.2.16...v0.2.17

• #115 Permanently retire automatic Chat recovery @LuozhuZhang
• #116 Reconcile retained GitHub merge outcomes @LuozhuZhang
• #118 Reconcile retained native cleanup @LuozhuZhang
• #119 Prepare Open Machine v0.2.17 @LuozhuZhang
• #121 Preserve retired recovery fields for v0.2.17 @LuozhuZhang

v0.2.16

Republished to include the complete managed-update preflight recovery fix. (#113)

Bug Fixes

• Fix legacy Task migration for prefix-related IDs such as task-one and task-one-c1. Sort manifest entries by POSIX path strings to match SQLite verification, preventing identical historical files from being rejected because of their order. Original hashes, bytes, IDs and activation guards remain authoritative. (#112)
• Allow the existing recovery path to complete an unfenced v0.2.15 import using the corrected candidate while preserving the original database identity, stable lock and legacy archive. Read original legacy history during activation preflight while the prepared database is inactive; newly added unresolved operations still block activation, and corrupt or dual authority remains rejected. No history deletion or effect replay is introduced. (#112, #113)

Documentation

• Document manifest ordering, original-history activation preflight and safe recovery before cutover. Pin installation examples to v0.2.16. (#112, #113)

Chores

• Update the package version to 0.2.16. State contract 18, SSH protocol 7 and worktree receipt format 6 remain unchanged. (#112)

Changelog

Full Changelog: v0.2.15...v0.2.16

• #112 Fix Task migration ordering and release v0.2.16 @LuozhuZhang
• #113 Restore managed activation after an unfenced failed import @LuozhuZhang

v0.2.15

New Features

• Store Task authority and history in one transactional SQLite ledger. Bounded summaries, operation/history pages and exact original-ID lookups let long tasks retain their evidence without exhausting the former cumulative record limit. Side-effect admission and original receipts retain their existing safety boundaries. (#110)
• Discover seven built-in operating Skills and their focused guides from one canonical package. Direct tool-to-guide navigation and bounded reads reduce the amount of unrelated guidance loaded for each operation. (#106)
• Show advisory task context in execution receipts, distinguishing standalone work, legacy checkpoints and verified structured supervision. Scope failures include precise continuation pointers without changing command results or admission rules. (#109)

Bug Fixes

• Preserve an existing verified management binding when Core is updated through a legitimate wheel-only installation. Persistent Stop remains available while first-time binding still requires a trusted retained payload. (#107)

Documentation

• Centralize operating guides under openmachine/skills/, retain compatible read routes, and retire scattered manuals. Document Task ledger reads, original-result recovery and guarded migration. (#106, #110)
• Pin installation examples to v0.2.15 and document the current SQLite requirement and state contract. (#111)

Chores

• Update the package version to 0.2.15. (#111)
• Advance the service state contract to 18. Managed activation imports legacy Task formats 1-4 and Markdown, preserves byte-identical archives, and fences old writers. After cutover, resume the original candidate if activation is interrupted; an older runtime must not restore stale JSON authority. SSH protocol 7 and worktree receipt format 6 remain unchanged. (#110)

Changelog

Full Changelog: v0.2.14...v0.2.15

• #107 Preserve existing management binding on Core updates @bella-chai
• #106 Centralize operating Skills and direct tool discovery @LuozhuZhang
• #109 Expose advisory execution task context @LuozhuZhang
• #110 Persist Task history in a transactional ledger @LuozhuZhang
• #111 Bump the package version and installation examples to v0.2.15 @LuozhuZhang

v0.2.14

New Features

• Discover, create and explicitly select Git worktrees for independent coding tasks. Creation pins a locally available base commit, preserves the original checkout and dirty files, and retains the original execution receipt for safe result recovery. Isolation remains an explicit task decision. (#103)

Bug Fixes

• Recover an expired continuation claim in the same Chat turn through an explicit renewal of the original claim. Lease expiry now returns renewal_required without forcing the turn to end; new effects remain blocked until renewal succeeds. Pause, cancellation, authority expiry, unverified work and bounded foreground waits retain their existing guards. (#102)

Documentation

• Check task leases before and after long external work or CI waits, and immediately before review, merge or another critical effect. Document bounded same-claim recovery and one corrected retry for verified observation-only revision drift. (#101, #102)
• Add a separately packaged worktree operating guide covering discovery, creation, selection, permissions and original-result recovery. (#103)
• Pin installation examples to v0.2.14 and refresh the README release summary. (#104)

Chores

• Update the package version to 0.2.14. (#104)
• Ship state contract 17, SSH protocol 7 and worktree creation receipt format 6. Ordinary format-5 and historical execution receipts remain readable. Configured SSH workers require the matching endpoint before using the new protocol. (#103)

Changelog

Full Changelog: v0.2.13...v0.2.14

• #101 Add lease checks around long external work @LuozhuZhang
• #102 Recover expired continuation claims without weakening stop guards @LuozhuZhang
• #103 Add on-demand Git worktree discovery, creation and selection @LuozhuZhang
• #104 Bump the package version and installation examples to v0.2.14 @LuozhuZhang

v0.2.13

New Features

• Wait for task progress with wait_task, which returns within 30 seconds with a change, completion, or a reason to stop waiting. Responses include whether the original work may still be running and guidance for resuming safely. (#95)
• Resolve or reopen pull-request review threads through the native GitHub integration, with exact PR, HEAD, thread and actor checks plus verified readback. (#98)
• Retire a deferred managed update with manage retire --operation-id ... when it is verified to be safely before activation, allowing a replacement update while preserving the original operation and prepared installation. (#93)
• Renew task claims within their existing authority and use bind_effect_scope to establish the resource scope of a historical GitHub request without repeating it or changing its original outcome. (#94)

Bug Fixes

• GitHub connection and rate-limit failures proven to precede a write, and workspace requests rejected before any change, now retain their no-effect evidence instead of leaving tasks unnecessarily uncertain. Rate-limit responses include bounded wait guidance. (#91, #92)
• Uncertain GitHub operations no longer block unrelated resources or freeze unrelated repository bindings during plan revision. Binding a historical request's exact scope can proceed after local HEAD changes, while new local work still requires the accepted HEAD. (#94, #96)
• Creating a PR with independent source and target branches no longer conflicts with unrelated numbered PRs in the same repository; duplicate creation and overlapping effects remain guarded. (#97)
• Compatible managed updates no longer stall on retained external GitHub uncertainty or verified historical workspace validation failures. Active executions and unresolved local effects continue to block unsafe activation. (#92)
• Historical uncertain Chat preparations can coexist with a compatible update once their exact original executions have terminated with verified cleanup and no unresolved control. Their preparation outcomes remain unchanged and do not imply that a browser receiver is ready. (#99)

Documentation

• Task and operating guides now cover bounded foreground waits, safe resumption and historical effect recovery, including checking installed capabilities before using newer task controls. (#94, #95, #96)
• Installation examples now pin v0.2.13, and the README summarizes this release with the implemented state contract, 16. (#100)

Chores

• Source verification and PR metadata checks now run separately in CI, with a local metadata preflight for validating PR titles and bodies before publication. (#94)
• Updated the package version to 0.2.13. (#100)

Changelog

Full Changelog: v0.2.11...v0.2.13

• #91 Preserve recoverable failure evidence and rate-limit guidance @LuozhuZhang
• #92 Keep proven no-effect history from blocking compatible updates @LuozhuZhang
• #93 Add explicit retirement for deferred pre-activation updates @LuozhuZhang
• #94 Scope uncertain effects and restore bounded task continuation @LuozhuZhang
• #95 Add bounded foreground waits with attention and resume guidance @LuozhuZhang
• #96 Narrow historical effect recovery guards for independent work @LuozhuZhang
• #97 Isolate PR creation conflicts by source and target branches @LuozhuZhang
• #98 Add native GitHub review-thread resolution and reopening @LuozhuZhang
• #99 Permit compatible updates after uncertain Chat preparations have settled @LuozhuZhang
• #100 Bump the package version and installation examples to v0.2.13 @LuozhuZhang