docs(changelog): finish v0.0.109 release entry

[prekshivyas]

Summary

Finish the v0.0.109 changelog after two user-visible fixes merged immediately before the release-note PR. The entry now records exact gateway-port conflict diagnostics and agent-base policy-explain classification.

Changes

• Add PR fix(readiness): name the process holding the gateway port #9149 with the exact complete-listener-set, PID fallback, stop-authority, and verified-only uninstall behavior.
• Add PR fix(policy): classify agent base-policy presets distinctly in explain #9082 with the agent-base policy-explain state, active reporting, and omitted policy add suggestion.
• Link the policy-explain documentation directly.

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 follow-up changes only the existing release entry; the changelog contract test validates its structure and links.
• 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: Reviewed the complete effective change to docs/changelog/2026-08-14.mdx against origin/main, the current source, tests, and owning documentation for PR fix(readiness): name the process holding the gateway port #9149 and PR fix(policy): classify agent base-policy presets distinctly in explain #9082, the documentation writing rules, and the documentation style. The gateway-port claim matches the complete-listener-set condition, conditional process-name output, unverified-PID stop guidance, and verified-only uninstall guidance. The agent-base classification claim and direct documentation route match current behavior. Changelog structure, terminology, and PR links are accurate. npx vitest run test/changelog-docs.test.ts passed 6 tests; npm run docs passed with 0 errors and 2 existing non-failing Fern warnings; git diff --check, the pre-commit hook, the commit-msg hook, and the pre-push hook passed.
• 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 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; npm run docs passed with 0 errors and 2 existing non-failing Fern warnings; published-route validation and git diff --check passed.
• 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 release-note-only follow-up.
• 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) — The build passed with 0 errors and 2 existing non-failing 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 updates the existing native changelog page.

---

Signed-off-by: Prekshi Vyas prekshiv@nvidia.com

Summary by CodeRabbit

• New Features
  • Added clearer gateway-conflict diagnostics, including listener process IDs and names.
  • Added targeted guidance for stopping unverified listeners and uninstalling verified managed conflicts on specific ports.
  • Clarified agent-base policy messages and linked to related documentation.

[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: 07139adf-6db9-4cc6-b797-653f176d252a

📥 Commits

Reviewing files that changed from the base of the PR and between 9f265f7 and 2d268cc.

📒 Files selected for processing (1)

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

---

📝 Walkthrough

Walkthrough

The v0.0.109 changelog documents gateway-conflict diagnostics and agent-base policy explanation updates, including listener process details, conditional remediation guidance, active preset reporting, and related documentation links.

Changes

Diagnostics documentation

Layer / File(s)	Summary
Document diagnostic behavior docs/changelog/2026-08-14.mdx	The changelog documents listener PIDs and process names, conditional stop and uninstall guidance, and active agent-base policy reporting without redundant policy add suggestions. It also adds related documentation links.

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

Merge Risk: ⚪ Minimal · up to 2d268

This PR only completes the existing v0.0.109 changelog entry and does not change product code or runtime behavior; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: aasthajh

🚥 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 changelog-only change that completes the v0.0.109 release 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/docs-v0.0.109-final

---

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

[github-actions]

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

3 terminology differences from the second opinion

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

• agent-base at docs/changelog/2026-08-14.mdx:69: primary classified it as established; the second opinion classified it as conflict.
• port-scoped at docs/changelog/2026-08-14.mdx:26: selected only by the second-opinion lane as established.
• complete listener set at docs/changelog/2026-08-14.mdx:24: 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.

• justified — unverified listener PIDs at docs/changelog/2026-08-14.mdx:25: Keep the modifier because it limits stop guidance to listeners without verified managed ownership.
• justified — port-scoped uninstall guidance at docs/changelog/2026-08-14.mdx:26: Keep the scope modifier because it identifies the limited uninstall action.
• established — agent-base at docs/changelog/2026-08-14.mdx:69: Keep `agent-base` as the exact established classification.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite for the commit under review.

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.