chore: prepare 0.3 code freeze

.agents/skills/prepare-code-freeze/SKILL.md

@@ -40,19 +40,34 @@ This workflow assumes `upstream` is the NVIDIA repository remote
    branch.
 6. Run `just set-version <next-version>` to bump all release-versioned package
    surfaces on `main`.
-7. Validate with targeted checks:
+7. Search documentation source for references to the old version and update
+   current-version install commands, package examples, and configuration
+   examples to `<next-version>` where appropriate:
+
+   ```bash
+   rg -n '<old-version>' README.md docs fern --glob '!docs/_build/**' || true
+   ```
+
+   Review matches before changing them. Leave intentional historical references
+   alone, such as release notes, changelogs, generated build output, and
+   third-party dependency attribution entries.
+8. Validate with targeted checks:
 
    ```bash
    ruby -e 'require "yaml"; YAML.load_file(".github/nightly-alpha-branches.yaml"); YAML.load_file(".github/workflows/nightly-alpha-tag.yaml")'
    just set-version <next-version>
+   rg -n '<old-version>' README.md docs fern --glob '!docs/_build/**' || true
    git diff --check
    ```
 
-8. Open a PR targeting `main` using `.github/pull_request_template.md`. The PR
+   Any remaining documentation matches for `<old-version>` should be intentional
+   and called out in the PR description.
+9. Open a PR targeting `main` using `.github/pull_request_template.md`. The PR
    must mention:
    - the new release branch
    - the nightly alpha branch config update
    - the `just set-version <next-version>` bump
+   - documentation old-version reference updates or intentional leftovers
    - that release-bound PRs now target the new `release/*` branch
 
 ## Guardrails

.github/nightly-alpha-branches.yaml

@@ -3,3 +3,4 @@
 
 branches:
   - main
+  - release/0.3

Cargo.toml

@@ -16,16 +16,16 @@ exclude = [".tmp", ".uv-cache"]
 resolver = "2"
 
 [workspace.package]
-version = "0.3.0"
+version = "0.4.0"
 edition = "2024"
 license = "Apache-2.0"
 repository = "https://github.com/NVIDIA/NeMo-Relay"
 
 [workspace.dependencies]
-nemo-relay = { version = "0.3.0", path = "crates/core", default-features = false }
-nemo-relay-adaptive = { version = "0.3.0", path = "crates/adaptive" }
-nemo-relay-ffi = { version = "0.3.0", path = "crates/ffi" }
-nemo-relay-cli = { version = "0.3.0", path = "crates/cli" }
+nemo-relay = { version = "0.4.0", path = "crates/core", default-features = false }
+nemo-relay-adaptive = { version = "0.4.0", path = "crates/adaptive" }
+nemo-relay-ffi = { version = "0.4.0", path = "crates/ffi" }
+nemo-relay-cli = { version = "0.4.0", path = "crates/cli" }
 uuid = "=1.18.1"
 
 [workspace.lints.rust]

crates/node/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nemo-relay-node",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "Node.js bindings for the NeMo Relay agent runtime.",
   "keywords": [
     "agents",

docs/getting-started/installation.mdx

@@ -20,7 +20,7 @@ Install the NeMo Relay CLI when you want the `nemo-relay` executable for
 coding-agent hook and LLM gateway observability.
 
 ```bash
-cargo install nemo-relay-cli@0.3.0
+cargo install nemo-relay-cli@0.4.0
 ```
 
 ## Python
@@ -29,7 +29,7 @@ Install the Python package when your application uses NeMo Relay through the
 Python wrapper.
 
 ```bash
-uv add nemo-relay@0.3.0
+uv add nemo-relay@0.4.0
 ```
 
 Use `uv add` from an application project that has a `pyproject.toml`; it records
@@ -52,8 +52,8 @@ npm install nemo-relay-node
 Add the Rust crates when your application uses NeMo Relay directly from Rust.
 
 ```bash
-cargo add nemo-relay@0.3.0
-cargo add nemo-relay-adaptive@0.3.0
+cargo add nemo-relay@0.4.0
+cargo add nemo-relay-adaptive@0.4.0
 ```
 
 - `nemo-relay` provides the core runtime APIs for scopes, middleware, subscribers, plugins, tool calls, and LLM calls.
@@ -70,7 +70,7 @@ Install the OpenClaw plugin through OpenClaw so OpenClaw can register and manage
 the package:
 
 ```bash
-openclaw plugins install npm:nemo-relay-openclaw@0.3.0
+openclaw plugins install npm:nemo-relay-openclaw@0.4.0
 openclaw gateway restart
 ```
 
@@ -85,7 +85,7 @@ Install the Python package with the supported framework extras when your
 application uses LangChain, LangGraph, or Deep Agents.
 
 ```bash
-uv add "nemo-relay[langchain,langgraph,deepagents]@0.3.0"
+uv add "nemo-relay[langchain,langgraph,deepagents]@0.4.0"
 ```
 
 The extras install the NeMo Relay Python package plus the dependencies needed by

docs/getting-started/quick-start/python.mdx

@@ -20,7 +20,7 @@ local checkout.
 Use this path when you want the published package for application development.
 
 ```bash
-uv add nemo-relay@0.3.0
+uv add nemo-relay@0.4.0
 ```
 
 Run `uv add` from an application project that has a `pyproject.toml`; it records

docs/getting-started/quick-start/rust.mdx

@@ -18,16 +18,16 @@ local checkout.
 Use the published crates when you are consuming a release:
 
 ```bash
-cargo add nemo-relay@0.3.0
-cargo add nemo-relay-adaptive@0.3.0
+cargo add nemo-relay@0.4.0
+cargo add nemo-relay-adaptive@0.4.0
 cargo add serde_json
 ```
 
 Install the published NeMo Relay CLI separately when you need coding-agent hook
 and LLM gateway observability:
 
 ```bash
-cargo install nemo-relay-cli@0.3.0
+cargo install nemo-relay-cli@0.4.0
 ```
 
 ### Install from the Repository
@@ -43,7 +43,7 @@ serde_json = "1"
 
 - `nemo-relay` is the core Rust runtime surface.
 - `nemo-relay-adaptive` is the companion crate for adaptive runtime primitives and Redis-backed learning components.
-- `nemo-relay-cli` is a binary crate. Use `cargo install nemo-relay-cli@0.3.0` when
+- `nemo-relay-cli` is a binary crate. Use `cargo install nemo-relay-cli@0.4.0` when
   you need the NeMo Relay CLI.
 
 ## Push a Scope and Emit a Mark

docs/observability-plugin/configuration.mdx

@@ -79,7 +79,7 @@ transport = "http_binary"
 endpoint = "http://localhost:4318/v1/traces"
 service_name = "nemo-relay"
 service_namespace = "agent"
-service_version = "0.3.0"
+service_version = "0.4.0"
 instrumentation_scope = "nemo-relay-observability"
 timeout_millis = 3000
 
@@ -96,7 +96,7 @@ transport = "http_binary"
 endpoint = "http://localhost:6006/v1/traces"
 service_name = "nemo-relay"
 service_namespace = "agent"
-service_version = "0.3.0"
+service_version = "0.4.0"
 instrumentation_scope = "nemo-relay-openinference"
 timeout_millis = 3000
 
@@ -153,7 +153,7 @@ config = plugin.PluginConfig(
                     endpoint="http://localhost:4318/v1/traces",
                     service_name="nemo-relay",
                     service_namespace="agent",
-                    service_version="0.3.0",
+                    service_version="0.4.0",
                     instrumentation_scope="nemo-relay-observability",
                     resource_attributes={"deployment.environment": "dev"},
                 ),
@@ -162,7 +162,7 @@ config = plugin.PluginConfig(
                     endpoint="http://localhost:6006/v1/traces",
                     service_name="nemo-relay",
                     service_namespace="agent",
-                    service_version="0.3.0",
+                    service_version="0.4.0",
                     instrumentation_scope="nemo-relay-openinference",
                     resource_attributes={"deployment.environment": "dev"},
                 ),
@@ -211,7 +211,7 @@ await plugin.initialize({
         endpoint: "http://localhost:4318/v1/traces",
         service_name: "nemo-relay",
         service_namespace: "agent",
-        service_version: "0.3.0",
+        service_version: "0.4.0",
         instrumentation_scope: "nemo-relay-observability",
         resource_attributes: {
           "deployment.environment": "dev",
@@ -222,7 +222,7 @@ await plugin.initialize({
         endpoint: "http://localhost:6006/v1/traces",
         service_name: "nemo-relay",
         service_namespace: "agent",
-        service_version: "0.3.0",
+        service_version: "0.4.0",
         instrumentation_scope: "nemo-relay-openinference",
         resource_attributes: {
           "deployment.environment": "dev",
@@ -267,7 +267,7 @@ let component = ComponentSpec::new(ObservabilityConfig {
         endpoint: Some("http://localhost:4318/v1/traces".into()),
         service_name: "nemo-relay".into(),
         service_namespace: Some("agent".into()),
-        service_version: Some("0.3.0".into()),
+        service_version: Some("0.4.0".into()),
         instrumentation_scope: Some("nemo-relay-observability".into()),
         resource_attributes: [("deployment.environment".into(), "dev".into())].into(),
         ..OtlpSectionConfig::default()
@@ -277,7 +277,7 @@ let component = ComponentSpec::new(ObservabilityConfig {
         endpoint: Some("http://localhost:6006/v1/traces".into()),
         service_name: "nemo-relay".into(),
         service_namespace: Some("agent".into()),
-        service_version: Some("0.3.0".into()),
+        service_version: Some("0.4.0".into()),
         instrumentation_scope: Some("nemo-relay-openinference".into()),
         resource_attributes: [("deployment.environment".into(), "dev".into())].into(),
         ..OtlpSectionConfig::default()

docs/supported-integrations/openclaw-plugin.mdx

@@ -40,7 +40,7 @@ Optional:
 Install the plugin with OpenClaw so OpenClaw can register and manage it:
 
 ```bash
-openclaw plugins install npm:nemo-relay-openclaw@0.3.0
+openclaw plugins install npm:nemo-relay-openclaw@0.4.0
 openclaw gateway restart
 ```
 
@@ -53,7 +53,7 @@ If you manage OpenClaw plugin dependencies directly in a Node.js project,
 install the package with npm:
 
 ```bash
-npm install nemo-relay-openclaw@0.3.0
+npm install nemo-relay-openclaw@0.4.0
 ```
 
 Installing with npm makes the package available to that project. Use

integrations/openclaw/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nemo-relay-openclaw",
-  "version": "0.3.0",
+  "version": "0.4.0",
   "description": "NeMo Relay-authored observability plugin for OpenClaw.",
   "type": "module",
   "repository": {
@@ -63,7 +63,7 @@
     "openclaw": "^2026.5.26"
   },
   "dependencies": {
-    "nemo-relay-node": "0.3.0"
+    "nemo-relay-node": "0.4.0"
   },
   "devDependencies": {
     "@types/node": "^24.0.0",