ODD roadmap: B01–B06 and delivery reconciliation
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 1/5
- Tiempo estimado
- Menos de una hora
- Aptitud para principiantes
- 20/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- github, javascript
- Área
- devtools
Línea de trabajo
This issue is a roadmap index that links to issues #13–#30 and records their scope and dependencies. Read the linked issues and reconciliation comments to understand the roadmap state; the body says this revision updates only the index. Done means the approved order, scope references and stated boundaries are accurately represented.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
ODD roadmap: B01–B06 and delivery reconciliation
Planning revision: bootstrap-odd15-boundary-v3, published only after explicit approval. This issue is the shared index of the approved roadmap and its current scope references. It does not grant implementation, assignment, closure or release authority.
Outcomes and approved order
| Order | Existing milestone | Outcome | Issues |
|---|---|---|---|
| B01 | CI guardrails and first release readiness | Reproducible CI, complete package and human readiness decision | #13–#15 |
| B02 | Real GitHub integration sandbox | Approval-gated, audited real integration | #16–#18 |
| B03 | Native cross-platform compatibility | Declared support and native path/descriptor/loading evidence | #19–#21 |
| B04 | Runtime reconciliation intent | Enforceable per-module apply/adapt/leave | #22–#24 |
| B05 | Partial apply recovery | Classify unknown outcomes and replan remaining drift safely | #25–#27 |
| B06 | Automated repository security review | Bounded contextual scanner, measured corpus and gated CI adapter | #28–#30 |
Work units and current scope
| Issue | Milestone | Conceptual state | Dependencies | Current scope / ODD |
|---|---|---|---|---|
| #13 | B01 | Acceptance review; delivery evidence exists | — | Reconciliation, original criteria retained |
| #14 | B01 | Acceptance review; fixture/gate evidence exists | #13 | Reconciliation, original criteria retained |
| #15 | B01 | Partial delivery; runtime and migration pending | #13, #14 | Current complete ODD |
| #16 | B02 | Planned | #13 | Original scope |
| #17 | B02 | Planned, blocked by prerequisites | #15, #16 | Current scope and live-validation boundary |
| #18 | B02 | Planned, blocked by prerequisites | #17 | Original scope |
| #19 | B03 | Planned; technically independent, approved block order retained | — | Original scope |
| #20 | B03 | Planned, blocked by prerequisites | #19 | Original scope |
| #21 | B03 | Planned, blocked by prerequisites | #20 | Original scope |
| #22 | B04 | Planned, blocked by prerequisites | #17 | Original scope |
| #23 | B04 | Planned, blocked by prerequisites | #22 | Original scope |
| #24 | B04 | Planned, blocked by prerequisites | #23 | Original scope |
| #25 | B05 | Planned, blocked by prerequisites | #22 | Original scope |
| #26 | B05 | Planned, blocked by prerequisites | #25 | Original scope |
| #27 | B05 | Planned, blocked by prerequisites | #26 | Original scope |
| #28 | B06 | Planned, blocked by prerequisite | #13 | Original scope |
| #29 | B06 | Planned, blocked by prerequisite | #28 | Original scope |
| #30 | B06 | Planned, blocked by prerequisites | #14, #29 | Original scope |
Separate candidate
Injected repository plan API is proposed outside the six existing milestones, without assignment or status:approved. It is not an additional prerequisite for #15 or permission to begin its phases.
Evidence and how to choose work
- At this snapshot the 18 original issues remain open with
status:approved, no assignees and no open related PR. Merged PR does not mean complete issue acceptance. - Delivered references such as #47 transport and #48 fixture extraction are merged PRs, not outstanding issue dependencies.
- Main 80feb7b237dec221c36b08f12ea95d58bebd64f0 incorporates #48; main CI is green. Historical local-only observations and PR #31's B01-only tracker are not this global index.
- Reconcile #13/#14 and complete #15's closure inventory first. Retain approved B01→B06 order; ask before changing priority. Independent work can be proposed, not implicitly started.
- Recheck live issue/PR claims and assignees before any start. Take work only on explicit issue-scoped authorization, identify the contributor and verify assignment. Availability checks are not concurrency locks.
- Bugs/tasks without an ODD inclusion signal remain outside this index. Legacy closed #1/#3/#7/#11 are not silently absorbed.
- No CONTRIBUTING or local contribution skill is introduced by this revision. Contribution support remains a separately proposed documentation unit; collaborators are not required to use Pi.
Open decisions and boundaries
Offline branch-protection contract, implementation and simulated tests belong to #15; actual auth/apply validation belongs to #17. Retain conditional default-on with explicit opt-out and compatibility/migration review before Source implementation. Record the SemVer decision and actual auto-publish behavior; no automatic release/version.
Retain current platform limits and the two inherited macOS/Windows skips. Do not infer live Projects, stored-secret, sandbox, agent-load or LLM behavior from fixtures.
This revision adds planning reviews on #15/#17 and updates only this index body. Original task issue bodies, labels, assignees, milestones and closure states remain unchanged; no implementation, assignment, closure or release is authorized.
- Lenguaje dominante
- JavaScript
- Estrellas
- 22
- Forks
- 3
- Merge medio
- 27 min
- PR fusionados (30 d)
- 27
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
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 egdev6/github-repository-bootstrap
-
status:approved type:chore
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
egdev6/github-repository-bootstrap#57 ·
Los mantenedores suelen responder en 1 día
-
enhancement
Dificultad 5/5 Más de una semana Aptitud para principiantes 22/100
egdev6/github-repository-bootstrap#49 ·
Los mantenedores suelen responder en 1 día
-
status:approved type:chore
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
egdev6/github-repository-bootstrap#30 ·
Los mantenedores suelen responder en 1 día
-
status:approved type:chore
Dificultad 5/5 Más de una semana Aptitud para principiantes 42/100
egdev6/github-repository-bootstrap#29 ·
Los mantenedores suelen responder en 1 día
-
enhancement status:approved
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
egdev6/github-repository-bootstrap#28 ·
Los mantenedores suelen responder en 1 día
Todos los issues de egdev6/github-repository-bootstrap
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
code-yeongyu/oh-my-openagent#10172 ·
Los mantenedores suelen responder en 1 día
-
Phase 2 PSA Capability & Career Profile
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
bcgov/digital-journeys#2310 ·
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
nodejs/node#66743 · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
enhancement good first issue help wanted
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
OWASP/cve-lite-cli#1335 ·
Los mantenedores suelen responder en 1 día
-
Channels status: needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
mastra-ai/mastra#27093 · 1 comentario ·
Los mantenedores suelen responder en 1 día