docs: refresh release notes for v0.0.72

[miyoungc]

Summary

• Add the v0.0.72 release-note section with links to the deeper docs pages for installer recovery, command diagnostics, inference, policy, and sandbox repair changes.
• Document the custom preset allowed_ips guard for user-authored policy files.

Related Issue

None.

Source summary

• fix(installer): recover sandboxes before onboarding #6132 -> docs/about/release-notes.mdx: Summarizes installer and upgrade recovery before generic onboarding, with links to quickstart and lifecycle docs.
• fix(security): validate Hermes endpoint URL and reject allowed_ips in user presets #6087 -> docs/network-policy/customize-network-policy.mdx: Documents that user-authored custom presets reject allowed_ips for ordinary endpoints; also summarized in release notes.
• fix(security): keep API keys out of curl probe argv #5975 -> docs/about/release-notes.mdx: Summarizes safer curl-based inference probes that keep API keys out of process arguments.
• feat(cli): add channel config status summary #6044 -> docs/about/release-notes.mdx: Summarizes compact channels status configuration reporting.
• fix(openclaw): disable EC2 metadata discovery #6096 -> docs/about/release-notes.mdx: Summarizes OpenClaw EC2 metadata discovery disablement and links to security guidance.
• [Linux][CLI&UX] nemoclaw <sb> exec rejects multi-line bash heredocs with "command argument contains newline" — single-line / semicolon workaround works #5980 and fix(exec): reject multi-line exec args with recovery guidance (#5980) #5991 -> docs/about/release-notes.mdx: Summarizes exec multiline argument rejection and recovery guidance.
• fix(inference): show registered providers and onboard tip on provider-not-found #6023 -> docs/about/release-notes.mdx: Summarizes registered-provider diagnostics for inference set failures.
• fix: refresh NVIDIA Endpoints featured models #6074 -> docs/about/release-notes.mdx: Summarizes the refreshed NVIDIA Endpoints featured-model selection behavior.
• feat(credentials): add CLI subcommand to register provider credentials #5969 -> docs/about/release-notes.mdx: Summarizes credentials add provider credential registration.
• fix(scripts): restore .openclaw perms after nemoclaw exec command #6060 -> docs/about/release-notes.mdx: Summarizes mutable OpenClaw config permission restoration after exec.
• fix(policy): restore Tavily egress for managed Python #6134 -> docs/about/release-notes.mdx: Summarizes restored Tavily access for managed Python workflows.
• fix(sandbox): compare hermes agent version in its runtime scheme #6089 -> docs/about/release-notes.mdx: Summarizes Hermes runtime version-scheme comparison during upgrade checks.
• fix(sandbox): respawn gateway after watchdog SIGTERM instead of exiting PID 1 #6131 -> docs/about/release-notes.mdx: Summarizes OpenClaw gateway watchdog recovery behavior.
• [Linux][Onboard] nemoclaw onboard with stdin EOF exits 0 silently and skips "Installation cancelled" message #5976 and fix(onboard): treat prompt stdin EOF as cancellation (#5976) #5990 -> docs/about/release-notes.mdx: Summarizes prompt stdin EOF cancellation behavior during onboarding.
• fix(cli): clarify status command scope #5540 -> docs/about/release-notes.mdx: Summarizes clarified host-level and per-sandbox status command scope.
• [Linux][CLI&UX] Sandbox-side policy denial error has no nemoclaw <name> logs --tail breadcrumb hint #5978 and fix(sandbox): surface policy-denial logs breadcrumb in connect shells (#5978) #6018 -> docs/about/release-notes.mdx: Summarizes policy-denial log breadcrumbs in connect shells.

Testing

• npm run docs:sync-agent-variants
• npm run docs
• Commit hooks passed during git commit, including commitlint and gitleaks.
• Pre-push hook passed during git push, including TypeScript CLI and package/tag version sync.

Checklist

• Documentation updated.
• npm run docs completed with 0 errors and 1 existing Fern warning.
• No source code or generated build artifacts committed.

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

Summary by CodeRabbit

• Documentation
  • Added release notes for v0.0.72 covering improved installer recovery, clearer CLI diagnostics, safer inference setup and provider switching, better credential handling, stronger policy boundaries, and more robust runtime repair behavior.
  • Updated network policy guidance to clarify when allowed_ips can be used, including a specific exception for the sandbox-to-host bridge endpoint.

[coderabbitai]

📝 Walkthrough

Walkthrough

This PR updates two documentation files: adding a new v0.0.72 release notes section describing installer recovery, CLI diagnostics, and inference onboarding safety improvements, and documenting a restriction on the allowed_ips field in custom network policy authoring guidance.

Changes

Documentation Updates

Layer / File(s)	Summary
Add v0.0.72 release notes docs/about/release-notes.mdx	New release notes section covering installer recovery ordering, backup restoration validation, CLI diagnostics improvements, inference/provider onboarding safety, credential handling, custom policy boundaries, and runtime repair behavior.
Document allowed_ips restriction docs/network-policy/customize-network-policy.mdx	Authoring guidance updated to state that allowed_ips is rejected for ordinary endpoints via --from-file/--from-dir due to SSRF risk, with the sole exception being the host.openshell.internal bridge endpoint.

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

Suggested labels: chore

🚥 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 clearly and accurately summarizes the main change: updating docs release notes for v0.0.72.
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.72-release-notes

---

_{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. Docs-only PR. The edits describe release notes and custom network policy guidance but do not change runtime behavior, workflow configuration, tests, policy YAML assets, or user-flow implementation, so no existing E2E job is required.

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 changes do not affect the E2E target workflow, target registry, runtime support, fixtures, live tests, or onboarding/runtime behavior.

Optional E2E targets

• None.

Relevant changed files

• None.

[github-actions]

🌿 Preview your docs: https://nvidia-preview-pr-6163.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: Custom preset allowed_ips restriction documented with correct bridge exemption.
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: Custom preset allowed_ips restriction documented with correct bridge exemption in docs/network-policy/customize-network-policy.mdx:278

Findings index

ID	Severity	Category	Location	Required action
PRA-1	Improvement	docs	docs/network-policy/customize-network-policy.mdx:278	No change needed — documentation accurately reflects the implemented security control

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 — Custom preset allowed_ips restriction documented with correct bridge exemption

• Location: docs/network-policy/customize-network-policy.mdx:278
• Category: docs
• Problem: The network policy docs now correctly state that user-authored custom presets must not declare allowed_ips except for the explicit host.openshell.internal bridge endpoint. This matches the implemented guard in src/lib/policy/index.ts (networkPoliciesHasAllowedIps) which rejects allowed_ips on all non-bridge endpoints, including prototype-chain-safe checks.
• Impact: Users authoring custom presets will understand the constraint and avoid rejected files; security posture is visible in docs
• Suggested action: No change needed — documentation accurately reflects the implemented security control
• Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
• Verification: Read src/lib/policy/index.ts:112-138 and src/lib/policy/preset-allowed-ips.test.ts to confirm implementation matches documentation
• Missing regression test: Already covered by preset-allowed-ips.test.ts (unit) and e2e/live/network-policy.test.ts:871-877 (E2E)
• Done when: The local improvement is applied, or the PR notes why it should be deferred.
• Evidence: Diff shows added lines 278-284 in customize-network-policy.mdx documenting the restriction; implementation verified in Turn 1

Since last review details

Current findings, using the urgency labels above:

PRA-1 Improvement — Custom preset allowed_ips restriction documented with correct bridge exemption

• Location: docs/network-policy/customize-network-policy.mdx:278
• Category: docs
• Problem: The network policy docs now correctly state that user-authored custom presets must not declare allowed_ips except for the explicit host.openshell.internal bridge endpoint. This matches the implemented guard in src/lib/policy/index.ts (networkPoliciesHasAllowedIps) which rejects allowed_ips on all non-bridge endpoints, including prototype-chain-safe checks.
• Impact: Users authoring custom presets will understand the constraint and avoid rejected files; security posture is visible in docs
• Suggested action: No change needed — documentation accurately reflects the implemented security control
• Expected follow-up: Prefer a current-PR fix when local to changed code; defer only with rationale or linked follow-up.
• Verification: Read src/lib/policy/index.ts:112-138 and src/lib/policy/preset-allowed-ips.test.ts to confirm implementation matches documentation
• Missing regression test: Already covered by preset-allowed-ips.test.ts (unit) and e2e/live/network-policy.test.ts:871-877 (E2E)
• Done when: The local improvement is applied, or the PR notes why it should be deferred.
• Evidence: Diff shows added lines 278-284 in customize-network-policy.mdx documenting the restriction; implementation verified in Turn 1

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: No advisor follow-up required beyond maintainer review.
Open items: 0 required · 0 warnings · 0 suggestions · 0 test follow-ups
Top item: No actionable findings

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]

🧹 Nitpick comments (1)

docs/network-policy/customize-network-policy.mdx (1)

302-305: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Content is accurate and matches the enforcement code.

The rejection rule, --from-file/--from-dir scope, SSRF rationale, and host.openshell.internal exception all match the guard logic in networkPoliciesHasAllowedIps/endpointHostIsGatewayBridge. One nuance not called out: the exception only applies to endpoint-level allowed_ips on that specific host — object-level allowed_ips is rejected even on a policy that also targets the bridge endpoint. Worth a brief clarifying phrase to avoid users trying allowed_ips at the policy-object level and being surprised.

🤖 Prompt for 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.

In `@docs/network-policy/customize-network-policy.mdx` around lines 302 - 305,
Clarify in customize-network-policy.mdx that the host.openshell.internal
exception only applies to endpoint-level allowed_ips on that bridge endpoint,
not to policy-object-level allowed_ips. Update the surrounding guidance near the
network policy rules so users know that networkPoliciesHasAllowedIps still
rejects object-level allowed_ips even when a policy includes
endpointHostIsGatewayBridge, and keep the rest of the allowed field guidance
unchanged.

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

Nitpick comments:
In `@docs/network-policy/customize-network-policy.mdx`:
- Around line 302-305: Clarify in customize-network-policy.mdx that the
host.openshell.internal exception only applies to endpoint-level allowed_ips on
that bridge endpoint, not to policy-object-level allowed_ips. Update the
surrounding guidance near the network policy rules so users know that
networkPoliciesHasAllowedIps still rejects object-level allowed_ips even when a
policy includes endpointHostIsGatewayBridge, and keep the rest of the allowed
field guidance unchanged.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7aa67af5-50a9-400c-bd20-ca34e86b7afd

📥 Commits

Reviewing files that changed from the base of the PR and between bdaecbc and 86b2f9c.

📒 Files selected for processing (2)

• docs/about/release-notes.mdx
• docs/network-policy/customize-network-policy.mdx