chore(beep boop 🤖): Bump uv.lock (main, mcore-dev) (2026-07-02)

[svcnvidia-nemo-ci]

🚀 PR to bump uv.lock in main.

🤖 This PR will be merged automatically once CI passes.

[svcnvidia-nemo-ci]

/ok to test cfe12fa

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[yaoyu-33]

MCore bump auto-fix status for dev:

Classification: Bridge broke itself for the shared ModelOpt/TransformerEngine quantization incompatibility; MCore broke Bridge for the dev-only NRX/MCP dependency resolution.
Evidence: On 2026-07-02 PDT, H100 job 84771263691 and GB200 job 84771263233 both failed in modelopt/torch/quantization/plugins/transformer_engine.py:178 with TypeError: object of type bool has no len(); Bridge still pins TransformerEngine b9d690e0 with ModelOpt 0.44.0rc5. Resiliency job 84771265453 invoked ft_launcher for test_inprocess_restart.py and exited before test execution with ModuleNotFoundError: No module named mcp.types; this lock resolves NRX 0.6.0.dev33+15a8515, mcp 2.0.0b1, and mcp-types 2.0.0b1. The MCore delta from the 2026-07-01 dev target is only documentation commit 66dc96f90ed4.
Fix PR: #4600 is the existing open quantization fix; no duplicate fix PR was opened. It is mergeable, blocked on review, and its H100/GB200 Qwen quantization, resiliency, and aggregate CI checks passed. It does not resolve the dev-only MCP failure.
Guards: none added or removed.
Validation: Read Linear journal MB-647; rechecked gh pr view 4626, gh pr diff 4626 --name-only, and gh pr checks 4626; inspected bounded Actions job-log API windows for all three failed jobs; compared MCore 5e846ab3cf44...66dc96f90ed4 (1 documentation-only commit); and rechecked PR #4600 live checks. No local or CW command was run because the duplicate-fix policy requires stopping when an existing open fix PR covers the target failure.
Next action: review and merge #4600 for the quantization blocker. A maintainer or dependency owner must then choose whether NRX should adapt to the MCP 2.0 split API or the dev lock should constrain MCP to a compatible pre-2.0 release, validate test_inprocess_restart.py, and rerun this dev bump.

[yaoyu-33]

/ok to test 24b911f