The dashboard issue Renovate maintains lists pending updates in a
handful of sections (Open / Awaiting Schedule / Pending Approval /
Detected dependencies / …) but the section headings alone are not
self-explanatory — easy to lose the patch+minor vs major
distinction we put in place via `dependencyDashboardApproval` for
majors.
Add a `dependencyDashboardHeader` markdown block that maps each
section to the triage action it expects from the maintainer:
which to batch-merge, which to leave alone, which to read the
changelog before approving. Re-state the pinned constraints
(Prisma majors blocked until the Prisma 7 ADR per ADR-0006; the
Trivy / gitleaks pins in workflow YAML which Renovate doesn't see).
Cross-link to docs/development.md for the full procedure.
Re-renders on the next Renovate run (no code change required —
the header is part of the dashboard issue body).
Julien Gautier