fix(security): refresh CUA dependency graphs

[0xjohnnydev]

Problem

The dependency backlog kept moving while this draft sat behind main. This refresh brings the dependency-only rollup onto current main and covers the patchable alerts in CUA-owned package graphs without mixing in the generated Fleet mirror.

There are no application-source changes in this PR.

What changed

• Updated the root, CUA Bench, CUA CLI, sandbox-apps, and sandbox Python locks for current patched releases, including GitPython, Pillow, aiohttp, cryptography, h2, pyasn1, PyMdown Extensions, setuptools, Click, and jaraco-context.
• Updated Torch to 2.13.0 and TorchVision to 0.28.0 because Torch 2.12.1 requires setuptools below the patched 83.0.0 floor. The two fixes cannot coexist independently.
• Updated docs to Next.js 16.2.11 and patched js-yaml, nanoid, PostCSS, Sharp, and tar resolutions.
• Updated Cuabot for patched Sharp, Hono server, brace-expansion, fast-uri, Hono, ip-address, and tar releases.
• Updated the shared TypeScript workspace for patched nanoid and PostCSS resolutions.
• Updated the Cua Driver agent-SDK example graph for patched Hono server, fast-uri, Hono, and ip-address releases.
• Consolidates the dependency work represented by fix(security): update Torch to 2.13.0 #2373, chore(deps): bump sharp from 0.34.5 to 0.35.0 in /libs/cuabot #2423, fix(security): update vulnerable Python dependencies #2452, fix(security): update vulnerable Cuabot dependencies #2453, build(deps): bump next from 16.2.6 to 16.2.11 in /docs #2471, build(deps): bump pyasn1 from 0.6.3 to 0.6.4 in /libs/cua-bench #2516, build(deps): bump setuptools from 80.10.2 to 83.0.0 in /libs/cua-bench #2517, build(deps-dev): bump postcss from 8.5.10 to 8.5.18 in /docs #2555, chore(deps): bump h2 from 4.3.0 to 4.4.1 #2961, chore(deps): bump pymdown-extensions from 11.0 to 11.0.1 #2985, and chore(deps-dev): bump gitpython from 3.1.50 to 3.1.58 #2986, plus the already-closed drafts named below.

Salvaged from #2373. The Torch dependency-floor changes remain credited to @0xjohnnydev in the commit trailer.

Definition of Done

• Every currently patchable non-Fleet Dependabot alert is represented in this draft. The affected CUA-owned manifests and locks resolve at or above the published patched versions.
• Python dependency graphs are internally consistent. Root, CUA Bench, CUA CLI, sandbox-apps, and sandbox pass independent lock checks. Exported root, CUA Bench, and CUA CLI graphs return no known advisories from pip-audit.
• JavaScript dependency graphs install from their committed locks. Docs, Cuabot, shared TypeScript, and the agent-SDK examples accept frozen/clean installs.
• The updated packages build in their owning projects. Docs builds with Next.js 16.2.11; Cuabot and shared TypeScript build; shared TypeScript tests pass; and the SOM, CUA Bench, and CUA CLI Python packages build.
• The review boundary remains dependency-only. Only manifests, lockfiles, and the contributor identity mapping requested by CI changed; no product source changed.
• Current-head GitHub Actions pass. All required checks pass on the refreshed head.
• A maintainer confirms the Node 20 floor. Hono server 2.0.10 raises that transitive runtime requirement from Node 18.
• A maintainer chooses this draft as the canonical dependency PR. After that choice, the overlapping direct dependency PRs can close without losing work.
• GitHub confirms alert closure after merge to main. An open draft cannot prove final closure.

Known limits

• Docs still reports two high-severity image-size advisories for which the advisory currently publishes no patched version. This PR does not claim to fix them.
• The agent-SDK example typecheck still fails on the same removed ActionTarget API references as current main; the dependency-only change neither introduced nor hides that existing source mismatch. Its clean install and dependency audit pass.
• Fleet dependencies are a generated mirror and require the repository's copybara-import workflow, so they remain outside this PR.

Validation

• Ran independent uv lock --check commands for all five Python projects changed here.
• Audited the exported root, CUA Bench, and CUA CLI Python graphs with pip-audit; no advisories remained.
• Ran package-manager audits for docs, Cuabot, shared TypeScript, and the agent-SDK examples. Only the two unpatched docs image-size advisories remain.
• Built docs, Cuabot, shared TypeScript, SOM, CUA Bench, and CUA CLI; ran the shared TypeScript tests.
• Reproduced the agent-SDK typecheck failure from an untouched origin/main archive to separate the existing source issue from this dependency update.

Prior drafts folded into this one

The earlier dependency-only drafts #2451, #2718, #2728, and #2729 were already closed in favor of this rollup.

[github-actions]

📦 Publishable packages changed

This comment is status-only. Editing it or adding task-list checkboxes cannot authorize a release.
Only owner-applied release:<service> labels can do that.

• ⏸️ pypi/bench — no owner-authorized release label

Ask the release owner to apply release:<service> labels to auto-release on merge (+ optional bump:minor or bump:major, default is patch).
Or add no-release to skip.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[github-actions]

📦 Publishable packages changed

This comment is status-only. Editing it or adding task-list checkboxes cannot authorize a release.
Only owner-applied release:<service> labels can do that.

• ⏸️ npm/cuabot — no owner-authorized release label
• ⏸️ pypi/bench — no owner-authorized release label

Ask the release owner to apply release:<service> labels to auto-release on merge (+ optional bump:minor or bump:major, default is patch).
Or add no-release to skip.

[github-actions]

📦 Publishable packages changed

This comment is status-only. Editing it or adding task-list checkboxes cannot authorize a release.
Only owner-applied release:<service> labels can do that.

• ⏸️ npm/cuabot — no owner-authorized release label
• ⏸️ pypi/bench — no owner-authorized release label
• ⏸️ pypi/som — no owner-authorized release label

Ask the release owner to apply release:<service> labels to auto-release on merge (+ optional bump:minor or bump:major, default is patch).
Or add no-release to skip.

[github-actions]

📦 Publishable packages changed

This comment is status-only. Editing it or adding task-list checkboxes cannot authorize a release.
Only owner-applied release:<service> labels can do that.

• ⏸️ npm/cuabot — no owner-authorized release label
• ⏸️ pypi/bench — no owner-authorized release label
• ⏸️ pypi/cli — no owner-authorized release label
• ⏸️ pypi/som — no owner-authorized release label

Ask the release owner to apply release:<service> labels to auto-release on merge (+ optional bump:minor or bump:major, default is patch).
Or add no-release to skip.

[github-actions]

📦 Publishable packages changed

This comment is status-only. Editing it or adding task-list checkboxes cannot authorize a release.
Only owner-applied release:<service> labels can do that.

• ⏸️ npm/cuabot — no owner-authorized release label
• ⏸️ pypi/bench — no owner-authorized release label
• ⏸️ pypi/cli — no owner-authorized release label
• ⏸️ pypi/som — no owner-authorized release label

Ask the release owner to apply release:<service> labels to auto-release on merge (+ optional bump:minor or bump:major, default is patch).
Or add no-release to skip.

[github-actions]

📦 Publishable packages changed

This comment is status-only. Editing it or adding task-list checkboxes cannot authorize a release.
Only owner-applied release:<service> labels can do that.

• ⏸️ npm/cuabot — no owner-authorized release label
• ⏸️ pypi/bench — no owner-authorized release label
• ⏸️ pypi/cli — no owner-authorized release label
• ⏸️ pypi/som — no owner-authorized release label

Ask the release owner to apply release:<service> labels to auto-release on merge (+ optional bump:minor or bump:major, default is patch).
Or add no-release to skip.

[0xjohnnydev]

Closing the broad rollup now that its dependency changes are preserved in smaller, independent drafts on current main: Python #3098, docs #3099, and the remaining JavaScript graphs #3100. Fleet remains on its separate canonical import path in #3086. All GitHub Actions on the three replacement drafts are passing.