#780 and #784 were green separately and red together: the gate landed with a base
that predated `scripts/check-doc-narrative.py`, so nothing ever ran ruff over it.
On merged main the shipped invocation is RED, which would have surfaced as a
mystery lint failure on whichever PR opened next.
Two findings, both in #784's files:
- `RUF100` on `# noqa: BLE001` twice — `BLE` is not in this repo's `select`, so
those directives suppress nothing. Enabling `BLE` instead was measured and
rejected: it fires 6 more times in `decisions_validate.py`, whose broad catches
are deliberate, and that is a ruleset decision for its own PR rather than a
side effect of unbreaking main. The non-enabled code is dropped; the `S110` on
the first site stays (S IS selected), and both explanatory comments stay.
- `scripts/tests/test_check_doc_narrative.py` was not ruff-formatted. Formatted;
suite still 807 passed, 2 skipped.
The general shape, for the next time two PRs touch disjoint files: a gate whose
population is "everything tracked" is only as green as its base. #813's CI could
not have caught this and neither could #811's.
Refs: #780, #784
timothy