Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

[Safe Outputs Conformance] MCE-001: add_comment tool description wording does not match conformance checker 50-link disclosure pattern

Cerrado Apto para principiantes
  • ¿Algo no está bien?
#68,972 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
68/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
bash, go, json
Área
devtools

Línea de trabajo

Las descripción de add_comment y la descripción del campo body están en pkg/workflow/js/safe_outputs_tools.json, y la expresión regular que falla está en check_mce_constraint_disclosure en scripts/check-safe-outputs-conformance.sh. Empieza comparando la redacción actual de max-links con el patrón 50 link que busca el verificador; después decide si reformulas el JSON o amplías la expresión regular, algo que deben confirmar los mantenedores. Se considera terminado cuando el verificador informa que MCE-001 pasa al ejecutarlo.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

automated conformance safe-outputs
Conformance Check Failure

Check ID: MCE-001
Severity: MEDIUM
Category: Implementation (MCP Constraint Enforcement, Section 8.3 MCE2)

Problem Description

scripts/check-safe-outputs-conformance.sh (check check_mce_constraint_disclosure) requires the add_comment tool description in pkg/workflow/js/safe_outputs_tools.json to contain the literal substring 50 link (case-insensitive) as proof that the 50-URL constraint is disclosed to the agent per spec Section 8.3 MCE2.

The description does disclose the limit, but with different wording:

"...the configured max-links URL occurrences in agent content (default: 50; generated footer and metadata links excluded)..."

Because the digit 50 and the word link/links never appear adjacent, the checker's grep -iE "50 link" does not match, and the check fails with a MEDIUM-severity false-positive-style result even though the underlying requirement (informing the agent of the link limit before it calls the tool) is satisfied.

This will keep re-triggering on every scheduled run of this conformance workflow until either the description wording or the checker pattern is adjusted, generating recurring noise.

Affected Components
  • Files:
    • pkg/workflow/js/safe_outputs_tools.json (canonical source, embedded via go:embed in pkg/workflow/safe_outputs_tools.go) — add_comment tool description (~line 525) and body field description (~line 533)
    • scripts/check-safe-outputs-conformance.sh — check_mce_constraint_disclosure (around line 684)
🔍 Current vs Expected Behavior
Current Behavior

The add_comment description states the link limit as "...(default: 50; generated footer and metadata links excluded)" — correct in substance, but it does not contain a string matching 50 link so the automated checker flags it as missing disclosure.

Expected Behavior

Either:

  1. The tool description text explicitly includes a phrase like "maximum 50 links" / "50 link limit" so the disclosure is unambiguous to both the agent and the automated conformance check, OR
  2. The checker's regex is broadened to also accept the existing "max-links ... default: 50" phrasing (and similar equivalent wording) so it does not flag substantively-conformant descriptions.
Remediation Steps

This task can be assigned to a Copilot coding agent with the following steps:

  1. Open pkg/workflow/js/safe_outputs_tools.json and locate the add_comment tool description and its body field description (two occurrences of the max-links wording).
  2. Reword the link-limit clause to literally include "50 links" (or "50 link limit"), e.g. change "...the configured max-links URL occurrences in agent content (default: 50; generated footer and metadata links excluded)..." to "...a maximum of 50 links (configurable via max-links; generated footer and metadata links excluded)...", keeping the meaning unchanged.
  3. Regenerate/sync actions/setup/js/safe_outputs_tools.json from the canonical source if it is a generated copy (check pkg/workflow/safe_outputs_tools_generation.go / generate_safe_outputs_tools.cjs for the regeneration step), and run make fmt.
  4. Re-run the conformance checker to confirm MCE-001 passes.
  5. If, instead, the maintainers prefer to keep the current wording, update the checker regex in scripts/check-safe-outputs-conformance.sh (check_mce_constraint_disclosure) to accept the existing "max-links...default: 50" phrasing instead of requiring the literal "50 link" substring.
Verification

After remediation, verify the fix by running:

bash scripts/check-safe-outputs-conformance.sh

The check MCE-001 should pass without errors.

References
  • Safe Outputs Specification: docs/src/content/docs/specs/safe-outputs-specification.md (Section 8.3 MCE2)
  • Conformance Checker: scripts/check-safe-outputs-conformance.sh
  • Run ID: §38688391715
  • Date: 2026-10-15

Generated by ✅ Daily Safe Outputs Conformance Checker · claude · agent · 83.3 AIC · ⊞ 5.3K · ◷

  • expires on Oct 15, 2026, 9:49 PM UTC-08:00
Lenguaje dominante
Go
Estrellas
5.4k
Forks
584
Merge medio
3 h 26 min
PR fusionados (30 d)
822

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de github/gh-aw

Todos los issues de github/gh-aw

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.