Avenger: enforce 8-minute runtime budget and failure-driven repair flow

[Copilot]

The Avenger workflow was failing in the agent job because the prompt encouraged broad, long-running local checks that exceeded the execution window. This update tightens the prompt so Avenger finishes within 8 minutes by triaging from the failing CI run first and only running targeted remediation.

• Problem framing

  • Shifted Avenger from “run broad maintenance steps” to “inspect failing CI signal, then apply smallest matching fix.”

• Prompt changes for bounded execution

  • Added a hard runtime requirement: complete within 8 minutes.
  • Added explicit prohibitions on expensive/unbounded patterns:
    • go build ./...
    • direct go test ./... / go test ./pkg/...
    • background polling loops (sleep + pgrep + repeated tail).

• Failure-driven repair sequence

  • Added a mandatory step to inspect ${{ needs.check_ci_status.outputs.ci_run_id }} first.
  • Made fmt/wasm/lint/test steps conditional on the detected failure category instead of running unconditionally.
  • Added early noop exit for non-actionable infra/transient failures.

• Compiled workflow parity

  • Regenerated avenger.lock.yml to keep compiled workflow metadata and prompt body in sync.

## Runtime Budget (Hard Requirement)

- Finish the entire run (analysis + fix + validation + PR/noop) within **8 minutes**.
- Keep commands targeted to the failing CI signal.
- Never run `go build ./...` or `go test ./...`/`go test ./pkg/...` directly.
- Never run background long-running checks with polling loops (`sleep` + `pgrep` + repeated `tail`).

[Copilot]

Pull request overview

Updates Avenger toward failure-driven CI repairs with an eight-minute prompt budget.

Changes:

• Adds targeted CI-failure inspection and conditional remediation.
• Prohibits broad or long-running validation commands.
• Regenerates compiled workflow metadata.

Show a summary per file

File	Description
.github/workflows/avenger.md	Revises Avenger’s repair prompt and runtime guidance.
.github/workflows/avenger.lock.yml	Synchronizes generated metadata and description.

Review details

Suppressed comments (1)

.github/workflows/avenger.md:195

• The mandatory failure triage is still Step 3, after the checkout has been merged and the potentially broad recompile step has been considered. Because the execution guidelines explicitly say to process steps in sequence, this does not implement the PR's stated “inspect the failing CI signal first, then remediate” flow. Move this inspection directly after Step 0 and perform merge/recompile only after an actionable failure category is known.

## Step 3: Inspect the failing CI run first (mandatory)

Use the CI Run ID from pre-check and identify the first failed job and failing signal before running any local validation:

• Files reviewed: 2/2 changed files
• Comments generated: 2
• Review effort level: Balanced

[github-actions]

🎉 This pull request is included in a new release.

Release: v0.87.1