Container View

Container View

Container	Responsibility	Technology
VM provisioning (vm/windows-labview/, vm/ubuntu-labview/)	Create, register, and track self-hosted build/test VMs as GitHub Actions runners	PowerShell, Bash, Python, VirtualBox, NSIS
Native SBOM pipeline (root Run-Pipeline.ps1, Build-Sbom.ps1, internal/, Test-SbomArtifact.ps1, Test-Environment.ps1)	Run the LabVIEW build-and-report pipeline directly on a self-hosted Windows runner (no Linux equivalent exists in this repo; Run-Pipeline.sh is a separate, unrelated LabVIEWCLI MassCompile/VI Analyzer tool for NI's own example VIs, not a SBOM pipeline)	PowerShell, Python
Containerized SBOM pipeline (docker/linux-sbom/, docker/windows-sbom/, root Run-LinuxSbom.ps1/Run-WindowsSbom.ps1 host-side launchers)	Run the same pipeline inside a container image	Docker, PowerShell, Python
Project registration (add-project.yml, Add-Project.ps1)	Validate and upsert a project's pipeline config into a consumer's repository variables	GitHub Actions, Python, PowerShell
Human escalation (New-HumanEscalation.ps1, Get-HumanEscalations.ps1)	Create/update structured, labeled GitHub issues for agent-unsolvable blockers	PowerShell, gh CLI
Repo onboarding (Enable-RepoIssueTracking.ps1)	Idempotently enable Issues + seed the escalation label on a repo	PowerShell, gh CLI
Standards compliance (docs/architecture/, this wiki, standards-compliance-recheck.yml, standards-assurance-scan.yml)	Stamp and re-check this repo's compliance against repo-standards-review	Markdown, GitHub Actions, self-hosted runner
Release automation (.github/workflows/release.yml)	Tag and publish a GitHub Release (draft-first) from a matching CHANGELOG.md section	GitHub Actions, gh CLI
Agent orientation (.github/skills/projectbuddy-identity/)	Orients an AI coding agent/session on what this repo is, its consumption model, and known open threads	Markdown, YAML (agent-platform skill format)
LUnit release gate (planned, #87, phased per ADR-0003)	Build a fresh, GitHub-hosted-runner ephemeral Windows/Linux LabVIEW container, deploy SHA-256-verified LUnit/LUnit CLI packages (no VIPM), run a pinned-commit ni/labview-icon-editor test suite via LabVIEWCLI, and gate releases on a passing, commit-bound JUnit report once both a Windows spike and a Linux feasibility spike succeed -- replaces persistent-VM GUI-activation as this engine's proof of real LabVIEW test execution, without retiring the VM families or resolving #62's separate VM-dispatch question	Docker, nationalinstruments/labview images, LabVIEWCLI, GitHub Actions
Agent diagnostics (#102, per ADR-0005)	Decode labview-benchmark-actor VS Code extension capture output (an external, independently-versioned schema this engine does not control) into a structured summary for agent/operator LabVIEW-VM troubleshooting -- read-only, diagnostic-only, never a CI gate	Python