Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

[Safe Outputs Conformance] MCE-001: add_comment tool description missing explicit CONSTRAINTS disclosure and "50 link" phrasing

クローズ 初心者向け
  • 何か問題がありますか？
#70,175 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
2/5
見積もり時間
1〜3時間
初心者へのやさしさ
68/100
issue の種類
バグ
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
github-actions, go, javascript
領域
tooling

調査の方向性

actions/setup/js/safe_outputs_tools.jsonから始めて、add_commentの説明を探し、pkg/workflow/js/safe_outputs_tools.jsonにある同期済みのコピーと比較します。actions/setup/js/generate_safe_outputs_tools.cjsと指定されたテストを確認し、生成後も文言が保持され、期待どおりであることを確かめます。両方のコピーでCONSTRAINTSと文字どおりの50 linkという表現を使って制限が明示され、適合性チェックに合格すれば完了です。

索引モデルが issue の本文から書いたものです。

説明

automated conformance medium-priority safe-outputs
Conformance Check Failure

Check ID: MCE-001
Severity: MEDIUM
Category: Implementation (Section 8.3 MCE2 — Tool Description Constraint Disclosure)

Problem Description

Per the Safe Outputs specification Section 8.3 (MCE2), the add_comment tool description MUST surface its enforcement constraints (character limit, mention limit, link limit) using recognizable, literal phrasing, and MUST contain an explicit CONSTRAINTS or IMPORTANT ... constraint disclosure block. The conformance checker (scripts/check-safe-outputs-conformance.sh, function check_mce_constraint_disclosure) scans pkg/workflow/js/safe_outputs_tools.json for these literal patterns and two sub-checks fail:

  1. No match for the literal phrase 50 link (case-insensitive).
  2. No match for CONSTRAINTS, IMPORTANT.*constraint, or validation constraint within the add_comment tool entry.
Affected Components

  • Files:

    • actions/setup/js/safe_outputs_tools.json (canonical source of the add_comment tool description)
    • pkg/workflow/js/safe_outputs_tools.json (synced copy embedded for the Go compiler — keep both in sync)
    • actions/setup/js/generate_safe_outputs_tools.cjs (runtime generator that composes the final description with suffixes/notes)
<b>🔍 Current vs Expected Behavior</b>
Current Behavior

The add_comment tool description (around line 525 of pkg/workflow/js/safe_outputs_tools.json) reads:

"...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..."

The 50-link default is disclosed, but phrased as "max-links URL occurrences (default: 50)" rather than the literal "50 link(s)" substring the spec checker expects, and there is no CONSTRAINTS: (or equivalent IMPORTANT ... constraint) lead-in labelling this as an enforced constraint block.

Expected Behavior

The description should contain a clearly labelled constraints section using literal, greppable phrasing, e.g.:

"CONSTRAINTS: Input is limited to 524288 characters, 10 mentions, and 50 links (configurable via max-links, default: 50)..."

This keeps the existing semantics identical (524288 chars / 10 mentions / default 50 links) while making the constraint disclosure explicit and literal, satisfying MCE2's requirement that agents reliably discover enforcement limits from the tool description text itself.

Remediation Steps

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

  1. In actions/setup/js/safe_outputs_tools.json, edit the add_comment tool's description field to prefix the constraint sentence with CONSTRAINTS: and rephrase the link limit using the literal substring 50 link (e.g., "50 links") instead of "(default: 50)" alone, while preserving the existing 524288-character and 10-mention figures.
  2. Apply the equivalent edit to pkg/workflow/js/safe_outputs_tools.json so the embedded Go copy stays byte-identical to the canonical source (check for an existing sync/codegen step before hand-editing both).
  3. Check actions/setup/js/generate_safe_outputs_tools.cjs for any place that appends additional suffixes to the add_comment description (e.g. discussions notes) to confirm the new CONSTRAINTS phrasing survives suffix concatenation.
  4. Update any tests asserting on the exact add_comment description text (e.g. actions/setup/js/generate_safe_outputs_tools.test.cjs, actions/setup/js/safe_outputs_mcp_add_comment_constraints.test.cjs, pkg/workflow/safe_outputs_tools_test.go) to match the new wording.
Verification

After remediation, verify the fix by running:

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

The check MCE-001 should pass without errors (no [MEDIUM] MCE-001 lines in the output).

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 (check_mce_constraint_disclosure, line ~665)
  • Run ID: 39206249052
  • Date: 2026-10-19

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

  • expires on Oct 19, 2026, 9:53 PM UTC-08:00
主要言語
Go
スター
5.4k
フォーク
584
平均マージ
3時間 26分
マージ済み PR（30日）
822

環境構築

Codespaces で開く

このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

github/gh-aw のほかの issue

github/gh-aw の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。