docs: prepare v0.0.74 release notes

[ericksoa]

Summary

This PR prepares the user-facing documentation for v0.0.74 before the release plan is frozen.
It expands the release notes across the 56-commit train and closes durable documentation gaps found during the pre-tag commit scan.

Changes

• Expand the v0.0.74 release notes to cover OpenShell 0.0.72, managed MCP, progressive tool disclosure, LangChain Deep Agents Code, onboarding, local inference, messaging, recovery, and contributor workflows.
• Correct the destroy contract for retained per-name volumes, gateway-unreachable --force cleanup, managed MCP ownership, and same-name recovery.
• Document separate remediation for an unreachable container DNS resolver versus one that answers with NXDOMAIN or REFUSED.
• Document the Windows on Arm N1X automatic Ollama safeguard and its remaining large-model limitations.
• State that messaging conflicts abort rebuild before backup or deletion, leaving the original sandbox intact.
• Link the agent-runnable value benchmark from the contributor task index.
• Synchronize generated agent command variants.
• Validate with npm run docs:sync-agent-variants and npm run docs; Fern completed with 0 errors and 2 existing warnings.
• Source summary:
  • #6020 and #5876 -> docs/about/release-notes.mdx: Consolidate the OpenShell 0.0.72 policy boundary and managed MCP lifecycle.
  • #6251 and #5989 -> docs/about/release-notes.mdx: Summarize progressive tool disclosure and sandbox-first inference controls.
  • #6232, #6082, #6219, #6214, #6215, #6230, and #6260 -> docs/about/release-notes.mdx: Summarize the experimental LangChain Deep Agents Code status, secret, version, rebuild, snapshot, and MCP boundaries.
  • #6166, #6254, #6265, #6164, and #6017 -> docs/about/release-notes.mdx: Summarize BuildKit prebuild, validated image reuse, bounded readiness, and preflight improvements.
  • #6150 -> docs/about/release-notes.mdx and docs/reference/troubleshooting.mdx: Separate unreachable-resolver remediation from reachable-but-rejected DNS responses.
  • #6234 -> docs/about/release-notes.mdx, docs/inference/use-local-inference.mdx, and docs/get-started/windows-preparation.mdx: Document N1X automatic 9B selection and the remaining explicit-large-model boundary.
  • #6129, #5987, #5955, and #6220 -> docs/about/release-notes.mdx, docs/manage-sandboxes/messaging-channels.mdx, docs/reference/commands.mdx, and docs/reference/commands-nemohermes.mdx: Document messaging policy persistence, status, and the pre-destructive conflict check.
  • #5963, #6050, #6094, #6238, #5988, #6235, #6181, and #5986 -> docs/about/release-notes.mdx, docs/reference/commands.mdx, and docs/reference/commands-nemohermes.mdx: Summarize day-two recovery and clarify retained-volume and local-only destroy semantics.
  • #6200, #6248, #6168, #6270, and #5649 -> docs/about/release-notes.mdx and CONTRIBUTING.md: Summarize contributor setup and verification improvements and expose the advisory value benchmark.

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: documentation-only release preparation; generated-variant synchronization and the Fern docs build validate the changed pages and routes.
• 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:

Verification

• PR description includes the DCO sign-off declaration and every commit appears as Verified in GitHub
• Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run check:diff passed 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: tests are not applicable to this documentation-only change; npm run docs validates the source and generated routes.
• Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result:
• 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)
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

---

Signed-off-by: Aaron Erickson aerickson@nvidia.com

Summary by CodeRabbit

• Documentation
  • Expanded setup guidance for Windows on Arm devices with safer default local model selection.
  • Clarified local inference and sandbox messaging behavior, including conflict checks before rebuilds and safer recovery steps.
  • Updated destroy/rebuild/reference docs with more detailed warnings, failure handling, and volume-retention guidance.
  • Improved troubleshooting instructions for Docker DNS issues with clearer paths for unreachable vs. blocked resolvers.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 1ae11d1c-e669-4a57-9a44-3a8d0c61537c

📥 Commits

Reviewing files that changed from the base of the PR and between 05004d3 and 9fea31a.

📒 Files selected for processing (1)

• docs/about/release-notes.mdx

✅ Files skipped from review due to trivial changes (1)

• docs/about/release-notes.mdx

---

📝 Walkthrough

Walkthrough

This PR updates documentation only. It expands release notes, adds a npm run bench entry, documents Windows-on-Arm N1X model selection, clarifies rebuild and destroy command behavior, and revises DNS troubleshooting guidance.

Changes

Documentation updates

Layer / File(s)	Summary
Release notes and bench script docs/about/release-notes.mdx, CONTRIBUTING.md	Expands the v0.0.74 release notes overview and bullet list; adds a npm run bench row to the main tasks table.
Windows on Arm N1X model selection docs/get-started/windows-preparation.mdx, docs/inference/use-local-inference.mdx	Documents automatic starter-model selection for Windows on Arm N1X and clarifies the selection boundary and remaining limitations.
Rebuild pre-backup conflict check docs/manage-sandboxes/messaging-channels.mdx, docs/reference/commands-nemohermes.mdx, docs/reference/commands.mdx	Describes a pre-rebuild staged messaging configuration recheck that aborts on credential or channel-resource conflicts before backup or deletion.
Destroy persistent-volume behavior docs/reference/commands-nemohermes.mdx, docs/reference/commands.mdx	Replaces permanent-deletion wording with persistent-volume retention, wipe-failure guidance, --cleanup-gateway, and --force scope details.
DNS troubleshooting updates docs/reference/troubleshooting.mdx	Adds conditional DNS recovery guidance and changes the verification lookup target to registry.npmjs.org.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• NVIDIA/NemoClaw#2463: Both PRs modify the DNS troubleshooting guidance in docs/reference/troubleshooting.mdx.
• NVIDIA/NemoClaw#2850: Both PRs touch messaging-channels documentation around rebuild behavior.
• NVIDIA/NemoClaw#4539: Both PRs update messaging-channel rebuild flow documentation and safeguards.

Suggested labels: chore

Suggested reviewers: cv, jyaunches

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the PR’s main intent: preparing v0.0.74 documentation and release notes.
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.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/v0.0.74-release-prep

---

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

[github-actions]

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

• None. No E2E is recommended because this is a docs-only PR. The changes cannot directly affect installer/onboarding execution, sandbox lifecycle, credentials, security boundaries, network policy enforcement, inference routing, deployment, or live assistant flows. Use the docs validation path instead of live E2E.

Optional E2E

• None.

New E2E recommendations

• None.

[github-actions]

E2E Target Recommendation

Required E2E targets: None
Optional E2E targets: None

Workflow run

Full E2E target advisor summary

E2E Target Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E targets

• None. Docs-only and contributor-guide changes do not affect the E2E target registry, workflow wiring, live fixtures, runtime support, or target behavior.

Optional E2E targets

• None.

Relevant changed files

• None.

[github-actions]

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

[github-actions]

PR Review Advisor (Nemotron Ultra) — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: Consider PRA-1: MCP command names verified accurate.
Open items: 0 required · 0 warnings · 1 suggestion · 0 test follow-ups
Since last review: 0 prior items resolved · 0 still apply · 0 new items found

Action checklist

• PRA-1 In-scope improvement: MCP command names verified accurate in docs/about/release-notes.mdx:26

Findings index

ID	Severity	Category	Location	Required action
PRA-1	Improvement	correctness	docs/about/release-notes.mdx:26	No action needed — documentation is correct

Review findings by urgency: 0 required fixes, 0 items to resolve/justify, 1 in-scope improvement

⚠️ Resolve or justify before merge

Investigate these in the current review; either fix them, explain why they are not applicable, or document the accepted risk.

• None.

💡 In-scope improvements

These are lower-risk, not throwaway. Prefer fixing them in this PR when they are local to changed code; defer only with rationale or a linked follow-up.

PRA-1 Improvement — MCP command names verified accurate

• Location: docs/about/release-notes.mdx:26
• Category: correctness
• Problem: Release notes list MCP commands as 'add, list, status, restart, and remove' — matches implementation (no 'inspect' or 'rotate' commands exist in src/commands/sandbox/). Previous draft had 'add, list, inspect, rotate, restart, remove'; this correction is accurate.
• Impact: None — documentation is correct and matches implementation
• Suggested action: No action needed — documentation is correct
• Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
• Verification: grep -r "mcp.*add\|mcp.*list\|mcp.*status\|mcp.*restart\|mcp.*remove" src/commands/sandbox/ | grep -v test
• Missing regression test: N/A — doc-only change reflecting existing behavior
• Done when: The local improvement is applied, or the PR notes why it should be deferred.
• Evidence: Release notes line 26 lists exact MCP commands; source commands confirm only these 5 exist

Since last review details

Current findings, using the urgency labels above:

PRA-1 Improvement — MCP command names verified accurate

• Location: docs/about/release-notes.mdx:26
• Category: correctness
• Problem: Release notes list MCP commands as 'add, list, status, restart, and remove' — matches implementation (no 'inspect' or 'rotate' commands exist in src/commands/sandbox/). Previous draft had 'add, list, inspect, rotate, restart, remove'; this correction is accurate.
• Impact: None — documentation is correct and matches implementation
• Suggested action: No action needed — documentation is correct
• Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
• Verification: grep -r "mcp.*add\|mcp.*list\|mcp.*status\|mcp.*restart\|mcp.*remove" src/commands/sandbox/ | grep -v test
• Missing regression test: N/A — doc-only change reflecting existing behavior
• Done when: The local improvement is applied, or the PR notes why it should be deferred.
• Evidence: Release notes line 26 lists exact MCP commands; source commands confirm only these 5 exist

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

[github-actions]

PR Review Advisor — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: Add or justify PRA-T1 and any related test follow-ups.
Open items: 0 required · 0 warnings · 0 suggestions · 1 test follow-up
Since last review: 1 prior item resolved · 0 still apply · 0 new items found

Action checklist

• PRA-T1 Add or justify test follow-up: Acceptance clause

Test follow-ups to resolve or justify

If these cover changed behavior, prefer adding them in this PR; otherwise state why existing coverage is enough or link the follow-up.

• PRA-T1 Acceptance clause — Validate with `npm run docs:sync-agent-variants` and `npm run docs`; Fern completed with 0 errors and 2 existing warnings. — add test evidence or identify existing coverage. This is PR-provided verification text only; this review did not execute commands. The diff is consistent with docs validation expectations and no broken local source references were found in read-only inspection.

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/about/release-notes.mdx`:
- Line 26: Reword the MCP command summary in the release notes so the actual
subcommands are clearly presented and consistently code-formatted. Update the
sentence around the MCP management features to emphasize the documented commands
in the relevant release-notes entry, using the exact symbols add, list, status,
restart, and remove, and avoid prose that implies extra actions like inspect or
refresh.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 0bb0d6bd-8045-444b-98b4-74ad632777b6

📥 Commits

Reviewing files that changed from the base of the PR and between 06b78aa and 05004d3.

📒 Files selected for processing (8)

• CONTRIBUTING.md
• docs/about/release-notes.mdx
• docs/get-started/windows-preparation.mdx
• docs/inference/use-local-inference.mdx
• docs/manage-sandboxes/messaging-channels.mdx
• docs/reference/commands-nemohermes.mdx
• docs/reference/commands.mdx
• docs/reference/troubleshooting.mdx