prepare-code-freeze

# Prepare Code Freeze Use this skill when the user asks to start, prepare, or automate a NeMo Relay code freeze. ## Workflow This workflow assumes `upstream` is the NVIDIA repository remote (`NVIDIA/NeMo-Relay`). The `origin` remote can be a maintainer's personal fork. 1. Confirm or infer the target release version from `upstream/main:Cargo.toml`. Derive the release branch as `release/<major>.<minor>`. 2. Prompt for `<next-version>` if the user did not provide it. This is the version that `main` moves to after the release branch is cut. 3. Fetch the latest `main` and create the release branch from `upstream/main`: ```bash git fetch upstream main git branch release/<major>.<minor> upstream/main git push upstream release/<major>.<minor> ``` If the remote release branch already exists, verify it points where expected before continuing. 4. Create a PR branch from latest `upstream/main`, for example `chore/version-bump-<major>.<minor>`. 5. Update `.github/nightly-alpha-branches.yaml` to include the new release branch. 6. Run `just set-version <next-version>` to update all project-owned unified-release version surfaces on `main`, including Cargo, Python, Node, plugins, lockfiles, and coding-agent manifests. Regenerate the dynamic worker-plugin fixture lockfile so its path dependencies use the new workspace version: ```bash cargo generate-lockfile --manifest-path crates/core/tests/fixtures/worker_plugin/Cargo.toml ``` 7. S...