docs: prepare v0.0.79 release notes

[jyaunches]

Summary

Adds the pre-tag v0.0.79 release notes entry to docs/about/release-notes.mdx so the release plan can be generated after docs merge.
The entry summarizes the merged v0.0.79 release train across inference, diagnostics, runtime hardening, policies, onboarding recovery, and release validation.

Changes

• Added the v0.0.79 release notes section with linked follow-up documentation for OpenRouter onboarding, managed vLLM changes, completion and logging, Deep Agents runtime limits, policy updates, onboarding recovery, and release validation.
• Source summary:
  • feat(inference): add OpenRouter onboarding support #6461 -> docs/about/release-notes.mdx: Documents OpenRouter onboarding support and links to inference/provider references.
  • feat(cli): add shell completion command for bash, zsh, and fish #6271 and feat(cli): add structured logging with --debug and NEMOCLAW_LOG_LEVEL #6272 -> docs/about/release-notes.mdx: Documents shell completion and structured logging highlights.
  • feat(status): warn when the gateway route drifts from the sandbox's recorded route #6465, fix(installer): report orphaned sandboxes honestly across uninstall and reinstall #6539, fix(cli): recommend and run 'openshell gateway remove' on all platforms (#6569) #6570, and fix(install): use my-assistant for DGX Spark express install sandbox name (#6525) #6528 -> docs/about/release-notes.mdx: Documents status route-drift, orphaned sandbox, gateway cleanup, and DGX Spark express-install diagnostics.
  • fix(inference): run managed vLLM Docker with argv #6523, fix(inference): serve Spark Qwen3.6 with qwen3_coder tool parser (#6457) #6551, fix(openclaw): bound managed inference compaction #6484, perf(onboard): calibrate provider validation timeouts #6488, perf(onboard): overlap gateway readiness probes #6324, and perf(onboard): use deadlines for gateway health waits #6542 -> docs/about/release-notes.mdx: Documents managed vLLM, Qwen3.6 tool parser, compaction, and timeout/readiness improvements.
  • fix(dcode): enforce sandbox process and file descriptor limits #6559, fix(dcode): allow plain OTLP endpoint URLs past the secret guard #6538, fix(runtime): keep proxy env POSIX-compatible #6560, fix(shields): support nested OpenShell PID namespaces #6568, fix(config): parse TOML dcode config in config get via sandbox tomllib #6552, fix(config): harden TOML config handling #6567, and fix(onboard): reconcile registered extra providers #6587 -> docs/about/release-notes.mdx: Documents runtime, credential, proxy, PID namespace, TOML, and provider-state hardening.
  • fix(policy): require github preset for git egress #6541, docs(network-policy): add Gmail policy preset and integration example #5415, docs(network-policy): document custom URL-based MCP server allowlist (#5322) #6246, fix(whatsapp): reconcile post-pair gateway restart without operator.admin #6496, and docs(overview): gate 'Messaging channels' to openclaw/hermes variants #6573 -> docs/about/release-notes.mdx: Documents GitHub policy, Gmail policy, MCP allowlist, WhatsApp, and messaging-variant updates.
  • refactor(onboard): make FSM resume recovery a single explicit path (#6227) #6253, fix(onboard): preserve pending route reservation across resume #6572, refactor(onboard): extract sandbox create-failure reporting and create step into modules #6444, fix(onboard): avoid forcing plain BuildKit progress #6536, and test(onboard): cover null-name resume sessions (Fixes #5783) #5860 -> docs/about/release-notes.mdx: Documents onboarding resume and create-step recovery improvements.
  • docs: define extension taxonomy and SDK readiness #6508, docs(get-started): streamline quickstarts #6527, docs: clarify legacy k3s sandbox resources #5506, fix(docs): preserve AgentOnly list spacing #6588, feat(ci): add deterministic PR risk plans #6446, feat(ci): add post-merge E2E risk shadow #6447, ci(e2e): guard queued Jetson dispatches #6582, test(openclaw): cover TUI idle timeout regression #6296, refactor(e2e): add bounded polling primitives for live readiness checks #6367, test(e2e): cover v0.0.55 gateway upgrades #6397, and test(core): cover wait utility behavior #6505 -> docs/about/release-notes.mdx: Documents docs, release-risk, and E2E validation updates.

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: Release-note prose only.
• 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 not applicable, release-note prose only.
• 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)

Docs validation note: npm run docs:check-agent-variants && npm run docs:check-routes && git diff --check passed. Full npm run docs is currently blocked before Fern validation because the pinned fern-api@5.65.2 package is unavailable from npm (ETARGET No matching version found).

---

Signed-off-by: Julie Yaunches jyaunches@nvidia.com

Summary by CodeRabbit

• Documentation
  • Added release notes for v0.0.79 with a new summary of recent improvements, including onboarding and inference options, operator/CLI diagnostics, sandbox recovery hardening, runtime limits, network policy behavior, and release validation updates.
  • Added updated references and links for the latest release.

[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: d5dcb1da-4ec7-4055-9de2-9b7cac0269a8

📥 Commits

Reviewing files that changed from the base of the PR and between ac9e1bc and 52c9b4f.

📒 Files selected for processing (1)

• docs/about/release-notes.mdx

---

📝 Walkthrough

Walkthrough

Added a new v0.0.79 release notes section to docs/about/release-notes.mdx, positioned above the existing v0.0.78 content, summarizing updates to onboarding, diagnostics, sandbox recovery, runtime limits, network policy, and documentation.

Changes

Release Notes Update

Layer / File(s)	Summary
Add v0.0.79 release notes section docs/about/release-notes.mdx	Inserted a heading, overview paragraph, and bullet points covering onboarding/inference options, operator/CLI diagnostics, sandbox recovery hardening, runtime limits/policy boundaries, network policy/messaging behavior, and documentation/release validation determinism ahead of the existing v0.0.78 section.

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

🚥 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 summarizes the docs-only change: preparing the v0.0.79 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.79-release-prep

---

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

[github-actions]

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

[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 release notes change; it cannot affect runtime behavior or real user flows, and the deterministic risk plan lists no required E2E jobs.

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 release notes change; it does not affect E2E target registry, workflow wiring, live support, fixtures, or runtime behavior.

Optional E2E targets

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

[github-actions]

PR Review Advisor (Nemotron Ultra) — 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.