docs(platform): mark DGX Station tested with limitations#7327
Conversation
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
📝 WalkthroughWalkthroughDGX Station platform, provider, onboarding, and installer guidance now describe tested-with-limitations coverage for one qualifying GB300, while documenting that dual-Station configurations remain unvalidated and lack dedicated CI coverage. Prompt assets and tests were synchronized with the revised wording. ChangesDGX Station qualification messaging
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
🌿 Preview your docs: https://nvidia-preview-pr-7327.docs.buildwithfern.com/nemoclaw |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall coverage in commit da664fc in the TypeScript / code-coverage/cliThe overall coverage in commit da664fc in the Show a code coverage summary of the most impacted files.
Updated |
PR Review Advisor — InformationalAdvisor assessment: Informational / high confidence Model lanes
Nemotron output stays in workflow artifacts and does not change the assessment above. E2E guidanceAdvisory only. E2E / PR Gate selects and runs jobs independently. Recommended E2E: 1 optional E2E recommendation
This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge. |
There was a problem hiding this comment.
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/changelog/2026-07-14.mdx`:
- Around line 8-18: Update the DGX Station GB300 support classification in the
changelog entries describing the express-install path and its availability,
replacing “Deferred” with “Tested with limitations” while preserving the
qualification that this applies to one qualifying GB300 system.
🪄 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: cf095acd-4211-4ffb-be38-ec199f2a9b1b
📒 Files selected for processing (14)
ci/platform-matrix.jsondocs/changelog/2026-07-14.mdxdocs/get-started/dgx-station-preparation.mdxdocs/get-started/prerequisites.mdxdocs/get-started/quickstart.mdxdocs/inference/choose-inference-provider.mdxdocs/inference/set-up-vllm.mdxdocs/reference/platform-support.mdxdocs/resources/prompt-assets/dgx-station.mddocs/resources/starter-prompt.mdscripts/install.shtest/install-express-prompt.test.tstest/starter-prompt-docs.test.tstest/station-doc-ownership.test.ts
There was a problem hiding this comment.
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 `@test/station-doc-ownership.test.ts`:
- Around line 65-74: Add assertions for the exact “dedicated CI coverage is not
available” caveat in both canonical-page content variables, stationPreparation
and quickstart. Keep the existing boundary assertions unchanged and ensure each
page’s observable documentation contract is covered.
🪄 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: fa8c04e9-e63a-4493-ad09-f73868372f2b
📒 Files selected for processing (13)
ci/platform-matrix.jsondocs/get-started/dgx-station-preparation.mdxdocs/get-started/prerequisites.mdxdocs/get-started/quickstart.mdxdocs/inference/choose-inference-provider.mdxdocs/inference/set-up-vllm.mdxdocs/reference/platform-support.mdxdocs/resources/prompt-assets/dgx-station.mddocs/resources/starter-prompt.mdscripts/install.shtest/install-express-prompt.test.tstest/starter-prompt-docs.test.tstest/station-doc-ownership.test.ts
🚧 Files skipped from review as they are similar to previous changes (10)
- docs/resources/prompt-assets/dgx-station.md
- docs/get-started/prerequisites.mdx
- docs/inference/choose-inference-provider.mdx
- test/install-express-prompt.test.ts
- docs/reference/platform-support.mdx
- docs/get-started/quickstart.mdx
- docs/resources/starter-prompt.md
- scripts/install.sh
- docs/inference/set-up-vllm.mdx
- test/starter-prompt-docs.test.ts
|
Advisor follow-up for head
|
senthilr-nv
left a comment
There was a problem hiding this comment.
Reviewed the accepted #6951 scope, documentation contracts, installer disclosure, immutable prompt-asset pin, focused tests, and current CI. The four qualified Station profiles and remaining dual-Station/dedicated-CI limitations are stated consistently. No blocking findings. This can be merged once main is stable.
<!-- markdownlint-disable MD041 --> ## Summary Add the canonical `v0.0.91` changelog entry that was missed before the release tag was cut. Correct the custom-image compatibility guidance because the tagged code still accepts the legacy inference route selector instead of removing it in v0.0.91. ## Changes - Add `docs/changelog/2026-07-22.mdx` with the release summary and detailed security, rebuild, Hermes, DGX Station, and historical-validation changes from the published v0.0.91 announcement. - Link shipped behavior to the most specific published OpenClaw and Hermes documentation routes. - Correct the v0.0.90 changelog and command reference so they match the compatibility fallback present in the tagged v0.0.91 code without inventing a new removal version. - Keep the immutable v0.0.91 release tag unchanged; this is the documented post-release recovery path. Source summary: - [#7332](#7332), [#7289](#7289), and [#7294](#7294) -> `docs/changelog/2026-07-22.mdx`: Summarize completed-image `node-tar` remediation and current and historical container verification. - [#7213](#7213), [#7363](#7363), [#7366](#7366), and [#7369](#7369) -> `docs/changelog/2026-07-22.mdx`: Summarize trusted base preparation, backup reuse, deletion convergence, and rebuild confidence. - [#7212](#7212) -> `docs/changelog/2026-07-22.mdx`: Summarize the Hermes API bearer-token lifecycle and supported retrieval command. - [#7327](#7327) and [#7328](#7328) -> `docs/changelog/2026-07-22.mdx`: Summarize qualified DGX Station guidance and reproducible coding-agent installation instructions. - [#7355](#7355), [#7360](#7360), [#7362](#7362), and [#7364](#7364) -> `docs/changelog/2026-07-22.mdx`: Summarize restored historical OpenClaw upgrade and Hermes rebuild validation. - [#7189](#7189) -> `docs/changelog/2026-07-20.mdx`, `docs/reference/commands.mdx`: Correct its forward-looking removal deadline after v0.0.91 shipped with the documented legacy fallback still present. - [#7282](#7282), [#7306](#7306), and [#7341](#7341) need no additional user-guide update because they already update their owned contributor or user-facing text directly. ## 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 dated changelog structure, SPDX syntax, version ordering, and published routes. - [ ] Tests not applicable — justification: - [x] 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: ## DGX Station Hardware Evidence - [ ] Tested on DGX Station - Tested commit: Not applicable; this documentation-only PR does not change Station preparation or runtime behavior. - 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 check:diff` passed 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` (6 passed). - [ ] Applicable broad gate passed — `npm test` for broad runtime/test-harness changes; `npm run check` for repo-wide validation/coverage changes — not run; this is a focused documentation-only change. - [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) — completed with 0 errors and 2 existing site-wide 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 native changelog entry uses the required parser-safe MDX SPDX comment and intentionally has no frontmatter. --- Signed-off-by: Apurv Kumaria <akumaria@nvidia.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Updated v0.0.91 guidance for custom Dockerfiles, including continued legacy compatibility and recommended migration to `NEMOCLAW_INFERENCE_PROVIDER_ID`. * Added release notes covering image security scanning, safer rebuild behavior, token management, DGX Station guidance, and deterministic release validation. * Clarified that existing custom images may continue using the legacy selector temporarily, with fallback removal planned for a future release. <!-- end of auto-generated comment: release notes by coderabbit.ai --> Signed-off-by: Apurv Kumaria <akumaria@nvidia.com> Co-authored-by: cjagwani <cjagwani@nvidia.com>
<!-- markdownlint-disable MD041 --> ## Summary The OpenClaw, Hermes, and Deep Agents Quickstarts now keep separate source pages with consistent first-run platform ownership. Each Quickstart retains immediate Docker, Windows, DGX Station, Express, and model choices while linking durable details to their canonical owners. The refactor preserves published Quickstart routes, navigation, supported workflows, and Commands and Troubleshooting content. ## Changes - Condense duplicated Docker and platform prose in all three Quickstarts into concise first-run summaries and canonical links. - Keep Docker installation behavior in Prerequisites, Windows preparation in its focused setup page, Station qualification and preparation in the Station page, managed model and headless workflows in Set Up vLLM, and validation status in Platform Support. - Preserve Hermes-specific remote dashboard and API setup, including `CHAT_UI_URL`, port forwarding, and API bearer-token retrieval. - Make each Quickstart installer command set the sandbox name used by its subsequent status, dashboard, and connect commands. - Preserve the complete headless Station workflow and render the correct OpenClaw, Hermes, and Deep Agents selection. - Keep existing routes, navigation entries, and redirects unchanged while generating agent-variant content from the canonical source pages. - Incorporate merged PR #7331, including its PackageKit boundary, without duplicating its integration-policy change. - Incorporate merged PR #7327 while keeping Platform Support as the canonical Station validation-status owner. - Incorporate merged PR #7285 while keeping its existing-vLLM ownership handoff in the canonical Station preparation page. ## Product Scope Verdict: In scope. The diff reorganizes existing Quickstart, Station, and vLLM documentation and updates its ownership test. It does not add an integration, solution recipe, custom image, third-party stack, or supported product surface. ## Type of Change - [ ] Code change (feature, bug fix, or refactor) - [ ] Code change with doc updates - [ ] Doc only (prose changes, no code sample modifications) - [x] Doc only (includes code sample changes) ## Quality Gates - [x] Tests added or updated for changed behavior - [ ] Existing tests cover changed behavior — justification: - [ ] Tests not applicable — justification: - [x] 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: ## DGX Station Hardware Evidence <!-- Required only when scripts/prepare-dgx-station-host.sh changes. Maintainers must review the linked evidence before approving or merging. This is human-reviewed evidence, not authenticated hardware provenance. Exceptional bypasses use existing repository governance and must be documented on the PR. --> - [ ] Tested on DGX Station - Tested commit: Not applicable; `scripts/prepare-dgx-station-host.sh` is unchanged in the PR diff. - Station profile/scenario: Documentation ownership refactor only. - 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 check:diff` passed when hooks were skipped or unavailable — canonical-base diff-aware hook stages passed against `upstream/main`. - [x] Targeted behavior tests pass for the current change set, or tests are marked not applicable above — `npx vitest run test/station-doc-ownership.test.ts test/check-docs-published-routes.test.ts test/check-docs-links.test.ts` (3 files, 44 tests passed). - [ ] Applicable broad gate passed — Not applicable; this is a focused documentation ownership refactor with targeted tests and the full docs build. - [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 2 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) — Not applicable; no pages were added. Additional validation: - `npm run docs:sync-agent-variants` - `npm run docs` - `npm run source-shape:check` - `git diff --check upstream/main...HEAD` - Generated OpenClaw, Hermes, and Deep Agents Set Up vLLM variants contain the expected agent selection and no residual `<AgentOnly>` directives. - Repository-required documentation writer agent review found no content loss, inaccurate claim, route or anchor drift, or agent-variant regression. This was not a human review. - Automated nine-category security review found no security issue in the documentation and ownership-test diff. This was not a sensitive-path or human security review. Adjacent pre-existing debt, intentionally outside this refactor: - The standalone Station override command and the generic installer command printed by Windows preparation omit `NEMOCLAW_AGENT`, so users following those commands directly must return to the agent-specific Quickstart to preserve Hermes or Deep Agents selection. --- Signed-off-by: Miyoung Choi <miyoungc@nvidia.com> Signed-off-by: Senthil Ravichandran <senthilr@nvidia.com> --------- Signed-off-by: Miyoung Choi <miyoungc@nvidia.com> Signed-off-by: Senthil Ravichandran <senthilr@nvidia.com> Co-authored-by: Senthil Ravichandran <senthilr@nvidia.com> Co-authored-by: Carlos Villela <cvillela@nvidia.com>
Summary
Physical validation on one DGX Station GB300 now covers generic Ubuntu 24.04 ARM64, stock DGX OS
7.5.0, the April 2026 NVIDIA Colossus BaseOS profile, and the June 2026 NVIDIA AI Developer Tools profile, but the platform matrix still classified all Station configurations as Deferred.This change sets the platform status to Tested with limitations and states that dual-Station configurations and dedicated CI coverage remain pending.
Related Issue
Fixes #6951.
Changes
DGX OS (Station)matrix entry tocaveatedwhile keepingci_testedfalse.Type of Change
Quality Gates
DGX Station Hardware Evidence
7.5.0run tested commit:7a7414b3d80a9cb38257a276cd926fd48a93ec0e7.5.0, April 2026 NVIDIA Colossus BaseOS, and June 2026 NVIDIA AI Developer Tools on one physical DGX Station GB300.0with released OpenShell0.0.85, local Nemotron Ultra, sandbox CUDA, bounded sysfs policy, and Hermes one-shot and TUI file-tool tasks.Verification
Signed-off-by:line and every commit appears asVerifiedin GitHubpre-commit,commit-msg, andpre-pushhooks passed, ornpm run check:diffpassed when hooks were skipped or unavailablenpm testfor broad runtime/test-harness changes;npm run checkfor repo-wide validation/coverage changes — command/result: Not run; focused generator, installer-disclosure, and documentation-contract tests cover this change.npm run docsbuilds without warnings (doc changes only) — 0 errors and 1 Fern warning.Signed-off-by: Miyoung Choi miyoungc@nvidia.com