Skip to content

chore(conformance): standards sweep 2026-07-16 — README conformance table + ruff/mypy floor bumps#47

Merged
ChelseaKR merged 1 commit into
mainfrom
conformance/sweep-2026-07-16
Jul 17, 2026
Merged

chore(conformance): standards sweep 2026-07-16 — README conformance table + ruff/mypy floor bumps#47
ChelseaKR merged 1 commit into
mainfrom
conformance/sweep-2026-07-16

Conversation

@ChelseaKR

Copy link
Copy Markdown
Owner

Part of the 2026-07-16 portfolio standards-conformance sweep. The repo was already at 27/31 on the portfolio checker; this PR closes the three safely fixable gaps — the README standards table used non-canonical heading/names the checker cannot recognize, and the dev tool floors for ruff/mypy were below the portfolio minimums even though the locked versions already exceed them.

Controls fixed

Control Change
readme_conformance_table Retitled ## Standards## Standards Conformance; rows renamed to the canonical standard names (e.g. CODE-QUALITYCode Quality, RESPONSIBLE-TECHResponsible-Tech Framework); AI Evaluation N/A cell reformatted so the reason parses (N/A — no LLM/GenAI SDK…); Internationalization row changed from N/A to Applies (declaration under review) to match the portfolio applicability manifest (see below); fixed the now-stale anchor in docs/adr/0006.
ruff_version_floor ruff>=0.6ruff>=0.15 in [project.optional-dependencies].dev (+ uv lock specifier refresh; locked 0.15.20 unchanged). ruff format --check + ruff check run clean at 0.15.22.
mypy_version_floor mypy>=1.11mypy>=1.18 (locked 2.1.0 unchanged). mypy --strict clean at 2.3.0 (49 files).

Left failing

Control Reason
i18n_declaration Intentionally left. docs/I18N.md declares an English-only N/A opt-out, but the portfolio applicability manifest marks I18N applies for this repo (conservative default pending fork reconciliation with queer-specfic-reader, backlog #17). Per sweep policy I must not add/normalize an N/A declaration for a standard the manifest marks applies, so the checker header line was not added. Resolve with the fork reconciliation and an owner declaration.

Verification

Checker score: 27/31 → 30/31 (only i18n_declaration remains, intentionally).

  • python3 …/STANDARDS/automation/conformance_check.py --repo <worktree> — 27/31 before, 30/31 after; no control flipped pass→fail.
  • .venv/bin/python -m ruff format --check . && … ruff check . — 98 files formatted, all checks passed (ruff 0.15.22).
  • .venv/bin/python -m mypy — Success: no issues found in 49 source files (mypy 2.3.0, strict).
  • uv lock — resolved 84 packages; only the two requires-dist specifier lines changed.
  • make verify — full gate green: lint, marker-hygiene, mypy, 389 tests passed (coverage 97.25% ≥ 85% floor), pip-audit clean, gitleaks clean, trivy clean, a11y (structural + pa11y/axe) 0 violations, offline eval passed.

Note: GitHub Actions is billing-blocked account-wide right now, so PR CI will not report; all verification above was run locally.

⚠️ Flags: ruff/mypy dev floors bumped (tools re-run clean locally); no other thresholds or gates touched.

🤖 Generated with Claude Code

https://claude.ai/code/session_01JEt7d9aeBFmPToT46Sciqw

…to Standards Conformance, bump ruff/mypy floors

- README: retitle '## Standards' to '## Standards Conformance' and use the
  canonical standard names the portfolio checker expects; the I18N row now
  states honestly that the manifest keeps I18N *applies* pending fork
  reconciliation with queer-specfic-reader (backlog #17).
- pyproject/uv.lock: raise dev floors ruff>=0.6→>=0.15, mypy>=1.11→>=1.18
  (locked versions 0.15.20 / 2.1.0 already satisfy them); ruff format/check
  and mypy --strict run clean at the new floors, and `make verify` passes.
- ADR 0006: fix the README anchor after the section rename.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JEt7d9aeBFmPToT46Sciqw
@ChelseaKR
ChelseaKR merged commit 9e35c5c into main Jul 17, 2026
6 checks passed
@ChelseaKR
ChelseaKR deleted the conformance/sweep-2026-07-16 branch July 17, 2026 08:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant