ruff-bumplisted

# Bump ruff Raise the ruff version floor across the repositories in scope and absorb everything the new release surfaces — one commit per rule, each justified against the rule's own documentation, behind the project's own quality gates. Three references carry the parts that are easy to get wrong. Read all three before acting on anything. - `references/release-triage.md` — how to work out what a release actually does to a specific repo, and how much care each class of fix needs. - `references/pin-sites-and-gating.md` — every file a version can be pinned in, and what to do when the resolver refuses to see the release. - `references/default-rule-set.md` — measuring and adopting a newly curated default rule set, and curating what it surfaces. User arguments: $ARGUMENTS ## Context Repository — run this command and read the output: ```bash git remote get-url origin 2>/dev/null || echo "(not a git repository)" ``` Default branch — run this command and read the output: ```bash git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null || git ls-remote --symref origin HEAD 2>/dev/null | sed -n 's|^ref: refs/heads/\([^[:space:]]*\).*|\1|p' || echo "(unknown)" ``` Currently resolved version — run this command and read the output: ```bash command -v ruff >/dev/null 2>&1 && ruff --version || echo "(not on PATH — resolve through the project's environment)" ``` Where ruff is pinned here — run this command and read the output: ```bash git grep -nI -- 'ruff' -- ':(glob)**/pypr