CUA Driver 0.20.0 Upstream Sync Plan

Delivery boundary

Deliver one pure prerequisite change before Issue #9334: move the vendored CUA Driver from the released 0.17.0 snapshot to released 0.20.0 while preserving the documented Qwen distribution and compatibility patches. Do not change the built-in Computer Use adapter or downloader pin.

Sequence

1. Verify the official Git tag, commit, npm dist-tag, and release metadata.
2. Apply the 0.17.0 to 0.20.0 libs/cua-driver delta with the repository sync script.
3. Cross-check every reject through a three-way merge using upstream 0.17.0 as the common ancestor.
4. Adopt 0.20 lifecycle, target, authorization, SDK, and browser-token behavior; retain Qwen identity, telemetry, coordinate, payload-filter, and Windows empty-title-window changes.
5. Restore the package lockfiles required by clean npm ci builds, align the standalone SDK examples with the published 0.20.0 packages, and advance Qwen release metadata to 0.20.0.
6. Validate source provenance, version parity, generated contracts, language SDKs, Rust packages, installer behavior, release wiring, and the enclosing Qwen workspace.
7. Run a debug runtime smoke test and record platform-specific or signed-release gaps separately from source failures.
8. Read the complete tracked and untracked diff in open-ended passes and require two consecutive clean passes after the final fix.

Stop conditions requiring a new decision

• changing Qwen's built-in Computer Use downloader or bootstrap behavior;
• replacing Qwen identities, install paths, signing ownership, or telemetry default with upstream values;
• copying upstream-only publication infrastructure or introducing new release secrets;
• dropping the documented local Windows patch before it is merged upstream; or
• adding Issue #9334 model-facing APIs to this synchronization change.