docs(sandbox): clarify legacy recovery evidence

[apurvvkumaria]

Summary

This docs-only follow-up to #8735 clarifies the managed-image evidence required during installer-driven legacy gateway recovery. OpenClaw and Hermes retain the exact-name pre-fingerprint confirmation exception, while Deep Agents still requires positive registry evidence.

Changes

• Render the pre-fingerprint confirmation exception only in the OpenClaw and Hermes guide variants.
• State that explicit managed-image confirmation is the only exception to the registry evidence requirement.

Type of Change

• Code change (feature, bug fix, or refactor)
• Code change with doc updates
• Doc only (prose changes, no code sample modifications)
• Doc only (includes code sample changes)

Quality Gates

• Tests added or updated for changed behavior
• Existing tests cover changed behavior — justification:
• Tests not applicable — justification: Docs-only clarification of behavior already tested and merged in fix(sandbox): repair legacy gateway upgrade recovery #8735.
• Docs updated for user-facing behavior changes
• Docs not applicable — justification:
• Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
• Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification:
• Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Documentation Writer Review

• Documentation writer subagent reviewed the completed changes
• Result: docs-updated
• Evidence: docs/manage-sandboxes/update-sandboxes.mdx
• Agent: Codex Desktop

DGX Station Hardware Evidence

• Tested on DGX Station
• Tested commit:
• Station profile/scenario:
• Result:
• Supporting evidence:

Verification

• PR description includes a Signed-off-by: line and every commit appears as Verified in GitHub
• Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run validate:pr passed after refreshing origin/main when hooks were skipped or unavailable
• Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result or justification: npm run docs and npx prek run --files docs/manage-sandboxes/update-sandboxes.mdx passed; generated variants preserve the agent-specific requirements.
• Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result: Not applicable to this one-page docs-only follow-up.
• Quality Gates section completed with required justifications or waivers
• No secrets, API keys, or credentials committed
• npm run docs builds without warnings (doc changes only) — passed with Fern's two existing hidden warnings.
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

---

Signed-off-by: Apurv Kumaria akumaria@nvidia.com

[coderabbitai]

📝 Walkthrough

Walkthrough

The sandbox recovery documentation now requires positive NemoClaw-managed-image evidence for Deep Agents, OpenClaw, and Hermes. It also documents an installer confirmation exception for listed pre-fingerprint OpenClaw or Hermes entries.

Changes

Sandbox recovery requirements

Layer / File(s)	Summary
Managed-image recovery evidence docs/manage-sandboxes/update-sandboxes.mdx	The recovery requirements now require registry evidence that NemoClaw managed the sandbox image. Listed pre-fingerprint OpenClaw or Hermes entries can use explicit installer confirmation instead.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: aasthajh

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the documentation change to legacy sandbox recovery evidence.

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/clarify-legacy-recovery-evidence

---

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

🌿 Preview your docs: https://nvidia-preview-pr-8749.docs.buildwithfern.com/nemoclaw

[github-actions]

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions

Model lanes

• GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
• Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
• Model comparison: normalized findings match; normalized terminology decisions differ; normalized E2E selections differ; severity counts match.

4 additional E2E selections from the second opinion

Advisory only. The primary lane did not select these E2E jobs or targets.

• state-backup-restore: The completed second-opinion lane identified E2E coverage that the primary lane omitted.
• rebuild-openclaw: The completed second-opinion lane identified E2E coverage that the primary lane omitted.
• rebuild-hermes: The completed second-opinion lane identified E2E coverage that the primary lane omitted.
• managed-image-multiarch-startup: The completed second-opinion lane identified E2E coverage that the primary lane omitted.

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

3 semantic terminology decisions

Terminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.

• established — managed-image confirmation at docs/manage-sandboxes/update-sandboxes.mdx:93: Keep “managed-image confirmation” for the installer authorization.
• justified — pre-fingerprint confirmation at docs/manage-sandboxes/update-sandboxes.mdx:87: Keep the “pre-fingerprint” modifier where the legacy-entry exception is distinguished from fingerprinted entries.
• justified — registry evidence at docs/manage-sandboxes/update-sandboxes.mdx:93: Keep the phrase because the preceding sentence defines the required evidence and the following sentence defines its sole exception.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite against this exact revision.

Recommended E2E: None

1 optional E2E recommendation

• openshell-gateway-upgrade

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.