docs(station): document OTA metadata fallback

[miyoungc]

Summary

This change documents the approved DGX Station OTA metadata fallback in the canonical Station preparation guide.
It states the public hardware boundary as recognized GB300 hardware while keeping exact PCI identifiers and the accepted-variant count as implementation details.

Changes

• #7223 -> docs/get-started/dgx-station-preparation.mdx: Document that qualification uses the latest reviewed DGX_OTA_VERSION; DGX_OTA_PRETTY_NAME must equal DGX OS when present; and marker-less OTA hosts require DGX_PRETTY_NAME=NVIDIA DGX GB300WS.
• Preserve the safe, root-owned release-file gate and DGX_PLATFORM=DGX Server for GALAXY-GB300 requirement.
• Describe the public PCI qualification boundary only as recognized GB300 hardware, without publishing identifiers or an accepted-variant count.
• Extend test/station-doc-ownership.test.ts to protect canonical ownership, the fallback wording, the public hardware term, and identifier exclusion.
• Leave Quickstart, Platform Support, and provider-selection summaries unchanged because their canonical links and summary-level statements remain accurate.
• Rebase on merged PackageKit documentation PR docs: clarify policy preview and Station package state #7331. The unpublished Quickstart deduplication work touches the ownership test nearby, so whichever branch lands second may need a mechanical rebase without a semantic wording dependency.

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:
• 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: At PR SHA 8cf7b91, the focused integration test passed 1 file and 4 tests. npm run docs passed with the route checker OK, 0 errors, and 2 existing Fern warnings. npm run check:diff passed. The exact-head review found no documentation issues: the OTA marker and fallback wording matches the implementation, the force override is limited to recognized GB300 hardware, and the ownership test excludes raw device IDs.
• Agent: Codex Desktop

DGX Station Hardware Evidence

• Tested on DGX Station
• Tested commit: Not applicable.
• Station profile/scenario: Documentation-only clarification of merged behavior.
• Result: No host behavior changed.
• Supporting evidence: Merged PR fix(installer): accept OTA-upgraded DGX OS on Station GB300 without image marker #7223 and the current Station classifier and hardware-detection tests.

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 check:diff passed when hooks were skipped or unavailable
• 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/changelog-docs.test.ts: 2 files and 10 tests passed.
• Applicable broad gate passed — Not run; focused documentation tests and the docs build cover this change.
• 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. Fern reported the existing light-mode accent contrast warning.
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

---

Signed-off-by: Miyoung Choi miyoungc@nvidia.com

Summary by CodeRabbit

• Documentation

  • Refined DGX Station qualification guidance for GB300 systems, including how OTA hosts qualify using the latest OTA version and accepted version ranges.
  • Clarified DGX_OTA_PRETTY_NAME expectations (including when it may be omitted after OTA upgrades) and strengthened DGX_PRETTY_NAME requirements when DGX_OTA_PRETTY_NAME is absent.
  • Tightened the warning for --force-station-install to specify it should only be used when automatic Station detection rejects recognized GB300 /etc/dgx-release metadata.

• Tests

  • Enhanced documentation ownership checks to validate OTA/GB300-specific text and key qualification requirements.

[copy-pr-bot]

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.

[coderabbitai]

📝 Walkthrough

Walkthrough

DGX Station documentation now defines additional DGX OS release-marker qualification rules and narrows --force-station-install guidance. Canonical documentation tests assert required GB300/OTA wording and reject obsolete token patterns.

Changes

DGX Station documentation

Layer / File(s)	Summary
DGX OS qualification rules docs/get-started/dgx-station-preparation.mdx	Documents DGX_OTA_VERSION, DGX_OTA_PRETTY_NAME, and fallback DGX_PRETTY_NAME requirements for stock and OTA-upgraded hosts.
Override warning and canonicality checks docs/get-started/dgx-station-preparation.mdx, test/station-doc-ownership.test.ts	Limits --force-station-install guidance to recognized GB300 metadata cases and adds assertions for required wording and disallowed token patterns.

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

Possibly related PRs

• NVIDIA/NemoClaw#7333: Updates the same DGX Station force-install warning and related documentation expectations.
• NVIDIA/NemoClaw#7419: Updates DGX Station GB300 qualification documentation and canonical-content tests.

Suggested labels: area: install

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: documenting the Station OTA metadata fallback.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/docs-station-ota-fallback

---

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

[github-actions]

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

[github-code-quality]

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit 8cf7b91 in the codex/docs-station-o... branch remains at 96%, unchanged from commit f764692 in the main branch.

TypeScript / code-coverage/cli

The overall coverage in commit 8cf7b91 in the codex/docs-station-o... branch remains at 80%, unchanged from commit f764692 in the main branch.

Show a code coverage summary of the most impacted files.

File	main f764692	codex/docs-station-o... 8cf7b91	+/-
src/lib/onboard...ndbox-create.ts	83%	33%	-50%
src/lib/onboard...-create-plan.ts	88%	75%	-13%
src/lib/onboard...ndbox-create.ts	91%	83%	-8%
src/lib/domain/.../connect-env.ts	97%	89%	-8%
src/lib/state/m...-acquisition.ts	89%	87%	-2%
src/lib/sandbox...rce-identity.ts	87%	87%	0%
src/lib/state/m...ock-identity.ts	95%	95%	0%
src/lib/shields/index.ts	71%	72%	+1%
src/lib/inferen...er-lifecycle.ts	65%	71%	+6%
src/lib/inferen...lama/process.ts	50%	100%	+50%

---

_{Updated July 24, 2026 03:06 UTC}

[github-actions]

PR Review Advisor — Informational

Advisor assessment: Informational / high confidence
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions
Status: No actionable findings remain in the canonical review ledger.

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 E2E selections match; severity counts match.

Nemotron output stays in workflow artifacts and does not change the assessment above.

E2E guidance

Advisory only. E2E / PR Gate selects and runs jobs independently.

Recommended E2E: None

1 optional E2E recommendation

• docs-validation

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

[prekshivyas]

Reviewed the documentation change, regression coverage, and current merge gates. All 56 checks are green; DCO and commit verification pass; no conflicts or unresolved major/critical review findings remain.