ci: platform-prod-secrets reads the Linux runner pool (fix base guard red)
Fixes a base red in the CI guard group (runs 41493448800, 41493705936). test_no_workflow_adds_a_single_size_linux_job failed with {'platform-prod-secrets.yml': (1, 0)} != {}, and "Validate fork runner routing" failed too.
platform-prod-secrets.yml (added by #32470, dispatch-only since #32479) pinned vars.LINUX_RUNNER || 'blacksmith-4vcpu-ubuntu-2404', which is one size. It now resolves its runner the same way cloud-vm-env-audit.yml, the other cmux-next-production job, does: forks get ubuntu-24.04; otherwise vars.LINUX_RUNNER, then fromJSON(vars.RUNNER_POOLS).linux_4. One line; no change to steps, secrets or permissions.
Checked locally at this head:
tests/test_ci_linux_single_size.pyandtests/test_ci_fork_runner_routing.pypass; both fail on base.- The other python steps of the ci guard group were run as well.
test_ci_fleet_rule_lints,test_ci_merge_mainandtest_supplychain_securityfail identically on base in this checkout (a sparse checkout and local environment), so this change doesn't cause them.
Agent session: agent session
🤖 Generated with Claude Code
![Autofix with [code]smith](https://pr-comments-assets.blacksmith.sh/codesmith/autofix-with-codesmith-dark-3x.png)
Open in [code]smith · Need help on this PR? Tag @codesmith-bot with what you need.
Summary by cubic
Fixes the CI guard group reds by having platform-prod-secrets.yml resolve its runner from the Linux runner pool instead of pinning a single size. The job now reads runners the same way cloud-vm-env-audit.yml does: forks get ubuntu-24.04, otherwise vars.LINUX_RUNNER then fromJSON(vars.RUNNER_POOLS).linux_4. Steps, secrets, and permissions are unchanged.