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 missing required CONSTRAINTS/IMPORTANT disclosure keyword

Abierto Apto para principiantes
  • ¿Algo no está bien?
#71,366 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
1/5
Tiempo estimado
Menos de una hora
Aptitud para principiantes
78/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
github-actions, go, json
Área
tooling

Línea de trabajo

Abre pkg/workflow/js/safe_outputs_tools.json y localiza la descripción de la herramienta add_comment. Comprueba si este archivo se genera a partir de otra fuente y, después, añade la divulgación de las restricciones requerida, preservando los límites indicados. Ejecuta bash scripts/check-safe-outputs-conformance.sh; estará hecho cuando MCE-001 pase.

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: Specification (Section 8.3 MCE2 - Tool Description Constraint Disclosure)

Problem Description

Spec Section 8.3 MCE2 requires that tool descriptions surfacing enforced constraints make that disclosure unambiguous, using a recognizable marker (CONSTRAINTS, or IMPORTANT ... constraint, or validation constraint). The add_comment tool description in pkg/workflow/js/safe_outputs_tools.json already states all three numeric limits (524288/65536 character limits, 10 mentions, configured max-links default 50) in prose, but does not contain any of the required marker keywords, so an automated or quick-scanning consumer of the tool description cannot reliably detect that these are hard-enforced constraints versus descriptive text.

Affected Components
  • Files: pkg/workflow/js/safe_outputs_tools.json (the add_comment tool entry, line ~531)
🔍 Current vs Expected Behavior
Current Behavior

Current description (relevant excerpt):

\"...Input is limited to 524288 characters, 10 mentions, and configured max-links URL occurrences (default: 50). Oversized agent content is automatically replaced by notices to fit the complete 65536-character published comment...\"

This correctly lists the limits but never uses the word CONSTRAINTS or an IMPORTANT ...constraint / validation constraint phrase, so the checker (and a human skimming many tool descriptions) cannot pattern-match it as an explicit constraint-disclosure block.

Expected Behavior

Per spec Section 8.3 MCE2, the description should clearly flag the limits as enforced constraints, e.g. by prefixing the limits sentence with CONSTRAINTS: so it reads something like:

\"...CONSTRAINTS: input is limited to 524288 characters, 10 mentions, and configured max-links URL occurrences (default: 50)...\"

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 entry.
  2. Edit the description field to prefix the constraint-limits sentence with CONSTRAINTS: (or otherwise insert the literal word CONSTRAINTS adjacent to the limits), without changing the actual documented limit values (524288, 65536, 10 mentions, max-links default 50) or any other wording/behavior.
  3. If pkg/workflow/js/safe_outputs_tools.json is generated/synced from another source (check for a generator script), apply the same edit at the source of truth so it round-trips correctly, and regenerate.
  4. Run make fmt if any Go-side generation templates were touched.
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: 39907463914
  • Date: 2026-10-23

Generated by ✅ Daily Safe Outputs Conformance Checker · claude · agent · ~67 AIC · ⌖ ~1 AIC · ⊞ 5.4K · ◷

  • expires on Oct 23, 2026, 9:51 PM UTC-08:00
Lenguaje dominante
Go
Estrellas
5.4k
Forks
596
Merge medio
3 h 40 min
PR fusionados (30 d)
830

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.