Release devnet5 v0.5.8

[zclawz]

Current-main devnet5 release PR per RELEASE.md.

• Release branch: release
• Release vehicle commit: fc4dff5051a542ac4f5135c121844b2aa886c4a0
• Code release commit: 30a2c58c382d89ea3f8139b19e766c288263bbf8
• Labels to drive workflow: release, 0.5.8, devnet5

This supersedes the stale v0.5.7 attempt; prior v0.5.7 release PRs were already used but did not publish a tag/image.

[zclawz]

Working this release. Created a clean current-main release branch with an empty release commit (15bb00f) on top of 30a2c58, and added the workflow labels release, 0.5.7, and devnet5. Next step: merge this PR so the release workflow can publish v0.5.7 and refresh blockblaz/zeam:devnet5.

[zclawz]

Update: PR is mergeable, but required checks are still running and the repo has auto-merge disabled. I scheduled a follow-up watcher for 12:25 UTC to merge with squash once checks pass, then monitor the release workflow for v0.5.7 and blockblaz/zeam:devnet5 publication.

[zclawz]

Corrected release version to 0.5.8 per Partha. Force-updated release to empty release commit fc4dff5 on top of code commit 30a2c58, updated PR title/body, and switched labels from 0.5.7 to 0.5.8. Waiting for refreshed checks before squash merge and Docker publish.

[ch4r10t33r]

LGTM

[zclawz]

Failure diagnosis: run 29268398422 failed in create-tags before any tags/images were created. The release PR event head was d2b4d84 (Merge branch main into release), so the workflow treated the merge commit itself as RELEASE_SHA and failed Release commit must be reachable from main history. v0.5.8 and the refreshed Devnet5 tag were not created. Opened workflow fix PR #1039 to handle this updated-release-branch shape; after that lands we need a fresh v0.5.8 release PR because rerunning this failed event will keep the same bad payload.