Repository actions

Run action scripts from the repository root. The documentation build is part of the Pages publication contract; it never installs its renderer.

Full CI contract

bash actions/validate.runtime.sh

The full orchestrator expects the pinned validation environment and executes the Ansible NVIDIA fact fixture. For a shell-only local review, run:

bash actions/test.documentation-contract.sh
bash actions/test.publication-manifest.sh
bash actions/test.runner-contract.sh
bash actions/test.gpu-contract.sh --shell-only
bash actions/test.ipmctl-contract.sh --shell-only
bash actions/test.llm-host-contract.sh --shell-only
bash actions/test.nvidia-contract.sh --shell-only
bash actions/test.nvlink-contract.sh --shell-only

These checks have no install or deployment side effect. Rendering/publishing commands are documented separately because they intentionally write a selected output directory. The LLM reviewed-source contract is intentionally left to GitHub Actions; CUDA compilation and runtime acceptance are performed only on the remote GPU host.

• Build documentation
• Publish Pages tree
• Validate runtime
• Validate Pages
• Action validation libraries
• Test documentation contract
• Test publication manifest
• Test shared runner contract
• Test sudo access policy
• Test runner staging
• Test GPU contract
• Test ipmctl contract
• Test LLM host contract
• Test LLM reviewed-source contract
• Test NVIDIA contract
• Test NVIDIA facts
• Test NVLink contract

www.pages.sh replaces its selected publish directory. Contract validation only reads project content, aside from temporary fixture locations. The ipmctl contract validates the vendored patch pack and exact pins statically; source compilation and hardware acceptance occur only on the target host.