fix: bump MCP and Pillow security pins

[christopherrobin88]

Summary

• Bump MCP from 1.26.0 to 1.28.1 across project extras, lazy dependency pins, and uv.lock.
• Bump Pillow from 12.2.0 to 12.3.0 across core metadata, lazy vision fallback, and uv.lock.
• Update the computer-use lazy MCP pin contract test so runtime lazy installs cannot revert the patched MCP version.

Why

A direct pip install of MCP/Pillow is not durable in Hermes because tools/lazy_deps.py can reassert pinned optional dependency versions on first real tool use. This keeps pyproject metadata, lazy dependency allowlist, tests, and lockfile in sync.

Verification

• scripts/run_tests.sh tests/test_project_metadata.py tests/tools/test_lazy_deps.py tests/tools/test_lazy_deps_durable_target.py tests/tools/test_vision_tools.py tests/tools/test_vision_native_fast_path.py → 204 passed, 0 failed.
• scripts/run_tests.sh tests/tools/test_computer_use.py::TestLazyMcpInstall::test_feature_registered_in_allowlist → 1 passed, 0 failed.
• Local runtime smoke test: computer_use capture succeeded after the MCP bump and MCP remained at 1.28.1.
• Local Pillow smoke test: PNG/JPEG resize, filter, save and load passed with Pillow 12.3.0.
• pip check → no broken requirements.
• Local hermes security audit --json → 0 findings across 147 components.

Notes

An unrelated existing Linux GNOME window-selection test in tests/tools/test_computer_use.py still fails when the whole file is run. It touches code outside this dependency bump and is not addressed here.

[alt-glitch]

This was generated by AI during triage.

Related: this combines the live Pillow update in #63942 and MCP update in #65926. The shared manifest/lock paths will conflict, so please consolidate on one remediation path for #60841.

[sycamoregroupltd]

Superseded for the MCP 1.28.1 security package-owner lane by canonical survivor PR #73219 at head 91d3644fc43fe827f67a1915454afb33889beca5. Closing this duplicate candidate to keep exactly one reviewable MCP survivor; no merge/deploy/runtime sync performed.

[sycamoregroupltd]

MCP package-owner lane note: canonical survivor is #73219 at head 91d3644fc43fe827f67a1915454afb33889beca5. This PR remains open because this account is not authorized to close it (GraphQL ClosePullRequest permission denied), but it is superseded for jarvis-os/t_9a6eac24 / t_44d6ed91 MCP 1.28.1 review routing. No merge/deploy/runtime sync performed.

[teknium1]

Thanks for identifying that the manifest, lazy installer, and lockfile must move together. The underlying issue remains present on current main: pyproject.toml:125, pyproject.toml:165, pyproject.toml:230, pyproject.toml:241, tools/lazy_deps.py:280, and tools/lazy_deps.py:287 still use Pillow 12.2.0 / MCP 1.26.0.

Problems

• The changed test_feature_registered_in_allowlist hunk no longer has a current-main target: rg finds no such test on HEAD, while the current computer-use lazy-install tests are at tests/tools/test_computer_use.py:762-792. GitHub reports this PR as CONFLICTING.
• The MEMBER discussion identifies overlapping remediation paths in #63942 and the MCP survivor route. These changes share pyproject.toml, tools/lazy_deps.py, and uv.lock, so they need one consolidated current-main resolution.

Suggested changes

• Salvage the pin changes against current main and regenerate the lock there. tests/test_project_metadata.py:196-238 already enforces that exact lazy pins match the committed lock resolution.
• Recreate any desired feature-specific computer-use assertion in the current test layout rather than applying the removed test hunk.

Automated hermes-sweeper review.

[teknium1]

This test target no longer exists on current main (rg finds no test_feature_registered_in_allowlist), while the current lazy-MCP tests are at tests/tools/test_computer_use.py:762-792. Recreate the assertion in the current test layout during consolidation.

[sycamoregroupltd]

Closing as superseded/redundant: main now carries the full security floor for both lanes — mcp==1.28.1 across [dev]/[mcp]/[computer-use] and Pillow==12.3.0 (commits a7efeb0 'fix(sec): update mcp to 1.28.1' and abcd213 'fix(sec): update pillow to 12.3.0', landed 2026-07-30). Maintainer teknium1 confirmed the same for the MCP lane when closing #73219 (2026-08-01). No merge/deploy/runtime mutation performed.

[sycamoregroupltd]

Maintainer closure request: this PR is fully redundant — its entire diff (Pillow==12.3.0 + mcp==1.28.1) is already on main via commits a7efeb0 ('fix(sec): update mcp to 1.28.1') and abcd213 ('fix(sec): update pillow to 12.3.0'), both landed 2026-07-30. Verified live today: main pyproject.toml pins mcp==1.28.1 in [dev]/[mcp]/[computer-use] and Pillow==12.3.0 as a core dep; uv.lock resolves pillow 12.3.0. The sycamoregroupltd account lacks ClosePullRequest permission (GraphQL closePullRequest denied), so please close this PR as superseded/redundant — same disposition teknium1 applied to #73219 on 2026-08-01. No merge/deploy/runtime mutation performed.