Internal mypy debt has grown past its recorded budget: 108 errors in 36 files against 106 in 35 #917

Deferred work · F-W20260729-OPS-23-internal · severity Low · cost ~1-2 days · recorded in docs/roadmap/risks-and-decisions.md:262

Summary

Phase 16 S1 wired the public-surface mypy --strict gate and recorded the package-wide typing debt as a budget instead of a blocker: 106 errors across 35 files, measured with mypy 1.20.2 and ./.venv/bin/python -m mypy --ignore-missing-imports forgelm/, with growth past 106 named as the signal to act. That signal has fired, and nothing in CI enforces the budget, which is why the growth went unnoticed.

Condition or budget

"Growth past 106 is the signal to act" — met: the recorded command reports 108 errors in 36 files on 2026-10-09.

State today (re-checked 2026-10-09)

Re-measured on development with the recorded command and mypy 1.20.2: Found 108 errors in 36 files (checked 104 source files).

Related

#748 corrects the stale "47" in the Phase 16 plan (documentation only).

Acceptance criteria

• The count is back to 106 or below, or the budget is re-baselined with a written reason.
• Growth past the budget fails CI (a ratchet), so the next increase is caught when it happens.
• The row is removed from the deferral table and the CHANGELOG names its ID (the table's removal contract).

_{Recorded in docs/roadmap/risks-and-decisions.md (read at f94595f) and re-checked against the code on 2026-10-09. The row leaves that table only when the fix is on main, the CHANGELOG names its ID and any promised guard exists.}