[Safe Outputs Conformance] MCE-001: add_comment tool description wording does not match conformance checker 50-link disclosure pattern
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
add_comment 的描述以及 body 字段的描述位于 pkg/workflow/js/safe_outputs_tools.json 中，失败的正则表达式位于 scripts/check-safe-outputs-conformance.sh 的 check_mce_constraint_disclosure 中。先将当前 max-links 的措辞与检查脚本所搜索的 50 link 模式进行比较，然后决定是改写 JSON 还是放宽正则表达式，这需要维护者确认。运行时，检查脚本报告 MCE-001 通过，即表示完成。
由索引模型根据 Issue 内容生成。
描述
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 viago:embedinpkg/workflow/safe_outputs_tools.go) —add_commenttooldescription(~line 525) andbodyfielddescription(~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:
- 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
- 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:
- Open
pkg/workflow/js/safe_outputs_tools.jsonand locate theadd_commenttooldescriptionand itsbodyfielddescription(two occurrences of the max-links wording). - 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.
- Regenerate/sync
actions/setup/js/safe_outputs_tools.jsonfrom the canonical source if it is a generated copy (checkpkg/workflow/safe_outputs_tools_generation.go/generate_safe_outputs_tools.cjsfor the regeneration step), and runmake fmt. - Re-run the conformance checker to confirm MCE-001 passes.
- 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
- 主要语言
- Go
- 星标
- 5.4k
- 派生
- 584
- 平均合并
- 3 小时 56 分钟
- 30 天内合并 PR
- 810
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/gh-aw 的其他 Issue
-
ai-inspected
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
automation cookie
难度 1/5 1 小时以内 新手友好度 68/100
维护者通常 1 天内回复
-
goroutineresourceleak (81st linter): paren_unwrap_gap across lock/cancel/channel detection, day one未关闭cookie sergo
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
agentic-workflows cascade-suspected
难度 4/5 3-5 天 新手友好度 22/100
维护者通常 1 天内回复
-
agentic-workflows cascade-suspected
难度 4/5 1-2 天 新手友好度 15/100
维护者通常 1 天内回复
相似的 Issue
-
area/import kind/bug
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
kind/documentation
难度 2/5 1-3 小时 新手友好度 80/100
kubernetes-sigs/dra-driver-nvidia-gpu#1569 ·
维护者通常 1 天内回复
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
难度 2/5 1-3 小时 新手友好度 65/100
openclaw/openclaw-enterprise#2571 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复