[martinlocklear]

Human note - written by Martin, verbatim, not AI-generated:

We're starting to have a lot of information all pushed to first order retrievability in these PRs. Let's push it down to second order retrievability (a single click) so the information is discoverable but not clutter

---

[authored by Cursor]

Summary

• Keep the [!IMPORTANT] reviewer-explanation callout visible (headline, team count, provenance) and move the per-team file/pattern breakdown into a default-collapsed <details> block.
• Applies to both publish targets (the sticky comment and the optional PR-body region). The DOMAIN_REVIEW_REASONS markers, comment/body plumbing, and the edit-only-on-change idempotency guard are unchanged; this is a rendering-only change.

Motivation

These PRs now carry a lot of always-visible automated output. This pushes the verbose file/pattern breakdown one click down so it stays discoverable without cluttering the PR. The callout has to stay outside the collapsed region because GitHub does not render alert callouts inside <details> (they degrade to plain blockquotes).

Background: Collapsible reviewer explanation plan

Test plan

• ruff check .github/scripts and ruff format --check .github/scripts pass
• pytest .github/scripts/test_pr_labeler.py — 117 passing
• CI checks green

[martinlocklear]

[authored by Cursor]

Conversation summary

This PR originated from a request to reduce clutter in the automated PR sections by pushing the reviewer-explanation detail (which teams CODEOWNERS requested and why) from always-visible ("first order") to one-click-away ("second order").

Plan doc: Collapsible reviewer explanation

Key decisions

• Callout stays visible, breakdown collapses. The purple [!IMPORTANT] callout (headline, team count, and the "maintained automatically" provenance) remains first-order; the per-team file/pattern list moves into a default-collapsed <details>.
• Callout kept outside the collapsed region. GitHub does not render alert callouts inside <details> (they degrade to plain blockquotes), so the callout sits as a top-level sibling above the <details> rather than inside it.
• Rendering-only. The DOMAIN_REVIEW_REASONS markers, comment/body publish paths, and the edit-only-on-change idempotency guard are untouched, so both publish targets keep working with no churn.

Alternatives considered

• Single <details>, drop the alert (thog-style). Fully collapses everything under one summary but loses the purple callout that distinguishes this section from Bugbot's note.
• Collapse only the file lists, keep team names visible. Most information at a glance, but the busiest markup; not chosen, for simplicity.

[martinlocklear]

[authored by Cursor]

Example render

Here is how the new collapsible reviewer-explanation section renders (comment variant, on a sample PR touching three teams' files). The [!IMPORTANT] callout stays visible; the per-team file/pattern breakdown is one click away.

Important

Why these teams were requested for review
3 teams own some of the files changed here, per CODEOWNERS. Expand for the files that matched.
_{Maintained automatically by the PR labeler.}

Which teams and files (3)

• scanning - scan engine, job control, reverification
  • pkg/engine/reverify.go (matched /pkg/engine/)
  • pkg/engine/scan.go (matched /pkg/engine/)
• integrations - sources, detectors, and analyzers
  • pkg/sources/github/github.go (matched /pkg/sources/)
• eng-leads - engineering leads; default reviewers for files no domain team owns
  • Makefile (matched *)

[sysread]

Lovely. Thank you.