GitHub Actions jobs fail before runner steps start

[support371]

Problem

Pull-request workflows are failing before any runner steps execute. This prevents CI from distinguishing code failures from infrastructure/account failures.

Latest evidence

PR #135, head cdabe0014e930d49b340196f681220e66108bf69:

• CI run 28756942761
  • Unit Tests: failure
  • returned step list: empty
  • Lint & Build: skipped
• CodeQL run 28756942763
  • Analyze (actions): failure with empty step list
  • Analyze (javascript-typescript): failure with empty step list

The same no-step failure pattern appeared on earlier Google Merchant PR runs, while independent Vercel preview builds succeeded.

Impact

• Required unit, lint, build, and CodeQL validation cannot execute.
• Pull requests must remain draft/unmerged even when a Vercel preview compiles.
• GitHub currently displays these as code-check failures even though no workflow step started.

Investigation checklist

1. Check GitHub Actions billing, spending limit, included minutes, and payment status.
2. Confirm Actions are enabled for the repository and organization/account.
3. Review repository Actions permissions and allowed-action policy.
4. Check for account-level suspension, usage restriction, or runner availability notices.
5. Re-run a minimal workflow after the account/runner condition is corrected.
6. Re-run the full CI and CodeQL workflows for PR fix(production): complete compliance pages, route hardening, and password recovery #135 before merging.

Merge gate

Do not merge PR #135 solely on Vercel preview success. Require a fresh CI run with visible checkout/install/test/lint/build steps and successful conclusions.

[support371]

Current follow-up on July 11, 2026:

• Canonical production main is now c35f2a85bc2dc1f5c3614a4120887122bd0de1cd.
• The GitHub connector reports no workflow runs associated with this commit.
• Vercel production is READY, but Vercel success is not a substitute for CI or CodeQL execution.

This issue therefore remains open. The next verification should produce a fresh workflow run with visible checkout/install/test/lint/build steps before any pending feature PR is merged.