v0.1.0-beta.37

Ez 0.1.0-beta.37

• OpenCode now lists installed models and provider variants in Choose AI, chat, and scheduled tasks. Provider credentials remain required for paid models; EZ_OPENCODE_PROVIDERS scopes the menu. The relay image includes pinned OpenCode 1.18.32.
• The isolated plugin broker allows an unbound plugin even when another installed plugin has a host network binding. Bound plugins still fail closed.
• Pi is available as a native executor with exact session IDs and pinned Pi 0.87.1 in the relay image. Curated Pi models require Pi provider credentials.

Existing deployments need an installer-owned bootstrap for the new Compose environment field before automatic main upgrade. The model-less default still follows the native client's provider choice. Unreal Agent support is deferred until provider configuration can stay outside the agent-writable workspace.

This beta has source, package, container, and synthetic relay acceptance. Real account and reboot acceptance remain deferred under the beta release policy.

Verification: reviewed release PR, main CI, and trusted publisher readback. The npm registry tarball matches candidate.tgz at SHA-256 9d63308f3a6ed658b1f2b5b498e9d811c35b9f3333ed330dd9a46e853ff33f64.

v0.1.0-beta.36

• Move relay run/outbox/inbox bookkeeping into relay memory behind the control
  delivery socket. A restart drops in-flight runs and queued deliveries by
  design; Telegram redelivery is the replay mechanism. The live socket replaces
  the relay flock as the single-relay guard.
• Slim the spawn core to spawn and stream only. Callers authorize admission and
  pass the one trigger suffix; the core no longer reads the run ledger, history
  or workspace.
• Add a dedicated plugin-broker service (isolated profile) that owns Docker
  access with no network access. Isolated plugin commands run over a Unix socket
  with single-use capabilities, pinned revisions and per-invocation receipts.
• Publish installed plugin versions through the broker and report the deployed
  build identity; show the running RC tag, isolation/transport mode and host
  platform in /status.
• Add ezenciel-agents-provision-telegram to attach a Telegram channel to an
  existing botless deployment using that deployment's installed image.
• Add the Telegram /tasks list with numbered detail, attach Telegram identity
  to an existing web owner, and infer Telegram transport from the token instead
  of EZ_TELEGRAM_ENABLED.
• Remove PagerDuty and Workforce Watch from core. Authorization, transport,
  scheduling, safety gates and delivery receipts remain.
• Stop waking the agent for software updates. The supervisor no longer writes an
  attention notice and the relay no longer queues a wrapper-owned
  software_update_attention run, so nothing outside the managed ez tools
  locator is injected into an operating agent. ez updates stays owner-invoked.
• Stop injecting a package-owned coding handbook into operating-agent
  AGENTS.md. Upgrades strip the old ez shared guidance block. Seed only the
  installer purpose. The managed ez tools locator binds the agent launcher
  (ez --help and ez tools list --details); inventory is generated on read.
  Do not create inbox/, work/, SOUL.md, or USER.md.
• Generalize compatibility bridge upgrades so .compat.N builds hand off to
  their canonical release, and allow reviewed legacy homes without docker.env.
• List the agent-bound Codex catalog in /ai for local relays, make declared
  provider models authoritative and migrate persisted provider selections.
• Source-checkout RC builds require a clean reviewed commit and an increasing
  .rc.N label; the label and commit SHA are baked into the image and shown
  first in /status.
• Existing host-capable deployments need one installer-owned migration before
  this release: ezenciel-agents-install migrate-ledger --deployment <dir> adds
  the authenticated loopback ledger endpoint. Pre-beta.36 deployments also need
  the installer-owned bootstrap because the new plugin-broker service and
  environment changes do not match the previous release's deployment gate.
• Fix plugin application context delivery into the command container, plugin
  status JSON parsing under Compose warnings, and EPERM lease liveness.

Artifact: candidate.tgz, 260 files, SHA-256
1b969e452ae6006d27bcb50254c33cced8aa8a0c2ff5c71932d69c889fed6b4d.

Beta limitations: real-account fresh-host/reboot acceptance remains pending
before stable release. Publication does not imply deployment. Pre-beta.36
deployments need the installer-owned bootstrap because the new plugin-broker
service and environment changes do not match the previous release's deployment
gate; existing host-capable deployments also run
ezenciel-agents-install migrate-ledger --deployment <dir> once. Compatible
main updates remain automatic while the effective deployment layout is
unchanged.

v0.1.0-beta.34

• Correct setup guidance for host-capable custom Codex providers and replace
  stale pinned-beta installation guidance with current release records.

• Record an isolation class at agent creation. The default is isolated: the
  native CLI runs in the relay (EZ_EXECUTOR_TRANSPORT=local). Pass
  --isolation host-capable to reuse the installer UID and host CLI login.
  Mismatched class and transport fail closed. Isolated Codex sets
  EZ_CODEX_SANDBOX=external. Host transport is not started for isolated
  agents. Unlabeled existing host transports stay host-capable.

• Install pinned Codex CLI 0.153.4 in the relay runtime image so isolated
  agents resolve codex on PATH. Isolated jobs keep auth in
  control/cli/codex and do not link the operator ~/.codex.

• Confine macOS host jobs to their bound workspace and prevent cross-agent
  plugin registry access.

• Support agent-scoped OpenRouter models through the native Codex engine and
  start a new native session when the provider or model changes.

• Resolve native CLIs from the host PATH, expose captured presets in application
  run receipts, and seed one purpose-scoped AGENTS.md for new agents.

Beta limitations: real-account fresh-host/reboot acceptance remains required before stable release. Publication does not imply deployment; saved installation policies apply. Custom Codex providers currently require host-capable setup.

v0.1.0-beta.33

Compatible plugin updates can add commands to existing services and register their aliases atomically, while preserving collision checks and rejecting changed existing routes or deployment authority. Contribution guidance and independent review instructions are simplified.

Exact candidate SHA256: de487da5623dd8037587d182f7e3e88d904de9479a61cc0064cfb35a6f2084c3.

Verification: required Node 22/24 and Docker CI; source Docker 456 passed/1 skipped; exact packed artifact clean install/help/runtime build,25 updater tests and runtime/status smoke checks. Production dependency audit: 0 vulnerabilities. Independent final-head review recorded on release PR #152. Mac process-inspection tests are restricted by the sandbox; Docker and hosted checks pass.

This is a SemVer/GitHub prerelease distributed through npm latest. Existing beta limitations for fresh-host/reboot and live provider acceptance remain. Publication is separate from installation; no runtime rollout is claimed by this release.

v0.1.0-beta.32

Reviewed daily beta release 0.1.0-beta.32. Final-head review, CI and exact packed Docker/runtime checks passed. See PR#148 for changes and evidence.

Human live-provider/audio/reboot acceptance remains the documented beta limitation; this publication does not claim production rollout.

SHA-256: 302f874e9f8041c8441e419da83cca64fd521e024acfea24de9d32857b5fc1b9

v0.1.0-beta.31

Ship owner-authorized contribution completion guidance.

Source: ac47f1c
Candidate SHA-256: dcd9e585a251671ce3804afa50930577bb9d46c5612032000143d30a84024b3c

v0.1.0-beta.30

0.1.0-beta.30

• Bind installed native command launchers to the deployment's canonical control directory.
• Make application registration use the owning agent's state and prevent caller environment variables from redirecting that authority.

Independent exact-head review, Node 22/24 CI, Docker CI, packed-artifact validation and runtime smoke all passed.

v0.1.0-beta.29

0.1.0-beta.29

• Republish the beta.28 Voice connection and web-serving contract at a monotonic
  version so installations already running private beta.28 QA builds can upgrade
  through the standard verified public-package path. Runtime behavior is unchanged.

This prerelease is the compatible public upgrade path for the Voice beta.1 QA.

v0.1.0-beta.28

Core beta 0.1.0-beta.28 adds authenticated application channels, named Telegram
conversations, owner-bound persistent plugin connections and loopback-only plugin
web serving. It also registers the public Voice plugin and documents the native
engine, transport and plugin ownership boundary.

This remains a beta for trusted-host deployments. Provider, device and public
ingress acceptance are separate from automated package and Docker verification.

Verified source: 97284868d2086397bf52cbf6a59c8b2ccb224e45

Verified artifact SHA-256: 6ff72bd4517b6617a3427bf725fc38b3b5002541198657433a239d51a4ec7318

v0.1.0-beta.27

Engine-first execution and responsive chat

• Literal task requests and native goal ownership; less prompt assembly and shared instruction overhead.
• Engine-owned concurrency, with per-request authorization, ownership and cancellation retained.
• Installed-plugin guidance discovered on demand.
• Chat delivery/acknowledgement guidance and inline newline handling.
• Active scheduled-task details and simpler client/model/reasoning selection in Telegram.
• Maintenance-loop and transport-failure isolation fixes.

Verified with independent review, Node 22/24 CI, isolated artifact tests and Docker relay smoke. Beta limitations remain: synthetic menu tests are not live Telegram UI acceptance, and package publication does not upgrade existing deployments.