After ~10 days of clean track record on Renovate (~30 PRs merged
without regression beyond the TS/ESLint/webpack-cli majors that
the dashboard-approval rule now catches), enable auto-merge for
patch / pin / digest / lockFileMaintenance updates. CI is the
gate — `check` / `scan` / `a11y` going red leaves the PR open for
manual triage. Minors keep needing human review (might widen
surface), majors are still dashboard-approval-gated.
The dashboard triage header is updated so the "Open" row reflects
the new reality (mostly minors, with red patches surfacing
briefly when CI fails). docs/development.md "Reviewing Renovate
PRs" gains a bullet describing the auto-merge behaviour for
contributors landing on the project later.
`automergeStrategy: "squash"` matches our trunk-based squash-merge
convention. `automergeType: "pr"` keeps a PR + CI run as the
audit trail (vs branch-direct push), and Gitea automerges the PR
once green via the bot's existing `repo:write` permission.
Julien Gautier