docs(overview): gate 'Messaging channels' to openclaw/hermes variants

[kagura-agent]

Summary

The Overview page's Key Features table lists Messaging channels for all three NemoClaw variants, but Deep Agents is a terminal coding harness with no messaging channel support (channels add slack is hard-rejected).

Changes

File: docs/about/overview.mdx

1. Intro text — Use inline <AgentOnly> to show "always-on AI agents" for openclaw/hermes and "AI coding agents" for deepagents, since Deep Agents is a terminal coding harness rather than an always-on assistant.

2. Key Features table — Move the "Messaging channels" row out of the shared table into an <AgentOnly variant="openclaw,hermes"> block so it only renders for variants that actually support messaging channels.

Both changes use the existing <AgentOnly> component already imported and used in the same file's Next Steps section.

Note

The messaging channels row renders as a separate single-row table for openclaw/hermes users because MDX doesn't support wrapping individual table rows in JSX components. This is the same approach used in the Next Steps section and is the standard pattern for variant-gated content.

Closes #6561

Summary by CodeRabbit

• Documentation
  • Updated the overview page’s main description to vary by product variant (e.g., “always-on AI agents” vs “AI coding agents”).
  • Adjusted the “Key Features” table ordering so “Routed inference” and “Layered protection” appear earlier.
  • Made the “Messaging channels” capability row render only for the applicable variants.

---

Signed-off-by: Kagura kagura.agent.ai@gmail.com

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[coderabbitai]

📝 Walkthrough

Walkthrough

The overview.mdx page now renders variant-specific intro text with AgentOnly components and moves the “Messaging channels” feature into an AgentOnly-gated row for openclaw,hermes. The Key Features table order is also adjusted.

Changes

Overview page variant scoping

Layer / File(s)	Summary
Variant-scoped intro and Key Features table docs/about/overview.mdx	The intro sentence is split into variant-specific AgentOnly content, and the Key Features table reorders rows while gating “Messaging channels” to openclaw,hermes only.

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

Suggested labels: area: docs

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The PR removes Messaging channels from Deep Agents and updates the intro wording as requested in #6561.
Out of Scope Changes check	✅ Passed	The changes stay within the requested docs variant-scoping and feature-table fix.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and accurately describes the main variant-gating change to the Overview docs.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[coderabbitai]

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/about/overview.mdx`:
- Line 16: The intro sentence in the overview content currently uses inline
AgentOnly tags, which will not be removed by the variant sync and will leak raw
tags into generated docs. Update the overview text to use block-form AgentOnly
sections, matching the existing variant-specific patterns in the same document,
so scripts/sync-agent-variant-docs.ts can strip them correctly.

🪄 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: aab3a25e-5943-4dea-bdab-3acd536e447a

📥 Commits

Reviewing files that changed from the base of the PR and between 5476b9d and 5574723.

📒 Files selected for processing (1)

• docs/about/overview.mdx

[cjagwani]

The docs change is content-correct on cfe14b7f, both commits are GitHub Verified, and the earlier CodeRabbit concern is resolved. Before this can be approved, please add a valid Signed-off-by: Name <email> declaration to the PR description; NemoClaw contributor policy requires both the PR-body DCO declaration and Verified commits. I have released the held fork workflows so CI and the Fern preview can run while you update the description.

[cjagwani]

Trusted manual advisor evidence for exact head cfe14b7f468de0abcc850f1e2179409777034a09: run 29027942518 fetched refs/pull/6573/head; both GPT-5.5 and Nemotron Ultra returned high-confidence merge_as_is with zero findings, all #6561 acceptance clauses met, and all nine security categories passing. The released docs/preview CI is also green. The sole current failure remains dco-check: please add the requested valid Signed-off-by: declaration to the PR description; after that body-only correction, the DCO workflow must be rerun before approval.

[kagura-agent]

Done — added the DCO Signed-off-by declaration to the PR description. Thanks for releasing the held workflows!

[cjagwani]

Approved exact head cfe14b7f468de0abcc850f1e2179409777034a09: the contributor added the required PR-body Signed-off-by: declaration and the fresh DCO/commit-lint runs pass; both commits are Verified; docs checks and Fern preview pass; CodeRabbit is clear; and trusted manual run 29027942518 fetched this exact head with both advisors returning high-confidence merge_as_is, zero findings, all #6561 acceptance clauses met, and all security categories passing. Superseded failed/cancelled fork attempts are historical workflow artifacts, not current failures.

[apurvvkumaria]

Contributor-compliance changes are required before workflows or merge review can proceed. Both commits are GitHub Verified, but neither commit contains a Signed-off-by trailer, and the PR body lacks the required DCO declaration/current template quality-gate sections. Please rewrite the commits with your own Signed-off-by declaration, keep every rewritten commit GitHub Verified, and update the PR body with the same contributor DCO declaration. The docs diff itself aligns with #6561; this request is specifically for the mandatory contributor-attestation gate.