Enable explicit AI credit budget guard for Daily Compiler Quality workflow

[Copilot]

Production monitoring workflows have been intermittently exhausting token/credit budgets, and this escalation asks to ensure budget guards are actually enabled in affected heavy workflows. This change removes ambiguity for Daily Compiler Quality by making its per-run AI credit cap explicit in workflow frontmatter.

• Problem focus

  • Daily aggregation/monitoring runs are failing under budget exhaustion patterns.
  • max_ai_credits needed to be explicitly turned on for impacted workflow configuration.

• What changed

  • Workflow frontmatter
    • Added an explicit per-run budget to daily-compiler-quality.md:
      • max-ai-credits: 1000
  • Compiled workflow sync
    • Regenerated the corresponding lock metadata so compiled config reflects the updated frontmatter.

• Why this matters

  • Ensures the workflow consistently carries an explicit AI credit guardrail rather than relying on implicit/default resolution paths.
  • Aligns the workflow with the requested “make sure it is turned on” requirement.

on:
  schedule: daily
  workflow_dispatch: null
max-ai-credits: 1000
max-daily-ai-credits: 100M

[Copilot]

Pull request overview

This PR makes the Daily Compiler Quality workflow’s per-run AI credit cap explicit in its workflow frontmatter, ensuring the AWF budget guardrail is unambiguous and consistently applied, and then syncs the compiled lock metadata to match.

Changes:

• Added an explicit max-ai-credits: 1000 per-run budget to .github/workflows/daily-compiler-quality.md.
• Regenerated .github/workflows/daily-compiler-quality.lock.yml so the frontmatter_hash reflects the updated frontmatter.

Show a summary per file

File	Description
.github/workflows/daily-compiler-quality.md	Adds an explicit per-run AI credit budget guardrail in workflow frontmatter.
.github/workflows/daily-compiler-quality.lock.yml	Updates compiled metadata hash to reflect the frontmatter change.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0