Investigate Blacksmith-backed GitHub Actions jobs stuck in queued state #69

Summary

Multiple GitHub Actions workflows that target blacksmith-* runners are staying queued instead of starting.

Evidence

Observed on March 26, 2026 while validating PR #68:

• test workflow run 23616917858 remained queued
  • unit (linux) queued on blacksmith-4vcpu-ubuntu-2404
  • unit (windows) queued on blacksmith-4vcpu-windows-2025
  • e2e (linux) queued on blacksmith-4vcpu-ubuntu-2404
  • e2e (windows) queued on blacksmith-4vcpu-windows-2025
• pr-management workflow run 23616917903 remained queued
  • check-duplicates queued on blacksmith-4vcpu-ubuntu-2404
• unrelated scheduled workflow beta run 23618573256 is also queued

At the same time, workflows on ubuntu-latest completed normally:

• pr-standards completed successfully for PR fix: handle symlinked local install target #68
• vouch-check-pr completed successfully for PR fix: handle symlinked local install target #68
• scheduled compliance-close runs are completing successfully

Impact

PRs can appear blocked even when the code change is locally validated and the non-Blacksmith checks are green.

Suspected area

Runner availability or Blacksmith integration health for both Linux and Windows queues.

Related

• PR fix: handle symlinked local install target #68
• this is separate from the code fix in issue Fix bun run install:local when ~/.local/bin/opencode is a symlink to the current build #67