docs: record the trigger-word fix that shipped in 0.5.0 - #4
Merged
Merged
Conversation
The 0.5.0 section was written before the phantom-trigger bug was found. The tag was later re-pointed to include the fix, so v0.5.0 on npm and the GitHub Release carry a user-visible behaviour change the notes never mention: an Agent that cannot reach a Skill no longer advertises a trigger word for it. Both support matrices said "the latest GitHub Actions run passes", which ages without anyone noticing. They now name the date, and the Windows row says what was actually found: concurrent commands can still fail a registry write there, because Windows refuses to rename onto a file another process holds open. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
知识库同步时发现的文档与产物不一致。
CHANGELOG 漏了一条已发布的变更
v0.5.0标签实际包含三个提交，其中f21b570（幽灵触发词修复）是在 0.5.0 小节写完之后才做的——当时标签被重新指向了含该修复的提交，但 CHANGELOG 没跟着补。结果：npm 上的 0.5.0 和 GitHub Release v0.5.0 都带着这个用户可见的行为变化（Agent 读不到的 Skill 不再显示触发词），而发布说明里一个字没提。
两份 README 的 CI 表述会随时间烂掉
「最近一次 GitHub Actions 通过」/「The latest GitHub Actions run passes」是没有锚点的说法，过半年还这么写就是假的。改成写明日期。
Windows 那一行同时补上了实际查到的情况：多条命令并发时仍可能写清单失败（Windows 不允许 rename 到被别的进程打开的文件）。这个问题的修复在 #3，本 PR 只如实描述现状。
验证
npm test98/98v0.4.0..v0.5.0全部三个提交🤖 Generated with Claude Code