@xdxer/dingtalk-agent 0.1.5-beta.7 → 0.1.5-beta.8

package/CHANGELOG.md

@@ -2,6 +2,20 @@
 
 All notable changes to `@xdxer/dingtalk-agent` are documented here. The project follows semantic versioning; prerelease entries describe release candidates and do not imply that Live canaries or registry publication have completed.
 
+## 0.1.5-beta.8 - 2026-07-23
+
+Follow-up to the beta.7 rename, from watching a real machine take the upgrade: the four core skills migrated cleanly, the two platform skills sat untouched and unannounced. The three defects below are the same shape — "clean up" was not carried through to the end. Ships on the `beta` dist-tag; `latest` stays at 0.1.4.
+
+### Fixed
+
+- Renamed platform skills were stranded, not migrated. `skill install` / `upgrade` only install `BUNDLED_SKILL_NAMES` (the four core skills), so the "replacement must exist before deleting the old copy" gate correctly declined to touch `dingtalk-agent-deploy-multica` and `multica-external` — but nothing ever installed their replacements either, leaving those machines permanently on pre-rename copies with no notice. Stale-copy handling is now a real migration: a legacy skill that is present but whose replacement is not installed gets the replacement installed first, then the old copy removed. This only ever acts on skills the machine already had, so it preserves existing capability rather than adding anything.
+- Dangling exposure symlinks survived cleanup. `~/.agents/skills/<name>` is deleted before `~/.claude/skills/<name>`, which leaves the latter pointing at nothing — and `rmSync` stats the *target*, so `force: true` swallowed the resulting `ENOENT` as "already gone" and left the link in place. The skill therefore stayed visible to Claude Code and was re-reported on every pass. Symlinks are now removed with `unlinkSync`.
+- `dingtalk-agent-boot-multica`, removed from the package back in 0.1.5-beta.2, was still installed on machines and still exposed to Hosts through its `~/.claude/skills` symlink. Withdrawn skills now have their own removal list; unlike a rename they have no replacement to gate on, so they are simply deleted.
+
+### Migration
+
+`dta upgrade` once more. A machine that took beta.7 has its platform skills carried to the new names on the next `skill install` / `upgrade`, and every removed copy is printed by name — the operation is never silent.
+
 ## 0.1.5-beta.7 - 2026-07-23
 
 **BREAKING.** All six first-party skills move to a `dta-` prefix. The names were previously drawn from three unrelated grammars (`dingtalk-*`, `dingtalk-agent-*`, and a bare `multica-external` with no first-party signal at all), and they all land in `~/.agents/skills/<name>/` — a flat namespace shared with Claude Code, Codex, and OpenCode that this repository does not own. The prefix puts the package owner in the first segment. Ships on the `beta` dist-tag; `latest` stays at 0.1.4.

package/dist/bin/dingtalk-agent.js

@@ -999,7 +999,9 @@ async function main() {
                 printSkillStatus(item, sub, dryRun);
             // 静默删目录会让人以为什么都没发生；说清楚删了哪几个旧名。
             for (const item of out.prunedLegacy || []) {
-                console.log(`   已清理改名前的旧副本 ${item.name} → 现用 ${item.replacedBy}`);
+                console.log(item.replacedBy
+                    ? `   已迁移 ${item.name} → ${item.replacedBy}`
+                    : `   已清理停用的 Skill ${item.name}`);
             }
         }
         else