chore: Misc release prep

[dagardner-nv]

Overview

• Remove references to alpha and RC tags
• Replace buildwithfern.com links with docs.nvidia.com

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• Closes FABRIC-135

• I confirm this contribution is my own work, or I have the right to submit it under this project's license.

• I searched existing issues and open pull requests, and this does not duplicate existing work.

Summary by CodeRabbit

• Documentation

  • Updated NeMo Fabric and NeMo Relay links across installation guides, package pages, project metadata, and examples to point to the official NVIDIA documentation site.
  • Refreshed installation instructions to reference the stable 0.1.0 package release instead of a pre-release version.

• Tests

  • Updated integration expectations to match the stable package version.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Enterprise

Run ID: 36556ff8-b31e-4c23-b7a9-0d479caba699

📥 Commits

Reviewing files that changed from the base of the PR and between f1ec2a9 and 945ebdd.

📒 Files selected for processing (1)

• adapters/claude/README.md

📜 Recent review details

⏰ Context from checks skipped due to timeout. (20)

• GitHub Check: Preview docs
• GitHub Check: Test (Python 3.12, linux-arm64)
• GitHub Check: Test (Python 3.14, linux-arm64)
• GitHub Check: Test (Python 3.13, macos-arm64)
• GitHub Check: Test (Python 3.13, linux-arm64)
• GitHub Check: Test (Python 3.11, linux-arm64)
• GitHub Check: Test (Python 3.11, linux-amd64)
• GitHub Check: Test (Python 3.13, linux-amd64)
• GitHub Check: Test (Python 3.11, macos-arm64)
• GitHub Check: Test (Python 3.12, macos-arm64)
• GitHub Check: Test (Python 3.12, linux-amd64)
• GitHub Check: Test (Python 3.14, windows-amd64)
• GitHub Check: Test (Python 3.13, windows-amd64)
• GitHub Check: Test (Python 3.11, windows-amd64)
• GitHub Check: Test (Python 3.12, windows-amd64)
• GitHub Check: Test (Python 3.14, linux-amd64)
• GitHub Check: Test (Python 3.14, macos-arm64)
• GitHub Check: Test (x86_64)
• GitHub Check: Test (arm64)
• GitHub Check: Pre-commit

🧰 Additional context used

📓 Path-based instructions (11)

**/*.{md,rst}

📄 CodeRabbit inference engine (.agents/skills/contribute-api/SKILL.md)

Update documentation and examples in the same branch as the public API change.

Files:

• adapters/claude/README.md

**/*

📄 CodeRabbit inference engine (.agents/skills/karpathy-guidelines/SKILL.md)

**/*: Before implementing, explicitly state assumptions, surface ambiguity and tradeoffs, present multiple interpretations when relevant, and ask for clarification rather than silently deciding or proceeding when requirements are unclear.
Prefer the minimum code needed to solve the requested problem: avoid speculative features, unnecessary abstractions, unrequested flexibility, and handling of impossible scenarios; simplify overcomplicated solutions.
When editing existing code, make surgical changes only: do not modify unrelated code, comments, formatting, or pre-existing dead code; match the existing style, and remove only unused imports, variables, or functions introduced by your changes.
Define verifiable success criteria for each task, such as writing regression tests for bugs and invalid-input tests for validation, then verify the implementation against those criteria. For multi-step work, state a brief plan with a verification check for each step.

**/*: Always spell NVIDIA in all caps; do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun, because the name begins with an “en” sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company; use trademark symbols with product names only when required by the document type or legal guidance.
Verify official capitalization, spacing, hyphenation, and spelling for NVIDIA and third-party product names; do not rewrite official product names for grammar or title-case rules.
Precede NVIDIA product names with NVIDIA on first mention when natural and accurate, and link the first mention when the destination helps the reader.
On first use, include the company name and full model qualifier when it helps identify the model; preserve official capitalization and punctuation, and use shorter family names only after establishing the full name.
For learning-oriented and developer content, do not force trademark symbols unless explicitly required; for press, ...

Files:

• adapters/claude/README.md

**/*.{md,mdx,rst}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,mdx,rst}: For NeMo Fabric documentation, verify technical claims against the current repository, public API, or documented command before reviewing style.
Always spell NVIDIA in all caps; do not use Nvidia, nvidia, or NV.
Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text; avoid raw URLs and weak anchors such as here or read more.
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative, parallel steps; split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English while preserving necessary technical precision.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once, and prefer refer to over see when directing readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical documentation.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values; use numerals for 10 or greater and commas in thousands.
Do not add trademark symbols to learning-oriented documentation unless the source, platform, or legal guidance explicitly requires them.
Do not replace precise technical terms with simpler words when doing so would lose precision.
Do not flag passive voice when the actor is unknown or the action is the important part.
Do not rewrite API names, package names, command flags, or code literals for style.

**/*.{md,mdx,rst}: Use consistent title case for technical-document headings and table headers; avoid quotation marks, ampersands, and exclamation marks in headings, while preserving official product, event, research, and whitepaper title ...

Files:

• adapters/claude/README.md

**/*.{md,rst,txt,adoc}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-language-mechanics.md)

**/*.{md,rst,txt,adoc}: For technical documentation, use professional, active, conversational, engaging, precise, and plain-English prose. Prefer active voice, present tense, short sentences, and scannable paragraphs. Avoid casual or imprecise language, swearing, threats, insults, jokes, puns, culture-specific idioms, marketing exaggeration, and unsupported third-party comparisons.
Use can for possibility and reserve may for permission; use after for temporal order; use refer to for cross-references; prefer short direct sentences and specific verbs; avoid unnecessary please in technical documentation.
Prefer active voice when the actor matters. Passive voice is acceptable when the actor is unknown or irrelevant, when the action or result is the focus, or in programmer documentation.
Use natural contractions in conversational technical prose, but do not force them in formal legal copy, API references, or generated text.
Prefer simpler English over Latinisms: use for example or such as instead of e.g., and so on instead of etc., that is instead of i.e., compared to instead of vs., and by, through, or using instead of via. Use industry-standard terms such as in silico, in vitro, and in vivo when appropriate, and italicize them in running text.
Use that without commas for essential clauses, and which with commas for nonessential clauses.
Format dates and times clearly: spell out months in body text; use forms such as June 12, 2025; avoid numeric or ordinal dates; capitalize days; use 12-hour time when appropriate; include a space before a.m. or p.m.; use ET and PT for needed time zones; avoid 24/7; and prefer from 12:30 to 1:00 p.m. for prose ranges.
Format numbers consistently: spell out zero through nine in body text, use numerals for 10 or greater and for technical values, use commas in thousands, do not begin a sentence with a numeral, spell out ordinals, and use numerals consistently within a category wh...

Files:

• adapters/claude/README.md

adapters/*/README.md

📄 CodeRabbit inference engine (AGENTS.md)

Update adapter integration READMEs when public behavior, examples, or supported bindings change.

Document installation, supported configuration, harness-only settings, credentials, lifecycle, telemetry, artifacts, limitations, focused test commands, and canonical typed SDK or harness-native YAML examples where applicable.

Files:

• adapters/claude/README.md

**/*.{md,mdx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

When public behavior, adapters, examples, or workspace structure changes, update the corresponding documentation, including relevant README files and SDK or API references.

**/*.{md,mdx}: Use the full product name NVIDIA NeMo Fabric on first use, typically in the title and H1; use NeMo Fabric thereafter. Use fabric alone only for the CLI tool and surround it with backticks.
Treat incorrect or stale commands, package names, paths, APIs, support claims, procedures, examples, terminology, or public behavior documentation as blocking issues.
Capitalize NVIDIA correctly and format code, commands, paths, and filenames as inline code where needed.
Use title case for technical-documentation headings.
Introduce code blocks, tables, and lists with complete lead-in sentences; ensure examples match current APIs and build commands.
Use descriptive anchor text, avoid raw URLs and generic labels such as here, and use repository-relative .mdx paths for links within docs/.
Prefer active voice, present tense, short sentences, plain English, consistent terminology, and imperative, parallel, scannable procedures.
Use after instead of once when expressing temporal sequence, and use can rather than may when describing possibility rather than permission.
Avoid ambiguous numeric dates and ordinal dates in body text.
For learning-oriented documentation, do not force trademark symbols unless the source document explicitly requires them.
When reporting documentation-review findings, lead with Must fix, Should fix, and Nice to have categories; include file path, line reference, current problem, rationale, and a concrete rewrite or direction.

Files:

• adapters/claude/README.md

**/*.{rs,py,html,md,mdx,toml,yaml,yml,sh,bash}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

All source files must include the specified SPDX copyright and Apache-2.0 license headers using the comment syntax appropriate to the file type.

Files:

• adapters/claude/README.md

adapters/*/{README.md,LICENSE,fabric-adapter.json,pyproject.toml,uv.lock,package.json,package-lock.json,src/**,tests/**}

📄 CodeRabbit inference engine (.agents/skills/contribute-adapter/SKILL.md)

Place each adapter under adapters/<name> with LICENSE -> ../../LICENSE, README.md, fabric-adapter.json, language-native package and lock files, a source entry point, and focused tests; Python adapters use the specified pyproject.toml, uv.lock, source path, and test naming convention.

Files:

• adapters/claude/README.md

**/*.{md,mdx,yml,py,rs,sh}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

Keep documentation aligned with current NeMo Fabric behavior, repository layout, entry points, commands, package names, APIs, bindings, and support claims.

Files:

• adapters/claude/README.md

{adapters/**,examples/**}

⚙️ CodeRabbit configuration file

{adapters/**,examples/**}: Review adapter and example changes for command correctness, config/schema consistency, artifact handling, and compatibility with the public NeMo Fabric contracts.

Files:

• adapters/claude/README.md

{*.md,**/*.md,**/*.mdx,**/*.ipynb}

⚙️ CodeRabbit configuration file

{*.md,**/*.md,**/*.mdx,**/*.ipynb}: Enforce the product name in user-facing prose: use "NVIDIA NeMo Fabric" on first use and "NeMo Fabric" thereafter. Flag standalone capitalized "Fabric" when it refers to the product. Do not flag the lowercase fabric CLI command, package/import/crate names, code identifiers, API symbols, configuration keys, file paths, or unrelated generic uses of the word.

Files:

• adapters/claude/README.md

🔇 Additional comments (1)

adapters/claude/README.md (1)

27-27: LGTM!

Also applies to: 61-61, 125-125

---

Walkthrough

Documentation links across adapters and package metadata now point to NVIDIA-hosted NeMo Fabric pages. Harbor setup instructions and integration expectations now pin the stable 0.1.0 release instead of a prerelease.

Changes

Documentation and release updates

Layer / File(s)	Summary
Migrate documentation links adapters/*, pypi.md, pyproject.toml, python/*	Replaces BuildWithFern documentation URLs with corresponding docs.nvidia.com/nemo/fabric links across adapter guides, package metadata, and Python documentation.
Update Harbor stable version examples/harbor/swebench/README.md, tests/integrations/test_harbor_runner.py	Changes the Harbor package pin and matching test expectation from 0.1.0a20260724 to 0.1.0.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• NVIDIA/NeMo-Fabric#97: Both PRs update NeMo Fabric documentation links and Relay installation references.
• NVIDIA/NeMo-Fabric#153: Both PRs update documentation and package metadata links in the same adapter and package files.
• NVIDIA/NeMo-Fabric#158: Both PRs modify package documentation metadata in pypi.md and pyproject.toml.

---

Important

Pre-merge checks failed

Please resolve all errors before merging. Addressing warnings is optional.

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title uses valid Conventional Commits syntax but is too generic because "Misc release prep" does not identify the documentation and release-tag updates.	Replace the summary with a specific imperative title, such as "chore: update release documentation links and tags".

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description identifies the main changes, links FABRIC-135, and includes both required confirmations, although it omits the reviewer-start section.
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

---

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

[github-actions]

Fern docs preview: https://nvidia-preview-pull-request-163.docs.buildwithfern.com/nemo/fabric

[coderabbitai]

Actionable comments posted: 2

🤖 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 `@adapters/claude/README.md`:
- Line 27: Replace all dead docs.nvidia.com/nemo/fabric links with their current
valid destinations across adapters/claude/README.md (installation, auth, and
Relay links), adapters/claude/pypi.md, adapters/claude/pyproject.toml
(Documentation metadata), adapters/codex/README.md, pypi.md, pyproject.toml
(Documentation metadata), python/README.md, python/pypi.md, and
python/pyproject.toml (Documentation metadata); update each referenced site,
including the listed line ranges, without changing unrelated content.

In `@adapters/codex/pypi.md`:
- Around line 28-30: The NeMo Fabric documentation links and package metadata
are stale; update all referenced documentation URLs to the live base URL
https://nvidia-nemo-fabric.docs.buildwithfern.com/nemo/fabric with matching
installation-guide anchors. Apply the corresponding link updates in
adapters/codex/pypi.md (28-30), adapters/codex/pyproject.toml (44),
adapters/common/README.md (18), adapters/common/pypi.md (26),
adapters/common/pyproject.toml (32), adapters/deepagents/README.md (29),
adapters/deepagents/pypi.md (33), adapters/deepagents/pyproject.toml (56),
adapters/hermes/README.md (27), adapters/hermes/pypi.md (34), and
adapters/hermes/pyproject.toml (48), including each pyproject.toml Documentation
field.

🪄 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: ASSERTIVE

Plan: Enterprise

Run ID: 6e77e8f8-721f-4eee-917c-8185bff793b9

📥 Commits

Reviewing files that changed from the base of the PR and between c310e9c and f1ec2a9.

📒 Files selected for processing (22)

• adapters/claude/README.md
• adapters/claude/pypi.md
• adapters/claude/pyproject.toml
• adapters/codex/README.md
• adapters/codex/pypi.md
• adapters/codex/pyproject.toml
• adapters/common/README.md
• adapters/common/pypi.md
• adapters/common/pyproject.toml
• adapters/deepagents/README.md
• adapters/deepagents/pypi.md
• adapters/deepagents/pyproject.toml
• adapters/hermes/README.md
• adapters/hermes/pypi.md
• adapters/hermes/pyproject.toml
• examples/harbor/swebench/README.md
• pypi.md
• pyproject.toml
• python/README.md
• python/pypi.md
• python/pyproject.toml
• tests/integrations/test_harbor_runner.py

📜 Review details

🧰 Additional context used

📓 Path-based instructions (37)

**/*

📄 CodeRabbit inference engine (.agents/skills/karpathy-guidelines/SKILL.md)

**/*: Before implementing, explicitly state assumptions, surface ambiguity and tradeoffs, present multiple interpretations when relevant, and ask for clarification rather than silently deciding or proceeding when requirements are unclear.
Prefer the minimum code needed to solve the requested problem: avoid speculative features, unnecessary abstractions, unrequested flexibility, and handling of impossible scenarios; simplify overcomplicated solutions.
When editing existing code, make surgical changes only: do not modify unrelated code, comments, formatting, or pre-existing dead code; match the existing style, and remove only unused imports, variables, or functions introduced by your changes.
Define verifiable success criteria for each task, such as writing regression tests for bugs and invalid-input tests for validation, then verify the implementation against those criteria. For multi-step work, state a brief plan with a verification check for each step.

**/*: Always spell NVIDIA in all caps; do not use Nvidia, nvidia, nVidia, nVIDIA, or NV.
Use an NVIDIA before a noun, because the name begins with an “en” sound.
Do not add a registered trademark symbol after NVIDIA when referring to the company; use trademark symbols with product names only when required by the document type or legal guidance.
Verify official capitalization, spacing, hyphenation, and spelling for NVIDIA and third-party product names; do not rewrite official product names for grammar or title-case rules.
Precede NVIDIA product names with NVIDIA on first mention when natural and accurate, and link the first mention when the destination helps the reader.
On first use, include the company name and full model qualifier when it helps identify the model; preserve official capitalization and punctuation, and use shorter family names only after establishing the full name.
For learning-oriented and developer content, do not force trademark symbols unless explicitly required; for press, ...

Files:

• adapters/common/pyproject.toml
• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/deepagents/pyproject.toml
• adapters/codex/README.md
• pypi.md
• tests/integrations/test_harbor_runner.py
• adapters/claude/README.md

**/*.{rs,toml}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

For any Rust change, run just test-rust and cargo fmt --all -- --check.

For Rust core, CLI, or shared runtime semantic changes, run Rust formatting and tests, and add Python tests when behavior is exposed through the SDK.

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml

**/{Cargo.toml,Cargo.lock,pyproject.toml,package.json}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

For new or updated dependencies, document the functional need, alternatives considered, and why the selected dependency is the narrowest fit.

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml

**/*.{toml,lock}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If a manifest or lockfile changes, run the license-diff script against origin/main, review transitive license changes, and run the attributions-rust and attributions-python pre-commit hooks.

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml

**/*.{yml,yaml,toml,lock}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

For CI or packaging changes, use maintain-ci or maintain-packaging, then run recipes and checks whose behavior changed.

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml

{pyproject.toml,adapters/**/pyproject.toml}

📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)

{pyproject.toml,adapters/**/pyproject.toml}: Update the literal project.version in the root setuptools project and every adapter pyproject.toml.
Keep internal exact-version requirements aligned: root nemo-fabric-* == <version> optional dependencies and each adapter's nemo-fabric-adapters-common == <version> dependency.

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml

**/*.{rs,py,toml}

📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)

When editing version helpers, verify every nemo-fabric-* workspace package through Cargo metadata and reject a static version in python/pyproject.toml.

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml
• tests/integrations/test_harbor_runner.py

**/*.{toml,rs,py}

📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)

Avoid blind repository-wide replacement of version-like strings; distinguish package-version references from examples and unrelated dependency versions.

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml
• tests/integrations/test_harbor_runner.py

**/*.{rs,py,html,md,mdx,toml,yaml,yml,sh,bash}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

All source files must include the specified SPDX copyright and Apache-2.0 license headers using the comment syntax appropriate to the file type.

Files:

• adapters/common/pyproject.toml
• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• pyproject.toml
• python/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/deepagents/pyproject.toml
• adapters/codex/README.md
• pypi.md
• tests/integrations/test_harbor_runner.py
• adapters/claude/README.md

adapters/*/{README.md,LICENSE,fabric-adapter.json,pyproject.toml,uv.lock,package.json,package-lock.json,src/**,tests/**}

📄 CodeRabbit inference engine (.agents/skills/contribute-adapter/SKILL.md)

Place each adapter under adapters/<name> with LICENSE -> ../../LICENSE, README.md, fabric-adapter.json, language-native package and lock files, a source entry point, and focused tests; Python adapters use the specified pyproject.toml, uv.lock, source path, and test naming convention.

Files:

• adapters/common/pyproject.toml
• adapters/hermes/README.md
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• adapters/deepagents/README.md
• adapters/codex/pyproject.toml
• adapters/common/README.md
• adapters/deepagents/pyproject.toml
• adapters/codex/README.md
• adapters/claude/README.md

adapters/*/pyproject.toml

📄 CodeRabbit inference engine (.agents/skills/contribute-adapter/SKILL.md)

Keep published Python runtime dependencies razor-thin and adapter-owned; directly imported SDK/client libraries must be declared, while external-process harness dependencies must not be installed or upgraded and test-only dependencies belong in [dependency-groups].

Files:

• adapters/common/pyproject.toml
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• adapters/codex/pyproject.toml
• adapters/deepagents/pyproject.toml

{adapters/**,examples/**}

⚙️ CodeRabbit configuration file

{adapters/**,examples/**}: Review adapter and example changes for command correctness, config/schema consistency, artifact handling, and compatibility with the public NeMo Fabric contracts.

Files:

• adapters/common/pyproject.toml
• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/claude/pyproject.toml
• adapters/hermes/pyproject.toml
• adapters/deepagents/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• adapters/claude/pypi.md
• adapters/codex/pyproject.toml
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/deepagents/pyproject.toml
• adapters/codex/README.md
• adapters/claude/README.md

**/*.{md,rst}

📄 CodeRabbit inference engine (.agents/skills/contribute-api/SKILL.md)

Update documentation and examples in the same branch as the public API change.

Files:

• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/codex/README.md
• pypi.md
• adapters/claude/README.md

**/*.{md,mdx,rst}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-guide.md)

**/*.{md,mdx,rst}: For NeMo Fabric documentation, verify technical claims against the current repository, public API, or documented command before reviewing style.
Always spell NVIDIA in all caps; do not use Nvidia, nvidia, or NV.
Format commands, code elements, expressions, package names, file names, and paths as inline code.
Use descriptive link text; avoid raw URLs and weak anchors such as here or read more.
Use title case consistently for technical documentation headings.
Introduce code blocks, lists, tables, and images with complete sentences.
Write procedures as imperative, parallel steps; split long procedures into smaller tasks.
Prefer active voice, present tense, short sentences, contractions, and plain English while preserving necessary technical precision.
Use can for possibility and reserve may for permission.
Use after for temporal relationships instead of once, and prefer refer to over see when directing readers to another resource.
Avoid culture-specific idioms, unnecessary Latinisms, jokes, and marketing exaggeration in technical documentation.
Spell out months in body text, avoid ordinal dates, and use clear time zones.
Spell out whole numbers from zero through nine unless they are technical values, parameters, versions, or UI values; use numerals for 10 or greater and commas in thousands.
Do not add trademark symbols to learning-oriented documentation unless the source, platform, or legal guidance explicitly requires them.
Do not replace precise technical terms with simpler words when doing so would lose precision.
Do not flag passive voice when the actor is unknown or the action is the important part.
Do not rewrite API names, package names, command flags, or code literals for style.

**/*.{md,mdx,rst}: Use consistent title case for technical-document headings and table headers; avoid quotation marks, ampersands, and exclamation marks in headings, while preserving official product, event, research, and whitepaper title ...

Files:

• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/codex/README.md
• pypi.md
• adapters/claude/README.md

**/*.{md,rst,txt,adoc}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/assets/nvidia-style-language-mechanics.md)

**/*.{md,rst,txt,adoc}: For technical documentation, use professional, active, conversational, engaging, precise, and plain-English prose. Prefer active voice, present tense, short sentences, and scannable paragraphs. Avoid casual or imprecise language, swearing, threats, insults, jokes, puns, culture-specific idioms, marketing exaggeration, and unsupported third-party comparisons.
Use can for possibility and reserve may for permission; use after for temporal order; use refer to for cross-references; prefer short direct sentences and specific verbs; avoid unnecessary please in technical documentation.
Prefer active voice when the actor matters. Passive voice is acceptable when the actor is unknown or irrelevant, when the action or result is the focus, or in programmer documentation.
Use natural contractions in conversational technical prose, but do not force them in formal legal copy, API references, or generated text.
Prefer simpler English over Latinisms: use for example or such as instead of e.g., and so on instead of etc., that is instead of i.e., compared to instead of vs., and by, through, or using instead of via. Use industry-standard terms such as in silico, in vitro, and in vivo when appropriate, and italicize them in running text.
Use that without commas for essential clauses, and which with commas for nonessential clauses.
Format dates and times clearly: spell out months in body text; use forms such as June 12, 2025; avoid numeric or ordinal dates; capitalize days; use 12-hour time when appropriate; include a space before a.m. or p.m.; use ET and PT for needed time zones; avoid 24/7; and prefer from 12:30 to 1:00 p.m. for prose ranges.
Format numbers consistently: spell out zero through nine in body text, use numerals for 10 or greater and for technical values, use commas in thousands, do not begin a sentence with a numeral, spell out ordinals, and use numerals consistently within a category wh...

Files:

• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/codex/README.md
• pypi.md
• adapters/claude/README.md

adapters/*/README.md

📄 CodeRabbit inference engine (AGENTS.md)

Update adapter integration READMEs when public behavior, examples, or supported bindings change.

Document installation, supported configuration, harness-only settings, credentials, lifecycle, telemetry, artifacts, limitations, focused test commands, and canonical typed SDK or harness-native YAML examples where applicable.

Files:

• adapters/hermes/README.md
• adapters/deepagents/README.md
• adapters/common/README.md
• adapters/codex/README.md
• adapters/claude/README.md

**/*.{md,mdx}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

When public behavior, adapters, examples, or workspace structure changes, update the corresponding documentation, including relevant README files and SDK or API references.

**/*.{md,mdx}: Use the full product name NVIDIA NeMo Fabric on first use, typically in the title and H1; use NeMo Fabric thereafter. Use fabric alone only for the CLI tool and surround it with backticks.
Treat incorrect or stale commands, package names, paths, APIs, support claims, procedures, examples, terminology, or public behavior documentation as blocking issues.
Capitalize NVIDIA correctly and format code, commands, paths, and filenames as inline code where needed.
Use title case for technical-documentation headings.
Introduce code blocks, tables, and lists with complete lead-in sentences; ensure examples match current APIs and build commands.
Use descriptive anchor text, avoid raw URLs and generic labels such as here, and use repository-relative .mdx paths for links within docs/.
Prefer active voice, present tense, short sentences, plain English, consistent terminology, and imperative, parallel, scannable procedures.
Use after instead of once when expressing temporal sequence, and use can rather than may when describing possibility rather than permission.
Avoid ambiguous numeric dates and ordinal dates in body text.
For learning-oriented documentation, do not force trademark symbols unless the source document explicitly requires them.
When reporting documentation-review findings, lead with Must fix, Should fix, and Nice to have categories; include file path, line reference, current problem, rationale, and a concrete rewrite or direction.

Files:

• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/codex/README.md
• pypi.md
• adapters/claude/README.md

**/*.{md,mdx,yml,py,rs,sh}

📄 CodeRabbit inference engine (.agents/skills/review-doc-style/SKILL.md)

Keep documentation aligned with current NeMo Fabric behavior, repository layout, entry points, commands, package names, APIs, bindings, and support claims.

Files:

• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/codex/README.md
• pypi.md
• tests/integrations/test_harbor_runner.py
• adapters/claude/README.md

{*.md,**/*.md,**/*.mdx,**/*.ipynb}

⚙️ CodeRabbit configuration file

{*.md,**/*.md,**/*.mdx,**/*.ipynb}: Enforce the product name in user-facing prose: use "NVIDIA NeMo Fabric" on first use and "NeMo Fabric" thereafter. Flag standalone capitalized "Fabric" when it refers to the product. Do not flag the lowercase fabric CLI command, package/import/crate names, code identifiers, API symbols, configuration keys, file paths, or unrelated generic uses of the word.

Files:

• adapters/hermes/README.md
• adapters/common/pypi.md
• adapters/deepagents/README.md
• python/README.md
• adapters/codex/pypi.md
• adapters/deepagents/pypi.md
• adapters/hermes/pypi.md
• python/pypi.md
• adapters/claude/pypi.md
• adapters/common/README.md
• examples/harbor/swebench/README.md
• adapters/codex/README.md
• pypi.md
• adapters/claude/README.md

{Cargo.toml,python/pyproject.toml,pyproject.toml}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Keep Rust workspace/package metadata and Python/maturin package metadata internally consistent, including package names, versions, import paths, and module names.

Files:

• pyproject.toml
• python/pyproject.toml

{Cargo.toml,Cargo.lock,pyproject.toml,uv.lock,python/pyproject.toml}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

{Cargo.toml,Cargo.lock,pyproject.toml,uv.lock,python/pyproject.toml}: Keep workspace, Python, and lockfile dependency versions aligned where required, and review both direct and transitive dependency changes from resolved lockfiles.
Inspect resolved transitive licenses, explicitly surface UNKNOWN, non-SPDX/custom, proprietary, source-available, copyleft, or network-copyleft terms, and route unresolved licensing questions to dependency approvers with distribution and linkage context.
Document the functional need, alternatives considered, rationale for the selected dependency, and any unresolved licensing question when introducing dependencies.

Files:

• pyproject.toml
• python/pyproject.toml

{Cargo.toml,pyproject.toml,python/pyproject.toml}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Before adding a dependency, prefer the standard library, an existing dependency, or a small local implementation when appropriate; otherwise select a maintained, narrow-fit dependency with clear SPDX metadata and a permissive license where possible.

Files:

• pyproject.toml
• python/pyproject.toml

{Cargo.toml,Cargo.lock,pyproject.toml,uv.lock}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

After updating manifests or lockfiles, run uv run --no-project python scripts/licensing/license_diff.py --base-ref origin/main and review added packages and license changes.

Files:

• pyproject.toml

{pyproject.toml,python/pyproject.toml,Cargo.toml,docs/package.json,.github/workflows/*.yml,justfile}

📄 CodeRabbit inference engine (.agents/skills/maintain-packaging/SKILL.md)

Reflect public packaging changes in release-facing documentation and ensure CI references the same package names and commands used by local workflows.

Files:

• pyproject.toml
• python/pyproject.toml

python/pyproject.toml

📄 CodeRabbit inference engine (.agents/skills/update-project-version/SKILL.md)

Keep project.dynamic = ["version"]; do not add a literal project.version, because Maturin derives the runtime version from Cargo metadata.

Files:

• python/pyproject.toml

{README.md,docs/**/*.{md,mdx,yml},examples/**/*.{md,mdx,yml}}

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

Keep package names, repository references, and build commands current in documentation and examples.

Files:

• examples/harbor/swebench/README.md

{docs/**/*.{md,mdx,yml},examples/**/*.{md,mdx,yml}}

📄 CodeRabbit inference engine (.agents/skills/contribute-docs/SKILL.md)

Update relevant getting-started, reference, adapter, and example documentation when the corresponding examples or adapters change.

Files:

• examples/harbor/swebench/README.md

examples/{README.md,**/*}

📄 CodeRabbit inference engine (AGENTS.md)

Update examples documentation and relevant examples when public behavior, the package, or supported bindings change.

Files:

• examples/harbor/swebench/README.md

**/*.{rs,py,pyi,json,yaml,yml}

📄 CodeRabbit inference engine (.agents/skills/contribute-api/SKILL.md)

Determine and update every affected public surface, including the CLI, PyO3 bindings, Python SDK, type stubs, schemas, and adapter contract, so they remain in parity.

Files:

• tests/integrations/test_harbor_runner.py

**/*.{rs,py}

📄 CodeRabbit inference engine (.agents/skills/prepare-pr/SKILL.md)

For native binding changes, run cargo check -p fabric-python --locked.

**/*.{rs,py}: Use snake_case for functions and variables; use PascalCase for Rust types and Python classes.
Run the relevant Rust and Python test suites for every affected language surface; changes to the Rust core or public schemas require both suites.

Files:

• tests/integrations/test_harbor_runner.py

**/*.{py,pyi}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

If Python code or a Python-facing adapter changes, run just test-python.

Files:

• tests/integrations/test_harbor_runner.py

**/*.{rs,py,pyi}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

**/*.{rs,py,pyi}: If public configuration types change, confirm schema snapshot tests in just test-rust pass and review generated schema diffs.
For schema or public contract changes, run both language suites and review changes under schemas/ and generated API references.

Files:

• tests/integrations/test_harbor_runner.py

**/*.{py,pyi,rs}

📄 CodeRabbit inference engine (.agents/skills/validate-change/SKILL.md)

For Python SDK or PyO3 binding changes, use python-tests, run focused pytest tests first, then just test-python; rebuild with just build-python when native code or packaging changes.

Files:

• tests/integrations/test_harbor_runner.py

tests/**/*.py

📄 CodeRabbit inference engine (.agents/skills/python-tests/SKILL.md)

tests/**/*.py: Use Pytest to run Python tests.
Do not add @pytest.mark.asyncio to tests; async tests are automatically detected and run by the async runner.
Do not add -> None return type annotations to test functions.
When mocking a class, use unittest.mock.MagicMock or unittest.mock.AsyncMock, using the spec argument when necessary, rather than defining a new class.
Prefix mocked class names with mock, not fake.
Prefer pytest fixtures over helper methods.
Do not repeat fixtures; place fixtures needed by multiple test files in conftest.py.
Define fixtures using @pytest.fixture(name="<fixture_name>"[, scope="<scope>"]) and a function named <fixture_name>_fixture; specify scope only when it is not function.
Prefer pytest.mark.parametrize over separate tests for different input types.
Use @pytest.mark.usefixtures when a fixture is needed but its return value is unused or it does not return a value.
Use the autouse restore_environ_fixture from tests/conftest.py to restore environment variables; modify variables with os.environ and do not use monkeypatch.setenv.
Avoid defensive programming in tests; access expected data directly so missing data raises a clear failure, such as using results["data"] instead of results.get("data").

Files:

• tests/integrations/test_harbor_runner.py

**/*.py

📄 CodeRabbit inference engine (CONTRIBUTING.md)

Use type annotations for public Python APIs and keep native binding declarations synchronized with their Rust implementations.

Files:

• tests/integrations/test_harbor_runner.py

**/*.{rs,py,json}

📄 CodeRabbit inference engine (CONTRIBUTING.md)

When adding functionality, include tests in the corresponding Rust crate or relevant tests/ area; public contract changes must keep checked-in JSON Schema snapshots and native Python binding declarations synchronized.

Files:

• tests/integrations/test_harbor_runner.py

{tests/**,python/tests/**}

⚙️ CodeRabbit configuration file

{tests/**,python/tests/**}: Tests should cover the behavior promised by the changed API surface, including error paths, lifecycle cleanup, and SDK/native parity where relevant.

Files:

• tests/integrations/test_harbor_runner.py

🔇 Additional comments (2)

examples/harbor/swebench/README.md (1)

30-30: 🩺 Stability & Availability

Verify that nemo-fabric==0.1.0 is available from Harbor’s package index.

The public PyPI endpoint for this exact release currently returns 404. Because FABRIC_PACKAGE is passed to the installation flow, Harbor will fail unless it resolves dependencies from another index containing 0.1.0. ()

As per coding guidelines, examples must remain aligned with current package names and build commands.

Source: Coding guidelines

tests/integrations/test_harbor_runner.py (1)

333-333: LGTM!

[zhongxuanwang-nv]

Thanks David!

[dagardner-nv]

/merge