test(policy): align command coverage loader

[cv]

Summary

Align the policy command builder test with the CommonJS-compatible loader used by policy and Shields tests. This prevents Vitest V8 coverage from splitting the same source across loader identities and dropping strict per-file coverage after shard rebalancing.

Changes

• Load the policy command builders through the existing CommonJS-compatible test seam.
• Keep direct assertions for every policy command builder and both gateway argument branches.

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: Only src/lib/policy/commands.test.ts changes; production policy behavior is unchanged. CI will run the strict merged coverage gate.
• 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:
• Station profile/scenario:
• Result:
• Supporting evidence:

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 — Normal pre-commit and commit-msg hooks passed during commit and pre-push hooks passed during publication.
• Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result or justification: focused policy command coverage passed (2 tests), with every commands.ts function covered. npm run typecheck:cli and npm run checks:repository passed.
• Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result: The authoritative 12-shard merged coverage gate will run in PR CI; local full-shard experiments were not completed.
• 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)

---

Signed-off-by: Carlos Villela cvillela@nvidia.com

Summary by CodeRabbit

• Tests
  • Updated test module loading to improve compatibility with the test environment.

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

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 6e74663c-10c5-481e-9b24-555defed7a3c

📥 Commits

Reviewing files that changed from the base of the PR and between 7428260 and c76a5a2.

📒 Files selected for processing (1)

• src/lib/policy/commands.test.ts

Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review.

---

📝 Walkthrough

Walkthrough

The policy command test replaces its static module import with a typed CommonJS require binding. The imported command builders remain unchanged.

Changes

Policy test import

Layer / File(s)	Summary
Typed CommonJS import src/lib/policy/commands.test.ts	The test uses a CommonJS require binding typed with typeof import("./commands.js").

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to c76a5

This change only updates policy test loading and does not alter production behavior; no actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: apurvvkumaria

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main change: aligning the policy command test coverage loader.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
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.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1 files.

✨ 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 fix/policy-coverage-loader-final

---

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