[Epic] Phase 16 · Trust surface hardening: remaining steps S4–S16
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
Research direction
This is a tracking epic, not a task to start on directly. Read docs/roadmap/phase-16-trust-surface-hardening.md for the S4-S16 step plan and CONTRIBUTING.md's 'Finding Work' section for how sub-issues are claimed. Pick an open step sub-issue whose scope you can reach from its listed files, and confirm it is unclaimed. Done here means every sub-issue is closed, so no code change is expected from this issue.
Written by the indexing model from the issue text.
Description
Epic · Roadmap · 15 issue(s)
Scope
The remaining steps of Phase 16 — Trust Surface Hardening, the execution plan approved on 2026-07-30 for the 83 remediation units of the 2026-07-29/30 full-project review. Pre-work and steps S1-S3 are delivered (13 of the 83 units closed); the 70 units in S4-S16 and the two standards those steps depend on are open.
Order. Behaviour → the contracts that describe behaviour → the documents that describe the contracts; work the steps in S4 → S16 order — no step reopens a file an earlier step settled for the same reason. S12 needs the SBOM / supply-chain standard and S13 the Docker standard first.
Each step is one root-cause family committed on its own, followed by an Opus review round and then a Sonnet review round, each with verified findings fixed before the next step begins. Every step issue lists the October 2026 review issues that track its units; close those from the step's PR where it fixes them.
How to work on it
Work the steps in S4 → S16 order (S12 and S13 also wait for their standard); claim a whole step, not a fragment of one, because each step lands as one root-cause family with its own review rounds. The two standards can be written at any time. See CONTRIBUTING.md, Finding Work: Issues and the Project Board; progress shows in the sub-issue list and in the project's Sub-issues progress field.
Done when
- Every sub-issue is closed (done, or closed with a reason).
Planned in docs/roadmap/phase-16-trust-surface-hardening.md (read at f94595f). Unit IDs (F-W20260729-…) come from the 2026-07-29/30 full-project review; the issue numbers next to them are the October 2026 review's records of the same defects.
- 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
-
Site: the theme-locked --code-comment grey (#6a6f80) on the dark code surface is 3.8:1, below WCAG AA, in both themes (F-W1-SITE-06)Possibly taken @vortsghost2025 claimed this today. Openarea: 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Deltares/imod-python#1940 ·
Maintainers usually reply within 1 day
-
effort: low prio: low ready
Difficulty 1/5 Under an hour Newbie friendliness 82/100
digitalfabrik/integreat-cms#4621 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
ioos/compliance-checker#1375 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day