[Epic] Phase 16 · Trust surface hardening: remaining steps S4–S16
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Python
- Estrellas
- 9
- Forks
- 1
- Merge medio
- 8 h 10 min
- PR fusionados (30 d)
- 5
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de HodeTech/ForgeLM
-
area: dev-tooling bug severity: low source: roadmap wave: 4
Dificultad 2/5 1-3 horas Aptitud para principiantes 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)Posiblemente ocupada @vortsghost2025 la tomó hoy. Abiertoarea: site bug good first issue severity: low source: review-2026-09 wave: 4
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
-
documentation good first issue severity: medium source: review-2026-09 wave: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
documentation good first issue severity: low source: review-2026-09 wave: 4
Dificultad 1/5 1-3 horas Aptitud para principiantes 80/100
-
documentation severity: medium source: review-2026-09 wave: 3
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Todos los issues de HodeTech/ForgeLM
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
task
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
danparshall/claude_researcher#87 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
datajoint/datajoint-python#1586 ·
Los mantenedores suelen responder en 1 día
-
1D intercept of length 1 is accepted as `fix_params` in population GLM with more than 1 unitPosiblemente ocupada @dhvani7014 la tomó hoy. Abiertobug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
flatironinstitute/nemos#642 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Broken links in the docsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 78/100
uniswap-python/uniswap-python#487 ·