[Safe Outputs Conformance] MCE-001: add_comment tool description missing explicit "50 link" limit phrase
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
从 pkg/workflow/js/safe_outputs_tools.json 中 add_comment 的描述入手，检查它是否如 issue 所述由 Go 源模板生成。将源描述更新为“maximum 50 links”，然后运行 bash scripts/check-safe-outputs-conformance.sh；MCE-001 通过即表示完成。
由索引模型根据 Issue 内容生成。
描述
Conformance Check Failure
Check ID: MCE-001
Severity: MEDIUM
Category: MCP Constraint Enforcement (Section 8.3 MCE2)
Problem Description
The safe-outputs conformance checker's MCE-001 check requires the add_comment tool description in pkg/workflow/js/safe_outputs_tools.json to literally contain the phrase "50 link" so agents can see the link-count ceiling at a glance. The current description discloses the same constraint using different wording — "the configured max-links URL occurrences in agent content (default: 50; generated footer and metadata links excluded)" — so the limit is present but not in the exact phrasing the check (and by extension, a quick-scanning agent) expects.
Affected Components
- Files:
pkg/workflow/js/safe_outputs_tools.json(tool-leveldescriptionforadd_comment, ~line 525) - Checker:
scripts/check-safe-outputs-conformance.sh(MCE-001,check_mce_constraint_disclosure)
<b>🔍 Current vs Expected Behavior</b>
Current Behavior
The add_comment description states the link ceiling as "the configured max-links URL occurrences in agent content (default: 50; ...)" — functionally correct but not literally matching the 50 link substring the checker greps for.
Expected Behavior
Per spec Section 8.3 MCE2, add_comment MUST surface its 65536-character, 10-mention, and 50-link constraints in its tool description in agent-legible terms. The description should state the link limit as something like "maximum 50 links" so both the automated check and a skimming agent recognize it unambiguously.
Remediation Steps
- In
pkg/workflow/js/safe_outputs_tools.json, reword theadd_commenttool description's link-limit clause to include an explicit "maximum 50 links" (or equivalent "50 link" phrasing) alongside the existing max-links explanation. - Check whether this description is generated from a Go source template rather than hand-edited JSON, and make the change at the source if so, then regenerate.
- Re-run the conformance checker to confirm MCE-001 passes.
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
- Conformance Checker: scripts/check-safe-outputs-conformance.sh
- Run: §39101480539
Generated by ✅ Daily Safe Outputs Conformance Checker · claude · agent · 59 AIC · ⌖ 0.818 AIC · ⊞ 5.3K · ◷
- expires on Oct 18, 2026, 9:48 PM UTC-08:00
- 主要语言
- Go
- 星标
- 5.4k
- 派生
- 584
- 平均合并
- 3 小时 16 分钟
- 30 天内合并 PR
- 829
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/gh-aw 的其他 Issue
-
agent-research
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
windows workflow
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
cookie sergo
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
MCP Gateway rejects digest-pinned container images: embedded JSON schema disagrees with containerPattern可能已有人在做 @pelikhan 于 1 天前认领。 未关闭ai-inspected
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
goroutineresourceleak (81st linter): paren_unwrap_gap across lock/cancel/channel detection, day one未关闭cookie sergo
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
blinklabs-io/dingo#5368 ·
维护者通常 1 天内回复
-
difficulty: easy enhancement frontend good first issue help wanted priority: P2
难度 2/5 1-3 小时 新手友好度 78/100
rafaelsilvabr/pdfHandler#18 ·
-
难度 2/5 1-2 天 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 83/100
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复