Walkthrough

This PR pins the OpenShell version across the codebase from 0.0.39 to 0.0.44, with the test sticky version updated from 0.0.40 to 0.0.45. Changes span blueprint configuration, installer scripts, TypeScript onboarding logic, and all related E2E and unit test scenarios.

Changes

OpenShell Version Pinning Update to 0.0.44

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• NVIDIA/NemoClaw#3383: Both PRs touch the OpenShell onboarding/install logic—this PR bumps pinned version values while the retrieved PR refactors ensureOpenshellForOnboard() and driver-binary checks, so changes are related at the function-logic level.
• NVIDIA/NemoClaw#3478: This PR updates the existing OpenShell version pinning E2E guard test (test-openshell-version-pin.sh and regression coverage) to new pinned/sticky versions (0.0.39→0.0.44 and 0.0.40→0.0.45), directly connected to the retrieved PR's addition of the same guard.
• NVIDIA/NemoClaw#3446: Both PRs touch the OpenShell pinning installer path—scripts/install-openshell.sh and onboarding modules—so this PR's version bump to 0.0.44 lands on the same MIN/MAX/PIN resolution behavior introduced in the retrieved PR.

Suggested labels

OpenShell, v0.0.44, E2E

Suggested reviewers

• jyaunches
• cv
• cjagwani

Poem

🐰 A pinned version bumps from thirty-nine to forty-four,
Sticky baseline hops from forty to forty-five galore,
E2E guards test the dance, too-new falls back in place,
Installation paths aligned, supervisor tags keep pace! 🚀

❌ Failed checks (1 warning)

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

• openshell-version-pin-e2e (low): Direct coverage for the changed OpenShell min/max/pin behavior: verifies a sticky too-new OpenShell 0.0.45 is replaced with pinned 0.0.44 instead of hard-failing.
• openshell-gateway-upgrade-e2e (high): Required because the PR changes the current OpenShell version used by the gateway upgrade scenario. It validates old-install upgrade, gateway replacement, restored durable state, registry continuity, and OpenClaw agent survival.
• cloud-onboard-e2e (high): Required real install/onboard validation for the new blueprint OpenShell bounds and installer env propagation. This catches asset availability, fresh install, sandbox creation, and inference.local/onboard readiness regressions that unit tests and stubbed E2Es cannot.
• gateway-drift-preflight-e2e (medium): Required because the PR changes the Docker supervisor tag fallback and runtime version identity used by Docker-driver gateway drift detection. This verifies stale/incompatible gateway state is still detected and fails closed.
• gateway-health-honest-e2e (medium): Required gateway lifecycle guard because onboard gateway startup code and OpenShell binary version guidance changed. It verifies a failing gateway binary is not incorrectly reported healthy.

Optional E2E

• onboard-inference-smoke-e2e (medium): Useful adjacent confidence for the onboard success contract after the OpenShell pin bump: onboard should not report success until the configured inference route has served a real completion.
• cloud-inference-e2e (high): Optional live assistant confidence that the new OpenShell 0.0.44 install/onboard stack still supports inference.local and real chat completion after sandbox creation.
• sandbox-survival-e2e (high): Optional broader sandbox lifecycle coverage for gateway restart/survival behavior under the new OpenShell/supervisor version. Not merge-blocking if the targeted gateway upgrade and drift tests pass.

New E2E recommendations

• ci-launchable-runtime-image (medium): No targeted existing E2E appears to assert that scripts/brev-launchable-ci-cpu.sh installs the same OpenShell version as blueprint.yaml and pre-pulls the matching openshell/supervisor tag. Launchable regressions can break PR E2E readiness before product tests start.
  • Suggested test: Add a launchable-openshell-pin E2E that boots the CPU launchable setup path and asserts openshell --version, supervisor image tag, and blueprint min/max/pin coherence.
• openshell-release-asset-coherence (medium): The stubbed version-pin E2E validates installer decision logic, while cloud onboard validates the happy path. A lightweight release-asset coherence guard would catch missing OpenShell 0.0.44 helper assets or checksum naming drift before full onboarding.
  • Suggested test: Add an OpenShell asset availability E2E/check that verifies the pinned release has CLI, gateway, sandbox, and checksum assets for supported Linux/macOS architectures.