Skip to content

0x2F 0.3.0

Choose a tag to compare

@AleksandrMalinin AleksandrMalinin released this 02 Nov 22:58
· 24 commits to main since this release

0x2F0.3.0 — release scope and upgrade

Release date:2026-11-02. npm 0x2f@0.3.0, tag v0.3.0.
Local work routing for macOS and Linux/POSIX, Node.js≥20. Current platform
verification uses macOS arm64/Node26.11.1 and Ubuntu26.04.1 x86_64/Node26.13.0.

Changes since published0.2.0

  • CANCEL targets the current execution occurrence, waits for the owned process
    group and preserves partial artifacts. Recovery distinguishes dead/mismatched
    process identity; saved numeric PIDs do not grant future signaling authority.
  • Git task worktrees separate executions from the original checkout. Immutable
    snapshots and saved patches support review and explicit apply. Archive/restore
    retain unfinished bytes; cleanup refuses unsupported ignored/index/reserved
    states instead of deleting data. Shared mode still permits external writers.
  • Project-configured checks freeze argv/timeout plans before launch and retain
    actual output hashes and exit receipts. They execute as the host OS user,
    outside provider sandboxing. READY/check success is separate from human ACCEPT.
  • Exact per-attempt input/context receipts retain notes, current rules, decisions
    and earlier results within explicit size limits. Tool evidence stays bound to
    its execution. Fresh-session continuation differs from native provider resume.
  • Explicit Linux remote-host commands use strict known hosts and recheck the
    pinned machine identity on the actual execution connection. The work executes
    on that host; tasks, dirty files and credentials are not migrated between hosts.
  • Quiescent private backup retains a self-contained workspace, Git and task state;
    integrity-checked restore uses a new root and disables execution/replay authority,
    relay credentials and host profiles. It does not automatically launch work.
  • Web/mobile surfaces add task creation, correction and occurrence-bound CANCEL;
    refused/ambiguous mutations preserve draft or require inspection. TUI/Web review
    exposes saved runs, input, changes and independent check evidence.
    -057 may observe0x2F externally through its opt-in engineering reader. No057 Core,
    renderer or Mobile public application is bundled or publicly upgraded by0.3.0.

Commands and precise authority boundaries.

Qualification linkage

Historical independent qualification used source checkpoint
839e980dd20db3ea058ef4abc707ceeb322a0e93 and candidate tarball0x2f-0.2.0.tgz, SHA256
4aa0dd547bf3245a78acca09133ecf070a48fc74e3cc5d5afff74e5270250626.
That candidate differs from published registry0.2.0. Its reports are not relabelled
as0.3.0 tests. On those bytes, Mac821tests and Linux811tests/10explicit skips,
installed69critical/83encrypted contracts per platform, and a full real Linux
Codex0.166.0/openai/gpt-6.1-sol two-run/check/restart/backup/restore loop passed.

The0.3.0 artifact comparison permits only package/ACP client version metadata
and current README release text. All other packaged product files must match
that candidate byte for byte. Fresh source regression/build and exact installed
package contracts/smokes are recorded in the 0.3.0 release checkpoint. The proven
AI loop is linked through unchanged behavior, without repeating paid/live models.

Upgrade and rollback

  1. Quiesce old workers and other writers; inspect active tasks before service stop.
  2. Preserve the previous prefix, service configuration and a consistent private
    workspace/state backup. Backups can contain secrets; retain owner-only access.
  3. Install the published0.3.0 into a separate prefix, verify it, then update the
    normal launcher/service during quiescence. Preserve pairing, machine identity,
    enabled/linger state, settings and provider defaults.
  4. Keep a matching0.3.0 executable for new isolated tasks. Old0.2.0 does not own
    their checkout/execution contracts and must not execute them against source.
  5. For rollback, quiesce the new runtime and restore the matching prior prefix
    and consistent old state, retaining newer evidence. Restored work has no live
    credentials/host/execution authority; configure trust deliberately afterward.

Limits and deferred work

Worktrees/check environments are not OS sandbox containment. Escaped process
groups, universal per-harness permission/resume/cancel parity, acknowledged live
steering, closed-client push, independent phone registrations, host-to-host task
migration, cold reboot/production rollback drills and long-duration thermal/pixel
behavior are not newly qualified. Mobile interruption/runtime-error recovery
remains UNVERIFIED in a separate owner-approved follow-up; it is not a0x2F gate.
No App Store/notarized057/Mobile distribution is part of this release.

Release artifact verification

Release commit: 33a09878a3f7c941771265e6d1f865cb1aee06f6.

SHA-256: 7cf66322908f446fcd777c62664b425e000a9a752e50d8cbc3e5e84f4285c1be.

Fresh source regression: 821 passed; syntax and client build passed. Exact installed package on Mac and Lenovo: 120 critical/ACP, 73 encrypted remote, 117 CLI/TUI/Web tests per platform; two-run/check/restart/backup/restore fixture and HTTP/CLI reopen smoke passed. Real AI qualification remains explicitly linked to the historical candidate through unchanged behavioral bytes.

Install: npm install -g 0x2f@0.3.0.