docs(changelog): add v0.0.110 release entry (#9380)

<!-- markdownlint-disable MD041 -->
## Summary

Add the canonical dated changelog entry required before planning the
v0.0.110 release. The entry summarizes user-facing changes merged since
v0.0.109 and links each change to its published documentation route and
source PR.

## Changes

- Add `docs/changelog/2026-08-17.mdx` with the exact `## v0.0.110`
release heading.
- Cover managed local inference, endpoint validation, onboarding and
recovery, explicit experimental Portable OpenClaw, messaging and policy
cleanup, backup and security hardening, and release qualification.
- Preserve the documentation skip list and the current supported-agent
matrix; test-only refactors, dormant activation work, and Pi-only
changes are intentionally excluded.

### Source-to-doc mapping

- #8711 -> `docs/changelog/2026-08-17.mdx`: Add the Muse Glimmer
llama.cpp profile.
- #9099 -> `docs/changelog/2026-08-17.mdx`: Update the Muse Glimmer vLLM
runtime.
- #9319 -> `docs/changelog/2026-08-17.mdx`: Select the provider required
by an explicit serving profile.
- #9311 -> `docs/changelog/2026-08-17.mdx`: Report probe-image pull
failures separately.
- #9345 -> `docs/changelog/2026-08-17.mdx`: Reuse mirrored Windows
Ollama.
- #9284 -> `docs/changelog/2026-08-17.mdx`: Complete the required Ollama
upgrade.
- #9320 -> `docs/changelog/2026-08-17.mdx`: Reject unsafe custom
endpoint URLs before mutation.
- #9119 -> `docs/changelog/2026-08-17.mdx`: Reject unsupported custom
endpoint URL components.
- #9236 -> `docs/changelog/2026-08-17.mdx`: Require native Anthropic
tool-use evidence.
- #9347 -> `docs/changelog/2026-08-17.mdx`: Distinguish Gemini runtime
404 diagnostics.
- #9307 -> `docs/changelog/2026-08-17.mdx`: Preserve the recorded API
family when only the model drifts.
- #9233 -> `docs/changelog/2026-08-17.mdx`: Fail incomplete Hermes route
synchronization.
- #9185 -> `docs/changelog/2026-08-17.mdx`: Serialize Model Router
lifecycle work across gateways.
- #9112 -> `docs/changelog/2026-08-17.mdx`: Stop Model Router after the
last routed sandbox is destroyed.
- #9229 -> `docs/changelog/2026-08-17.mdx`: Verify fresh sandbox
execution readiness.
- #9299 -> `docs/changelog/2026-08-17.mdx`: Verify a separate agent API
host forward before reporting ready.
- #9318 -> `docs/changelog/2026-08-17.mdx`: Honor explicit sandbox
recreation.
- #9325 -> `docs/changelog/2026-08-17.mdx`: Measure readiness reuse
windows from collection completion.
- #9352 -> `docs/changelog/2026-08-17.mdx`: Guide users away from the
deprecated global start command.
- #9370 -> `docs/changelog/2026-08-17.mdx`: Persist managed OpenClaw
agent identity.
- #9366 -> `docs/changelog/2026-08-17.mdx`: Pass messaging dependencies
during reused onboarding.
- #9321 -> `docs/changelog/2026-08-17.mdx`: Detect proxied connect
sessions.
- #9285 -> `docs/changelog/2026-08-17.mdx`: Run probe-only recovery when
absent authority cannot be created.
- #9282 -> `docs/changelog/2026-08-17.mdx`: Complete probe-only recovery
without platform evidence.
- #8920 -> `docs/changelog/2026-08-17.mdx`: Preserve legacy gateway
identity.
- #9198 -> `docs/changelog/2026-08-17.mdx`: Report sandbox config-read
failures.
- #9201 -> `docs/changelog/2026-08-17.mdx`: Remove only the exact Docker
orphan on destroy.
- #9176 -> `docs/changelog/2026-08-17.mdx`: Use rootless Podman for
Portable lifecycle operations.
- #9197 -> `docs/changelog/2026-08-17.mdx`: Preflight Portable CPU
delegation.
- #9289 -> `docs/changelog/2026-08-17.mdx`: Narrow Portable policy
defaults.
- #9270 -> `docs/changelog/2026-08-17.mdx`: Preserve Portable model
intent.
- #9339 -> `docs/changelog/2026-08-17.mdx`: Reconcile timed-out Portable
stop state.
- #9209 -> `docs/changelog/2026-08-17.mdx`: Clean receipt-owned Portable
Podman resources.
- #9186 -> `docs/changelog/2026-08-17.mdx`: Separate Podman activation
readiness.
- #9376 -> `docs/changelog/2026-08-17.mdx`: Settle Portable OpenClaw
pairing before readiness.
- #9296 -> `docs/changelog/2026-08-17.mdx`: Retire messaging channel
presets the host no longer configures.
- #9327 -> `docs/changelog/2026-08-17.mdx`: Drop retired channels from
reused messaging selections.
- #9306 -> `docs/changelog/2026-08-17.mdx`: Remove gateway-enforced
presets without a local record.
- #9248 -> `docs/changelog/2026-08-17.mdx`: Activate Google Chat pairing
approval.
- #9374 -> `docs/changelog/2026-08-17.mdx`: Accept schema-owned
messaging plan fields.
- #9317 -> `docs/changelog/2026-08-17.mdx`: Accept safe hard-linked
package files during backup.
- #9288 -> `docs/changelog/2026-08-17.mdx`: Remove managed CLI shims
with destroyed user data.
- #9239 -> `docs/changelog/2026-08-17.mdx`: Read voice credentials from
fixed descriptors.
- #9269 -> `docs/changelog/2026-08-17.mdx`: Accept bounded native
OpenClaw device modes.
- #9371 -> `docs/changelog/2026-08-17.mdx`: Isolate OpenClaw
startup-guard output.
- #9351 -> `docs/changelog/2026-08-17.mdx`: Restore staging Launchable
validation.
- #9350 -> `docs/changelog/2026-08-17.mdx`: Retry transient
collaborator-permission reads.
- #9353 -> `docs/changelog/2026-08-17.mdx`: Retry transient
exact-artifact downloads.
- #9226 -> `docs/changelog/2026-08-17.mdx`: Add bounded Brev readiness
diagnostics.
- #9237 -> `docs/changelog/2026-08-17.mdx`: Report same-commit E2E
reliability.
- #9232 -> `docs/changelog/2026-08-17.mdx`: Execute native-runtime
qualification.
- #9275 -> `docs/changelog/2026-08-17.mdx`: Define E2E selection and
retry guidance.
- #9234 -> `docs/changelog/2026-08-17.mdx`: Move documentation review
after merge.
- #9365 -> `docs/changelog/2026-08-17.mdx`: Mount documentation reviewer
inputs before startup.

## 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 release-entry
contract.
- [ ] Tests 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:

## DGX Station Hardware Evidence

- [ ] Tested on DGX Station
- Tested commit: Not applicable; documentation-only change.
- 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 validate:pr` passed after refreshing `origin/main` 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` (7 passed)
- [x] 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 one
prose-only changelog page; `npm run docs` passed the repository's strict
documentation gate.
- [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) — passed
with 0 errors and the 2 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)
— the SPDX header is present; dated changelog pages intentionally do not
use frontmatter.

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


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

## Summary by CodeRabbit

* **Documentation**
  * Added release notes for v0.0.110.
* Documented experimental managed llama.cpp and Portable OpenClaw
profiles.
* Covered inference validation, onboarding and recovery improvements,
rootless lifecycle handling, messaging and policy updates, backups,
credential handling, filesystem protections, and release qualification
updates.

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

Author: cjagwani

docs/changelog/2026-08-17.mdx

@@ -0,0 +1,55 @@
+{/*
+ * SPDX-FileCopyrightText: Copyright (c) 2026 NVIDIA CORPORATION & AFFILIATES. All rights reserved.
+ * SPDX-License-Identifier: Apache-2.0
+ */}
+
+## v0.0.110
+
+NemoClaw v0.0.110 adds an Experimental managed llama.cpp profile for Meta Muse Glimmer 30B on one DGX Spark and requires native tool-use evidence from custom Anthropic-compatible endpoints.
+It strengthens the explicit experimental Portable OpenClaw path with rootless Podman lifecycle authority, CPU-delegation preflight, and receipt-bound uninstall.
+It also improves onboarding recovery, local inference diagnostics, messaging and policy cleanup, backup and uninstall safety, and release qualification.
+
+- Managed llama.cpp onboarding now recommends the compatible Meta Muse Glimmer 30B profile on one DGX Spark while retaining NVIDIA Nemotron as a lower-priority choice.
+  Profile selection is deterministic, exact recipe selection remains available for automation, and typed recipe contracts constrain templates and reasoning settings.
+  The Experimental managed vLLM Muse Glimmer profile now uses its qualified pinned runtime, and `onboard --profile` selects the provider required by the requested serving profile instead of falling through to the provider menu.
+  Local inference setup also distinguishes a probe-image pull failure from a networking failure, reuses a positively identified Windows-host Ollama daemon under WSL mirrored networking, and completes a required Ollama upgrade before continuing.
+  For more information, refer to [Set Up llama.cpp](/user-guide/openclaw/inference/local-inference/set-up-llama-cpp), [Set Up vLLM](/user-guide/openclaw/inference/local-inference/set-up-vllm), and [Use Ollama](/user-guide/openclaw/inference/local-inference/set-up-ollama).
+  Related changes: [PR #8711](https://github.com/NVIDIA/NemoClaw/pull/8711), [PR #9099](https://github.com/NVIDIA/NemoClaw/pull/9099), [PR #9319](https://github.com/NVIDIA/NemoClaw/pull/9319), [PR #9311](https://github.com/NVIDIA/NemoClaw/pull/9311), [PR #9345](https://github.com/NVIDIA/NemoClaw/pull/9345), and [PR #9284](https://github.com/NVIDIA/NemoClaw/pull/9284).
+- Custom endpoint onboarding, `inference set`, and rebuild recovery now reject unsafe URL characters and unsupported URL components before network or state mutation.
+  OpenClaw onboarding for a custom Anthropic-compatible endpoint requires a native streaming `tool_use` block and matching stop reason instead of accepting JSON-shaped assistant text.
+  Google Gemini diagnostics distinguish a Chat Completions route `404` from native model-catalog validation, while sandbox status preserves the recorded API family when only the model drifts.
+  Hermes route changes fail when the in-sandbox configuration cannot synchronize, and Model Router setup and teardown serialize lifecycle work across the current user's gateways so destroy cannot stop a replacement router or overwrite a concurrent onboarding session.
+  For more information, refer to [Custom Endpoint Security](/user-guide/openclaw/inference/custom-endpoints/custom-endpoint-security), [Set Up an Anthropic-Compatible Endpoint](/user-guide/openclaw/inference/custom-endpoints/set-up-anthropic-compatible-endpoint), [Use Google Gemini](/user-guide/openclaw/inference/hosted-inference/use-google-gemini), [Verify the Inference Route](/user-guide/openclaw/inference/validate-inference/verify-inference-route), and [Set Up Model Router](/user-guide/openclaw/inference/hosted-inference/set-up-model-router).
+  Related changes: [PR #9320](https://github.com/NVIDIA/NemoClaw/pull/9320), [PR #9119](https://github.com/NVIDIA/NemoClaw/pull/9119), [PR #9236](https://github.com/NVIDIA/NemoClaw/pull/9236), [PR #9347](https://github.com/NVIDIA/NemoClaw/pull/9347), [PR #9307](https://github.com/NVIDIA/NemoClaw/pull/9307), [PR #9233](https://github.com/NVIDIA/NemoClaw/pull/9233), [PR #9185](https://github.com/NVIDIA/NemoClaw/pull/9185), and [PR #9112](https://github.com/NVIDIA/NemoClaw/pull/9112).
+- Fresh OpenClaw and Hermes onboarding now waits for a durable sandbox ID and a successful no-op command after OpenShell reports `Ready`.
+  Deployment verification also probes a separate agent API host forward before reporting the sandbox ready, and names the exact forward recovery command when that endpoint is unavailable.
+  An explicit `--recreate-sandbox` request bypasses stale saved build or policy fingerprints, and managed OpenClaw registration records its validated agent identity for later rebuild and restore authority.
+  Readiness observations now age from collection completion, so slow probes do not immediately invalidate their own results, and rebuild recovery can defer an unanswered route query to authoritative onboarding while still rejecting a confirmed route mismatch.
+  Reused onboarding passes the selected messaging dependencies, session reporting recognizes proxied `connect` processes, and recovery can use probe-only convergence without failing solely because platform evidence is absent.
+  Legacy gateway upgrades preserve a proven gateway identity and scope cleanup to the exact selected gateway, while sandbox destroy removes only an identity-bound Docker orphan and preserves recovery state on any mismatch.
+  The deprecated global `nemoclaw start` command exits successfully with migration guidance instead of starting a tunnel, leaving sandbox startup to `nemoclaw <sandbox> start` and tunnel startup to `nemoclaw tunnel start`.
+  For more information, refer to [Recover and Rebuild Sandboxes](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/recover-and-rebuild-sandboxes), the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands), and [Troubleshooting](/user-guide/openclaw/reference/troubleshooting).
+  Related changes: [PR #9229](https://github.com/NVIDIA/NemoClaw/pull/9229), [PR #9299](https://github.com/NVIDIA/NemoClaw/pull/9299), [PR #9318](https://github.com/NVIDIA/NemoClaw/pull/9318), [PR #9325](https://github.com/NVIDIA/NemoClaw/pull/9325), [PR #9352](https://github.com/NVIDIA/NemoClaw/pull/9352), [PR #9370](https://github.com/NVIDIA/NemoClaw/pull/9370), [PR #9366](https://github.com/NVIDIA/NemoClaw/pull/9366), [PR #9321](https://github.com/NVIDIA/NemoClaw/pull/9321), [PR #9285](https://github.com/NVIDIA/NemoClaw/pull/9285), [PR #9282](https://github.com/NVIDIA/NemoClaw/pull/9282), [PR #8920](https://github.com/NVIDIA/NemoClaw/pull/8920), [PR #9198](https://github.com/NVIDIA/NemoClaw/pull/9198), and [PR #9201](https://github.com/NVIDIA/NemoClaw/pull/9201).
+- The explicit experimental Portable OpenClaw profile now keeps sandbox lifecycle operations under the selected current-user rootless Podman socket and exact container identity, uses native OpenShell GPU injection, and preserves a sandbox whose identity cannot be verified.
+  Portable onboarding verifies the cgroups v2 CPU controller at the root hierarchy, per-user slice, user manager, and `app.slice` before mutation, with documented administrator-owned Ubuntu 22.04 preparation and rollback.
+  Portable OpenClaw onboarding publishes readiness only after paired-device and active-operator scopes settle against the current lifecycle receipt; connect, recovery, and launch preflight perform at most one bounded repair or report incomplete onboarding.
+  Fresh Portable onboarding defaults to the narrower `weather`, `public-reference`, and `github` policy presets, retains explicit model intent, and reconciles a timed-out stop only after the exact receipt-owned container reaches `Running=false`.
+  Portable uninstall removes only receipt-owned Podman resources and NemoClaw-owned selectors, preserves ambiguous state for retry, and leaves ordinary Docker, model stores, and unrelated user resources unchanged.
+  For more information, refer to [Platform Support](/user-guide/openclaw/reference/platform-support), [Network Policies Reference](/user-guide/openclaw/reference/network-policies), [Uninstall NemoClaw](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/uninstall-nemoclaw), and [Troubleshooting](/user-guide/openclaw/reference/troubleshooting).
+  Related changes: [PR #9176](https://github.com/NVIDIA/NemoClaw/pull/9176), [PR #9197](https://github.com/NVIDIA/NemoClaw/pull/9197), [PR #9289](https://github.com/NVIDIA/NemoClaw/pull/9289), [PR #9270](https://github.com/NVIDIA/NemoClaw/pull/9270), [PR #9339](https://github.com/NVIDIA/NemoClaw/pull/9339), [PR #9209](https://github.com/NVIDIA/NemoClaw/pull/9209), [PR #9186](https://github.com/NVIDIA/NemoClaw/pull/9186), and [PR #9376](https://github.com/NVIDIA/NemoClaw/pull/9376).
+- Later onboarding runs now record when the host stops configuring a messaging channel, remove its stale egress preset, and preserve in-sandbox QR-paired channels whose state the host cannot determine.
+  Managed startup validation accepts schema-owned messaging package pins and approved credential placeholder assignments while continuing to reject raw credentials, mismatched keys, and malformed or misplaced values.
+  `policy remove` can remove a preset enforced by the live gateway even when the local registry lacks it, and reports an unavailable gateway separately from a gateway that does not hold the preset.
+  Experimental Google Chat pairing approval becomes active for the next message after direct approval, with managed restart recovery when activation partially commits.
+  For more information, refer to [Enable Channels During Onboarding](/user-guide/openclaw/manage-sandboxes/messaging-channels/enable-channels-during-onboarding), [Set Up Google Chat](/user-guide/openclaw/manage-sandboxes/messaging-channels/set-up-google-chat), and [Apply Policy Presets](/user-guide/openclaw/network-policy/configure-policies/apply-policy-presets).
+  Related changes: [PR #9296](https://github.com/NVIDIA/NemoClaw/pull/9296), [PR #9327](https://github.com/NVIDIA/NemoClaw/pull/9327), [PR #9306](https://github.com/NVIDIA/NemoClaw/pull/9306), [PR #9248](https://github.com/NVIDIA/NemoClaw/pull/9248), and [PR #9374](https://github.com/NVIDIA/NemoClaw/pull/9374).
+- Snapshot backup now accepts multiply linked regular package files in a Hermes sandbox while continuing to reject unsafe symbolic links and special files.
+  `uninstall --destroy-user-data` removes installer-managed user-local CLI shims when sibling evidence does not require the shared package, and full Portable uninstall follows its separate receipt-bound cleanup contract.
+  The experimental voice gateway reads startup credentials from fixed inherited file descriptors instead of accepting credential paths in process arguments, and Shields accepts only bounded native OpenClaw device-store modes while restoring mutable state.
+  OpenClaw startup guard output now stays in a root-only child directory while the shared runtime directory remains traversable, preserving access to the root-owned managed CA bundle without exposing guard diagnostics to sandbox processes.
+  For more information, refer to [Create and Restore Snapshots](/user-guide/openclaw/manage-sandboxes/state-and-backups/create-and-restore-snapshots), [Uninstall NemoClaw](/user-guide/openclaw/manage-sandboxes/operate-sandboxes/uninstall-nemoclaw), [Filesystem Controls](/user-guide/openclaw/security/security-controls/filesystem-controls), and the [NemoClaw CLI Commands Reference](/user-guide/openclaw/reference/commands).
+  Related changes: [PR #9317](https://github.com/NVIDIA/NemoClaw/pull/9317), [PR #9288](https://github.com/NVIDIA/NemoClaw/pull/9288), [PR #9239](https://github.com/NVIDIA/NemoClaw/pull/9239), [PR #9269](https://github.com/NVIDIA/NemoClaw/pull/9269), and [PR #9371](https://github.com/NVIDIA/NemoClaw/pull/9371).
+- Release qualification again treats the trusted staging Launchable deployment as required evidence and retains bounded, secret-safe readiness diagnostics and transient collaborator-permission retries.
+  The E2E workflow reports same-commit first-pass and retry reliability, retries only transient reads of the exact trusted contract artifact, executes the credential-free native-runtime qualification matrix without enabling production Podman selection, and documents canonical target selection and retry rules.
+  Post-merge documentation catch-up now runs after merges through separated author, reviewer, and publisher boundaries, while release prep continues to require the dated changelog entry on `main` before tag planning.
+  Related changes: [PR #9351](https://github.com/NVIDIA/NemoClaw/pull/9351), [PR #9350](https://github.com/NVIDIA/NemoClaw/pull/9350), [PR #9353](https://github.com/NVIDIA/NemoClaw/pull/9353), [PR #9226](https://github.com/NVIDIA/NemoClaw/pull/9226), [PR #9237](https://github.com/NVIDIA/NemoClaw/pull/9237), [PR #9232](https://github.com/NVIDIA/NemoClaw/pull/9232), [PR #9275](https://github.com/NVIDIA/NemoClaw/pull/9275), [PR #9234](https://github.com/NVIDIA/NemoClaw/pull/9234), and [PR #9365](https://github.com/NVIDIA/NemoClaw/pull/9365).