Retire two PR #29 deferral rows whose work is done or moot (F-PR29-A8-07, F-PR29-A8-02 / C-2)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- Under an hour
- Newbie friendliness
- 50/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- markdown, python
- Domain
- build-system, documentation
Research direction
Open docs/roadmap/risks-and-decisions.md at line 90 and find the PR #29 deferral table rows F-PR29-A8-07 and F-PR29-A8-02. Check the SonarCloud project for open hotspots and the gate on the current head, and time tools/build_usermanuals.py to confirm the performance claim. For each row, add a dated addendum with the evidence, remove it, and name its ID in the CHANGELOG. Done when both rows are gone and the CHANGELOG entry exists.
Written by the indexing model from the issue text.
Description
Deferred work ·
F-PR29-A8-07 / F-PR29-A8-02· severity Low · cost ~30 min · recorded indocs/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.
- Dominant language
- Python
- Stars
- 9
- Forks
- 1
- Avg merge
- 8h 10m
- Merged PRs (30d)
- 5
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from HodeTech/ForgeLM
-
area: dev-tooling bug severity: low source: roadmap wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
area: site bug good first issue severity: low source: review-2026-09 wave: 4
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
documentation good first issue severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Difficulty 1/5 1-3 hours Newbie friendliness 80/100
-
documentation severity: medium source: review-2026-09 wave: 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
All issues in HodeTech/ForgeLM
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 1/5 Under an hour Newbie friendliness 62/100
-
Difficulty 1/5 Under an hour Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
topoteretes/cognee#5773 ·
Maintainers usually reply within 1 day
-
MiKTeX: a failed build reports no errors because texify --quiet switches the log to file:line: styleOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
SublimeText/LaTeXTools#1718 ·