docs: refresh release notes for v0.0.67

[miyoungc]

Summary

Refresh the docs for the v0.0.67 release using the GitHub announcement and release-range commit scan.

Changes

• Add v0.0.67 release notes for onboarding recovery, Discord proxy behavior, OpenClaw agent apply deletion, and compact AI-agent docs routing.
• Clarify onboard --resume repair checks in the OpenClaw and Hermes command references.
• Clarify Discord's managed proxy path and agents apply delete behavior in the relevant docs pages.

Source Summary

• chore: retire docs-to-skills and make single compact user skill #5699 -> docs/resources/agent-skills.mdx, docs/about/release-notes.mdx: Reflects the compact nemoclaw-user-guide docs-routing skill and canonical MCP/Markdown docs entry points.
• fix(discord): stop emitting a non-loopback per-account proxy (#5544) #5571 -> docs/manage-sandboxes/messaging-channels.mdx, docs/about/release-notes.mdx: Documents Discord using the managed proxy path instead of a rejected per-account proxy.
• test(e2e): harden WhatsApp policy assertions #5704 -> docs/about/release-notes.mdx: Captures the WhatsApp policy assertion hardening in the release note context.
• Follow-up commit 46ead831e -> docs/reference/commands.mdx, docs/reference/commands-nemohermes.mdx, docs/about/release-notes.mdx: Documents resume repair checks across later nonterminal onboarding phases.
• Follow-up commit ee0725a32 -> docs/reference/commands.mdx, docs/about/release-notes.mdx: Documents that agents apply uses OpenClaw's confirmation-skipping delete mode for orphan agents.

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)

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)
• Tests added or updated for new or changed behavior
• No secrets, API keys, or credentials committed
• Docs updated for user-facing behavior changes
• 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)

Verification run:

• bash test/e2e/e2e-cloud-experimental/check-docs.sh --only-cli passed.
• npm run docs passed with the pre-existing Fern light-mode accent contrast warning: The contrast ratio between the accent color and the background color for light mode is 2.41:1. It should be at least 3:1.

---

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

Summary by CodeRabbit

• Documentation
  • Added release notes for v0.0.67 covering onboarding recovery, messaging reliability, OpenClaw agent workflows, and AI-agent documentation routing.
  • Clarified Discord channel requirements, including routing through the top-level managed proxy.
  • Updated onboarding resume guidance to note rerunning preflight, gateway, provider, and sandbox repair checks.
  • Refined CLI command reference details for orphan-agent deletion behavior and how interactive flags affect prompts vs. deletion.

[github-actions]

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

[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: 2519df55-019b-488b-84d0-7401521a6c0d

📥 Commits

Reviewing files that changed from the base of the PR and between dd644b1 and 73038e4.

📒 Files selected for processing (1)

• docs/reference/commands.mdx

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

• docs/reference/commands.mdx

---

📝 Walkthrough

Walkthrough

Documentation-only update adding a v0.0.67 release notes section and clarifying three behavioral details: --resume onboarding always reruns preflight/gateway/provider/sandbox repair checks, agents apply orphan deletion uses --force only without forwarding --non-interactive to OpenClaw, and Discord traffic routes through the top-level managed proxy with no per-account proxy written.

Changes

Documentation Clarifications and Release Notes

Layer / File(s)	Summary
CLI --resume and agents apply clarifications docs/reference/commands.mdx, docs/reference/commands-nemohermes.mdx	--resume description now states it reruns preflight, gateway, provider, and sandbox repair checks even when the saved session reached a later nonterminal phase. agents apply orphan deletion mechanics clarified: uses --force only, and --non-interactive controls only the host-side prompt.
Discord proxy note and v0.0.67 release notes docs/manage-sandboxes/messaging-channels.mdx, docs/about/release-notes.mdx	Adds a Discord channel requirements note about top-level managed proxy routing and the loopback-only OpenClaw constraint. Inserts the v0.0.67 release notes section covering onboarding recovery, messaging reliability, OpenClaw agent workflows, and AI-agent documentation routing.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐇 A hop through the docs, a nibble of prose,
Resume reruns checks — that's how the onboard goes.
Discord skips per-account, the proxy's on top,
Agents delete with --force and then they stop.
v0.0.67 blooms in the notes — what a crop! 🌿

Suggested labels

integration: discord, area: messaging

🚥 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 is concise and clearly describes a real part of the changeset, though it emphasizes the release notes more than the broader docs refresh.
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.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/v0.0.67-refresh

---

_{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 changes update release notes and command/messaging documentation text, including descriptions of existing behavior, but do not modify runtime code, onboarding/session state transitions, sandbox lifecycle, credentials, network policy assets, inference routing, deployment, workflows, or real assistant user-flow tests.

Optional E2E

• None.

New E2E recommendations

• None.

[github-actions]

Vitest E2E Scenario Recommendation

Required Vitest E2E scenarios: None
Optional Vitest E2E scenarios: None

Workflow run

Full Vitest E2E advisor summary

Vitest E2E Scenario Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required Vitest E2E scenarios

• None. Docs-only changes; no Vitest E2E scenario behavior is affected.

Optional Vitest E2E scenarios

• None.

Relevant changed files

• None.

[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
Since last review: 0 prior items resolved · 0 still apply · 0 new items found

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.