Problem
CI checks out and builds the pinned Home runtime at $GITHUB_WORKSPACE/Home/lang/zig-out/bin/home-tool, but build-backed Home-tool gates can still resolve build.zig’s workstation fallback ($HOME/Code/Home/lang/zig-out/bin/home-tool). On GitHub-hosted runners that path does not exist.
Current failures:
Both jobs successfully build the pinned Home checkout first, then fail their Zig build run artifacts with exit 127 at /home/runner/Code/Home/lang/zig-out/bin/home-tool. Relying on ambient HOME_TOOL environment lookup is no longer sufficient with current Zig build behavior.
Required implementation
- Pass
-Dhome-tool="$GITHUB_WORKSPACE/Home/lang/zig-out/bin/home-tool"explicitly to every CIzig buildgate that executes repository TypeScript tools. - Keep the local documented fallback for developer machines.
- Avoid symlink/path workarounds and do not silently skip tool-backed gates.
- Audit all workflow build invocations so direct and build-backed Home-tool calls use the same pinned checkout.
Acceptance
threads-reference-audit,threads-reference-probes, andbenchmark-comparison-testexecute the pinned CI binary.- No
/home/runner/Code/Homefallback appears in their logs. - Dependency inventory and workflow YAML remain valid.