chore(master): release 0.5.3

[arcbox-labs]

🤖 I have created a release beep boop

0.5.3 (2026-07-24)

Bug Fixes

• net: detect and reap zombie fast-path flows on both legs (dc0295e)
• net: start the dead-flow deadline at solicitation, not the last guest frame (bafee56)
• virtio: drop RX frames that don't fit the chain instead of truncating (b341beb)
• virtio: poison a chain on an out-of-RAM descriptor; update poll_rx docs (f33337c)

Performance Improvements

• agent: expedite RCU grace periods to cut runc create ~8x (ABX-496) (6e67d6f)
• runtime: exec the container runtime from a read-only block image (ABX-498) (#499) (bde8fb0)
• storage: ext4 metadata volume for fsync-hot boltdb state (ABX-496) (#497) (e4aca03)

Tests

• e2e: live validation of the host-networking reconciler (#352) (696ea7f)
• e2e: observe the removal before timing the sweep; pin the fail-safe (d46dbcd)

Styles

• e2e: apply rustfmt to reconciler_teardown test (f2a1050)

Miscellaneous Chores

• assets: bump boot assets to 0.6.10 (FEX procfs fix, ABX-494) (4b52760)

---

This PR was generated with Release Please. See documentation.

[pullfrog]

✅ No new issues found.

Reviewed changes — release-please version bump of the workspace from 0.5.2 to 0.5.3; no source code changes.

• Root manifest bump — .release-please-manifest.json root component . moves to 0.5.3; fleet correctly stays at 0.1.3 (separate release cadence).
• CHANGELOG entry — new 0.5.3 section listing the 4 net/virtio bug-fix commits merged since 0.5.2, matching the head of master.
• Version pins — workspace.package.version and every x-release-please-version internal path-dep in Cargo.toml, plus all corresponding crate entries in Cargo.lock, bumped in lockstep. Manual-cadence and external deps (arcbox-hv 0.3.20, arcbox-helper 1.0.2, arcbox-boot 0.5.1) correctly left untouched.

Fully mechanical and internally consistent across all three files. Mergeable as-is.

  ^{｜ Fix it ➔ ｜ View workflow run ｜ Using Claude Opus ｜ 𝕏}

[greptile-apps]

Greptile Summary

This PR prepares the ArcBox 0.5.3 release. The main changes are:

• Bumps the root workspace and internal crate versions to 0.5.3.
• Updates the Cargo lockfile to match the new version.
• Advances the release manifest while leaving the fleet release unchanged.
• Adds changelog entries for the fixes, performance improvements, tests, and asset update.

Confidence Score: 5/5

This looks safe to merge.

No blocking issues found in the changed code.

T-Rex Logs

What T-Rex did

• General contract validation shows the workspace now resolves 54 packages, exposes 51 inherited packages updated from 0.5.2 to 0.5.3, internal requirements updated to ^0.5.3, and, importantly, zero consistency errors with exit code 0.
• The locked dependency fetch completed with exit code 0, confirming a successful dependency resolution as part of the contract validation.
• Artifacts were prepared to support review, including a Python-based summary and logs accessible via URLs for inspection of the results.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
Cargo.toml	Bumps the workspace version and release-managed internal dependency requirements to 0.5.3.
Cargo.lock	Updates workspace package entries to the 0.5.3 release version.
.release-please-manifest.json	Advances the root release to 0.5.3 while preserving the separate fleet version.
CHANGELOG.md	Adds release notes for the changes included in version 0.5.3.

_{Reviews (6): Last reviewed commit: "chore: update Cargo.lock for release" | Re-trigger Greptile}

[arcbox-labs]

🤖 Created releases:

• v0.5.3

🌻