Skip to content

Review OpenShell v0.0.101 migration and security contracts #8599

Closed

Description

@apurvvkumaria

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.101 source boundary.
  • Review the full v0.0.85...v0.0.101 user 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.101 runtime.
  • 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

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.101 credential 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

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.

Activity

  1. added
    area: policyNetwork policy, egress rules, presets, or sandbox policy
    area: sandboxOpenShell sandbox lifecycle, runtime, config, or recovery
    needs: triageAwaiting maintainer classification
    on Aug 8, 2026
  2. self-assigned this
    on Aug 8, 2026
  3. apurvvkumaria commented on Aug 8, 2026

    @apurvvkumaria
    CollaboratorAuthor

    Exact-head review and ordinary qualification are complete for PR #8617 at 5279c514079657101e18231b0c49846c16a9af91 (DCO-signed and GitHub Verified).

    Passing exact-head evidence:

    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/93101776033

    Classification: base-wide, not candidate-caused. The trusted controller remains at main a76e297019c88c74d77ddadd4ffc96089278b8fa. Its security-posture job disables the CLI build and does not restore the exact-commit artifact containing nemoclaw/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.

  4. apurvvkumaria commented on Aug 8, 2026

    @apurvvkumaria
    CollaboratorAuthor

    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.

  5. apurvvkumaria commented on Aug 8, 2026

    @apurvvkumaria
    CollaboratorAuthor

    Fresh trusted qualification is terminal and did not produce an acceptable receipt.

    Dispatch 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.

  6. added a commit that references this issue on Aug 9, 2026
    b57c8b9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area: policyNetwork policy, egress rules, presets, or sandbox policyarea: sandboxOpenShell sandbox lifecycle, runtime, config, or recoveryneeds: triageAwaiting maintainer classification

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions