refactor(inference): make the catalog own vLLM profiles

[prekshivyas]

Summary

Move the existing managed vLLM model and hardware profile matrix into the compiled managed-inference catalog. Runtime selection, profile listing, model preparation, and probe policy now derive from the same declarative source instead of duplicating model-specific TypeScript branches.

This foundation preserves the current supported matrix. It does not add Linux Muse Glimmer or Nemotron 3.5 Lightning profiles and does not change vLLM or llama.cpp port behavior.

Depends on #9660, which refreshes the llama.cpp image's Ubuntu curl package tuple. This PR does not otherwise change the llama.cpp image.

Design context: managed inference catalog and declarative profile migration.

Changes

• Add versioned model YAML resources and a model schema to the managed-inference catalog compiler.
• Migrate the currently supported Spark, Station, N1x, and generic Linux vLLM profiles and recipes into YAML.
• Derive the vLLM registry, runtime variants, defaults, preparation steps, orchestration references, and endpoint probe policies from compiled catalog data.
• Route explicit provider/model intent through declarative requirements and materialize selected host-local recipes into the existing runtime boundary.
• Add host architecture, compute capability, GPU memory, and unified-memory facts used by catalog qualification.
• Add compiler, resolver, registry, materialization, profile-list, runtime-selection, and package-contract coverage. The catalog-only model test protects the requirement that a new model/profile can be discovered without editing the TypeScript registry.

The compiler boundary is required because catalog resources are consumed by the CLI, packaged artifact, profile list, resolver, and runtime launcher. Keeping independent TypeScript model tables would allow those consumers to drift and would continue requiring code changes for each profile.

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:
• 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; scripts/prepare-dgx-station-host.sh is unchanged.
• Station profile/scenario: Existing profile migration only.
• Result: Not applicable.
• Supporting evidence: Not applicable.

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 validate:pr passed after refreshing origin/main when hooks were skipped or unavailable
• Targeted behavior tests pass for the current change set, or tests are marked not applicable above — 460/460 focused CLI tests, 52/52 integration tests, and 2/2 package-contract tests passed. CI-regression coverage also passed for 112/112 llama.cpp image tests, 80/80 Station preparation tests, 14/14 Station controller tests, 3/3 onboarder tests, and 1/1 Docker-authority test.
• Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result:
• 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)
• Doc pages follow the style guide (doc changes only)
• New doc pages include SPDX header and frontmatter (new pages only)

Additional verification:

• npm run catalog:compile
• npm run catalog:check
• npm run build:cli
• npm run typecheck:cli
• npm run validate:pr

---

Signed-off-by: Prekshi Vyas prekshiv@nvidia.com

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

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

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: adb7beb4-8ccc-460a-8e80-1715b94fdc38

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

---

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

[github-actions]

PR Review Advisor — Informational

Advisor assessment: Informational / low confidence
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions
Status: PR review advisor failed: PR review advisor SDK execution failed: session: investigate omitted required analysis; turn: investigate: investigate omitted required analysis

Model lanes

• GPT-5.6 Terra (primary): Failed
• Nemotron 3 Ultra (second opinion): Failed

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite for the commit under review.

Recommended E2E: inference-routing

Manual-only E2E: cloud-onboard, managed-image-multiarch-startup, security-posture, onboard-repair, onboard-resume, cloud-inference, network-policy
The manual PR workflow does not run these selectors for the commit under review. Run them from reviewed code on main.

Workflow run details

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

[github-actions]

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

[github-code-quality]

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall line coverage in commit b55196f in the agent/managed-infere... branch remains at 96%, unchanged from commit dbf48ba in the main branch.

---

_{Updated August 19, 2026 18:40 UTC}