Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Chiusa Adatta ai principianti
  • Qualcosa non va?
#68,972 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
68/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
bash, go, json
Ambito
devtools

Direzione di ricerca

La descrizione di add_comment e la descrizione del campo body si trovano in pkg/workflow/js/safe_outputs_tools.json, mentre la regex che fallisce si trova in check_mce_constraint_disclosure in scripts/check-safe-outputs-conformance.sh. Inizia confrontando la formulazione attuale di max-links con il pattern 50 link che il checker cerca, poi decidi se riformulare il JSON o ampliare la regex, cosa che i maintainer devono confermare. Il lavoro è completato quando il checker riporta MCE-001 come superato durante l'esecuzione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
Go
Stelle
5.4k
Fork
584
Merge medio
3h 16m
PR unite (30g)
826

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/gh-aw

Tutte le issue di github/gh-aw

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.