Repository navigation
Review OpenShell v0.0.101 migration and security contracts #8599
Copy link
Copy link
Closed
Labels
area: policyNetwork policy, egress rules, presets, or sandbox policyNetwork policy, egress rules, presets, or sandbox policyarea: sandboxOpenShell sandbox lifecycle, runtime, config, or recoveryOpenShell sandbox lifecycle, runtime, config, or recoveryneeds: triageAwaiting maintainer classificationAwaiting maintainer classification
Description
Important
This child is reserved for #8590 integration-owner dispatch.
Do not start implementation without an explicit assignment from that owner.
Problem Statement
Parent epic: #8590.
OpenShell v0.0.101 changes runtime and security contracts beyond the version selector.
A complete review must identify every affected producer and consumer before implementation starts.
Proposed Design
Scope
- Review the full
v0.0.99...v0.0.101source boundary. - Review the full
v0.0.85...v0.0.101user upgrade boundary. - Review middleware, credentials, policies, proxy isolation, gateway, drivers, SDK, and dependencies.
- Record changes to output, errors, names, labels, identifiers, aliases, arguments, metadata, sockets, and reconnect behavior.
- Generate the child-visible credential manifest from the published
v0.0.101runtime. - Confirm that new upstream functions remain disabled by default.
- Build an invariant table for every changed shared contract.
- Search every producer and consumer of each changed contract.
Owned boundaries
- Own the migration inventory, security review, and compatibility recommendations.
- Do not change selectors, qualification gates, runtime compatibility code, or policy compatibility code.
Dependencies
- Use the final merged baseline from fix(openshell): complete v0.0.99 compatibility #8583.
- Use trusted artifact identities from Record OpenShell v0.0.101 baselines and release trust #8598 when they become available.
Required evidence
- Publish the complete source and user-boundary comparison.
- Link each changed contract to all affected consumers.
- Link each contract to positive, negative, legacy, and live tests.
- Record security changes and default-disabled upstream functions.
- Assign each required correction to one child issue.
Acceptance criteria
- Review both upgrade boundaries.
- Complete the changed-contract invariant table.
- Review the generated
v0.0.101credential manifest. - Confirm that default security boundaries do not expand.
- Assign every required correction to one owning child issue.
- Link the completed review to [Epic] Qualify and pin OpenShell v0.0.101 #8590.
Handoff
- Report reviewed paths, risks, required tests, and unresolved questions.
- Report each affected shared contract and its consumers.
- Link the review evidence to [Epic] Qualify and pin OpenShell v0.0.101 #8590.
Implementation starts in a separate Codex thread.
Alternatives Considered
Review changes during selector implementation. This approach would hide dependencies and increase correction cycles.
Category
Platform
Checklist
- I searched existing issues and this is not a duplicate.
- This is a design proposal, not a "please build this" request.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
area: policyNetwork policy, egress rules, presets, or sandbox policyNetwork policy, egress rules, presets, or sandbox policyarea: sandboxOpenShell sandbox lifecycle, runtime, config, or recoveryOpenShell sandbox lifecycle, runtime, config, or recoveryneeds: triageAwaiting maintainer classificationAwaiting maintainer classification
Activity
apurvvkumaria commentedon Aug 8, 2026
Exact-head review and ordinary qualification are complete for PR #8617 at
5279c514079657101e18231b0c49846c16a9af91(DCO-signed and GitHub Verified).Passing exact-head evidence:
merge_as_iswith zero findings. The advisory Nemotron lane failed after a partial review and produced no finding.The installer-hash job verified every pinned release asset, then failed only with
no current-head trusted full E2E dispatch receipt was found: https://github.com/NVIDIA/NemoClaw/actions/runs/31256993557/job/93101776033Classification:
base-wide, not candidate-caused. The trusted controller remains at maina76e297019c88c74d77ddadd4ffc96089278b8fa. Itssecurity-posturejob disables the CLI build and does not restore the exact-commit artifact containingnemoclaw/dist/shared/sandbox-name.cjs; current-main run https://github.com/NVIDIA/NemoClaw/actions/runs/31243363889/job/93077846620 and #8598's authenticated attempt show the identical collection failure. A read-only scan found no later main commit or open PR repairing this preparation path.PR #8617 remains open. Do not waive the receipt or dispatch a knowingly doomed run. After an external trusted-base repair merges, review that base delta and dispatch one fresh exact-head qualification run.
apurvvkumaria commentedon Aug 8, 2026
The one permitted post-repair qualification for frozen PR #8617 is complete: run 31263982351 failed (66 successful, 7 skipped, 24 failed jobs), so no successful trusted receipt exists and the PR is not accepted.
The base repair did fix its target: Hermes security-posture passed after restoring the exact candidate CLI artifact. The remaining failure wave is base-wide/external. OpenClaw security-posture failed with HTTP 429 on #8617, #8616, and the identical-tree repaired-main run; 19 of the 24 failed #8617 job names also fail on repaired main. The four #8617 files do not touch the implicated live runtime paths.
Head 5279c51 remains frozen and provisionally ready only. The one-run limit is honored: no rerun, merge, branch movement, or acceptance.
apurvvkumaria commentedon Aug 8, 2026
Fresh trusted qualification is terminal and did not produce an acceptable receipt.
5279c514079657101e18231b0c49846c16a9af91a76e297019c88c74d77ddadd4ffc96089278b8faa816474c2b91e5e01e560326c750324c05571c4a9581ee0f-7a9a-4524-9964-6c24b994dcf2Dispatch identity, setup/provenance, the exact candidate/base binding, and the exact CLI artifact all authenticated successfully. Seventeen failed job names recur across the paired #8616/#8617 runs; fourteen have the same or semantically identical terminal signature, including rate limits, inference/service readiness, stale generated-image, websocket-handshake, package-registry DNS, and shared protected-runtime failures. The #8617 delta remains limited to documentation, source-shape budget, the credential contract, and its non-live contract test and does not touch the failed live runtime paths. This is therefore classified as shared base/external qualification failure, with no candidate-specific failure evidenced.
Success is still mandatory. #8617 remains implementation-complete, frozen, provisionally ready, and not accepted. The run was not rerun or waived; the head was not moved; no dependent child, candidate, or merge is unlocked.
docs(security): review OpenShell v0.0.101 contracts (NVIDIA#8617)