Apply progressive disclosure to ready_for_review PR comment workflows

[Copilot]

PR comments from ready_for_review-triggered workflows (Test Quality Sentinel, Design Decision Gate, Matt Pocock Skills Reviewer, PR Code Quality Reviewer) dump large walls of text immediately visible on every PR. Restructure all four to use <details>/<summary> so only the actionable headline is visible by default.

Changes

test-quality-sentinel.md

• Comment format: only score headline + one-sentence summary + verdict stay visible; metrics table, classification table, flagged tests, and language support each get their own <details> block
• Drops the old "wrap tables with >10 rows" heuristic — all classification/flagged content collapses unconditionally

design-decision-gate.md

• Blocking comment: headline + 🔒 notice visible; "What to do next", "Why ADRs Matter", and ADR format reference collapse
• Verification comment: headline + one-line status visible; summary and divergences list collapse

mattpocock-skills-reviewer.md

• Inline review comments: 1-sentence visible lead, code examples and analysis in <details><summary>💡 …</summary>
• Overall review body: verdict + one-line summary visible, themes/highlights collapse

pr-code-quality-reviewer.md

• Inline comments: 1-sentence impact statement visible, detailed fix suggestions in <details>
• Formatting guidelines updated to mandate the pattern explicitly

Before / after (Test Quality Sentinel):

<!-- Before: entire table + per-test analysis + language support immediately visible -->
### Test Quality Score: 60/100
⚠️ Acceptable with suggestions
| Metric | Value |
| ... | ... |   ← immediately visible

<!-- After: only headline visible -->
⚠️ **Test Quality Score: 60/100 — Acceptable with suggestions**
> Analyzed 1 test(s): 1 design, 0 implementation, 0 violation(s).

<details>
<summary>📊 Metrics & Test Classification (1 tests analyzed)</summary>
...all tables here...
</details>

[Copilot]

Pull request overview

Restructures multiple ready_for_review-triggered workflow comment templates to use progressive disclosure (<details>/<summary>) so PRs show only short, actionable headlines by default, with verbose analysis collapsed.

Changes:

• Updated Test Quality Sentinel / Design Decision Gate / Matt Pocock Skills Reviewer / PR Code Quality Reviewer comment formats to collapse long sections under <details>.
• Adjusted formatting guidelines in the workflow templates to mandate progressive disclosure patterns.
• Regenerated issue-monster.lock.yml, updating action sourcing/versioning and several workflow steps.

Show a summary per file

File	Description
.github/workflows/test-quality-sentinel.md	Collapses metrics/classification/flagged test details under <details> and updates formatting requirements.
.github/workflows/design-decision-gate.md	Collapses “next steps”, ADR background, and verification details under <details> blocks.
.github/workflows/mattpocock-skills-reviewer.md	Updates inline comment/review body examples to keep a brief lead visible and collapse details.
.github/workflows/pr-code-quality-reviewer.md	Requires one-sentence visible lead in comments, with detailed suggestions in <details>.
.github/workflows/issue-monster.lock.yml	Large regenerated lock workflow with updated setup mechanics, image versions, and metadata.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (6)

.github/workflows/issue-monster.lock.yml:775

• actions/checkout is configured with repository: github/gh-aw but no ref, which will default to the repository’s default branch rather than the workflow’s commit/PR SHA. Because the next step runs a local action (./actions/setup), this can execute code from the wrong revision; set ref to the current commit (or remove repository: when checking out the current repo) so the local action matches the workflow revision.

      - name: Checkout actions folder
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          repository: github/gh-aw
          sparse-checkout: |
            actions
          persist-credentials: false
      - name: Setup Scripts

.github/workflows/issue-monster.lock.yml:1407

• actions/checkout is configured with repository: github/gh-aw but no ref, which will default to the repository’s default branch rather than the workflow’s commit/PR SHA. Because the next step runs a local action (./actions/setup), this can execute code from the wrong revision; set ref to the current commit (or remove repository: when checking out the current repo) so the local action matches the workflow revision.

      - name: Checkout actions folder
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          repository: github/gh-aw
          sparse-checkout: |
            actions
          persist-credentials: false

.github/workflows/issue-monster.lock.yml:1556

• actions/checkout is configured with repository: github/gh-aw but no ref, which will default to the repository’s default branch rather than the workflow’s commit/PR SHA. Because the next step runs a local action (./actions/setup), this can execute code from the wrong revision; set ref to the current commit (or remove repository: when checking out the current repo) so the local action matches the workflow revision.

      - name: Checkout actions folder
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          repository: github/gh-aw
          sparse-checkout: |
            actions
          persist-credentials: false

.github/workflows/issue-monster.lock.yml:1769

• actions/checkout is configured with repository: github/gh-aw but no ref, which will default to the repository’s default branch rather than the workflow’s commit/PR SHA. Because the next step runs a local action (./actions/setup), this can execute code from the wrong revision; set ref to the current commit (or remove repository: when checking out the current repo) so the local action matches the workflow revision.

      - name: Checkout actions folder
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          repository: github/gh-aw
          sparse-checkout: |
            actions
          persist-credentials: false

.github/workflows/issue-monster.lock.yml:2244

• actions/checkout is configured with repository: github/gh-aw but no ref, which will default to the repository’s default branch rather than the workflow’s commit/PR SHA. Because the next step runs a local action (./actions/setup), this can execute code from the wrong revision; set ref to the current commit (or remove repository: when checking out the current repo) so the local action matches the workflow revision.

      - name: Checkout actions folder
        uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
        with:
          repository: github/gh-aw
          sparse-checkout: |
            actions
          persist-credentials: false

.github/workflows/issue-monster.lock.yml:1692

• This workflow now sets GH_AW_VERSION: dev, which makes runs non-reproducible and weakens provenance compared to a pinned release version. If this file is meant to be a lockfile, consider compiling it with a released/pinned gh-aw version so the runtime metadata reflects an immutable version.

          GH_AW_PHASE: detection
          GH_AW_PROMPT: /tmp/gh-aw/aw-prompts/prompt.txt
          GH_AW_VERSION: dev
          GITHUB_API_URL: ${{ github.api_url }}
          GITHUB_AW: true

• Files reviewed: 5/5 changed files
• Comments generated: 6