[jackie-cqz]

Change

Pin zcode-acp-server to 0.75.0. Compared with 0.72.0, the CLI entry, runtime selection, official CLI resolver and attachment converter are byte-identical. The upgrade includes headless resume/replay improvements and stops writing a disabled sandbox template into unarmed workspaces; update the setup guide accordingly. Align the built-in version assertion in the legacy-registration regression while preserving checks for the old custom commands and arguments.

Validation

• Built the independent upgrade branch's standalone Codeg server.
• Real 0.75.0 bridge tests: initialize, Build/Plan/Yolo transitions, actual stdio MCP tool execution, reject_once (no write), allow_once (verified write), cancellation after observing an active native turn, and successful next prompt.
• Verified that an unarmed workspace has no sandbox discovery template.
• Codeg end-to-end: streaming replies, exact image/PDF transport, unchanged transcript after server restart, same external session ID, managed MCP reinjection with a real tool call after restart, and config mode transitions.
• Local package hash audit confirms the four unchanged launch/conversion modules.
• git diff --check passed.

This PR does not enable additional Codeg UI capabilities and is independent of the attachment and statistics follow-ups.

Combined validation

The three independent follow-ups merge cleanly on main 95de8873 and were exercised together:

• Server library: 5425 passed, 1 existing ignored, no filtered/skipped tests. The IPv6 localhost case was rechecked and included in this final run.
• Frontend: 837 related attachment/composer/transport and turn-metadata/session-statistics tests passed.
• Bridge 0.75.0: 12 real Codeg API stages passed across attachments, uploads, cold restoration, exact native token/cache/time reconciliation, cancellation, rejection and successful subsequent sends.
• Desktop all-targets with test-utils, server and MCP Clippy passed with -D warnings -A clippy::nonminimal_bool. Strict server Clippy reports only the unchanged predicate at src-tauri/src/computer/helper/mod.rs:667; the allowance is confined to that lint.

Windows x64, Node 24.15.0 and Rust 1.96.1. The 20 GiB Rust-cache guard stayed enabled, with debug symbols and incremental compilation disabled and one compile job.

Related independent follow-ups: #1003, #1005.

[xintaofei]

@jackie-cqz thanks for the bump and for the detailed validation write-up.

I checked the compatibility claims against the published npm packages, and they hold: dist/cli.js, dist/runtime.js, the official CLI resolver (dist/backend/resolve.js) and the attachment converter (dist/handlers/prompt-content.js) are byte-identical between 0.72.0 and 0.75.0.

Main already carries the same upgrade, though, in e2961c2. It pins zcode-acp-server@0.75.0, makes the same change to the legacy-registration assertion, and updates the sandbox paragraph in docs/agents/zcode.md for the 0.73.0 change. This PR now conflicts with main in that doc and in the registry comment, and the only new guide text it would add is the Windows validation paragraph at the top. So we won't be merging this one, since main supersedes it.

That paragraph is worth keeping somewhere: it records a run against official ZCode on Windows through mode changes, permissions, cancellation, stdio MCP and session restoration after a Codeg server restart. If you'd like it in the docs, the existing validation sentence under Current scope is the natural place for it, rather than a second validation paragraph. #1003 already edits that sentence, so it could mention 0.75.0 there.

If there's something in this PR that main doesn't cover and I've missed it, let me know.

[xintaofei]

codeg work task 418 is done — it made no changes, so nothing was pushed to this pull request.