uniner-cli 1.0.5 → 1.0.6

package/README.md

@@ -21,9 +21,9 @@ npm install -g uniner-cli
 安装过程：
 
 1. npm 装本壳包（约 50KB）
-2. `postinstall` 钩子从 `static.uniner.com` 拉取约 250MB 便携包
-3. 解压到 `%USERPROFILE%\.uniner-cli\<version>\`
-4. 写入 `%USERPROFILE%\.claude\skills\uniner-cli\SKILL.md`
+2. `postinstall` 钩子从 `static.uniner.com` 拉取对应平台的便携包（Windows ~280MB / macOS ~75MB / Linux ~185MB）
+3. 解压到 `~/.uniner-cli/<version>/`
+4. 写入 `~/.claude/skills/uniner-cli/SKILL.md`
 
 完成后任意终端：
 
@@ -35,12 +35,12 @@ uniner-cli --help
 
 | 项 | 要求 |
 |---|---|
-| 操作系统 | 64 位 Windows 10 / 11 |
+| 操作系统 | Windows 10/11 x64 · macOS 12+ ARM64 · Linux x64 |
 | Node.js | >= 14 |
-| 磁盘空间 | ≥ 1.5 GB |
+| 磁盘空间 | ≥ 500 MB（单平台） |
 | 网络 | 能访问 `static.uniner.com` |
 
-> Linux / macOS 支持在路上。
+> 安装脚本会自动检测当前系统并下载对应版本。
 
 ## 使用示例
 
@@ -61,7 +61,7 @@ uniner-cli excel data write --file out.xlsx --cell B2 --value "hello"
 uniner-cli tool ocr ddddocr --img captcha.png
 ```
 
-完整命令树（一级 + 二级 + 三级参数）见安装后 `%USERPROFILE%\.uniner-cli\<version>\skills\cli\SKILL.md`。
+完整命令树（一级 + 二级 + 三级参数）见安装后 `~/.uniner-cli/<version>/skills/cli/SKILL.md`。
 
 ## 升级
 
@@ -80,19 +80,21 @@ npm install -g uniner-cli@latest
 ## 卸载
 
 ```bash
-# 1. 先清理运行时数据（删 ~/.uniner-cli/ 和 Claude Code 技能）
-uniner-cli-uninstall
-
-# 2. 再卸载 npm 包本身
 npm uninstall -g uniner-cli
 ```
 
-> **为什么是两步？** npm 7+ 出于安全考虑不再在卸载时运行 lifecycle 脚本，所以我们提供 `uniner-cli-uninstall` 命令让你显式触发清理。
+卸载时 `preuninstall` 钩子会自动清理：
+
+- `~/.uniner-cli/` 整个运行时目录（含所有版本）
+- `~/.claude/skills/uniner-cli/SKILL.md` 技能文件
 
-清理会移除：
+> `~/.claude/skills/uniner-cli/scenarios/` 下用户积累的场景数据不会被自动删除，需手动清理。
 
-- `%USERPROFILE%\.uniner-cli\<version>\` 安装目录
-- `%USERPROFILE%\.claude\skills\uniner-cli\SKILL.md` 技能
+如需手动触发清理（如 npm 包已不在但残留仍在）：
+
+```bash
+uniner-cli-uninstall
+```
 
 ## 环境变量
 
@@ -104,13 +106,19 @@ npm uninstall -g uniner-cli
 
 确认 npm 全局 bin 在 PATH 上：
 
-```powershell
+```bash
+# macOS / Linux
+npm config get prefix
+echo $PATH | tr ':' '\n' | grep npm
+
+# Windows (PowerShell)
 npm config get prefix
-# 应输出类似 C:\Users\xxx\AppData\Roaming\npm
 $env:Path -split ';' | Where-Object { $_ -like '*npm*' }
 ```
 
-如果没有，手动加 `%APPDATA%\npm` 到 PATH。
+如果没有，手动将 npm 全局 bin 目录加入 PATH：
+- macOS / Linux: `$(npm config get prefix)/bin`
+- Windows: `%APPDATA%\npm`
 
 ### 安装时下载失败 / 超时
 
@@ -140,7 +148,7 @@ npm uninstall -g uniner-cli
 npm install -g uniner-cli
 ```
 
-## 备选安装方式（不走 npm）
+## 备选安装方式（仅 Windows，不走 npm）
 
 如果你不想要 Node.js 依赖，可以用 PowerShell 一行安装（基于 Inno Setup 安装器）：
 
@@ -148,6 +156,8 @@ npm install -g uniner-cli
 iwr https://static.uniner.com/soft/editor/uninercli/install.ps1 -UseBasicParsing | iex
 ```
 
+> macOS / Linux 用户请使用 npm 安装。
+
 两种方式互不干扰，但**不要**同时启用——会有两份 SKILL.md / 两份二进制。
 
 ## 链接
@@ -156,6 +166,16 @@ iwr https://static.uniner.com/soft/editor/uninercli/install.ps1 -UseBasicParsing
 - 技术支持：support@uniner.com
 - Claude Code：[https://claude.com/claude-code](https://claude.com/claude-code)
 
+## Changelog
+
+### 1.0.6 (2026-06-28)
+
+- **fix**: 修复 `npm uninstall -g uniner-cli` 未清理 `~/.uniner-cli/` 和 `~/.claude/skills/uniner-cli/SKILL.md` 的问题（新增 `preuninstall` 钩子）
+
+### 1.0.5 (2026-06-27)
+
+- 首个公开版本，支持 Windows 10/11 (x64)、macOS (Apple Silicon)、Linux (x64)
+
 ## License
 
 Proprietary. (C) 2026 Uniner Tech.

package/bin/uniner-cli-uninstall.js

@@ -1,145 +1,48 @@
-#!/usr/bin/env node
-// uniner-cli-uninstall - removes the runtime tree and Claude Code skill.
-//
-// npm 7+ no longer runs preuninstall/postuninstall lifecycle scripts on
-// uninstall (security tightening). So we ship this command for users to
-// run BEFORE `npm uninstall -g uniner-cli` to clean their machine.
-//
-// Recommended workflow:
-//   uniner-cli-uninstall              # this script: clean ~/.uniner-cli/ + skill
-//   npm uninstall -g uniner-cli       # npm: remove the npm package itself
-//
-// Idempotent: if files are already gone, just no-ops.
-
-'use strict';
-
-const fs   = require('fs');
-const path = require('path');
-
-const {
-    pkg,
-    rootDir,
-    versionDir,
-    skillDir,
-    skillFile,
-} = require('../lib/paths');
-
-function log(msg)  { console.log(`[uniner-cli] ${msg}`); }
-function warn(msg) { console.warn(`[uniner-cli] [WARN] ${msg}`); }
-
-function rmRf(p) {
-    try {
-        if (fs.existsSync(p)) {
-            fs.rmSync(p, { recursive: true, force: true });
-            log(`Removed ${p}`);
-            return true;
-        }
-        return false;
-    } catch (e) {
-        warn(`Could not remove ${p}: ${e.message}`);
-        return false;
-    }
-}
-
-function rmFile(p) {
-    try {
-        if (fs.existsSync(p)) {
-            fs.unlinkSync(p);
-            log(`Removed ${p}`);
-            return true;
-        }
-        return false;
-    } catch (e) {
-        warn(`Could not remove ${p}: ${e.message}`);
-        return false;
-    }
-}
-
-function main() {
-    console.log('');
-    console.log('==========================================');
-    console.log('  uniner-cli uninstall cleanup');
-    console.log('==========================================');
-
-    const myVersion = pkg.version;
-    const myVersionDir = versionDir(myVersion);
-    let didSomething = false;
-
-    // 1. Remove our version's runtime tree.
-    if (rmRf(myVersionDir)) didSomething = true;
-
-    // 2. If ~/.uniner-cli/ has no other versions, drop the whole directory.
-    try {
-        const root = rootDir();
-        if (fs.existsSync(root)) {
-            const remaining = fs.readdirSync(root);
-            if (remaining.length === 0) {
-                fs.rmdirSync(root);
-                log(`Removed empty ${root}`);
-                didSomething = true;
-            } else {
-                log(`Other uniner-cli versions still installed: ${remaining.join(', ')}`);
-                log(`Keeping ${root}`);
-            }
-        }
-    } catch (e) {
-        warn(`Could not inspect ${rootDir()}: ${e.message}`);
-    }
-
-    // 3. Remove ONLY the SKILL.md file. NEVER rm -rf the whole skill dir,
-    //    because the user's accumulated scenarios/<name>/ subdirectories
-    //    live there and represent real work they've sedimented over time.
-    //    If they really want everything gone they can do it manually; we
-    //    surface the path below so they know where to look.
-    const dir = skillDir();
-    if (rmFile(skillFile())) didSomething = true;
-
-    // 4. Look for scenarios/ — if there are any, keep them and tell the user.
-    let scenariosKept = 0;
-    const scenariosDir = path.join(dir, 'scenarios');
-    if (fs.existsSync(scenariosDir)) {
-        try {
-            scenariosKept = fs.readdirSync(scenariosDir).filter(n => {
-                const meta = path.join(scenariosDir, n, 'meta.json');
-                return fs.existsSync(meta);
-            }).length;
-        } catch (_) {
-            // best-effort
-        }
-    }
-
-    // 5. If skill dir is now genuinely empty, remove it. Otherwise keep it.
-    try {
-        if (fs.existsSync(dir)) {
-            const remaining = fs.readdirSync(dir);
-            if (remaining.length === 0) {
-                fs.rmdirSync(dir);
-                log(`Removed empty ${dir}`);
-                didSomething = true;
-            }
-        }
-    } catch (_) {
-        // best-effort
-    }
-
-    if (!didSomething) {
-        log('Nothing to clean — already removed.');
-    }
-
-    console.log('');
-    if (scenariosKept > 0) {
-        console.log('==========================================');
-        console.log(`  ${scenariosKept} scenario(s) PRESERVED at:`);
-        console.log(`    ${scenariosDir}`);
-        console.log('  (your accumulated knowledge — not deleted)');
-        console.log('  To delete them too:');
-        console.log(`    rm -rf "${scenariosDir}"          # bash`);
-        console.log(`    Remove-Item "${scenariosDir}" -Recurse -Force   # PowerShell`);
-        console.log('==========================================');
-    }
-    console.log('Cleanup done. To complete uninstall, also run:');
-    console.log('  npm uninstall -g uniner-cli');
-    console.log('');
-}
-
-main();
+#!/usr/bin/env node
+// uniner-cli-uninstall — manual cleanup command.
+//
+// Since v1.0.6 we register a `preuninstall` lifecycle hook that does the
+// same cleanup automatically when you run `npm uninstall -g uniner-cli`.
+// This manual command is still available for users who want verbose
+// feedback, or who want to clean up without going through npm
+// (e.g. the npm package is already gone but the runtime files remain).
+//
+// Recommended workflow:
+//   npm uninstall -g uniner-cli              # hook runs the cleanup automatically
+//
+// If something is still left behind, run this to force a verbose cleanup:
+//   npx uniner-cli-uninstall                 # before uninstalling
+//   # or, after npm already removed the package:
+//   node ~/.uniner-cli/<version>/bin/uniner-cli-uninstall.js   (if the shim is gone)
+//
+// Idempotent: if files are already gone, just no-ops.
+
+'use strict';
+
+const { cleanup } = require('../scripts/cleanup');
+
+console.log('');
+console.log('==========================================');
+console.log('  uniner-cli uninstall cleanup');
+console.log('==========================================');
+
+const result = cleanup({ verbose: true });
+
+console.log('');
+if (result.scenariosKept > 0) {
+    console.log('==========================================');
+    console.log(`  ${result.scenariosKept} scenario(s) PRESERVED at:`);
+    console.log(`    ${result.scenariosDir}`);
+    console.log('  (your accumulated knowledge — not deleted)');
+    console.log('  To delete them too:');
+    console.log(`    rm -rf "${result.scenariosDir}"          # bash`);
+    console.log(`    Remove-Item "${result.scenariosDir}" -Recurse -Force   # PowerShell`);
+    console.log('==========================================');
+}
+
+if (result.didSomething) {
+    console.log('Cleanup done.');
+} else {
+    console.log('Nothing to clean — already removed.');
+}
+console.log('');

package/lib/SKILL.md.template

@@ -5,7 +5,7 @@ description: RPA 自动化 CLI 工具，提供浏览器自动化、Excel 操作
 
 # uniner-cli Skill
 
-> 由 UninerCLI Installer v{{VERSION}} 自动安装到 `%USERPROFILE%\.claude\skills\uniner-cli\`
+> 由 UninerCLI Installer v{{VERSION}} 自动安装到 `~/.claude/skills/uniner-cli/`
 > 安装位置（绝对路径）：`{{INSTALL_PATH}}`
 
 ## 🛑 任务结束硬性规则（最重要，先读这一节）
@@ -152,7 +152,7 @@ uniner-cli [全局选项] <模块> <子命令> <命令> [命令选项]
 ## 关键注意事项（6 条 TOC，详情看链接）
 
 1. **Chrome CDP 自动管理** — 别手动 kill Chrome；客户机必须装 Chrome 或 Edge
-2. **session 持久化** — `$TEMP\.uniner-cli\sessions.json`；CLI 退出后用 `web browser reconnect` 恢复
+2. **session 持久化** — `$TEMP/uniner-cli-sessions/sessions.json`（Windows: `%TEMP%\uniner-cli-sessions\sessions.json`）；CLI 退出后用 `web browser reconnect` 恢复
 3. **Vue/Element UI 组件** — 日期选择器、级联下拉等，用 `execute-js` 直接操作组件模型，不要硬 input
 4. **desktop 返回 -999** = Agent 服务未启动；此时改用 `web action execute-js` 或 `tool system execute`
 5. **Linux 平台** — Playwright 默认 HTTPS-only，访问 HTTP 站点需改 wrapper 加 `--disable-features=HttpsOnlyMode`，或用 Firefox `--browser-type 1`
@@ -162,14 +162,14 @@ uniner-cli [全局选项] <模块> <子命令> <命令> [命令选项]
 
 | 主题 | 路径 |
 |---|---|
-| 命令树全集 + 三级参数 | [{{INSTALL_PATH}}\skills\cli\SKILL.md]({{INSTALL_PATH}}\skills\cli\SKILL.md) |
-| SDK ↔ CLI 命令映射 | [{{INSTALL_PATH}}\skills\cli\sdk-cli-mapping.md]({{INSTALL_PATH}}\skills\cli\sdk-cli-mapping.md) |
-| Windows 配置指南 | [{{INSTALL_PATH}}\skills\windows-setup-guide.md]({{INSTALL_PATH}}\skills\windows-setup-guide.md) |
-| Linux 配置指南 | [{{INSTALL_PATH}}\skills\linux-setup-guide.md]({{INSTALL_PATH}}\skills\linux-setup-guide.md) |
-| 实战案例（TMS 抓单） | [{{INSTALL_PATH}}\skills\tms-workflow-test-report.md]({{INSTALL_PATH}}\skills\tms-workflow-test-report.md) |
-| Helper 脚本（Chrome 启动 / Vue 日期 / 表格提取） | [{{INSTALL_PATH}}\skills\cli\helpers\]({{INSTALL_PATH}}\skills\cli\helpers\) |
-| 用户手册 | [{{INSTALL_PATH}}\docs\]({{INSTALL_PATH}}\docs\) |
-| 工作目录（保存截图/Excel/下载） | [{{INSTALL_PATH}}\workdir\]({{INSTALL_PATH}}\workdir\) |
+| 命令树全集 + 三级参数 | [{{INSTALL_PATH}}/skills/cli/SKILL.md]({{INSTALL_PATH}}/skills/cli/SKILL.md) |
+| SDK ↔ CLI 命令映射 | [{{INSTALL_PATH}}/skills/cli/sdk-cli-mapping.md]({{INSTALL_PATH}}/skills/cli/sdk-cli-mapping.md) |
+| Windows 配置指南 | [{{INSTALL_PATH}}/skills/windows-setup-guide.md]({{INSTALL_PATH}}/skills/windows-setup-guide.md) |
+| Linux 配置指南 | [{{INSTALL_PATH}}/skills/linux-setup-guide.md]({{INSTALL_PATH}}/skills/linux-setup-guide.md) |
+| 实战案例（TMS 抓单） | [{{INSTALL_PATH}}/skills/tms-workflow-test-report.md]({{INSTALL_PATH}}/skills/tms-workflow-test-report.md) |
+| Helper 脚本（Chrome 启动 / Vue 日期 / 表格提取） | [{{INSTALL_PATH}}/skills/cli/helpers/]({{INSTALL_PATH}}/skills/cli/helpers/) |
+| 用户手册 | [{{INSTALL_PATH}}/docs/]({{INSTALL_PATH}}/docs/) |
+| 工作目录（保存截图/Excel/下载） | [{{INSTALL_PATH}}/workdir/]({{INSTALL_PATH}}/workdir/) |
 
 ## 典型完整流程（参考）
 
@@ -182,8 +182,8 @@ uniner-cli web browser open --url "https://example.com/login"
 # 2. 输账号密码 + 截验证码 + OCR
 uniner-cli web element input --xpath "//input[@id='user']" --value "u01"
 uniner-cli web element input --xpath "//input[@id='pwd']" --value "p01"
-uniner-cli web element screenshot --xpath "//img[@id='captcha']" --output "{{INSTALL_PATH}}\workdir\cap.png"
-uniner-cli tool ocr ddddocr --img "{{INSTALL_PATH}}\workdir\cap.png"
+uniner-cli web element screenshot --xpath "//img[@id='captcha']" --output "{{INSTALL_PATH}}/workdir/cap.png"
+uniner-cli tool ocr ddddocr --img "{{INSTALL_PATH}}/workdir/cap.png"
 # 从返回 JSON 的 data.result 取识别文本
 
 # 3. 提交登录
@@ -195,8 +195,8 @@ uniner-cli web navigation wait --type element --xpath "//table"
 uniner-cli web action execute-js --code "return Array.from(document.querySelectorAll('table tr')).map(r => Array.from(r.cells).map(c => c.textContent.trim()))"
 
 # 5. 写 Excel
-uniner-cli excel file create --file "{{INSTALL_PATH}}\workdir\out.xlsx"
-uniner-cli excel data write-range --file "{{INSTALL_PATH}}\workdir\out.xlsx" --cell A1 --values "<上一步的 JSON 二维数组>"
+uniner-cli excel file create --file "{{INSTALL_PATH}}/workdir/out.xlsx"
+uniner-cli excel data write-range --file "{{INSTALL_PATH}}/workdir/out.xlsx" --cell A1 --values "<上一步的 JSON 二维数组>"
 
 # 6. 关浏览器
 uniner-cli web browser close
@@ -209,9 +209,11 @@ uniner-cli web browser close
 每个场景一个目录，三件套：`meta.json` + `steps.json` + `SKILL.md`，存到：
 
 ```
-%USERPROFILE%\.claude\skills\uniner-cli\scenarios\<kebab-case-name>\
+~/.claude/skills/uniner-cli/scenarios/<kebab-case-name>/
 ```
 
+（Windows: `%USERPROFILE%\.claude\skills\uniner-cli\scenarios\<kebab-case-name>\`）
+
 **4 步标准流程**：
 
 ```bash
@@ -331,7 +333,7 @@ Open Claude Code, paste this:
    I ran 'uniner-cli skill run' and step 'click-search' failed.
    Error: timeout
    Please look at the scenario at:
-     C:\Users\xxx\.claude\skills\uniner-cli\scenarios\tms-export
+     ~/.claude/skills/uniner-cli/scenarios/tms-export
    Especially steps.json. Help me figure out why and suggest a fix.
 ──────────────────────────────────
 ```
@@ -368,4 +370,4 @@ uniner-cli skill delete <name> --yes   # 删除（默认 dry-run）
 - `uniner-cli --help` 看一级
 - `uniner-cli web --help` 看二级
 - `uniner-cli web element click --help` 看具体参数
-- 仍不确定 → Read [{{INSTALL_PATH}}\skills\cli\SKILL.md]({{INSTALL_PATH}}\skills\cli\SKILL.md)
+- 仍不确定 → Read [{{INSTALL_PATH}}/skills/cli/SKILL.md]({{INSTALL_PATH}}/skills/cli/SKILL.md)

package/package.json

@@ -1,6 +1,6 @@
 {
     "name":  "uniner-cli",
-    "version":  "1.0.5",
+    "version":  "1.0.6",
     "description":  "uniner-cli — RPA automation CLI: browser automation (Playwright/CDP), Excel, OCR, desktop/SAP, crypto/HTTP/email tools. Auto-installs a Claude Code skill on install.",
     "keywords":  [
                      "rpa",
@@ -25,7 +25,8 @@
                 "uniner-cli-uninstall":  "bin/uniner-cli-uninstall.js"
             },
     "scripts":  {
-                    "postinstall":  "node scripts/postinstall.js"
+                    "postinstall":   "node scripts/postinstall.js",
+                    "preuninstall":  "node scripts/preuninstall.js"
                 },
     "engines":  {
                     "node":  "\u003e=14"

package/scripts/cleanup.js

@@ -0,0 +1,123 @@
+// Shared cleanup logic for uninstall.
+// Extracted so both the npm lifecycle hook (preuninstall.js) and the
+// manual command (bin/uniner-cli-uninstall.js) can share it.
+
+'use strict';
+
+const fs   = require('fs');
+const path = require('path');
+
+const {
+    rootDir,
+    skillDir,
+    skillFile,
+} = require('../lib/paths');
+
+function rmRf(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.rmSync(p, { recursive: true, force: true });
+            return true;
+        }
+        return false;
+    } catch (_) {
+        return false;
+    }
+}
+
+function rmFile(p) {
+    try {
+        if (fs.existsSync(p)) {
+            fs.unlinkSync(p);
+            return true;
+        }
+        return false;
+    } catch (_) {
+        return false;
+    }
+}
+
+/**
+ * Run the full uninstall cleanup.
+ *
+ * @param {object}  [opts]
+ * @param {boolean} [opts.verbose=false]  Print progress lines to stdout.
+ *                                         The preuninstall hook should pass false
+ *                                         because npm swallows lifecycle output
+ *                                         unless --verbose is used; the manual
+ *                                         command passes true so the user sees
+ *                                         what happened.
+ * @returns {{ didSomething: boolean, scenariosKept: number, scenariosDir: string|null }}
+ */
+function cleanup(opts) {
+    const verbose = (opts && opts.verbose) || false;
+
+    function log(msg) {
+        if (verbose) {
+            console.log(`[uniner-cli] ${msg}`);
+        }
+    }
+
+    const root = rootDir();
+    let didSomething = false;
+
+    // 1. Remove the entire ~/.uniner-cli/ tree (all versions).
+    //    The version-specific layout exists so the installer can support
+    //    multi-version coexistence, but on uninstall the user wants a full
+    //    removal — orphaned old version dirs would just waste disk space.
+    if (rmRf(root)) {
+        log(`Removed ${root}`);
+        didSomething = true;
+    }
+
+    // 2. Remove ONLY the SKILL.md file. NEVER rm -rf the whole skill dir,
+    //    because the user's accumulated scenarios/<name>/ subdirectories
+    //    live there and represent real work they've sedimented over time.
+    const dir = skillDir();
+    if (rmFile(skillFile())) {
+        log(`Removed ${skillFile()}`);
+        didSomething = true;
+    }
+
+    // 3. Count scenarios/ subdirs that contain a meta.json.
+    let scenariosKept   = 0;
+    const scenariosPath = path.join(dir, 'scenarios');
+    if (fs.existsSync(scenariosPath)) {
+        try {
+            scenariosKept = fs.readdirSync(scenariosPath).filter(n => {
+                const meta = path.join(scenariosPath, n, 'meta.json');
+                return fs.existsSync(meta);
+            }).length;
+        } catch (_) {
+            // best-effort
+        }
+    }
+
+    // 4. If skill dir is now genuinely empty, remove it. Otherwise keep it.
+    try {
+        if (fs.existsSync(dir)) {
+            const remaining = fs.readdirSync(dir);
+            if (remaining.length === 0) {
+                fs.rmdirSync(dir);
+                log(`Removed empty ${dir}`);
+                didSomething = true;
+            } else if (verbose) {
+                log(`Keeping ${dir} (${scenariosKept} scenario(s) preserved)`);
+            }
+        }
+    } catch (_) {
+        // best-effort
+    }
+
+    if (!didSomething) {
+        log('Nothing to clean — already removed.');
+    }
+
+    return {
+        didSomething,
+        scenariosKept,
+        scenariosDir: scenariosKept > 0 ? scenariosPath : null,
+    };
+}
+
+module.exports = { cleanup };

package/scripts/preuninstall.js

@@ -0,0 +1,25 @@
+#!/usr/bin/env node
+// preuninstall.js — npm lifecycle hook, runs automatically on
+// `npm uninstall -g uniner-cli`.
+//
+// Cleans up the runtime tree (~/.uniner-cli/<version>/) and the skill file
+// (~/.claude/skills/uniner-cli/SKILL.md). Preserves user scenarios under
+// ~/.claude/skills/uniner-cli/scenarios/ — those represent accumulated
+// knowledge and are never deleted automatically.
+//
+// IMPORTANT: This script MUST exit 0 in all cases, otherwise it would
+// abort the user's `npm uninstall`. Errors are swallowed silently.
+//
+// The manual `uniner-cli-uninstall` command is still useful for users who
+// want verbose feedback, or who want to clean up before the npm package is
+// gone (e.g. if the hook somehow didn't fire).
+
+'use strict';
+
+const { cleanup } = require('./cleanup');
+
+try {
+    cleanup({ verbose: false });
+} catch (_) {
+    // Never fail the uninstall — swallow all errors.
+}