docs: refresh v0.0.70 release docs

[miyoungc]

Summary

Refreshes the v0.0.70 release docs from the release announcement and the v0.0.69..v0.0.70 commit range.
It also documents the channels start policy restoration behavior that was missing from the shared OpenClaw and Hermes command references, and bumps the Fern CLI version used for docs validation.

Changes

• Replaced the stale v0.0.70 release-notes entry with the actual release themes, including CLI, onboarding, inference, messaging, Windows, documentation, and release-validation changes.
• Documented that channels start reapplies the matching built-in network policy preset before rebuild and rolls back to disabled if policy restoration fails.
• Bumped fern/fern.config.json from 5.55.0 to 5.59.0 for the docs refresh.
• Source summary:
• fix(onboard): retry Docker Desktop gateway bridge probe #5754 -> docs/about/release-notes.mdx: Notes Docker Desktop gateway bridge retry behavior during onboarding.
• feat(cli): add nemoclaw use to set default sandbox #5930 -> docs/about/release-notes.mdx: Links nemoclaw use default sandbox selection to the command reference.
• fix(onboard): support reasoning-compatible endpoints #5948 -> docs/about/release-notes.mdx: Links reasoning-compatible endpoint validation to inference documentation.
• fix(windows): handle unavailable WSL runtime in windows bootstrap script #5950 -> docs/about/release-notes.mdx: Links Windows bootstrap WSL recovery behavior to Windows preparation and troubleshooting docs.
• fix(rebuild): clear stale policy presets from registry after rebuild #5856 -> docs/about/release-notes.mdx: Notes rebuilt policy preset registry repair.
• fix(hermes): remove stale openclaw state dir #5882 and fix(hermes): retire stale OpenClaw base guard #5949 -> docs/about/release-notes.mdx: Notes Hermes stale base-image state repair.
• fix(messaging): restore channel policy on start #6016 -> docs/reference/commands.mdx, docs/reference/commands-nemohermes.mdx, and docs/manage-sandboxes/messaging-channels.mdx: Documents channel policy restoration and rollback on channels start.
• docs: explain quickstart egress approvals (Fixes #5841) #5859 -> docs/about/release-notes.mdx: Links quickstart network approval guidance.
• docs(messaging): clarify Teams group allowlists (Fixes #5853) #5863 -> docs/about/release-notes.mdx: Links Teams allowlist guidance in the messaging page.
• test(e2e): retire legacy shell lanes #5756, test(e2e): wire sandbox operations into Vitest #5926, test(e2e): prove security posture parity for both agents #6010, and test(e2e): make docs validation a first-class Vitest lane #6011 -> docs/about/release-notes.mdx: Summarizes the Vitest E2E validation cutover.

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: doc-only prose refresh with no runtime behavior change.
• 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
• Git hooks passed during commit and push, or npx prek run --from-ref main --to-ref HEAD passes
• Targeted tests pass for changed behavior
• Full npm test passes (broad runtime changes only)
• 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)

npm run docs exited 0 and Fern reported one existing light-mode accent contrast warning.
fern check --warnings confirmed the warning is the site theme contrast ratio, not content introduced by this PR.

---

Signed-off-by: Miyoung Choi miyoungc@nvidia.com

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates documentation only. It rewrites the v0.0.70 release notes to describe E2E migration completion, day-two CLI improvements, drift-tolerant validation, and Vitest-based release testing. It also adds channel-restart network policy restoration behavior across three command reference docs, and bumps the fern config version.

Changes

Documentation Updates

Layer / File(s)	Summary
v0.0.70 release notes content update docs/about/release-notes.mdx	Rewrites the release notes section to cover E2E migration, day-two CLI steering, drift-tolerant validation, messaging/Hermes repair, expanded operator docs, and Vitest scenario validation replacing prior gateway auth/Hermes recovery content.
Channel restart network policy documentation docs/manage-sandboxes/messaging-channels.mdx, docs/reference/commands-nemohermes.mdx, docs/reference/commands.mdx	Documents that channels start reapplies the matching built-in network policy preset before rebuilding, and rolls back to disabled state without rebuilding if restoration fails.
Fern config version bump fern/fern.config.json	Bumps the version field from 5.55.0 to 5.59.0.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• cv

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately reflects the main change: refreshing v0.0.70 documentation, including release notes and command docs.
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.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

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

---

_{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 required because this is a docs-only/docs-tooling PR. The changes cannot affect installer/onboarding, sandbox lifecycle, credentials, security boundaries, network policy enforcement, inference routing, deployment, or live assistant user flows.

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 documentation tooling configuration changes do not affect the E2E target registry, workflow machinery, fixtures, runtime support, or live target behavior.

Optional E2E targets

• None.

Relevant changed files

• None.

[github-actions]

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

[github-code-quality]

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in the docs/v0.0.70-release... branch is 96%. Coverage data for the main branch is not yet available.

Show a code coverage summary of the most covered files.

File	main	docs/v0.0.70-release... edba6bc	+/-
nemoclaw/src/se...cret-scanner.ts	—	100%	—
nemoclaw/src/commands/slash.ts	—	100%	—
nemoclaw/src/li...bprocess-env.ts	—	100%	—
nemoclaw/src/bl...eprint/state.ts	—	98%	—
nemoclaw/src/onboard/config.ts	—	98%	—
nemoclaw/src/bl...int/snapshot.ts	—	97%	—
nemoclaw/src/bl...print/runner.ts	—	95%	—
nemoclaw/src/co...ration-state.ts	—	94%	—
nemoclaw/src/bl...ate-networks.ts	—	94%	—
nemoclaw/src/index.ts	—	94%	—

TypeScript / code-coverage/cli

The overall coverage in the docs/v0.0.70-release... branch is 68%. Coverage data for the main branch is not yet available.

Show a code coverage summary of the most covered files.

File	main	docs/v0.0.70-release... edba6bc	+/-
src/lib/shields...nsition-lock.ts	—	86%	—
src/lib/actions...dbox/rebuild.ts	—	80%	—
src/lib/actions...all/run-plan.ts	—	80%	—
src/lib/state/o...oard-session.ts	—	80%	—
src/lib/state/sandbox.ts	—	72%	—
src/lib/onboard/preflight.ts	—	69%	—
src/lib/shields/index.ts	—	67%	—
src/lib/onboard...er-gpu-patch.ts	—	59%	—
src/lib/actions...licy-channel.ts	—	58%	—
src/lib/onboard.ts	—	20%	—

---

_{Updated June 30, 2026 20:53 UTC
Code Coverage is in Public Preview. Learn more and provide us with your feedback.}

[github-actions]

PR Review Advisor (Nemotron Ultra) — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: Consider PRA-1: Verify release notes align with actual v0.0.70 tag contents.
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: Verify release notes align with actual v0.0.70 tag contents in docs/about/release-notes.mdx:1

Findings index

ID	Severity	Category	Location	Required action
PRA-1	Improvement	docs	docs/about/release-notes.mdx:1	Before tagging v0.0.70, cross-check this release-notes.mdx against the actual v0.0.70 commit range and linked issues (#5754, #5930, #5948, #5950, #5856, #5882, #5949, #6016, #5859, #5863, #5756, #5926, #6010, #6011). No code change needed — doc verification only.

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 — Verify release notes align with actual v0.0.70 tag contents

• Location: docs/about/release-notes.mdx:1
• Category: docs
• Problem: Release notes v0.0.70 rewritten from 'hardens OpenShell gateway auth and Hermes recovery' to broader scope (E2E migration complete, day-two ops, messaging repair, Windows bootstrap, docs). Overlapping PR chore(openshell): upgrade supported version to 0.0.72 #6020 upgrades OpenShell to 0.0.72. Ensure this doc reflects what actually ships in v0.0.70.
• Impact: If release notes diverge from tagged release, users and automated changelog consumers get incorrect information about v0.0.70 features.
• Suggested action: Before tagging v0.0.70, cross-check this release-notes.mdx against the actual v0.0.70 commit range and linked issues (fix(onboard): retry Docker Desktop gateway bridge probe #5754, feat(cli): add nemoclaw use to set default sandbox #5930, fix(onboard): support reasoning-compatible endpoints #5948, fix(windows): handle unavailable WSL runtime in windows bootstrap script #5950, fix(rebuild): clear stale policy presets from registry after rebuild #5856, fix(hermes): remove stale openclaw state dir #5882, fix(hermes): retire stale OpenClaw base guard #5949, fix(messaging): restore channel policy on start #6016, docs: explain quickstart egress approvals (Fixes #5841) #5859, docs(messaging): clarify Teams group allowlists (Fixes #5853) #5863, test(e2e): retire legacy shell lanes #5756, test(e2e): wire sandbox operations into Vitest #5926, test(e2e): prove security posture parity for both agents #6010, test(e2e): make docs validation a first-class Vitest lane #6011). No code change needed — doc verification only.
• Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
• Verification: Compare release-notes.mdx v0.0.70 section against `git log v0.0.69..v0.0.70 --oneline` and linked issue deliverables
• Missing regression test: N/A — doc accuracy check, not automatable as regression test
• Done when: The local improvement is applied, or the PR notes why it should be deferred.
• Evidence: PR body maps 14 issues to release notes content; overlapping PR chore(openshell): upgrade supported version to 0.0.72 #6020 targets OpenShell 0.0.72

Since last review details

Current findings, using the urgency labels above:

PRA-1 Improvement — Verify release notes align with actual v0.0.70 tag contents

• Location: docs/about/release-notes.mdx:1
• Category: docs
• Problem: Release notes v0.0.70 rewritten from 'hardens OpenShell gateway auth and Hermes recovery' to broader scope (E2E migration complete, day-two ops, messaging repair, Windows bootstrap, docs). Overlapping PR chore(openshell): upgrade supported version to 0.0.72 #6020 upgrades OpenShell to 0.0.72. Ensure this doc reflects what actually ships in v0.0.70.
• Impact: If release notes diverge from tagged release, users and automated changelog consumers get incorrect information about v0.0.70 features.
• Suggested action: Before tagging v0.0.70, cross-check this release-notes.mdx against the actual v0.0.70 commit range and linked issues (fix(onboard): retry Docker Desktop gateway bridge probe #5754, feat(cli): add nemoclaw use to set default sandbox #5930, fix(onboard): support reasoning-compatible endpoints #5948, fix(windows): handle unavailable WSL runtime in windows bootstrap script #5950, fix(rebuild): clear stale policy presets from registry after rebuild #5856, fix(hermes): remove stale openclaw state dir #5882, fix(hermes): retire stale OpenClaw base guard #5949, fix(messaging): restore channel policy on start #6016, docs: explain quickstart egress approvals (Fixes #5841) #5859, docs(messaging): clarify Teams group allowlists (Fixes #5853) #5863, test(e2e): retire legacy shell lanes #5756, test(e2e): wire sandbox operations into Vitest #5926, test(e2e): prove security posture parity for both agents #6010, test(e2e): make docs validation a first-class Vitest lane #6011). No code change needed — doc verification only.
• Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
• Verification: Compare release-notes.mdx v0.0.70 section against `git log v0.0.69..v0.0.70 --oneline` and linked issue deliverables
• Missing regression test: N/A — doc accuracy check, not automatable as regression test
• Done when: The local improvement is applied, or the PR notes why it should be deferred.
• Evidence: PR body maps 14 issues to release notes content; overlapping PR chore(openshell): upgrade supported version to 0.0.72 #6020 targets OpenShell 0.0.72

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 — Changes requested

Merge posture: Do not merge yet
Primary next action: Resolve or justify PRA-1: Confirm Fern docs-tool version bump provenance/advisory status.
Open items: 0 required · 1 warning · 0 suggestions · 0 test follow-ups
Top item: Confirm Fern 5.59.0 docs tool provenance/advisory status

Action checklist

• PRA-1 Resolve or justify: Confirm Fern docs-tool version bump provenance/advisory status in fern/fern.config.json:3

Findings index

ID	Severity	Category	Location	Required action
PRA-1	Resolve/justify	security	fern/fern.config.json:3	Record or attach the normal dependency/advisory/provenance check for `fern-api@5.59.0`, or add a brief justification showing why this exact version is required and acceptable for the docs build.

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

⚠️ 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.

PRA-1 Resolve/justify — Confirm Fern docs-tool version bump provenance/advisory status

• Location: fern/fern.config.json:3
• Category: security
• Problem: This PR changes the docs generator selected by repository scripts from `fern-api@5.55.0` to `fern-api@5.59.0`. The version is exactly pinned and affects docs tooling rather than NemoClaw runtime code, but `package.json` resolves the value from `fern/fern.config.json` and invokes it via `npx --yes`, so the PR is changing third-party executable tooling without local advisory/provenance evidence in the diff.
• Impact: If the bumped docs tool version has a supply-chain issue or incompatible behavior, docs validation/publishing can execute unreviewed changed third-party code in the docs workflow context. This is lower risk than runtime dependency drift, but it still crosses the trusted-code boundary for documentation builds.
• Recommended action: Record or attach the normal dependency/advisory/provenance check for `fern-api@5.59.0`, or add a brief justification showing why this exact version is required and acceptable for the docs build.
• Expected follow-up: Resolve in this PR or explain why the risk is acceptable.
• Verification: Read `fern/fern.config.json:3` and `package.json` `docs:*` scripts to confirm the version is consumed as `npx --yes fern-api@${FERN_VERSION}`; then check the repository's dependency/security tooling output for `fern-api@5.59.0`.
• Missing regression test: No runtime regression test is needed for this docs-only tool bump. Existing docs validation should cover compatibility; the missing evidence is an automated dependency/advisory or provenance check result for `fern-api@5.59.0`.
• Done when: The risk is fixed or explicitly justified in the PR. Verification: Read `fern/fern.config.json:3` and `package.json` `docs:*` scripts to confirm the version is consumed as `npx --yes fern-api@${FERN_VERSION}`; then check the repository's dependency/security tooling output for `fern-api@5.59.0`.
• Evidence: `fern/fern.config.json` changes `"version": "5.55.0"` to `"version": "5.59.0"`; `package.json` docs scripts resolve that config value and run `npx --yes "fern-api@${FERN_VERSION}"`.

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

• None.

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.