Certify native Windows Source compiler execution

[dayflaree]

Objective

Complete future native Windows Source compiler validation when a Windows environment with real tools is available.

Background

Issue #133 now tracks the no-claim boundary that is actionable from the Linux maintainer environment. This issue preserves the original empirical certification goal for a future native Windows host or runner.

Required work

• Use a real Windows machine or Windows runner.
• Use real native Source compiler tools: VBSP, VVIS, and VRAD.
• Record exact compiler paths, versions if available, game/tool install context, and environment details.
• Run sourceweaver compile with those native tools.
• Capture per-step logs, exit codes, warnings/errors/leak status, generated BSP path, and artifact hashes.
• Update the compiler smoke-test matrix with a completed native Windows row.
• Post evidence with CI/session URLs when available.

Acceptance criteria

• Evidence is from native Windows execution.
• The row does not reuse Proton/Wine evidence.
• VBSP, VVIS, and VRAD all run through Source Weaver's compile pipeline.
• A generated BSP and logs are retained outside the repo with hashes.
• No proprietary tools, SDK binaries, game content, BSPs, or private assets are committed.

Non-goals

• Do not run this on Linux through Proton/Wine.
• Do not claim CI Windows Rust build/test coverage as Source compiler validation.

[dayflaree]

Blocker status checked after completing all currently actionable tickets.

Result

This remains open. I did not certify native Windows Source compiler execution because this session ran on a Linux host and no native Windows VBSP/VVIS/VRAD execution evidence exists.

Commands run

cd /home/elijah/projects/sourceweaver
git status --short --branch
gh issue view 142 --repo dayflaree/sourceweaver --json number,title,state,body,labels,comments
uname -a
command -v vbsp.exe || true
command -v vvis.exe || true
command -v vrad.exe || true
command -v cmd.exe || true
rg -n "Row B: Native Windows Source compiler execution|native Windows Source compiler execution is not certified|native Windows VBSP/VVIS/VRAD|future issue #142|windows-latest" docs/source-compiler-smoke-test-matrix.md docs/compatibility-matrix.md docs/release.md README.md CHANGELOG.md

Evidence

• Repository status before check: clean on main tracking origin/main.
• Current host is Linux.
• No native Windows command shell or native Windows VBSP/VVIS/VRAD executable path was available from the local shell.
• Docs keep Row B as not validated and explicitly separate CI Windows Rust checks, Windows packaging, and Proton/Wine rows from native Windows compiler evidence.

Blocker log:

c0f435d96a01d503fdb01c29547c813059b4746865a769b17d50b806bbe6ecc8  /tmp/sourceweaver-issue142-blocker-check.log

Required evidence to close later

• Native Windows host/session details.
• Native Windows VBSP, VVIS, and VRAD paths/versions.
• Real sourceweaver compile run through those native tools.
• Logs, exit codes, generated BSP hashes, game/tool context, and redistribution boundaries.

Redistribution and legal boundary

No native Windows Source compiler tools, SDK binaries, game content, BSPs, private paths, or private assets were committed or redistributed. This comment records the blocker and leaves the future-certification ticket open.

[dayflaree]

Completion-plan dependency update

This ticket is now part of the Completion certification and production readiness milestone.

Dependencies to close first or complete alongside this issue:

• Provision native Windows Source compiler certification host #157 — provision a native Windows host/self-hosted runner with real VBSP/VVIS/VRAD.
• Prepare legal certification fixtures and evidence workspace #159 — prepare legal VMF input and non-repo evidence workspace.
• Add external certification evidence bundle validator #160 — validate the evidence bundle shape before closure.

Closure path:

1. Use Provision native Windows Source compiler certification host #157 to get native Windows OS evidence and real vbsp.exe, vvis.exe, and vrad.exe paths/versions.
2. Use Prepare legal certification fixtures and evidence workspace #159 to supply a legal VMF input and standard evidence directory.
3. Run sourceweaver compile through native Windows tools only.
4. Capture VBSP/VVIS/VRAD logs, exit codes, generated BSP hash, and sanitized environment information.
5. Update docs/compatibility matrices in a commit, run the full local gate, push, wait for green CI, then close.

Wine/Proton evidence remains out of scope for this issue.

[dayflaree]

Tracker update from the 2026-08-08 full review:

This ticket is now active completion-certification work rather than a future placeholder. It remains blocked by #157. Use the #159 workspace seed bundle and validate the final evidence with #160.

Completion evidence should include: native Windows OS/build; proof that the tools are native vbsp.exe, vvis.exe, and vrad.exe; exact executable paths and versions; compile profile; command lines; exit codes; sanitized VBSP/VVIS/VRAD logs; generated BSP hash; Source Weaver report hash; legal/redistribution boundary; and validated/unvalidated claims.