npm - @vtxmacro/cli - Versions diffs - 2026.8.54 → 2026.8.56 - Mend

@vtxmacro/cli 2026.8.54 → 2026.8.56

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (4) hide show

package/README.md +10 -5
package/bin/vtx-service-bootstrap.js +1540 -0
package/bin/vtx.js +161 -51
package/package.json +1 -1

package/README.md CHANGED Viewed

@@ -16,11 +16,16 @@ verifies the Codex runtime's version and digest before use; it does not borrow a
 Codex binary from PATH or an editor extension.
 For Windows-login auto-start, install and configure the CLI from native Windows;
 a CLI installed only inside WSL cannot start the WSL virtual machine at login.
-An npm update does not replace code already loaded by a running durable service.
-After updating, check `vtx inference-host service status --json`. If the service
-was already desired-running, run `vtx inference-host service stop` followed by
-`vtx inference-host service start`, then verify status and logs. Leave an
-intentionally stopped service stopped until you want to run it.
+New service installations use a private verified launcher. At login and every
+service start, it checks the official npm registry, verifies the exact release
+integrity and installed CLI version in a new versioned directory, starts it as a
+candidate, and selects it only after every configured worker reports ready. A
+failed candidate is rejected and the last working runtime resumes. The service
+keeps only the active release and one rollback release. If the update check is
+unavailable, it keeps the last verified runtime. An intentionally stopped
+service stays stopped and makes no update request. Hosts installed before this
+automatic updater need one final normal npm update and service reinstall to
+adopt it.
 ## Configure