docs: polish v0.0.97 changelog wording

[cjagwani]

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

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

• 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 one-line prose correction.
• 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) — not applicable; this corrects an existing native changelog entry.

---

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

Summary by CodeRabbit

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

[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: 5363e410-72a2-4ba3-bc88-3ac2515882fe

📥 Commits

Reviewing files that changed from the base of the PR and between f08322d and 71cb065.

📒 Files selected for processing (1)

• docs/changelog/2026-07-28.mdx

---

📝 Walkthrough

Walkthrough

The v0.0.97 changelog changes “OpenClaw compatible” to “OpenClaw-compatible” in the reasoning-effort setting entry. No behavior, options, or public declarations changed.

Changes

Changelog wording

Layer / File(s)	Summary
Reasoning-effort changelog wording docs/changelog/2026-07-28.mdx	Hyphenates “OpenClaw-compatible” while preserving the documented commands, environment variable, and allowed values.

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

Possibly related PRs

• NVIDIA/NemoClaw#7768: Adds the changelog document containing the wording updated here.

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 is concise and accurately reflects the documentation-only changelog wording polish in v0.0.97.
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-review-followup

---

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

[github-actions]

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

[github-actions]

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions

Model lanes

• GPT-5.6 Terra (primary): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
• Nemotron 3 Ultra (second opinion): Completed · high confidence · 0 blockers · 0 warnings · 0 suggestions
• Model comparison: normalized findings match; normalized E2E selections match; severity counts match.

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

Workflow run details

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