Retire two PR #29 deferral rows whose work is done or moot (F-PR29-A8-07, F-PR29-A8-02 / C-2) #926

Deferred work · F-PR29-A8-07 / F-PR29-A8-02 · severity Low · cost ~30 min · recorded in docs/roadmap/risks-and-decisions.md:90

Summary

Two rows of the PR #29 deferral table outlived their reason. F-PR29-A8-07 (SonarCloud hotspots): the live SonarCloud project shows no hotspot left to review and a passing gate on the current head. F-PR29-A8-02 / C-2 (tools/build_usermanuals.py performance): the builder renders all 134 pages in under a second in-process and only runs in path-filtered workflows, so a pinned 5× speed-up test would be noise.

Condition or budget

None.

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

Both rows are still in the table; neither has a dated addendum.

Related

#779 and #532 already cover the other stale rows (A6-12, A6-18, A2-13, the anchor slugifier, the lock file).

Acceptance criteria

• Each row gets a dated addendum with the evidence and is removed, as the table's removal contract allows for work that is done or moot.
• 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.}