feat: quality gate closes poor-quality PRs + align gh-aw to v0.60.0

.github/workflows/copilot-setup-steps.yml

@@ -23,4 +23,4 @@ jobs:
       - name: Install gh-aw extension
         uses: github/gh-aw/actions/setup-cli@c942baa88222271ac35ad1f8c34cde55d596bdee # v0.60.0
         with:
-          version: v0.58.1
+          version: v0.60.0

.github/workflows/quality-gate.md

@@ -29,6 +29,9 @@ safe-outputs:
     max: 1
     footer: "always"
     github-token: ${{ secrets.GH_AW_WRITE_TOKEN }}
+  close-pull-request:
+    max: 1
+    github-token: ${{ secrets.GH_AW_WRITE_TOKEN }}
   add-comment:
     github-token: ${{ secrets.GH_AW_WRITE_TOKEN }}
   add-labels:
@@ -68,7 +71,7 @@ This workflow runs when a review is submitted on a pull request.
 5. Make your decision:
    - If code quality is good AND impact is LOW or MEDIUM: Submit an APPROVE review with a brief summary of what was evaluated (e.g., "Low-impact test addition with good coverage. Auto-approving for merge."). Also add the label `quality-gate-approved` to the PR — this label is used by the PR Rescue workflow to know which PRs are safe to re-approve after rebase. The PR has auto-merge enabled — your approval satisfies the required review and triggers automatic merge.
    - If code quality is good but impact is HIGH: Add a comment to the PR explaining: what the high-impact areas are, why manual review is recommended, and what specifically a human reviewer should look at. Do NOT approve — auto-merge will remain blocked until a human approves.
-   - If code quality is poor: Add a comment explaining the quality concerns. Do NOT approve.
+   - If code quality is poor: Close the PR with a comment explaining the quality concerns (what's wrong and what needs to be fixed). The source issue stays open so the implementer can retry. Do NOT approve.
 
 Be conservative — when in doubt about impact level, round up. It's better to flag something for human review than to auto-merge a risky change.