Publish codex init image with agynd tracing correlation

[casey-brooks]

Summary

agynio/agents-orchestrator#207 is still red in centralized E2E on the codex full-chain tracing deeplink test even after the E2E image pin cleanup.

Latest failing validation run: https://github.com/agynio/agents-orchestrator/actions/runs/26902699431

Evidence

The rerun after agynio/e2e#189 uses:

• CODEX_INIT_IMAGE=ghcr.io/agynio/agent-init-codex:0.13.27
• CLAUDE_INIT_IMAGE=ghcr.io/agynio/agent-init-claude:0.1.27
• AGN_INIT_IMAGE=ghcr.io/agynio/agent-init-agn:0.5.5
• AGN_EXPOSE_INIT_IMAGE=ghcr.io/agynio/agent-init-agn:0.5.5

go-core now passes, including TestAgentExposeLifecycle_ListAddRemove, so the remaining failure is tracing only.

Codex failure:

Error: ListSpans(filter: { messageId: 6c40ebba-c433-47e3-a77a-9a0cae3636c0 }) returned no trace id after 120s. Check message-id correlation and ensure the codex agent init image is up to date (override via CODEX_INIT_IMAGE). Last ListSpans snapshot: total=0, names=-, traceIds=-, messageTextMatches=0, messageIdAttributes=-.

Why this repo owns part of the fix

agent-init-codex has versions.env pinned to AGYND_VERSION=0.14.16, and PR #56/tag v0.13.27 exists in git, but GitHub Releases still list v0.13.22 as the latest published release. Centralized E2E is now pinned to ghcr.io/agynio/agent-init-codex:0.13.27, so we need the image/release path to be explicitly published and verified with the current agynd tracing correlation bits.

Related owning issue for daemon-side tracing context: agynio/agynd-cli#135.
Tracker: agynio/agents-orchestrator#207.

Required outcome

• Publish/verify the ghcr.io/agynio/agent-init-codex:0.13.27 image contains agynd v0.14.16.
• If the image already contains agynd v0.14.16, use this issue to capture the release evidence and coordinate the next daemon/tracing fix in Keep message-id trace context for claude/codex exports agynd-cli#135.
• Do not skip or narrow the centralized E2E tests.