docs(changelog): follow up v0.0.106 release entry

[jyaunches]

Summary

This PR updates the August 10, 2026 v0.0.106 release entry with gateway readiness fixes that merged after PR #8756.
PRs #8765, #8767, and #8768 remain outside this entry because they are open and do not carry the v0.0.106 release label.

Changes

• Document acceptance of OpenShell v0.0.101 Server: endpoint output and target-bound process tags when trusted listener evidence matches the configured gateway.
• Document preservation of selected-gateway stale state so onboarding can reconcile a registered gateway when a gateway-scoped OpenShell status check cannot connect.
• Record evidence-backed exclusions for internal image, startup, qualification, proxy-environment, CI, and test-harness changes in PRs fix(images): replay MCP discovery permissions #8754, fix(sandbox): reject managed startup env wrapper without nemoclaw-start terminator #8609, fix(e2e): repair protected managed-image qualification #8762, fix(sandbox): reconcile readonly gateway-token trust anchor on source #8432, fix(e2e): extend Docker Hub login retries #8766, and refactor(sandbox): give rebuild test harnesses one shared core #8581.
• Exclude PRs fix(sandbox): wait through managed container restart transitions #8765, fix(sandbox): preserve Shields parent ownership on restart #8767, and fix(installer): preserve managed storage remediation #8768 because their changes are absent from main and the PRs do not carry the v0.0.106 release label.
  The release entry must be updated after any of those PRs merges for v0.0.106.

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 dated changelog SPDX placement, version headings, forbidden terms, and link form.
• 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: docs/changelog/2026-08-10.mdx; an independent Codex Desktop subagent reviewed the writing rules and documentation style, terminology, structure, voice, code-sample presentation, links, source and test accuracy, release meaning, product scope, and evidence-backed exclusions at commit 190bf882c.
• Agent: Codex Desktop

DGX Station Hardware Evidence

• Tested on DGX Station
• Tested commit: Not applicable; scripts/prepare-dgx-station-host.sh is unchanged.
• 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 validate:pr passed after refreshing origin/main 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 tests.
• 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 a documentation-only release-entry update.
• 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) — result: passed with 0 errors and 2 existing warnings.
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only) — no page was added.

---

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

Summary by CodeRabbit

• Bug Fixes
  • Improved gateway readiness detection for OpenShell v0.0.101 endpoint output.
  • Process tags are now accepted only when they match trusted listener information for the configured gateway.
  • Preserved stale gateway status during connection failures to support accurate onboarding reconciliation.

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[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: cc8a8349-3161-4e77-bb08-0bc2c49a903b

📥 Commits

Reviewing files that changed from the base of the PR and between 4298c03 and 66d93e1.

📒 Files selected for processing (1)

• docs/changelog/2026-08-10.mdx

---

📝 Walkthrough

Walkthrough

The changelog records OpenShell v0.0.101 gateway readiness validation and stale gateway state preservation during disconnected status checks.

Changes

Gateway readiness documentation

Layer / File(s)	Summary
Document gateway readiness behavior docs/changelog/2026-08-10.mdx	The changelog documents trusted endpoint and process-tag evidence checks and preservation of stale gateway state for onboarding reconciliation.

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

Possibly related PRs

• NVIDIA/NemoClaw#8756: Refines the same changelog entry for OpenShell readiness changes.
• NVIDIA/NemoClaw#8757: Introduces related trusted-gateway identity handling and listener validation.

Suggested labels: area: docs, chore, v0.0.106

Suggested reviewers: sandl99

🚥 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 identifies the changelog follow-up for the v0.0.106 release entry, which matches the documentation change.
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/docs-v0.0.106-follow-up

---

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

[github-actions]

🌿 Preview your docs: https://nvidia-preview-pr-8770.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 · medium 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 terminology decisions differ; normalized E2E selections match; severity counts match.

4 terminology differences from the second opinion

Advisory only. These are normalized differences from the primary terminology receipt.

• trusted listener evidence at docs/changelog/2026-08-10.mdx:14: primary classified it as justified; the second opinion classified it as define.
• registered gateway at docs/changelog/2026-08-10.mdx:15: selected only by the second-opinion lane as established.
• stale state at docs/changelog/2026-08-10.mdx:15: selected only by the second-opinion lane as established.
• gateway-scoped at docs/changelog/2026-08-10.mdx:15: selected only by the second-opinion lane as established.

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

3 semantic terminology decisions

Terminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.

• define — target-bound process tags at docs/changelog/2026-08-10.mdx:14: Define the term in the owning readiness documentation or use established repository terminology when one exists.
• justified — trusted listener evidence at docs/changelog/2026-08-10.mdx:14: Retain the modifier because it distinguishes accepted listener verification from unverified endpoint output.
• justified — gateway-scoped OpenShell status check at docs/changelog/2026-08-10.mdx:15: Retain the modifier because it identifies the gateway that owns the status query.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite against this exact revision.

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.