Migrate dev tooling from black/isort/pylint to ruff

[hf-krechan]

Migrate this repo's dev tooling from black/isort/pylint to ruff, using the
migrating-black-isort-pylint-to-ruff skill.

• pyproject.toml: lint+formatting dependency groups merged into one ruff group
• [tool.black]/[tool.isort]/[tool.pylint."MESSAGES CONTROL"] translated into [tool.ruff]
• .pre-commit-config.yaml rewritten to astral-sh/ruff-pre-commit
• CI lint + formatting jobs rewritten to ruff check / ruff format --check, same path scope as before
• README updated
• PR opened and CI green

This issue is picked up automatically by a fleet worker. If the worker
gets stuck, it will comment here with what it tried and why, and relabel
this ruff-migration:blocked for a human to take over. On success it
comments the PR link and relabels ruff-migration:done.

[hf-krechan]

Migration work done locally, about to push branch migrate-to-ruff and open a PR. Summary of what changed:

• pyproject.toml: merged the formatting (black, isort) and linting (pylint) dependency groups into one linting group holding just ruff==0.16.0; translated [tool.black]/[tool.isort]/[tool.pylint."MESSAGES CONTROL"] into [tool.ruff]/[tool.ruff.lint] (select = E, W, F, I, UP, B, N, PL, RUF; ignore = PLR0913/PLR0917/PLR0912/PLR0915/RUF001-3 per the standard baseline; extend-exclude = ["*.md"] since ruff format touches fenced code in docs).
• Deleted tests/.pylintrc and .pylintrc_autogen_code (both dead pylintrc files) - their disables either have no ruff equivalent (R0801 duplicate-code, R0903 too-few-public-methods, W0621 redefined-outer-name, docstring rules we don't select) or were translated into a per-file-ignores entry for src/borm/models/** (F401, E501, mirroring the autogenerated-code rcfile).
• .pre-commit-config.yaml: replaced psf/black + pycqa/isort hooks with astral-sh/ruff-pre-commit v0.16.0 (ruff-check --fix, ruff-format).
• CI: .github/workflows/pythonlint.yml and the release workflow .github/workflows/python-publish.yml (this one only runs on release: events - easy to miss, but it had its own copy of the pylint invocation) now run ruff check src/borm tests, matching pylint's old combined scope. .github/workflows/formatting.yml's matrix (tool: ["black", "isort"]) is preserved via matrix.include pairing each tool value with a real ruff command, plus an explicit job name: so the required status check names (black (3.11, ubuntu-latest, black) / black (3.11, ubuntu-latest, isort)) stay byte-identical - confirmed these are actual required checks via the branch protection API before doing this.
• Also fixed a real (non-cosmetic) regression risk: both alembic.ini files (postgresql_db, mysql_db) had a post_write_hook that shelled out to black via the console_scripts runner to format autogenerated migration files. Since black is being removed entirely, this would've broken the next alembic revision --autogenerate. Switched both to an exec-type hook calling ruff format instead (verified working with a smoke test against a dummy revision file - ruff has no console_scripts entry point, unlike black, so exec is the correct hook type here, not console_scripts).
• README: badge alt-text mentioning ''Black'' updated to ''Formatting''.
• Left the dead # pylint: disable=... comments in place (base_class.py, base.py, create_db.py, both migrations/env.py) since ruff never read them and most have no ruff equivalent to translate to.

Local lean verification (resource-constrained box, so no full mypy/pytest run): ruff check src/borm tests, ruff format --check ., and ruff check --select I . all clean. uv.lock diff double-checked - only removes pylint/black/isort transitive deps and adds ruff, no unrelated churn. Next: push branch, open PR, request Copilot review, and poll CI.

[hf-krechan]

Migration complete: #273

[hf-krechan]

Migration complete: #273

[hf-kklein]

Done in b3fd1e7693 — "refactor: replace black, isort and pylint with ruff (#273)", on main since 2026-08-03.

black, isort and pylint are gone from the dev dependencies and the formatting/linting workflows run uv run ruff format --check . / uv run ruff check … (the legacy job names were kept on purpose so the required status checks in branch protection keep matching).

Closing as completed.