docs(adr): record check precision defaults in an ADR that amends ADR 0003
Los mantenedores suelen responder en 1 día
Ya se ha fusionado un pull request relacionado.
- #8707 de @melodic-automation-lanes — fusionado
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 73/100
- Tipo de issue
- Documentación
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- markdown, shell
- Área
- documentation
Línea de trabajo
Lee ADR 0003 y el ADR más reciente, docs/adr/0079-dispatch-tagged-phase-reviews-to-quality-gate-at-the-phase-boundary.md, para seguir el formato y el contexto de las decisiones del proyecto. Crea el siguiente ADR numerado en docs/adr/, añade la enmienda especificada y los detalles de la decisión y, después de editar, ejecuta scripts/check-adr-numbers.sh --check. La tarea estará terminada cuando el ADR registre las reglas de precisión y excepción, mencione el criterio de la escala de aplicación y #3756, y supere la comprobación de números.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Refs: #7572
Agent Brief
Type: Task
Summary: Write one new ADR that amends ADR 0003 with the precision defaults for checks: zero effective false positives for a blocking check, under 10% for an advisory one, plus the exception rules.
Current behavior:
docs/adr/0003-verification-guards-earn-default-on-by-measured-precision.mdsays a guard earns default-on by measured precision but states no number; its reference guard shipped at 57% precision (docs/adr/0003-verification-guards-earn-default-on-by-measured-precision.md:48-49).- No ADR carries an
Amends:line for ADR 0003 (rg -l 'Amends: \[?ADR 0003' docs/adrprints nothing on main). The newest ADR isdocs/adr/0079-dispatch-tagged-phase-reviews-to-quality-gate-at-the-phase-boundary.md. - House style for the line is
- Amends: [ADR 0049](0049-run-ci-lanes-on-github-hosted-runners-under-trigger-and-token-hardening.md),in the header list (docs/adr/0074-review-risky-dependabot-updates-in-a-model-job-and-act-in-a-scripted-job.md:7). feedback.disable_not_useful_ratioandexceptions.max_daysexist only in the decision record, not in any tracked file (rg -n 'disable_not_useful|max_days' docs plugins scriptsprints nothing).
Desired behavior:
- A new
docs/adr/NNNN-<kebab-title>.md, numbered one above the highest on main when the lane runs, in the shape ofdocs/adr/0079-dispatch-tagged-phase-reviews-to-quality-gate-at-the-phase-boundary.md(title,- Status: accepted,- Date:, Context, Decision, Consequences), written the way/architecture:record-decisionwrites one. - Its header list carries
- Amends: [ADR 0003](0003-verification-guards-earn-default-on-by-measured-precision.md). - Decision text:
- A blocking check ships with 0 effective false positives on its corpus.
- An advisory check stays under 10% false positives; the 10% is named as a corpus-precision proxy, not a measured per-guard rate.
feedback.disable_not_useful_ratiois not adopted until #3756 produces a per-guard signal.- Exceptions expire after 90 days by default, as a team setting.
- Break glass is an inline exception that carries a reason, an expiry and a person's approval.
- Existing guards keep their recorded justification; nothing is re-graded by this ADR.
- Consequences name the enforcement ladder's guardrail criterion (
docs/conventions/enforcement-ladder/README.md) as the reader of these numbers, and #3756 as the open work that grades guards.
Key interfaces:
docs/adr/0003-verification-guards-earn-default-on-by-measured-precision.md(read; not edited).scripts/check-adr-numbers.sh(the number must not collide).
Acceptance criteria:
-
rg -l 'Amends: \[?ADR 0003' docs/adrlists exactly one file, the new ADR. - The new ADR contains
0 effective false positives,10%,90 daysand#3756(rg -c '0 effective false positives|10%|90 days|#3756' <new file>is at least 4). -
scripts/check-adr-numbers.sh --checkexits 0. - The diff touches only
docs/adr/.scripts/check-changelog-fragments.sh --check-required origin/mainpasses with no fragment, because no plugin's shipped files change. - CI's
lint-repojob (which runscheck-adr-numbers.shand the markdown lint) passes. In the lane, runscripts/check-adr-numbers.sh --checkat most once, after the last edit.
Out of scope:
- Editing ADR 0003 itself or any guard.
- Adding the 90-day exception setting to a plugin; this ADR records the default only.
- The ladder's guardrail criterion text (sibling slice ladder-v2).
Origin:
- 0 effective false positives blocking, under 10% advisory: ours, from Google's published bar, D31, Q199, D84.
- 10% named as a corpus-precision proxy: ours, D116, Q559.
- Drop
feedback.disable_not_useful_ratiountil #3756: owner's, D84. - Exception expiry 90 days as judgment inside the team setting: owner's, D84.
- Break glass inline exception with reason, expiry and approval: hers (Lauren's), D64.
Do not run with: none. No other open slice edits docs/adr/ for ADR 0003; two ADR-writing PRs racing for one number is caught by check-adr-numbers.sh.
Slice of #7572, drafted by the Issue Triage session from the thread's recorded decisions.
- Lenguaje dominante
- Shell
- Estrellas
- 22
- Forks
- 2
- Merge medio
- 6 h 58 min
- PR fusionados (30 d)
- 951
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin 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 melodic-software/claude-code-plugins
-
priority: medium status: needs-decision work-class: scoped
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
melodic-software/claude-code-plugins#9339 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
-
pipeline-canary priority: low status: ready work-class: mechanical
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
melodic-software/claude-code-plugins#9263 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
good first issue priority: low
Dificultad 1/5 Menos de una hora Aptitud para principiantes 90/100
melodic-software/claude-code-plugins#9251 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area: security needs-triage priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
melodic-software/claude-code-plugins#9211 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
priority: low
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
melodic-software/claude-code-plugins#9202 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de melodic-software/claude-code-plugins
Issues similares
-
source:reader type:enhancement
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
stephrobert/blog-roadmap#115 ·
-
Python Volcengine provider returns failures instead of raising themPosiblemente ocupada @Ricardo-M-L la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
agent-infra/sandbox#248 ·
-
chore priority:low size:S
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
celo-org/celopedia-skills#98 ·
Los mantenedores suelen responder en 1 día
-
Git for Windows shouldn't be locked on their `.windows.1` versionsPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertogit windows
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
jenkins-infra/packer-images#3179 ·
Los mantenedores suelen responder en 1 día
-
ready-for-pr
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
kunchenguid/firstmate#7679 · 1 comentario ·
Los mantenedores suelen responder en 1 día