Opened Chrome using the Sam profile and navigated to GitHub Billing and licensing. The billing overview showed the exact blocker: GitHub says 100% of the Actions budget has been used and additional usage will be stopped. Clicked Update your budget and reached Edit monthly budget for Product: Actions, Budget scope: Account.
The visible budget amount is $50. Stop usage when budget limit is reached is checked. Receive budget threshold alerts is checked. I stopped before clicking Update budget because that is the cost-changing step.
Increase the Actions monthly budget above current usage, for example to $100 as a finite cap, leave threshold alerts enabled, then click Update budget. Alternative is unchecking stop-usage, but that is less controlled.
Sam updated the GitHub Actions budget on 2026-05-28. The red 100% budget stop banner disappeared on refresh. I dispatched sail-seo workflow Weekly Site Audit in smoke mode to verify Actions could run again.
First smoke run proved dispatch worked but failed because sail-seo had no Actions secrets configured. I synced the exact required repo secrets from the local vault: AHREFS_API_KEY, AHREFS_MCP_TOKEN, WP_APP_USER, WP_APP_PASSWORD, SSH_HOST, SSH_USER, SSH_PORT, and SSH_PASS. PAGESPEED_API_KEY is still missing from the vault, but the smoke path does not require it.
Second smoke run succeeded: https://github.com/samaguiar1982-cpu/sail-seo/actions/runs/26594062569
The GitHub Actions budget block is cleared and a real smoke workflow completed successfully. Remaining optional cleanup is to add PAGESPEED_API_KEY before running the full audit mode.
Future agents should treat the GitHub Actions day-15 billing block as resolved unless a newer run shows the budget warning again. If running full audit mode on sail-seo, add or verify PAGESPEED_API_KEY first.
Sam selected Option A on 2026-05-28: treat the GitHub Actions block as resolved because the sail-seo smoke workflow completed successfully.