Skip to content

docs: add v0.0.97 changelog - #7768

Merged
cv merged 1 commit into
mainfrom
codex/release-prep-v0.0.97
Jul 28, 2026
Merged

docs: add v0.0.97 changelog#7768
cv merged 1 commit into
mainfrom
codex/release-prep-v0.0.97

Conversation

@cjagwani

@cjagwani cjagwani commented Jul 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

Add the canonical dated changelog entry for NemoClaw v0.0.97 before the release plan captures origin/main.
The entry groups the user-visible and maintainer-facing changes since v0.0.96 while preserving the Deferred dual-Station status, experimental runtime-identity boundary, and pending physical IGX validation.

Changes

  • Add docs/changelog/2026-07-28.mdx with the parser-safe MDX SPDX comment and exact ## v0.0.97 heading.
  • Summarize the 43 merged PRs in the release range, omitting internal-only changes from the public entry and linking each grouped change to its most specific published documentation.
  • Keep the experimental Okta reference explicitly opt-in and outside normal onboarding, keep the two-Station path Deferred, and state that physical IGX Orin validation remains pending.

Source summary

  • #7440, #7443, and #7445 -> docs/changelog/2026-07-28.mdx: Document read-only host readiness reports and fail-closed platform qualification.
  • #7030 -> docs/changelog/2026-07-28.mdx: Document the Deferred trusted two-Station vLLM evaluation.
  • #7265 -> docs/changelog/2026-07-28.mdx: Document the bounded experimental direct-runner Okta runtime-identity reference.
  • #7711 and #7648 -> docs/changelog/2026-07-28.mdx: Document compatible-endpoint reasoning effort and retired NVIDIA Build model paths.
  • #7746, #7763, and #7681 -> docs/changelog/2026-07-28.mdx: Document safe compatible-provider creation, replacement refusal, and narrow OpenShell bridge URL handling.
  • #7641, #7690, #7631, and #7710 -> docs/changelog/2026-07-28.mdx: Document paused-container recovery, recreation journaling, pre-mutation uninstall checks, and source-checkout OpenShell selection.
  • #7624 and #7762 -> docs/changelog/2026-07-28.mdx: Document Jetson release diagnostics and bounded render-device group propagation.
  • #7639, #7760, #7721, and #7761 -> docs/changelog/2026-07-28.mdx: Document Telegram, MCP media-type, Hermes image-mode, and locked-restart fixes.
  • #7653 and #7680 -> docs/changelog/2026-07-28.mdx: Document Deep Agents policy tasks and the bounded Claude Code OAuth path.
  • #7679 -> docs/changelog/2026-07-28.mdx: Document the checksum-bound libssh2 and Python HTMLParser backports.
  • #7655, #7651, #7664, #7666, #7670, #7719, and #7741 -> docs/changelog/2026-07-28.mdx: Document exact candidate E2E evidence, Launchable selection, diagnostic consolidation, and trusted WSL validation.

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: test/changelog-docs.test.ts validates the dated changelog contract, MDX header, heading uniqueness, and release-entry structure.
  • Tests not applicable — justification:
  • 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:

Documentation Writer Review

  • Documentation writer subagent reviewed the completed changes
  • Result: docs-updated
  • Evidence: The committed docs/changelog/2026-07-28.mdx blob exactly matches the reviewed file. Completeness, factual accuracy, link shape, parser-safe MDX header, one-sentence-per-line style, .docs-skip compliance, and bounded product claims passed.
  • Agent: Codex Desktop documentation writer subagent

DGX Station Hardware Evidence

  • Tested on DGX Station
  • Tested commit: Not applicable; this PR changes only the dated changelog.
  • Station profile/scenario: Not applicable.
  • Result: Not applicable.
  • Supporting evidence: Not applicable.

Verification

  • PR description includes a Signed-off-by: line 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 — npx vitest run test/changelog-docs.test.ts passed 6/6.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — not applicable to this doc-only release entry.
  • 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) — completed with 0 errors and 2 pre-existing Fern warnings.
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only) — native changelog entries use the required parser-safe MDX SPDX comment and intentionally have no frontmatter.

Signed-off-by: Charan Jagwani cjagwani@nvidia.com

Summary by CodeRabbit

  • New Features
    • Added improved host readiness reporting and Jetson onboarding guidance.
    • Added controls for reasoning effort with compatible endpoints and enhanced managed MCP discovery.
    • Improved Deep Agents task publication and preset support.
  • Bug Fixes
    • Hardened provider switching, sandbox recovery, uninstall behavior, and Telegram connectivity.
    • Improved container image integrity checks, media-type handling, and checksum validation.
    • Enhanced vLLM evaluation behavior and release diagnostics.
  • Documentation
    • Added the NemoClaw v0.0.97 changelog.

@cjagwani cjagwani added area: docs Documentation, examples, guides, or docs build v0.0.97 Release target labels Jul 28, 2026
@cjagwani cjagwani self-assigned this Jul 28, 2026
@coderabbitai

coderabbitai Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Adds the v0.0.97 changelog document, including licensing metadata and release notes covering host readiness, providers, recovery, integrations, images, onboarding, and validation behavior.

Changes

Release notes

Layer / File(s) Summary
v0.0.97 release documentation
docs/changelog/2026-07-28.mdx
Adds the SPDX header and release notes for NemoClaw v0.0.97 across the listed product areas.

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

Suggested labels: area: docs, v0.0.98

Suggested reviewers: aasthajh, afourniernv, ahunnargikar-nvidia

🚥 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 concisely describes the main change: adding the v0.0.97 changelog entry.
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 codex/release-prep-v0.0.97

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

@github-actions

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 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/changelog/2026-07-28.mdx`:
- Line 23: Update the changelog entry to hyphenate “OpenClaw-compatible” when
describing the endpoints, leaving the remainder of the sentence unchanged.
- Line 43: Update the changelog entry describing the claude-code preset so the
literal HTTP methods and endpoint path are individually formatted as inline
code, while preserving the existing wording and access scope.
🪄 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: d3358473-802e-4ef6-b480-e86e49fa7169

📥 Commits

Reviewing files that changed from the base of the PR and between 125ca30 and da6aa27.

📒 Files selected for processing (1)
  • docs/changelog/2026-07-28.mdx

The runner validates the complete profile and DNS destinations before mutation, keeps refresh material out of plans and command arguments, records resource ownership as it applies changes, and uses those receipts for compensation and rollback.
The shipped blueprint and normal onboarding do not enable this component, custom Okta domains are outside the reviewed policy, and this release does not add Entra, OBO, OAuth bootstrap, production middleware, or real-tenant certification.
For more information, refer to [Architecture Details](/user-guide/openclaw/reference/architecture).
- OpenClaw compatible endpoints can now set `NEMOCLAW_REASONING_EFFORT` or pass `inference set --reasoning-effort` with `low`, `medium`, `high`, or `default` on `openai-completions` routes.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Hyphenate the compound adjective.

Use OpenClaw-compatible endpoints; this matches the reported LanguageTool finding.

🧰 Tools
🪛 LanguageTool

[grammar] ~23-~23: Use a hyphen to join words.
Context: ...claw/reference/architecture). - OpenClaw compatible endpoints can now set `NEMOCL...

(QB_NEW_EN_HYPHEN)

🤖 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/changelog/2026-07-28.mdx` at line 23, Update the changelog entry to
hyphenate “OpenClaw-compatible” when describing the endpoints, leaving the
remainder of the sentence unchanged.

Source: Linters/SAST tools

Hermes image assembly normalizes executable modes before metadata validation, and locked restart integrity accepts the generated v1 managed MCP state record while retaining fail-closed hashing and failed-reload rollback.
For more information, refer to [Choose Messaging Channels](/user-guide/openclaw/manage-sandboxes/messaging-channels/choose-messaging-channels), [Manage MCP Servers with OpenClaw](/user-guide/openclaw/manage-sandboxes/mcp-servers/manage-mcp-servers), [Manage MCP Servers with Hermes](/user-guide/hermes/manage-sandboxes/mcp-servers/manage-mcp-servers), and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
- Deep Agents now publishes the bounded approval, baseline, preset, custom-preset, and live-policy tasks that apply to its maintained runtime.
The `claude-code` preset permits browser login only through `GET` and `POST` on `platform.claude.com/v1/oauth/**`, without widening unrelated Anthropic or telemetry access.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Format the endpoint details as code.

The documentation rules require literal methods and paths to use code formatting.

Proposed fix
-  The `claude-code` preset permits browser login only through GET and POST on platform.claude.com/v1/oauth/**, without widening unrelated Anthropic or telemetry access.
+  The `claude-code` preset permits browser login only through `GET` and `POST` on `platform.claude.com/v1/oauth/**`, without widening unrelated Anthropic or telemetry access.

As per coding guidelines, use code formatting for literal values and paths.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The `claude-code` preset permits browser login only through `GET` and `POST` on `platform.claude.com/v1/oauth/**`, without widening unrelated Anthropic or telemetry access.
The `claude-code` preset permits browser login only through `GET` and `POST` on `platform.claude.com/v1/oauth/**`, without widening unrelated Anthropic or telemetry access.
🤖 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/changelog/2026-07-28.mdx` at line 43, Update the changelog entry
describing the claude-code preset so the literal HTTP methods and endpoint path
are individually formatted as inline code, while preserving the existing wording
and access scope.

Source: Coding guidelines

@cv
cv merged commit f08322d into main Jul 28, 2026
64 of 65 checks passed
@cv
cv deleted the codex/release-prep-v0.0.97 branch July 28, 2026 23:34
@github-actions

github-actions Bot commented Jul 28, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: Review the warnings below.
Findings: 0 blockers · 1 warning · 0 suggestions

Model lanes

  • GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 1 warning · 0 suggestions
  • Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
  • Model comparison: normalized findings differ; normalized E2E selections match; Nemotron reported the same number of blockers, 1 fewer warning, the same number of suggestions.

Nemotron output stays in workflow artifacts and does not change the assessment above.

E2E guidance

Advisory only. E2E / PR Gate selects and runs jobs independently.

Recommended E2E: None

1 warning · 0 suggestions

Warnings

Warnings do not block.

PRA-1 Warning — Align recovery guidance with automatic paused-container recovery

  • Location: docs/changelog/2026-07-28.mdx:31
  • Category: docs
  • Problem: The release entry says Docker-driver recovery unpauses a paused original container before it reports recovery. The supported recovery guide still directs an operator to run the printed `docker unpause` guidance when a container is paused.
  • Impact: Operators can follow conflicting recovery procedures and unnecessarily perform a manual container operation after upgrading.
  • Recommendation: Update the recovery guide to describe the automatic unpause behavior, or narrow the release entry if paused containers still require manual unpause.
  • Verification: Compare the paused-container instructions in `docs/manage-sandboxes/recover-rebuild-sandboxes.mdx` with the release-entry claim.
  • Test coverage: A documentation-link or content test should verify that paused-container recovery guidance matches the supported automatic recovery behavior.
  • Evidence: `docs/changelog/2026-07-28.mdx:31` states that Docker-driver recovery unpauses a paused original container before reporting recovery. `docs/manage-sandboxes/recover-rebuild-sandboxes.mdx:23` directs operators of paused containers to follow printed `docker unpause` guidance.

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

cjagwani added a commit that referenced this pull request Jul 29, 2026
<!-- markdownlint-disable MD041 -->
## Summary

Address the valid compound-adjective finding published by CodeRabbit
after the v0.0.97 changelog PR merged.
This keeps the canonical release entry polished before the release plan
captures `origin/main`.

## Changes

- Change “OpenClaw compatible endpoints” to “OpenClaw-compatible
endpoints” in `docs/changelog/2026-07-28.mdx`.
- Preserve the release entry's behavior, links, and bounded product
claims unchanged.

### Source summary

- [#7768](#7768) ->
`docs/changelog/2026-07-28.mdx`: Apply the valid post-merge CodeRabbit
wording correction.

## Type of Change

- [ ] Code change (feature, bug fix, or refactor)
- [ ] Code change with doc updates
- [x] Doc only (prose changes, no code sample modifications)
- [ ] Doc only (includes code sample changes)

## Quality Gates

- [ ] Tests added or updated for changed behavior
- [x] Existing tests cover changed behavior — justification:
`test/changelog-docs.test.ts` validates the dated changelog contract,
MDX header, heading uniqueness, and release-entry structure.
- [ ] Tests not applicable — justification:
- [x] 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:

## Documentation Writer Review

- [x] Documentation writer subagent reviewed the completed changes
- Result: `docs-review: pass`
- Evidence: Reviewed the committed changelog blob
`9538ab72f400173d7f8ea6c06549485b8eead892` at exact HEAD
`71cb065fcdacb392cc0ffccdbca14fe3fa0432f9`. The diff from merged
`origin/main` is only “OpenClaw compatible” to “OpenClaw-compatible”;
completeness, accuracy, links, parser-safe MDX, `.docs-skip` compliance,
style, and bounded product claims remain valid.
- Agent: Codex Desktop documentation writer subagent
<!-- docs-review-head-sha: 71cb065 -->
<!-- docs-review-agents-blob-sha: be20a09 -->

## DGX Station Hardware Evidence

- [ ] Tested on DGX Station
- Tested commit: Not applicable; this PR changes only one changelog
phrase.
- Station profile/scenario: Not applicable.
- Result: Not applicable.
- Supporting evidence: Not applicable.

## Verification

- [x] PR description includes a `Signed-off-by:` line and every commit
appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run check:diff` passed when hooks were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — `npx vitest run
test/changelog-docs.test.ts` passed 6/6.
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — not applicable to this one-line prose
correction.
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only) —
completed with 0 errors and 2 pre-existing Fern warnings.
- [x] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)
— not applicable; this corrects an existing native changelog entry.

---
Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Documentation**
* Clarified the wording of the v0.0.97 changelog entry for
OpenClaw-compatible endpoints and reasoning-effort configuration.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Charan Jagwani <cjagwani@nvidia.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: docs Documentation, examples, guides, or docs build v0.0.97 Release target

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants