update-project-version

# Update Project Version ## Companion Guidance Use `karpathy-guidelines` alongside this skill for implementation or review work. Keep changes scoped, surface assumptions, and define focused validation before editing. Use this skill when changing the released NeMo Relay version, including pre-release or build-metadata variants used during packaging. ## Source Of Truth - `Cargo.toml` `[workspace.package].version` is the source of truth for the Rust workspace and Python build versioning. - Keep `Cargo.toml` `[workspace.dependencies]` self-references aligned when the workspace version changes. - `crates/node/package.json` carries its own npm package version and must stay aligned with the workspace-root `package-lock.json`. - `integrations/openclaw/package.json` carries the OpenClaw npm plugin version and must stay aligned with the workspace-root `package-lock.json`. - `package-lock.json` records Node package versions under `packages["crates/node"].version` and `packages["integrations/openclaw"].version`. The workspace-root lockfile may not have a top-level `version` field. ## Workflow 1. Read the current version from `Cargo.toml` and decide the exact target version string. 2. Run `just set-version <version>` to update release-version source files: - `[workspace.package].version` - `workspace.dependencies.nemo-relay.version` - `workspace.dependencies.nemo-relay-adaptive.version` - `workspace.dependencies.nemo-relay-pii-redaction.version` - `w...