Skip to content

docs: add v0.0.96 release follow-up - #7649

Merged
cv merged 3 commits into
mainfrom
codex/docs-v0.0.96-follow-up-2
Jul 27, 2026
Merged

docs: add v0.0.96 release follow-up#7649
cv merged 3 commits into
mainfrom
codex/docs-v0.0.96-follow-up-2

Conversation

@cv

@cv cv commented Jul 27, 2026

Copy link
Copy Markdown
Collaborator

Summary

docs/changelog/2026-07-25.mdx now includes the user-facing fixes that merged after #7607 and before the v0.0.96 tag.
The follow-up covers safer bulk backup and clone restore behavior, policy and inference repairs, cleaner onboarding diagnostics, and OpenClaw base-image validation while leaving test-only and maintainer-internal merges out of the release entry.

Changes

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: This PR changes release-entry prose only. The changelog contract test and Fern validation cover the dated entry, published routes, and rendering requirements.
  • 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: At exact PR head 29316da26, a Codex Desktop documentation writer reviewed docs/changelog/2026-07-25.mdx against AGENTS.md, WRITING.md, and docs/CONTRIBUTING.md. The review confirmed that the full entry accurately reflects the merged user-visible behavior, retains fix(images): support Docker Engine gateway builds #7622's existing wording, appropriately excludes internal and test-only PRs, and uses conforming terminology, structure, links, and release classification. It also confirmed that the review follow-ups use active third-person release-entry voice, name the actor and recovery requirement directly, and accurately preserve the trusted-backup, cached-release refresh, and local-build fallback constraints. The changelog test passed 6/6, and the docs build completed with 0 errors and 2 pre-existing hidden warnings.
  • Agent: Codex Desktop

DGX Station Hardware Evidence

  • Tested on DGX Station
  • Tested commit:
  • Station profile/scenario:
  • Result:
  • Supporting evidence:

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 — command/result or justification: npx vitest run test/changelog-docs.test.ts passed 6/6 tests after the final review fix.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result: Not applicable to this prose-only changelog change.
  • 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) — exited 0 with 0 errors and 2 pre-existing hidden warnings after the final review fix.
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Carlos Villela cvillela@nvidia.com

Summary by CodeRabbit

  • Documentation
    • Expanded the changelog to clarify persistent policy exclude/policy restore behavior across rebuilds and snapshot restores, including reporting on removed endpoints and exclusion consistency.
    • Updated claude-code preset guidance to allow the npm-installed OpenShell launcher path while maintaining endpoint/HTTP method scope.
    • Documented hardened handling for invalid gateway-management declarations, improved gateway/agent-version diagnostics scope, and clarified onboarding/restore credential and reasoning precedence.
    • Tightened bulk backup/restore guidance (safety windows, approval limits, and failure recovery) and refined OpenClaw base selection to avoid incompatible cached releases and :latest fallback.

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@cv cv added area: docs Documentation, examples, guides, or docs build v0.0.96 labels Jul 27, 2026
@cv cv self-assigned this Jul 27, 2026
@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

The v0.0.96 changelog documents policy exclusion persistence, diagnostic and error handling, onboarding and recovery flows, backup/restore safeguards, and OpenClaw base-image selection rules.

Changes

v0.0.96 operational behavior

Layer / File(s) Summary
Policy and diagnostic behavior
docs/changelog/2026-07-25.mdx
Documents persistent exact-entry policy exclusions, constrained Claude Code launcher access, sanitized gateway-management errors, gateway-scoped probes, and failed-onboarding reservation visibility.
Onboarding, backup, and recovery contracts
docs/changelog/2026-07-25.mdx
Documents Ollama and Hermes onboarding behavior, per-sandbox backup-all processing, lockdown failure recovery, snapshot approval limits, and corrupt Shields-state rejection.
OpenClaw base-image selection
docs/changelog/2026-07-25.mdx
Documents immutable-inventory validation, one-time cached-release refresh behavior, and local-build replacement instead of :latest fallback.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

  • NVIDIA/NemoClaw#7564: Updates the same v0.0.96 changelog entry with overlapping operator-facing behavior documentation.

Suggested reviewers: prekshivyas

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
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.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly summarizes the main change: a documentation-only v0.0.96 release follow-up entry.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/docs-v0.0.96-follow-up-2

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.

🧹 Nitpick comments (1)
docs/changelog/2026-07-25.mdx (1)

62-62: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use active voice in the recovery and image-selection clauses.

Rewrite the passive constructions so the product or operator is the subject, for example: “NemoClaw rejects corrupt persisted Shields state…” and “onboarding refreshes an incompatible cached exact release once, then uses a current local build…”

As per coding guidelines, MDX documentation should use active voice and direct language.

Also applies to: 72-72

🤖 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-25.mdx` at line 62, Rewrite the recovery and
image-selection clauses in the changelog entry using active voice and direct
language, making NemoClaw or the operator the subject; update both the
corrupt-state statement and the incompatible cached-release/onboarding statement
while preserving their existing behavior and conditions.

Sources: Coding guidelines, Learnings

🤖 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/changelog/2026-07-25.mdx`:
- Line 62: Rewrite the recovery and image-selection clauses in the changelog
entry using active voice and direct language, making NemoClaw or the operator
the subject; update both the corrupt-state statement and the incompatible
cached-release/onboarding statement while preserving their existing behavior and
conditions.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: af73db3e-174a-48b7-a7e7-639a5feaf3de

📥 Commits

Reviewing files that changed from the base of the PR and between d0a95dc and 7b40648.

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

Signed-off-by: Carlos Villela <cvillela@nvidia.com>

@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: 1

🤖 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-25.mdx`:
- Around line 62-63: Rephrase the recovery sentence in the NemoClaw changelog
entry using third-person historical product-behavior wording, such as stating
that operators must restore the state from a trusted host backup. Preserve the
existing warning that “shields up” and an ordinary rebuild do not replace
corrupt persisted state.
🪄 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: f3788f36-4b81-4325-bb8c-9b343c626426

📥 Commits

Reviewing files that changed from the base of the PR and between 7b40648 and 49ab444.

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

Comment thread docs/changelog/2026-07-25.mdx Outdated
@github-actions

github-actions Bot commented Jul 27, 2026

Copy link
Copy Markdown
Contributor

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 differ; 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

6 optional E2E recommendations
  • state-backup-restore
  • shields-config
  • onboard-resume
  • gateway-guard-recovery
  • inference-routing
  • mcp-bridge

Workflow run details

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

Signed-off-by: Carlos Villela <cvillela@nvidia.com>
@cv
cv merged commit 3d88c04 into main Jul 27, 2026
88 of 92 checks passed
@cv
cv deleted the codex/docs-v0.0.96-follow-up-2 branch July 27, 2026 18:14
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant