chore(master): release 0.8.2

[arcbox-labs]

🤖 I have created a release beep boop

0.8.2 (2026-10-03)

Features

• agent: add an in-memory table for the Mac's AppleDouble sidecars (9e5dfa4)
• agent: add the machine export's id table (c83e606)
• agent: answer EnsureMachineExport with an export on the bridge NIC (4e80448)
• agent: keep the Mac's AppleDouble sidecars out of the machine (76b127d)
• agent: map machine export attributes and ownership (2c44340)
• agent: serve the machine root as an NFSv3 filesystem (9ed3b53)
• agent: write through the machine root export (b325e39)
• cli: add machine clone, export, import, resize and default (7b56e3b)
• cli: let machine exec and ssh pick the default machine and a user (5702361)
• cli: uninstall the host mount root and the layout before it (3d17602)
• cli: unmount machine roots a daemon left on uninstall (d45b33b)
• constants: derive the docker and machine mount points from one host mount root (fe37506)
• core: resize user machines against the host and keep a default machine (85d42fa)
• daemon: add the machine export mount mechanics (ed9d01b)
• daemon: mount running machines' roots under ~/ArcBoxMachines (93f1c67)
• daemon: mount the docker export and machine roots under one host root (2cafe0c)
• daemon: register the local-domain names with mDNSResponder (6c32222)
• daemon: release the mounts a previous daemon left under the host root (8fb75a1)
• engine: ask a machine for its root export and announce its stop (d88b6c5)
• engine: change a machine's CPU and memory after it is created (320879b)
• engine: clone a stopped machine with a copy-on-write data disk (8e7e0e5)
• engine: export and import machines through the archive (d9728e2)
• engine: read a machine archive's manifest and restore its data disk (8142d2d)
• engine: write machines to a sparse tar.zst archive (0eec7bb)
• net: stream local-domain DNS changes for a mirror of the table (86273f1)
• protocol,api: add machine clone, export, import, resize and default RPCs (0ee9bca)
• protocol: add the EnsureMachineExport agent RPC (c75c0ea)

Bug Fixes

• agent: power a distro machine off through its own poweroff command (6020a63)
• daemon: bind the DNS socket before the VM boots (420d1fe)
• daemon: recognize the ~/ArcBox mount behind a symlink and bound mount_nfs (bf3705f)
• daemon: retry a machine root unmount that failed (b5411f2)
• daemon: unmount ~/ArcBox without stat'ing it and force it when busy (3044b3f)
• deps: update dependencies for disclosed vulnerabilities (#709) (479d630)
• docker: republish container ports after a System VM restart (02abbb0)
• engine: let a force stop wait for the host to release a machine's root (0b3116c)
• engine: wait for the host's release before a graceful stop too (a1515ee)
• fs: send Linux errno values in FUSE replies (#718) (032942d)
• migration: expose prepared replacement targets (#729) (fc1cbca)
• net: answer unknown local-domain names with NODATA, not NXDOMAIN (0b27750)
• transport: describe the vsock address with libc::sockaddr_vm (dc8f3d8)

Code Refactoring

• agent: clear the clippy 1.99 findings on the musl target (af91385)
• api: split the machine service's rootfs resolution out of create (1ea055c)
• core: read the host mount table where the daemon and abctl share it (a62d2e7)
• daemon: read the mount table through arcbox-core (43a9192)
• engine: share the machine name check and VirtioFS share list (4c81641)

Tests

• app: compare emptiness assertions against an empty value (426352d)
• computer: compare emptiness assertions against an empty value (8dd3914)
• e2e: follow the single host mount root (1c23dd2)
• e2e: improve sandbox phase polling resolution (#690) (550f94b)
• e2e: read and write a machine's root through its host mount (abdefeb)
• engine: compare emptiness assertions against an empty value (1a471e6)
• runtime: compare emptiness assertions against an empty value (aae51fa)
• virt: compare emptiness assertions against an empty value (fcabbcd)

Documentation

• agents: name the single host mount root in the mount notes (3b9283d)
• agents: record machine root mounts, lifecycle verbs and the fixed NFS teardown (2b7dbfd)
• agents: record the vendored fleet proto contract (f7df107)
• describe machine clone, export, import, resize and the default machine (9e64496)
• name the machine directory contents and the transfer staging directories (6e6d85b)
• readme: name the docker export mount point in the feature list (ba330e5)
• record the machine root export decision and measurements (7e0b01b)
• record the single host mount root (ADR 0003) (5d46007)

Continuous Integration

• guest: run the agent's unit tests on the Linux runner (#689) (60a9004)

Miscellaneous Chores

• master: release fleet-agent 0.1.7 (#727) (65594b3)
• master: release sdk-typescript 0.1.5 (#730) (91d85b8)
• net: remove the unused multicast mDNS responder (79f41d3)

---

This PR was generated with Release Please. See documentation.

[greptile-apps]

Confidence Score: 5/5

[Low risk] Version bump and changelog for release.

The release metadata changes appear safe to merge.

Summary

This release PR updates ArcBox to 0.8.2.

• Updates the release manifest, workspace crate versions, and lockfile.
• Adds the 0.8.2 changelog and records the TypeScript SDK 0.1.5 release.

_{Reviews (15) · Last reviewed commit: "chore: update lockfiles for release"}

[pullfrog]

✅ No new issues found.

Reviewed changes

Mechanical release-please PR cutting 0.8.2 from master — version regeneration only, no behavioral surface.

• Version bump — .release-please-manifest.json root entry and Cargo.toml workspace.package.version (plus every internal dep carrying the # x-release-please-version marker) move 0.8.1 → 0.8.2. Crates on their own cadence (arcbox-hv 0.3.20, arcbox-helper 1.1.0, external arcbox-boot 0.8.0) are correctly left untouched, matching the inline comments in Cargo.toml.
• Lockfile refresh — Cargo.lock bumps all arcbox-* crates to 0.8.2; every changed line is a version string, no dependency edges moved.
• Changelog — new 0.8.2 entry lists exactly one fix, fix(docker): republish container ports after a System VM restart (02abbb0), which is verifiably the only commit since the 0.8.1 release commit (7e029e99), so nothing was omitted.
• Release config invariants intact — release-please-config.json keeps draft: true + force-tag-creation: true on the root package only, and fleet/SDK tags still carry component prefixes, consistent with the release-process contract in AGENTS.md.

Verified against the release checklist: the tag push will trigger Release Build, and the draft stays assetless until package-and-release attaches the tarball — expected post-merge flow, nothing to change in this PR.

  ^{｜ View workflow run ｜ Using glm-5.3-flash ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes

Mechanical release-please PR — the delta since the prior pullfrog review (1bbe0151) is generated text only, re-cut after new commits landed on master.

• Expanded 0.8.2 changelog entry — the rebased release commit (e74d40df) now lists the transport fix (dc8f3d8), the agent clippy refactor (af91385), and five test: emptiness-assertion commits that landed on master since the prior review.
• Version/lockfile regeneration re-applied (baf189a1) — same shape as before: every changed line in Cargo.lock and every marked pin in Cargo.toml is a 0.8.1 → 0.8.2 version string; no dependency edges moved.

Verified against the full 7e029e99..origin/master range (11 commits): all 9 root-eligible commits appear in the changelog, and the 2 unlisted ones — 06775e1d and the new b049d30c test(fleet) — touch only fleet/ paths, so the root package's exclude-paths excludes them by design (the fleet-agent rides its own 0.1.7 train). Own-cadence pins (arcbox-hv 0.3.20, arcbox-helper 1.1.0, external arcbox-boot 0.8.0) remain untouched, and the PR head sits directly on master tip af913858. Post-merge flow per AGENTS.md unchanged: tag push triggers Release Build, the draft stays assetless until package-and-release attaches the tarball.

  ^{｜ View workflow run ｜ Using glm-5.3-flash ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes

Incremental re-review of the delta since the prior pullfrog review (baf189a1) — the release was re-cut on top of master tip 7e0b01b, and the delta is generated release text only.

• Expanded 0.8.2 changelog entry — the rebase swept in the machine root export train that landed on master: 12 features (agent NFSv3 root export, EnsureMachineExport RPC, daemon ~/ArcBoxMachines mounts, CLI unmount-on-uninstall, engine/protocol support), 2 daemon fixes (symlink-aware ~/ArcBox recognition, stat-free forced unmount), the machine-root e2e test, and the export decision docs (7e0b01b).
• Version/lockfile re-cut (12fc8d2 + 08cf30c) — same shape as both prior reviews: the manifest root entry and every pin marked # x-release-please-version move 0.8.1 → 0.8.2; every changed Cargo.lock line is a version string with no dependency edges moved; the lockfile text is identical to the previously approved state (the range-diff since baf189a1 shows no lockfile delta at all).
• Changelog completeness verified — over the full 7e029e99..origin/master range (27 commits): all 25 root-eligible commits appear in the entry; the 2 unlisted ones (b049d30c test(fleet), 06775e1d feat(fleet-agent)) touch only fleet/ paths and are excluded by the root package's exclude-paths by design (the fleet-agent rides its own 0.1.7 train). Own-cadence pins (arcbox-hv 0.3.20, arcbox-helper 1.1.0, external arcbox-boot 0.8.0) remain untouched, and the PR head sits directly on master tip 7e0b01bd.

Post-merge flow per AGENTS.md unchanged: the tag push triggers Release Build, and the draft stays assetless until package-and-release attaches the tarball.

  ^{｜ View workflow run ｜ Using glm-5.3-flash ｜ 𝕏}

[pullfrog]

✅ No new issues found.

Reviewed changes

Incremental re-review of the delta since the prior pullfrog review (08cf30c8) — the release was re-cut on top of the new master tip b5411f2, and the PR's own content remains generated release text only.

• Expanded 0.8.2 changelog entry — the rebase swept in the 14 commits that landed on master since 7e0b01b: 9 features (machine clone/export/import/resize/default across cli, core, engine, and protocol/api), 2 refactors (api rootfs split, engine shared helpers), 1 daemon fix (retry a failed machine-root unmount), and 2 docs. The entry now lists 39 root-eligible commits (21 features, 5 fixes, 3 refactors, 6 tests, 4 docs).
• Lockfile re-cut (0fec8b1) — the regenerated Cargo.lock is content-identical to the previously reviewed state relative to base: every changed line is still a 0.8.1 → 0.8.2 version bump and no dependency edges moved. The three dependency lines master itself gained from the archive train are base-side and pass through unchanged.

Verified: git rev-list 7e0b01bd..b5411f2 confirms exactly 14 commits in the delta, all root-eligible (the range's 35 changed files include no fleet/ or sdk/ paths), and all 14 appear in the entry — composing with the previously verified 7e029e99..7e0b01bd range (25 root-eligible) matches the entry's 39 exactly. The manifest stays root-only (fleet 0.1.6, sdk/typescript 0.1.4, sdk/python 0.1.3 untouched); own-cadence pins (arcbox-hv 0.3.20, arcbox-helper 1.1.0, external arcbox-boot 0.8.0) remain untouched; and the head sits directly on master tip b5411f2. Post-merge flow per AGENTS.md unchanged: the tag push triggers Release Build, and the draft stays assetless until package-and-release attaches the tarball.

  ^{｜ View workflow run ｜ Using glm-5.3-flash ｜ 𝕏}

[arcbox-labs]

🤖 Created releases:

• v0.8.2

🌻