Problem
The maintainer workflow can declare a PR complete after review without explicitly checking performance/coverage snapshots, verifying the merge postcondition, or continuing to the next ready issue when the user has opted into autonomous maintenance.
It also lacks a documented fallback for requesting Copilot review when the dedicated GitHub tool is unavailable.
Acceptance criteria
- Require inspection of performance, coverage, and analysis reports before merge.
- Treat meaningful negative drift as actionable rather than merging blindly.
- Verify merge or auto-merge state after requesting it.
- Document the GitHub requested-reviewers API fallback for Copilot and verify the assignment.
- When the user explicitly requests continuous autonomous work, clean up the completed branch and start the next ready issue instead of yielding.
Problem
The maintainer workflow can declare a PR complete after review without explicitly checking performance/coverage snapshots, verifying the merge postcondition, or continuing to the next ready issue when the user has opted into autonomous maintenance.
It also lacks a documented fallback for requesting Copilot review when the dedicated GitHub tool is unavailable.
Acceptance criteria