[ci-scan-feedback] Add pipeline-category gate to fixer prompt

[Copilot]

The CI failure fixer ignored the advisory fix-policy table and opened a help-wanted PR proposing a product-code workaround for a PGO codegen bug (#129360). The fix-policy table listed JIT/GC/PGO codegen as out-of-bounds, but nothing enforced it.

Changes

• .github/workflows/ci-failure-fix.md — Inserted a mandatory Step 5.1.1 "Pipeline-category gate" between the fix-policy table (Step 5.1) and the fix-attempt step (Step 5.2). The gate:
  • Parses the KBE's pipeline metadata: build definition id (from the Build: link / AzDO API) plus the pipeline/definition name and failing-leg name.
  • Treats the KBE as JIT/GC/PGO stress — out of bounds for any fix or workaround PR — when the definition id is in 109–160, 230, or 235, or the name/leg matches (case-insensitive) jitstress|gcstress|pgo|r2r|superpmi|jit-cfg|jit-experimental|interpreter.
  • Short-circuits matching KBEs directly to the loop-in comment path (Step 5.5), explicitly forbidding both product fixes and sidestep workarounds (e.g. buffer-size normalization), and records a routing reason.
  • Otherwise falls through to Step 5.2 unchanged.

This converts the existing fix-policy table from advisory to enforceable, routing codegen-stress KBEs to a loop-in comment instead of an out-of-bounds workaround PR.

Notes

• Prompt-only change. ci-failure-fix.lock.yml imports the markdown at runtime via {{#runtime-import .github/workflows/ci-failure-fix.md}}, so no lock-file recompilation is required.

[Copilot]

Pull request overview

This PR updates the CI Outer-Loop Failure Fixer prompt to enforce the existing “JIT/GC/PGO stress (codegen)” out-of-bounds policy by adding a mandatory pipeline-category gate step before any fix attempt. The goal is to prevent the workflow from opening workaround PRs for codegen-stress failures and instead route those KBEs directly to the loop-in comment path.

Changes:

• Adds Step 5.1.1 “Pipeline-category gate” between the fix-policy table (Step 5.1) and fix attempt (Step 5.2).
• Defines gating criteria based on AzDO build definition ID ranges and pipeline/leg name keyword matches.
• Specifies a required short-circuit routing message and directs gated KBEs to Step 5.5 (loop-in comment), reinforcing “no PR” behavior for those pipelines.

Show a summary per file

File	Description
.github/workflows/ci-failure-fix.md	Adds a mandatory pipeline-category gate step to route JIT/GC/PGO/codegen-stress KBEs directly to loop-in comments instead of attempting fixes/workarounds.

Copilot's findings

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

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.