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

package/CHANGELOG.md

@@ -2,6 +2,49 @@
 
 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.
+
+### Changed
+
+- Renamed, with directories, frontmatter `name`, the platform registry, and `package.json#files` all moved together: `dingtalk-basic-behavior` → `dta-basic-behavior`, `dingtalk-agent-compose` → `dta-agent-compose`, `dingtalk-agent-eval` → `dta-agent-eval`, `dingtalk-people-group-memory` → `dta-people-group-memory`, `dingtalk-agent-deploy-multica` → `dta-deploy-multica`, `multica-external` → `dta-ops-multica`.
+- Two naming grammars are now stated and enforced: core skills are `dta-<domain>`, platform skills are `dta-<role>-<platform>` where `<role>` equals the role in the `src/agent-platform.ts` registry. The old `ops` role carried the name `multica-external`, so the filesystem and the registry disagreed about what that skill was; they no longer can.
+- `skill install` / `skill upgrade` (and therefore `setup`) delete the pre-rename copies from `~/.agents/skills` and `~/.claude/skills` after the new names are in place. A renamed skill is not a second skill — leaving both installed means two nearly identical descriptions are visible to every Host at once, and which one triggers is undefined. Removal is limited to names registered in `LEGACY_SKILL_RENAMES` and to this package's own two install locations; current-name copies and third-party skills are untouched, and repeating the operation is a no-op.
+- An Agent Project manifest that still declares the old Basic name in `agent.skills` is accepted and counts as declaring Basic, but the name is **not** normalized: path resolution keeps following the declared name, because the directory checked into the user's repository still carries it. This is the one place `dta` cannot migrate on the user's behalf.
+
+### Added
+
+- `check:docs` gains a fourth finding kind, `legacy-skill-name`: any pre-rename name appearing anywhere in the repository fails the check. The allowlist is explicit and short — historical evidence that must not be rewritten (`CHANGELOG.md`, `evals/baselines/`, the dated `docs/roadmap/` studies) plus the migration machinery that has to spell the old names out loud. A one-time sweep cleans the present; only a standing gate keeps it clean.
+- Contract scenarios #67–#69 cover the pruning of stale copies, manifest tolerance for the old Basic name, and self-consistency of the naming grammar (prefix, directory basename = frontmatter `name` = registry name, platform role/suffix shape, complete rename ledger, and `package.json#files` coverage). All three run in-process and add no measurable time to the core suite.
+
+### Fixed
+
+- `dta doctor` output is re-laid out (PR #20). Three concrete defects, not cosmetics: the `⚠️` summary and its `detail` printed the same platform-skill drift twice; `detail` joined four canonical paths and the drift string with ` | ` into a 200+ character line that always wrapped; and three separator styles (`·`, `;`, `|`) coexisted with no column aligned. The cause was that the renderer only ever received pre-joined sentences, so `DoctorCheck` now carries structured `value` / `items` fields (additive — existing `--json` assertions are untouched) and the printer lays out one fact per line with indented details, aligned by `displayWidth`. The three client checks and the `hosts` section are merged into one block instead of stating the same thing twice. Status glyphs stay `✅`/`⚠️`/`❌`: colour may be added, but the glyphs that carry the meaning are part of the stable stdout interface.
+- `dta doctor` pointed at a command that could not fix the problem it reported. On platform-skill drift it suggested `skill upgrade`, which only iterates `BUNDLED_SKILL_NAMES` and never touches a platform skill; on an `ahead` copy it omitted `--allow-downgrade`, which `upgradeGlobalSkill` requires before it will overwrite. Repair commands are now generated per skill from `canonical.state`, and the `outdated` / `modified` / `ahead` states are spelled out in words rather than printed as bare identifiers.
+- `package-lock.json` is realigned to `0.1.5-beta.7`; the manifest had been bumped without it.
+- `check:docs` walked into directories that `.gitignore` had already declared as not-repository-content: `.claude/worktrees/` (full working copies of other branches) and `.dingtalk-agent/` (runtime state). The markdown count had silently grown from 88 to 773, and the new `legacy-skill-name` gate then failed on pre-rename names sitting in someone else's branch — making `release:check` unpassable on any machine that has a worktree. The walker now derives its skip set from `.gitignore`'s directory entries instead of keeping a second hardcoded list.
+- `lab/robot-eval/suite.json` pinned `dta-basic-behavior@0.12.0` while the skill's `metadata.version` had moved to 0.13.0, so the robot-pool scenario's version-sync assertion failed.
+- `npm run release:check` now builds first. The contract runner imports 17 modules from `dist/` at load time, so the gate only ever worked when `dist/` happened to be current — any newly added source file turned the whole release gate into an opaque `ERR_MODULE_NOT_FOUND` before a single check ran.
+
+### Migration
+
+Existing installs need `dta upgrade` (or `dta skill upgrade`) once; it installs the new names and removes the old copies in the same run. Beyond this repository, three steps are **not** automated: push the renamed platform skills to the Multica workspace and delete the old-named server-side entries (`bootstrap.sh` pulls by name, so both present means pulling the wrong one), and redeploy any deployed Agent whose instructions reference the old Basic name.
+
 ## 0.1.5-beta.6 - 2026-07-23
 
 The CLI's output layer becomes a human/machine dual channel: a person at a terminal gets colour, hierarchy and step-by-step progress, while an Agent capturing stdout through a Bash tool reads text with **not a single ANSI escape** in it (PR #17). Ships on the `beta` dist-tag; `latest` stays at 0.1.4.

package/README.en.md

@@ -54,7 +54,7 @@ dta bootstrap --json      # Was the body recognized? Check definition.status and
 dta agent audit --json    # Expect partial — the role semantics are still template text, which is correct
 ```
 
-`release-manager` is a complete sample of a release-manager digital employee: it picks up "can we ship this version?" in a group, checks the gates, summarizes the verdict, and requires human confirmation before moving on. Replace the role duties in `agent/AGENTS.md` with your own, run `agent audit` again, and the only gap left is the load probe — which needs an Agent Host, see the [Compose Skill](skills/core/dingtalk-agent-compose/SKILL.md).
+`release-manager` is a complete sample of a release-manager digital employee: it picks up "can we ship this version?" in a group, checks the gates, summarizes the verdict, and requires human confirmation before moving on. Replace the role duties in `agent/AGENTS.md` with your own, run `agent audit` again, and the only gap left is the load probe — which needs an Agent Host, see the [Compose Skill](skills/core/dta-agent-compose/SKILL.md).
 
 ### Full delivery chain
 
@@ -89,11 +89,11 @@ Turning an Agent into a DingTalk digital employee takes six stages, and dta cove
 
 | Lifecycle stage | What dta does | With what |
 |---|---|---|
-| **① Body and employee skills** | An inheritable, verifiable shared behavior contract: when to speak, whether a message is even a task, who must approve an outbound action, how risk is graded, what counts as done, what to remember and forget. You write only the few dozen lines that differ by role | `dingtalk-basic-behavior` · `agent enhance` · `examples/agents/` |
+| **① Body and employee skills** | An inheritable, verifiable shared behavior contract: when to speak, whether a message is even a task, who must approve an outbound action, how risk is graded, what counts as done, what to remember and forget. You write only the few dozen lines that differ by role | `dta-basic-behavior` · `agent enhance` · `examples/agents/` |
 | **② Identity acquisition and event perception** | Normalize differently shaped raw events into a stable structure; freeze the reply target and execution identity into a snapshot message text cannot alter, making wrong-recipient structurally impossible; bind permissions and outbound ownership per field; one event yields exactly one Run, losing and duplicating nothing across crashes | `prepare` · `run` · Field config |
 | **③ Managed-platform deployment** | See the plan before anything lands: frozen hashes for the body and the whole Skill tree plus a write budget; independent readback and a load smoke test after writing; re-running the same version writes nothing; failures roll back and shipped agents can be retired (today this lands on Multica) | `deploy` · `promote` · `--retire` |
 | **④ Driving it to work inside DingTalk** | Outbound has only four atoms; before an action the gate blocks overreach and target drift, after it a platform readback is mandatory; no blind retries when the outcome is uncertain; a "done" report must carry re-verifiable evidence | `act` · Action Gate · `task checkpoint` |
-| **⑤ Evaluation design** | Not a scoring tool but a method: how to pick the cheapest sufficient level, which evidence surfaces one verdict must collect, which failures may never be averaged away, how a real incident becomes a replayable case, and what blocks a release | `lab` · `workspace eval` · `dingtalk-agent-eval` |
+| **⑤ Evaluation design** | Not a scoring tool but a method: how to pick the cheapest sufficient level, which evidence surfaces one verdict must collect, which failures may never be averaged away, how a real incident becomes a replayable case, and what blocks a release | `lab` · `workspace eval` · `dta-agent-eval` |
 | **⑥ Observation and feedback** | Bind a production finding to the exact version that ran, desensitize it, and feed it back into evaluation material, without ever changing the Agent's behavior on its own | `observe` |
 
 ## When to use it
@@ -181,9 +181,9 @@ Prepared Runs expose four message atoms: `ack`, `reply`, `ask`, and `silence`. A
 | Understand the Agent architecture and how the repo is divided | [Architecture](docs/ARCHITECTURE.md) |
 | Install, upgrade, or troubleshoot | [Installation](docs/INSTALLATION.md) |
 | Understand evaluation and evidence levels | [Self-test](docs/SELF-TEST.md) |
-| Create or audit an Agent | [Compose Skill](skills/core/dingtalk-agent-compose/SKILL.md) |
-| Test or debug a delivered Agent | [Eval Skill](skills/core/dingtalk-agent-eval/SKILL.md) |
-| Read the shared behavior protocol (a contract written for models, not a tutorial) | [Basic Behavior Skill](skills/core/dingtalk-basic-behavior/SKILL.md) |
+| Create or audit an Agent | [Compose Skill](skills/core/dta-agent-compose/SKILL.md) |
+| Test or debug a delivered Agent | [Eval Skill](skills/core/dta-agent-eval/SKILL.md) |
+| Read the shared behavior protocol (a contract written for models, not a tutorial) | [Basic Behavior Skill](skills/core/dta-basic-behavior/SKILL.md) |
 | Copy a complete example and edit from there | [Example Agents](examples/agents) |
 | Which platforms and open-source projects we keep absorbing practices from | [Prior Art](docs/PRIOR-ART.md) |
 

package/README.md

@@ -53,7 +53,7 @@ dta bootstrap --json      # 本体被识别了吗：看 definition.status 与 st
 dta agent audit --json    # 预期 partial：岗位语义还是模板，这是正确结果
 ```
 
-`release-manager` 是一个发布管理员数字员工的完整样例：它在群里接"这个版本能发吗"，检查门禁、汇总结论、需要人确认才推进。把 `agent/AGENTS.md` 里的岗位职责换成你自己的，再跑一次 `agent audit`，缺口就只剩加载探针，那需要一个 Agent Host，见 [Compose Skill](skills/core/dingtalk-agent-compose/SKILL.md)。
+`release-manager` 是一个发布管理员数字员工的完整样例：它在群里接"这个版本能发吗"，检查门禁、汇总结论、需要人确认才推进。把 `agent/AGENTS.md` 里的岗位职责换成你自己的，再跑一次 `agent audit`，缺口就只剩加载探针，那需要一个 Agent Host，见 [Compose Skill](skills/core/dta-agent-compose/SKILL.md)。
 
 ### 完整交付链
 
@@ -88,11 +88,11 @@ dta observe --promotion-id <promotion-id> --input <observation.json> --dry-run -
 
 | 开发生命周期 | dta 做的 | 用什么 |
 |---|---|---|
-| **① 本体与员工技能** | 一套可继承、可验证的共享行为合同：什么时候该开口、消息算不算任务、外部动作要谁批准、风险怎么分级、什么算完成、哪些要记哪些能忘。你只写岗位不一样的那几十行 | `dingtalk-basic-behavior` · `agent enhance` · `examples/agents/` |
+| **① 本体与员工技能** | 一套可继承、可验证的共享行为合同：什么时候该开口、消息算不算任务、外部动作要谁批准、风险怎么分级、什么算完成、哪些要记哪些能忘。你只写岗位不一样的那几十行 | `dta-basic-behavior` · `agent enhance` · `examples/agents/` |
 | **② 身份获取与事件感知** | 把格式各异的原始事件归一成稳定结构。回复对象和执行身份会冻结成正文改不动的快照，发错人在结构上就做不到；权限和出口按场域绑定；同一个事件只产生一个 Run，崩了也不会丢、不会重复 | `prepare` · `run` · Field 配置 |
 | **③ 托管平台部署** | 先看计划再落盘：冻结本体和整棵 Skill 树的 hash 和写预算，写完独立回读、发加载烟测，重复跑同一版不再写入。出问题能回滚，上了线也能退役（当前落地于 Multica） | `deploy` · `promote` · `--retire` |
 | **④ 驱动它在钉钉里干活** | 外发就四个原语。动作做之前挡掉越权和发错目标，做完之后强制回读平台确认；结果不确定时不许乱重发，报完成得留下能再核验的证据 | `act` · Action Gate · `task checkpoint` |
-| **⑤ 评测设计** | 一套评测方法：帮你选够用的最低层级，决定一次结论要看哪几类证据，避免个别失败被平均分掩盖，把真实事故变成能复跑的用例，也给出什么时候不能上线 | `lab` · `workspace eval` · `dingtalk-agent-eval` |
+| **⑤ 评测设计** | 一套评测方法：帮你选够用的最低层级，决定一次结论要看哪几类证据，避免个别失败被平均分掩盖，把真实事故变成能复跑的用例，也给出什么时候不能上线 | `lab` · `workspace eval` · `dta-agent-eval` |
 | **⑥ 观测与反馈** | 把线上发现的问题绑定到具体哪一版，脱敏后回流评测素材，不会自动改动 Agent 的行为 | `observe` |
 
 ## 什么时候该用它
@@ -180,9 +180,9 @@ Prepared Run 只开放 `ack`、`reply`、`ask`、`silence` 四个消息原子动
 | 理解 Agent 架构与仓库分工 | [Architecture](docs/ARCHITECTURE.md) |
 | 安装、升级与排障 | [Installation](docs/INSTALLATION.md) |
 | 理解评测与证据分层 | [Self-test](docs/SELF-TEST.md) |
-| 创建或审计 Agent | [Compose Skill](skills/core/dingtalk-agent-compose/SKILL.md) |
-| 测试或调试已交付的 Agent | [Eval Skill](skills/core/dingtalk-agent-eval/SKILL.md) |
-| 查看公共行为协议（写给模型读的合同，不是教程） | [Basic Behavior Skill](skills/core/dingtalk-basic-behavior/SKILL.md) |
+| 创建或审计 Agent | [Compose Skill](skills/core/dta-agent-compose/SKILL.md) |
+| 测试或调试已交付的 Agent | [Eval Skill](skills/core/dta-agent-eval/SKILL.md) |
+| 查看公共行为协议（写给模型读的合同，不是教程） | [Basic Behavior Skill](skills/core/dta-basic-behavior/SKILL.md) |
 | 复制一个完整示例开始改 | [Example Agents](examples/agents) |
 | 从哪些平台与开源项目持续吸收最佳实践 | [Prior Art](docs/PRIOR-ART.md) |
 

package/dist/bin/dingtalk-agent.js

@@ -31,7 +31,7 @@ import { runRobotEvaluation } from '../src/robot-evals.js';
 import { runOpenCodeEvaluation } from '../src/opencode-evals.js';
 import { runStorageEvaluation } from '../src/storage-evals.js';
 import { runPersonalEventEvaluation } from '../src/personal-event-evals.js';
-import { doctor } from '../src/doctor.js';
+import { CHECK_LABELS, doctor } from '../src/doctor.js';
 import { doctorDevelopmentWorkspace, inspectAgentProject, showDevelopmentWorkspace, } from '../src/development-workspace.js';
 import { buildScheduleShow, buildSchedulePlan } from '../src/schedule-plan.js';
 import { applyOpenCodeWorkspace, evalOpenCodeWorkspace, planOpenCodeWorkspace, runOpenCodeWorkspace, useOpenCodeWorkspace, } from '../src/opencode-provider.js';
@@ -994,9 +994,16 @@ async function main() {
         }
         if (o.json)
             console.log(JSON.stringify(out, null, 2));
-        else if ('skills' in out)
+        else if ('skills' in out) {
             for (const item of out.skills)
                 printSkillStatus(item, sub, dryRun);
+            // 静默删目录会让人以为什么都没发生；说清楚删了哪几个旧名。
+            for (const item of out.prunedLegacy || []) {
+                console.log(item.replacedBy
+                    ? `   已迁移 ${item.name} → ${item.replacedBy}`
+                    : `   已清理停用的 Skill ${item.name}`);
+            }
+        }
         else
             printSkillStatus(out, sub, dryRun);
         return;
@@ -1862,34 +1869,80 @@ function printSkillStatus(out, action, dryRun) {
         console.log(muted('   新 Agent 会话将自动发现；当前会话未发现时请重启 Claude Code/Codex。'));
     }
 }
+/**
+ * doctor 的版面。改造前的问题不是"不够花哨"，是三条实打实的：
+ *   1. 同一事实说两遍——⚠️ 摘要和它的 detail 重复平台 Skill 漂移；三个客户端
+ *      的 Skill 可见性在 check 区和「本机 Coding Agent」区各说一次。
+ *   2. 一行塞太多——detail 用 ` | ` 把四条 canonical 路径和平台 Skill 状态拼在
+ *      一起，200+ 字符，终端里必然折行。
+ *   3. 分隔符混用 `·` `;` `|` 三种，没有一列是对齐的。
+ * 所以这里按「一行一件事、明细缩进、列对齐」重排，并把客户端合并成一节。
+ */
 function printDoctor(out) {
-    console.log(`${strong('dingtalk-agent doctor')} · ${mark(out.ready ? 'pass' : 'fail', out.ready ? 'READY' : 'NOT READY')}`);
-    for (const check of out.checks) {
-        const glyph = check.level === 'pass' ? '✅' : check.level === 'warn' ? '⚠️' : '❌';
-        console.log(`${mark(levelOf(check.level), glyph)} ${check.summary}`);
-        if (check.detail)
-            console.log(`   ${muted(check.detail)}`);
-        if (check.fix)
-            console.log(`   修复: ${noun(check.fix)}`);
-    }
-    if (out.hosts.length) {
-        // Host 面回答"本地能在哪跑"，不改变上面的 ready 结论。
-        console.log(`\n${strong('本机 Coding Agent:')}`);
-        const width = Math.max(...out.hosts.map((host) => displayWidth(host.label)));
-        for (const host of out.hosts) {
-            const label = host.label + ' '.repeat(width - displayWidth(host.label));
-            const where = host.cli.found
-                ? [host.cli.path, host.cli.version].filter(Boolean).join('  ')
-                : `未找到 ${host.cli.command}`;
-            console.log(`  ${mark(levelOf(host.cli.found), host.cli.found ? '✅' : '❌')} ${label}  ${noun(where)}`);
-            console.log(muted(`     Skill 可见性: ${host.skillExposure.exists ? '已暴露' : '未暴露'} · ${host.skillExposureRoot}`));
-        }
-    }
-    if (out.nextSteps.length) {
-        console.log(`\n${strong('下一步:')}`);
-        for (const step of out.nextSteps)
-            console.log(`  ${noun(step)}`);
+    const { theme } = stdoutUi();
+    // 字形沿用全 CLI 既定的 ✅/⚠️/❌（bin 里各出现 24/11/5 次）。上一版换成
+    // ✔/!/✗ 让 doctor 成了唯一的异类，也违反 AGENTS.md「stdout 是稳定的人/
+    // 机器接口」——颜色可以加，承载语义的字形不能动。三者都是 2 列宽，对齐不受影响。
+    const glyph = (level) => level === 'pass' ? mark('pass', '✅')
+        : level === 'warn' ? mark('warn', '⚠️') : mark('fail', '❌');
+    const clientIds = new Set(['claude-code', 'codex', 'opencode']);
+    const envChecks = out.checks.filter((check) => !clientIds.has(check.id));
+    const clientChecks = out.checks.filter((check) => clientIds.has(check.id));
+    console.log(`${strong('dingtalk-agent doctor')} · ${out.ready ? mark('pass', 'READY') : mark('fail', 'NOT READY')}`);
+    console.log('');
+    // 左列按显示宽度对齐——中文标签用 String.length 补齐必然错位
+    const labelWidth = Math.max(...envChecks.map((check) => displayWidth(CHECK_LABELS[check.id])));
+    for (const check of envChecks) {
+        const label = padRight(CHECK_LABELS[check.id], labelWidth);
+        console.log(`  ${glyph(check.level)} ${strong(label)}  ${check.value || check.summary}`);
+        const items = check.items || [];
+        const itemWidth = items.length ? Math.max(...items.map((i) => displayWidth(i.label))) : 0;
+        const valueWidth = items.length ? Math.max(...items.map((i) => displayWidth(i.value || ''))) : 0;
+        for (const item of items) {
+            console.log(`      ${noun(padRight(item.label, itemWidth))}  ${padRight(item.value || '', valueWidth)}${item.note ? `  ${muted(item.note)}` : ''}`);
+        }
+        if (check.level !== 'pass' && check.fix) {
+            // 一条命令一行。挤在同一行里用「与」串起来的命令没法直接复制。
+            const commands = plain(check.fix).replace(/^运行\s*/, '').split(/\s*与\s*/);
+            commands.forEach((command, index) => {
+                console.log(`      ${muted(index === 0 ? '修复' : '    ')}  ${noun(command)}`);
+            });
+        }
+    }
+    if (clientChecks.length) {
+        console.log('');
+        console.log(`  ${strong('Coding Agent')}`);
+        const nameWidth = Math.max(...clientChecks.map((c) => displayWidth(CHECK_LABELS[c.id])));
+        const hostOf = (id) => out.hosts.find((host) => host.name === id);
+        // 版本列去掉冗余括注与前缀：claude 报 "2.1.218 (Claude Code)"、codex 报 "codex-cli 0.144.6"
+        const versions = clientChecks.map((c) => (hostOf(c.id)?.cli.version || '')
+            .replace(/\s*\(.*\)\s*$/, '').replace(/^\S+-cli\s+/, ''));
+        const versionWidth = Math.max(...versions.map(displayWidth));
+        clientChecks.forEach((check, index) => {
+            const host = hostOf(check.id);
+            const name = padRight(CHECK_LABELS[check.id], nameWidth);
+            const version = padRight(versions[index], versionWidth);
+            const where = host?.cli.found ? tilde(host.skillExposureRoot) : `未安装 ${host?.cli.command || ''}`;
+            console.log(`  ${glyph(check.level)} ${strong(name)}  ${muted(version)}  ${check.value || check.summary}  ${noun(where)}`);
+        });
     }
+    // 「下一步」此前逐字重复上面已经打过的修复命令。只留没展示过的。
+    const shown = new Set(out.checks.filter((c) => c.level !== 'pass' && c.fix).map((c) => c.fix));
+    const remaining = out.nextSteps.filter((step) => !shown.has(step));
+    if (remaining.length) {
+        console.log('');
+        for (const step of remaining)
+            console.log(`  ${strong('下一步')}  ${noun(plain(step))}`);
+    }
+}
+/** 反引号在终端里不是强调，是噪声；着色已经承担了同一职责。 */
+function plain(text) {
+    return text.replace(/`/g, '');
+}
+/** 家目录缩成 ~/，省掉对读者零信息量的前缀。 */
+function tilde(path) {
+    const home = process.env.HOME || '';
+    return home && path.startsWith(home) ? `~${path.slice(home.length)}` : path;
 }
 function printProjectInfo(out) {
     console.log(`${strong('dingtalk-agent Project')} · ${noun(out.project.name)}`);