docs(contributing): clarify extension terminology checklist

[jyaunches]

Summary

• Clarify the contributor-facing extensibility terminology checklist in docs/CONTRIBUTING.md.
• Reference PR docs: define extension taxonomy and SDK readiness #6508 as the separate decision record without duplicating it.
• Keep ownership boundaries for VoiceClaw integration via existing messaging and provider contracts #5998, refactor(messaging): organize channels into plugin-style modules #6097, Observability plugin support for external telemetry adapters #3915, OpenClaw VoiceClaw support: voice-call plugin boundary and core runtime work #6201, and OpenShell VoiceClaw support: validate sandbox contracts and track networking follow-ons #6207 separate.

Verification

• Broker validation docs passed.
• Final broker repository status shows only docs/CONTRIBUTING.md changed.

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

Request broker-controlled commit, push, and draft PR creation.

[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]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: b0a0fc6f-86e1-4623-a45f-808902c941a0

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/issue-6229-r2-contributor-checklist

---

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

[github-actions]

E2E Advisor Recommendation

Required E2E: None
Optional E2E: None

Workflow run

Full advisor summary

E2E Recommendation Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E

• None. Docs-only change limited to docs/CONTRIBUTING.md. It cannot affect NemoClaw runtime behavior or user flows, so no E2E jobs are required.

Optional E2E

• None.

New E2E recommendations

• None.

[github-actions]

E2E Target Recommendation

Required E2E targets: None
Optional E2E targets: None

Workflow run

Full E2E target advisor summary

E2E Target Advisor

Base: origin/main
Head: HEAD
Confidence: high

Required E2E targets

• None. Docs-only change outside E2E target workflow, registry, fixtures, live tests, runtime support, and target-relevant source paths; no E2E target dispatch is needed.

Optional E2E targets

• None.

Relevant changed files

• None.

[github-actions]

🌿 Preview your docs: https://nvidia-preview-pr-6517.docs.buildwithfern.com/nemoclaw

[github-actions]

PR Review Advisor — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: No advisor follow-up required beyond maintainer review.
Open items: 0 required · 0 warnings · 0 suggestions · 0 test follow-ups
Since last review: 1 prior item resolved · 0 still apply · 0 new items found

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.

[github-actions]

PR Review Advisor (Nemotron Ultra) — No blocking findings

Merge posture: No blocking advisor findings
Primary next action: No advisor follow-up required beyond maintainer review.
Open items: 0 required · 0 warnings · 0 suggestions · 0 test follow-ups
Since last review: 1 prior item resolved · 0 still apply · 0 new items found

Workflow run details

This is an automated, non-binding review; it still expects maintainers and agents to respond to each required or warning item. Treat suggestions as current-PR improvements when they touch changed code; defer only with maintainer rationale or a linked follow-up. A human maintainer must make the final merge decision.