fix(work-items): a work-loop lane's own triage labels must not admit an item
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 1-2 天
- 新手友好度
- 48/100
调研方向
Read plugins/work-items/skills/work-loop/SKILL.md, especially the labeler precondition and intake sweep, then trace label-provenance and the test or eval that checks admission. Reproduce the case where the lane applies agent-ready or work-class: itself and verify the change prevents admission by default. Done when a test or eval covers that self-labeled case.
由索引模型根据 Issue 内容生成。
描述
Problem
The work-loop admission gate (labeler precondition plus label-provenance) accepts an agent-ready / work-class: label as admission evidence when someone allowed to grant admission applied it. A local lane's intake sweep runs as the lane's gh identity, which for local lanes is usually the operator (admin). So labels the lane applies itself during triage count as admission evidence.
Issue text that steers the autonomous triage sweep into applying agent-ready plus work-class: mechanical therefore leads label-provenance to return admitted: true, and /work-items:work builds and pushes the item. Barring the sweep from writing work-class: labels is only opt-in, through the launch prompt.
This path existed before #7009. The new gate shuts out triage-role humans but cannot tell the lane's own decision apart from a human's.
References: plugins/work-items/skills/work-loop/SKILL.md (labeler precondition and step 2, the intake sweep).
Fix
Pick one:
label-provenancerefuses awork-class:oragent-readylabel whose latest labeler is the lane's own write identity. A separate trusted identity, or a human, must apply it.- The intake sweep defaults to never writing
work-class:oragent-ready, and routes its proposal to human attention.
Done when
- A label the lane applied itself can never admit an item, by default.
- A test or eval covers the self-labeled case.
Refs: #7009
- 主要语言
- Shell
- 星标
- 22
- 派生
- 2
- 平均合并
- 8 小时 24 分钟
- 30 天内合并 PR
- 947
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
melodic-software/claude-code-plugins 的其他 Issue
-
needs-human needs-triage priority: medium
难度 2/5 1-3 小时 新手友好度 65/100
melodic-software/claude-code-plugins#7455 · 1 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 68/100
melodic-software/claude-code-plugins#7351 · 2 条评论 ·
维护者通常 1 天内回复
-
agent-ready priority: high work-class: scoped
难度 2/5 1-3 小时 新手友好度 74/100
melodic-software/claude-code-plugins#7312 · 3 条评论 ·
维护者通常 1 天内回复
-
priority: medium
难度 2/5 1-3 小时 新手友好度 76/100
melodic-software/claude-code-plugins#7288 · 2 条评论 ·
维护者通常 1 天内回复
-
knowledge: docpage-digest dual verification defines no verdict vocabulary or pass/fail threshold未关闭needs-human
难度 2/5 1-3 小时 新手友好度 78/100
melodic-software/claude-code-plugins#7286 · 2 条评论 ·
维护者通常 1 天内回复
查看 melodic-software/claude-code-plugins 的全部 Issue
相似的 Issue
-
bug needs-triage
难度 1/5 1 小时以内 新手友好度 78/100
mattpocock/skills#1281 ·
维护者通常 1 天内回复
-
github_actions
难度 2/5 1-3 小时 新手友好度 62/100
hiero-ledger/hiero-consensus-node#27621 ·
维护者通常 1 天内回复
-
application-issue
难度 2/5 1-3 小时 新手友好度 72/100
Installomator/Installomator#3427 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
software-mansion/argent#1483 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100