style(extract,propose): the formatter was never in the acceptance, so it went red unseen

`ruff format --check .` was clean on `fbad5b0` and red on `6ff18fd`: blank
lines around the new `strip_converter_attribute` and the new `member` closure.
Round 9's order named only `ruff check`, and STATE's "ruff clean" read wider
than what was measured -- an acceptance that names one of a tool's two gates
reports green for the gate it did not run.

Three hunks, blank lines only, no behaviour. From here the acceptance is BOTH
`ruff check` and `ruff format --check .`, both named in the report with the
version they ran under (0.15.22 here).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-09 22:05:51 +02:00
commit 6ff84d71c8
2 changed files with 2 additions and 1 deletions

View file

@ -934,6 +934,7 @@ def _contents_run_positions(
concept while its neighbours were not. What still bounds the rule is the run
LENGTH, which is what the `CONTENTS_RUN` sweep bought and is unchanged.
"""
def member(candidate: Candidate) -> bool:
if candidate.rule == RULE_TABLE_BLOCK:
return False