chore(core): re-capture the ruff fixtures at 0.16.2, and record what did not move

The bump landed as one line in the ledger; this is the part that has to be checked by
running. Both versions were installed side by side and pointed at identical input.

**Nothing changed.** findings.json, nofix.json and syntax-error.json are byte-identical at
0.16.0 and 0.16.2, and over two real packages out of the tools venv (vulture, deptry:
124 and 78 findings) the full finding sets — code, location, message, fix applicability —
compare equal. The doc comments that named 0.16.0 as the verified version now name 0.16.2,
because that claim was re-established rather than assumed.

Only clean.json moves, and not because of ruff: it was three bytes where ruff emits two.
`[]` has no trailing newline, and its three siblings all end in `]`. It had been typed
rather than captured, inside the one directory `.gitattributes` marks `-text` specifically
so captures stay byte-exact.

Two things worth knowing before the next bump, both found by running:

`spikes/capture.py` does not capture these. It knows pip and uv; the health fixtures come
from a synthetic sample with paths normalized to `C:\proj`, and reconstructing that sample
is most of the work. Two of my first attempts differed from the committed documents, and
running 0.16.0 against them is what proved the difference was mine and not ruff's — a
version-to-version diff on one interpreter would have called both a regression.

ruff's built-in default rule set is much wider than `E4,E7,E9,F`: `--isolated`, with no
config anywhere on this machine, still reports S110 from flake8-bandit. Whatever the Health
screen renders, it is not the small default a reader would assume.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
poli0981andClaude Opus 5 committed 2026-08-13 17:42:33 +07:00
1 parent dbd362fd4d
commit d7d3e5f685
5 files changed
+6 -5

No files matched your search

@@ -280,7 +280,7 @@ expression: out
"description": "One ruff finding.",
"properties": {
"code": {
"description": "The rule code, e.g. `F401`.\n\nOptional because the field is not ours. ruff 0.16.0 always sets it — a syntax error comes\nthrough as `invalid-syntax` rather than null, which is **not** what CODE-HEALTH-SPEC §6\nassumed — but tolerating null costs one `??` in the UI and stops a format change from\nfailing every run.",
"description": "The rule code, e.g. `F401`.\n\nOptional because the field is not ours. ruff 0.16.2 always sets it — a syntax error comes\nthrough as `invalid-syntax` rather than null, which is **not** what CODE-HEALTH-SPEC §6\nassumed — but tolerating null costs one `??` in the UI and stops a format change from\nfailing every run.",
"type": [
"string",
"null"
+2 -1
View File
@@ -89,7 +89,8 @@ pub const MIN_TOOLS_PYTHON: (u32, u32) = crate::envs::MIN_PROBE_PYTHON;
///
/// * **deptry 0.25.1** — `0` clean, `1` findings
/// * **vulture 2.16** — `0` none, `1` invalid input, `2` bad arguments, `3` dead code
/// * **ruff 0.16.0** — `0` clean, `1` violations, `2` error
/// * **ruff 0.16.2** — `0` clean, `1` violations, `2` error (re-checked at 0.16.2 on 2026-08-13;
/// 0.16.0 and 0.16.2 produced identical finding sets over two real packages)
///
/// A pin bump has to re-check this, and its real gate is the fixture corpus plus the integration
/// job — not this comment.
+1 -1
View File
@@ -151,7 +151,7 @@ pub struct RuffFindings {
pub struct RuffFinding {
/// The rule code, e.g. `F401`.
///
/// Optional because the field is not ours. ruff 0.16.0 always sets it — a syntax error comes
/// Optional because the field is not ours. ruff 0.16.2 always sets it — a syntax error comes
/// through as `invalid-syntax` rather than null, which is **not** what CODE-HEALTH-SPEC §6
/// assumed — but tolerating null costs one `??` in the UI and stops a format change from
/// failing every run.
+1 -1
View File
@@ -1 +1 @@
[]
[]
+1 -1
View File
@@ -597,7 +597,7 @@ export interface RuffFinding {
/**
* The rule code, e.g. `F401`.
*
* Optional because the field is not ours. ruff 0.16.0 always sets it — a syntax error comes
* Optional because the field is not ours. ruff 0.16.2 always sets it — a syntax error comes
* through as `invalid-syntax` rather than null, which is **not** what CODE-HEALTH-SPEC §6
* assumed — but tolerating null costs one `??` in the UI and stops a format change from
* failing every run.