What changed in each release.

• The behaviour of 0.3.0, described below, published. The upgrade notes for 0.3.0 apply unchanged.
• The release build remaps the cargo home, the source export and the build target to /cargo, /mantle and /target, so the binaries name no directory of the build host. The 0.3.0 binaries named the CI runner’s home, and the organization’s release checks refused to upload them.

Not yet verified for 0.3.1: installation from the published assets and any run on a live worker with Substrate 0.16.1.

• Compatibility change: Substrate 0.16.1 (was 0.7.10), SDK revision f2fd606b88a0b778970e8babe9a96eb600cd57b2, wire bundle substrate-wire/0.25.0. A new worker installs the daemon from Substrate’s signed release archive, checked against pinned digests. A 0.2.0 worker cannot be used; see below.
• agent.kind: command: the session’s process is a declared argv, run without a shell and without an agent credential. See configuration.
• Wire behaviour that changed between Substrate 0.7.10 and 0.16.1, such as storage limits that are not a multiple of 1024 bytes and the 16-attachment limit per subject, is listed in CHANGELOG.md.
• The specification is pinned to ESS 0.77.0. The native inventory is 508 scenarios.
• The documentation is split into a short README and these site pages.

Upgrading from 0.2.0

A 0.2.0 worker runs Substrate 0.7.10, and the 0.3.0 CLI and helpers cannot use it. The 0.3.0 Substrate SDK refuses a daemon that does not advertise substrate-wire/0.25.0; 0.7.10 advertises substrate-wire/0.17.0. mantle doctor fails its live Substrate version check, and mantle worker upgrade --check reports incompatible; --apply reports the same and changes nothing.

No Mantle command moves an existing worker to Substrate 0.16.1. Cloud-init installs the daemon when mantle worker up creates the VM; on an existing VM, worker up starts it and does not replace the running daemon. Sessions on 0.3.0 need a new worker created by the 0.3.0 mantle worker up. Keep the 0.2.0 CLI for sessions on a 0.2.0 worker, and save wanted work from its workspaces before you retire it. Substrate’s state store upgrade is one-way: earlier daemons refuse a store that 0.16.1 has stamped.

Tag 0.3.0 exists and its tagged-source CI passed, but it has no GitHub release and no published assets: the upload was refused because the binaries named the CI runner’s home directory. Install 0.3.1 instead.

Not yet verified for 0.3.0: any run on a live worker with Substrate 0.16.1 (doctor, Claude Code, Codex or command sessions), and the upgrade path above, which is read from the code. The integration source records 508 native scenarios passing in the coverage ledger.

• Compatibility change: mantle stop NAME keeps the workspace and the private agent home. mantle destroy NAME --yes deletes them. restart starts a fresh agent in the retained workspace; it does not resume a conversation.
• mantle exec returns the remote exit code and output; missing or indeterminate results fail. Release 0.1.4 could exit 0 when the remote command failed.
• Named profiles, mantle doctor, JSON metadata and creation receipts.
• Verified Linux x86-64 bundles: the CLI, the mantle-release installer, the mantle-acceptance runner and the static worker helpers; offline helper upgrades that keep worker data.
• Historical 0.1.4 STOPPING records keep their destroy intent. Existing workers need the matching helpers and the pinned Substrate 0.7.10.

Tagged-source CI passed all 499 conformance scenarios, the static worker builds and the bundle verification; the publisher checked the four uploaded asset digests and the remote tag. Source commit 54710558ebe096a8e5faf98bbb430ff7f9eaa17e. Release · what is verified.

Integrates the final 0.1.3 release and acceptance records and refreshes the documentation. Runtime behaviour is unchanged from 0.1.3: attachment-readiness handshake, Substrate 0.7.10’s bounded output queue, pinned Codex 0.153.4. After receiving the corrected versioned CLI and isolated profile command, the operator confirmed that attachment worked; this is an operator statement, and full authenticated lifecycle qualification remains incomplete.

Upgrading a 0.1.4 worker

Upgrade the laptop CLI, the worker launcher and the Substrate runtime together. Check mantle list and mantle status NAME, preserve wanted project changes and workspace data, and plan maintenance before replacing a running daemon: restarting Substrate can interrupt its executions. mantle worker up starts services but does not restart an already running older daemon, and defers changed shared binaries while services are active, so running it again does not prove the worker has the compatible runtime. Verify installed and running versions after maintenance, or provision a separate worker for new sessions. From 0.2.0 on, use offline upgrades.

Build the 0.1.4 CLI and static worker binaries from the 0.1.4 tag; the release has source archives only.

A production Codex attachment had failed with session.output-backpressure. 0.1.3 waits for the terminal client to be ready before replaying launcher output and adopts the signed Substrate 0.7.10 daemon with its exact SDK revision. A temporarily full output queue now waits up to one second per frame for its consumer. Queue and output limits are unchanged and terminal recording policy is unchanged; a stalled consumer can still end an attachment with session.output-backpressure.

Evidence: a local, confined synthetic test delivered the full 262,144-byte replay twice through real PTYs, with the exact keyboard reply and restored terminal settings, and reattached to the same agent; that run’s final workspace-destroy call returned operation.outcome-unknown, so its command exited 1, and cleanup was confirmed separately (log). On an isolated KubeVirt worker with the signed Substrate 0.7.10 daemon, two real Codex 0.153.4 attachments through 100×50 PTYs ran 12 seconds each and detached with exit 0; the second reused the same agent, and existing workers and sessions were preserved (record). These establish transport behaviour, not visual screen correctness, device login or authenticated model and tool use.

New agent and mantle exec requests select gcc as the Rust linker and C compiler and g++ as the C++ compiler; Ubuntu’s cc alternatives resolve outside the confined mount set. Filesystem and network boundaries are unchanged. This still holds in 0.2.0.

Evidence on a live KubeVirt worker: a confined cargo check of a package with native dependencies exited 0 (62.76 s on the worker, 0.13 s of laptop CPU); two Codex workspaces passed marker-isolation checks; TLS to OpenAI through the gateway worked; an unlisted destination and direct egress were refused. These were supplementary commands, not authenticated model-issued tool calls (audit). In this release mantle exec could still exit 0 after a remote failure; 0.2.0 fixed that.

Fixes a GNU/musl statfs field type mismatch in the static worker build, keeping the verified-tmpfs requirement for volatile diagnostics. CI now builds all three static worker binaries. 187 Rust tests and 336 native scenarios passed.

Manifests select pinned Codex 0.153.4 with ChatGPT device login; Claude Code stays available. Both agents use the existing Substrate terminal transport, so Codex no longer waits for a non-recording capture feature. Codex auth and conversation files stay in its private workspace home, diagnostics on verified tmpfs, launcher replay in memory. Workers are provisioned independently of Claude credentials, the gateway admits the two Codex destinations, and terminal attachments stay cancellable under backpressure. Device login, authenticated turns, token refresh and lifecycle parity were not verified.