jpmschweitzerandClaude
8bdf950fcf
The gate had no `select`, so it linted with whatever the installed ruff version defaults to. `dev` pins only `ruff>=0.6` and CI installs that extra fresh on every run, which made the rule set a function of when pip last resolved rather than of this code. Two developers on one commit could get different answers, and so could CI and a laptop. This surfaced when T-47's converged setup reinstalled ruff and pulled 0.16.3: `make lint` failed on UP017 and BLE001 in main.py, a file the commit before it had not touched. Under the previous install the same code passed. Nothing about the code changed — only the linter's idea of what to look at, which had grown to 413 rules with nobody choosing them. Naming the families fixes that; pinning the version would only have frozen the symptom and moved the surprise to whoever unpinned it. 217 rules now, selected on purpose, and a future ruff release becomes a decision instead of a broken push. ASYNC is included deliberately — this is a websocket gateway, and it is the family whose findings would be real bugs rather than style. BLE is deliberately excluded: main.py catches bare Exception when a device disappears mid-send, which is correct there, and selecting BLE would mean a noqa on every such site to say so. UP017 is fixed rather than suppressed (datetime.timezone.utc -> UTC, identical semantics, and requires-python is already >=3.11); isort then reordered the import, which is the whole of the main.py diff. Verified the selection is load-bearing rather than decorative: a probe file with a mutable default argument fails the explicit set (B006, exit 1) and passes ruff's minimal default set (exit 0), so the rules named here are doing work the fallback would not. Probe deleted; lint, typecheck and the 9-test suite all green after. Co-Authored-By: Claude <noreply@anthropic.com>