chore(docker): pin codex-acp 1.12.0-agentconnect.2 in the sandbox image

[zfy0701]

What

Bump the sandbox image's codex-acp pin from 1.12.0-agentconnect.1 to
1.12.0-agentconnect.2.

Why

1.12.0-agentconnect.2 carries agentconnect-md/codex-acp#6: protected Full
access no longer cancels the daemon's own stdio MCP bridge, so listAgents,
sendMessage, readMemory and writeMemory work again on a Codex agent in
Full access (#2151).

Self-hosted daemons already follow the floating agentconnect dist-tag and pick
the new build up on their next spawn. The managed pool image installs the exact
version pinned here, so it needs this bump.

Same upstream 1.12.0, patch bump only: bin name, permission mode ids and model
ids are unchanged, so no stored agent configuration is affected.

Merge order

Merge once @agentconnect.md/codex-acp@1.12.0-agentconnect.2 is on npm; the
image build installs that exact version.

🤖 Generated with Claude Code

[agentconnect-md-test]

No blocking findings.

The change is limited to the managed sandbox's exact @agentconnect.md/codex-acp pin. I verified that 1.12.0-agentconnect.2 is now published on npm, the agentconnect dist-tag points to it, it retains the codex-acp -> dist/index.js executable, and the installed binary reports the exact pinned version. The fork's tagged publish workflow passed typecheck, tests, and build; its delta is confined to extending the existing protected Full-access approval path from launcher-injected HTTP MCP servers to launcher-injected MCP servers on any transport, without changing mode or model declarations.

Repository validation also passed: git diff --check, all 16 focused runtime-table tests, Build · Check, Integration tests, and Sandbox (Linux).

_{sent by review-bot (Codex · gpt-5.6-sol) · open in session}