[cv]

Failure

cargo deny check advisories reports RUSTSEC-2026-0333 in noyalib 0.0.28, which OpenShell's openshell-policy-schema pins exactly. The fix, noyalib 0.0.53, is in OpenShell #4348 and was released in v0.1.3. NemoClaw pins its OpenShell crates, images, Helm chart, and docs to one release, so the dependency can't move on its own.

v0.1.3 also includes sandbox and policy fixes that apply to NemoClaw: full binary scope for uninspected credentials (#4171), removal of privileged control-socket filters (#4279), audit of every endpoint in a proposal (#4313), Rust and Rego sharing endpoint path matching (#4336), and canonical profile revision hashing (#4122).

Decision

Move everything pinned to v0.1.2 to v0.1.3, tag commit e1f3c82caa3e:

• Crates: openshell-core, openshell-sdk, and openshell-policy. Cargo.lock changes by about 20 lines, including noyalib 0.0.53.
• Vendored SDK: re-copied from v0.1.3 and identical to upstream except for its manifest. It is still needed because upstream still enables openshell-core telemetry.
• versions.json: OpenShell version, revision, and the gateway, supervisor, sandbox, and Helm chart digests. GHCR's v0.1.2 tags matched the old pins.
• Examples, fixtures, generated schema, and configuration reference: the new default gateway digest.
• Docs: pinned links and version statements.

I checked the changes that could affect NemoClaw:

• Helm values: fix(onboard): repair existing Ollama loopback override #3384 moves gateway settings under gatewayConfig, but the new chart maps every legacy server.* value NemoClaw sets: OIDC, workspace mode, and storage size. Unauthenticated access stays off. gateway.rs is unchanged; Live / Kind exercises the real chart.
• New protocol fields: sandbox restart policy and service authorization mode default to the previous behavior when unset, and NemoClaw doesn't set them.
• Doc claims: the SDK limits table, CLI gateway selectors, TLS modes, upstream proxy chaining, example profiles, and GPU write-back all still hold at v0.1.3.
• Profile annotations: the comment on NemoClaw's single-annotation workaround now notes that v0.1.3 canonicalizes profile hashes. Splitting the annotation would change stored state, so it's left for a follow-up to Sandbox never becomes ready on pinned OpenShell v0.1.2: provider_env_revision changes on every read #12458.

Validation

• cargo ci passed: 1,309 workspace tests and all 112 lifecycle tests. Clippy needed no code changes.
• cargo ci schema passes, so the regenerated schema and reference match.
• Live / Docker (run 37973280647) and Live / Kind (run 37973287315) passed on linux_arm64 and linux_amd64 with the v0.1.3 images and Helm chart, including the legacy server.* values.

[github-actions]

v1 documentation preview: https://nvidia-preview-nemoclaw-v1-pr-12930.docs.buildwithfern.com/nemoclaw