weflow-cli 1.6.0 → 1.6.2

package/CHANGELOG.md

@@ -4,11 +4,40 @@ The npm package is published separately from GitHub. It may lag behind the `mast
 
 All notable user-facing changes are recorded here. This project follows [Semantic Versioning](https://semver.org/).
 
+## 1.6.2
+
+### Fixed
+
+- Read every message shard, not just the configured one. WeChat rolls a conversation into a new `message_N.db` over time and encrypts each shard with its own PBKDF2-derived key. `sessions`, `messages`, `contacts`, `export json/txt/excel`, `evidence` and the MCP server opened only `message_0.db` with the single configured key, so anything written after the last shard roll was **invisible** - and the commands still reported success. On the machine this was found on, one conversation showed 31 messages ending 2026-08-30 instead of 1145 ending 2026-09-17. Only `export html` merged shards (its Python exporter always had), which is why the two read paths disagreed.
+- `export <talker> html --limit N` now honours the limit. It reached only the fallback renderer; the primary path passed the flag nowhere, so a capped export of a busy chat silently produced the entire history.
+- `export <talker> excel` works at all. `exceljs` is CJS-only, so `await import('exceljs')` yields a namespace whose only member is `default`; `new ExcelJS.Workbook()` on the namespace is a `TypeError`, which a bare `catch {}` turned into the uninformative "Excel 导出失败". The reason is now reported too.
+- Group messages no longer show the sender's own `wxid_...:` prefix in the text (`波: [强]`, not `波: wxid_ogfiei1l1ye722: [强]`). Only `parsedContent` is normalised; `content`/`rawContent` keep the stored value.
+- `contacts` no longer emits a blank row for `Name2Id`'s placeholder entry.
+- `fav list` no longer blames the data channel when the actual blocker is a missing favorites key. Added `check --json` → `favoritesReady`, which distinguishes "database found" from "usable".
+- Subprocess failures now include the last stderr line, redacted of key-shaped strings. A missing config key used to surface as `统计失败 (exit 1)` with no cause; it now names the cause and the command that fixes it.
+- `daily-stats` / `daily` no longer tell users to run `config set bizKey`, which the CLI rejects as an unwritable key.
+- `init --refresh` no longer fails with "密钥提取失败" when a perfectly good key is already configured. The hook only fires at the login moment, so a refresh run against an already-logged-in WeChat always times out; the fallback then consulted **only** `favPassphrase`, which `init` itself never writes (it writes `decryptKey`, and `favPassphrase` is set only when a usable `favorite.db` exists). Reads use `favPassphrase || decryptKey`, so the fallback rejected keys the rest of the tool was happily using. Reported as "最新版本的微信密钥解不开了" (Issue #9) after a WeChat upgrade, where `init --refresh` is exactly what the CLI tells users to run. The fallback now matches the read path, and the summary distinguishes a fresh capture ("密钥获取成功") from reusing what was configured ("已沿用配置中的密钥") instead of claiming success either way. Reaching that point also lets `enableFavorites` run, so favorites start working for users who previously died here.
+
+### Added
+
+- `scripts/health_check.py` and `docs/HEALTH-CHECK.md`: a periodic, zero-token health check whose exit code is the verdict, covering version drift, shard read consistency, session freshness, export formats and the watcher tasks.
+
+## 1.6.1
+
+### Fixed
+
+- Report the real version from `--version` and `capabilities`. The version was a literal in the CLI source and `npm version` only rewrites `package.json`, so the 1.6.0 package announced itself as `1.5.1` - which made a user's bug report impossible to tell apart from a stale install, and took a clean install to disprove.
+- Keep the discovered database list when the NT scan cannot read WeChat's memory. `nt_decrypt.py scan` returned early on "Weixin.exe 未运行" *before* walking the filesystem, and the caller discarded the whole result on any error. The passphrase-derivation path - the correct one for current WeChat, and one that needs only the file list - therefore never ran, so a run that had already captured the passphrase still ended with no usable keys and `sessions` reported "WCDB 初始化失败: -1006".
+
+### Documentation
+
+- Added `docs/RELEASING.md`: versioning rules, the pre-publish check for local media and keys, npm credentials with 2FA, and the China-mirror sync step that otherwise leaves users unable to install a fresh release.
+
 ## 1.6.0
 
 ### Documentation
 
-- Synchronized setup, operations, architecture, security, MCP, and maintenance guidance with the current `1.6.0` source baseline.
+- Synchronized setup, operations, architecture, security, MCP, and maintenance guidance with the current `1.6.1` source baseline.
 - Clarified source-versus-npm version drift, no-AI daily runs, staged data-directory discovery, media-export limitations, and local-data privacy boundaries.
 - Replaced the outdated architecture image with a GPT-image-2 diagram covering current CLI, MCP, service, workflow, data, and privacy boundaries.
 

package/README.md

@@ -321,6 +321,8 @@ python scripts/fav_server.py --date YYYY-MM-DD
 - [项目维护状态](./docs/PROJECT_STATE.md)：当前能力、限制、优先级与交接入口。
 - [技术决策记录](./docs/DECISIONS.md)：长期维护中的关键设计取舍。
 - [分支与合并记录](./docs/BRANCHES.md)：分支用途、合并时间线与并行开发的对齐约定。
+- [发布清单](./docs/RELEASING.md)：版本号、打包敏感内容检查、npm 凭据、国内镜像同步。
+- [定期体检](./docs/HEALTH-CHECK.md)：一条命令查出版本漂移、分片漏读、会话不更新与导出失败。
 - [电子数据证据指南](./docs/EVIDENCE_GUIDE.md)：证据保全、法律边界与使用注意事项。
 - [贡献指南](./CONTRIBUTING.md) 与 [安全策略](./SECURITY.md)：开发、反馈和敏感问题处理。
 - [变更记录](./CHANGELOG.md)：版本更新摘要。

package/bin/weflow-cli.ts

@@ -28,6 +28,26 @@ function resolvePackageRoot(): string {
   return resolvePackageRootFrom(import.meta.url)
 }
 
+/**
+ * Version reported by `--version` and `capabilities`.
+ *
+ * Read from package.json instead of written here. A literal has to be updated
+ * by hand on every release, and when that is forgotten `--version` lies about
+ * what is installed - which is exactly what happened: the 1.6.0 package
+ * shipped a hardcoded `1.5.1`, so a user's bug report could not be told apart
+ * from a stale install, and diagnosing it needed a clean install to disprove.
+ */
+function resolveCliVersion(): string {
+  try {
+    const pkg = JSON.parse(readFileSync(join(resolvePackageRoot(), 'package.json'), 'utf8'))
+    return String(pkg.version || '0.0.0')
+  } catch {
+    return '0.0.0'
+  }
+}
+
+const CLI_VERSION = resolveCliVersion()
+
 function pythonProcessEnv(apiKey?: string, variable = 'DEEPSEEK_API_KEY'): NodeJS.ProcessEnv {
   return createPythonProcessEnv(apiKey ? { [variable]: apiKey } : {})
 }
@@ -247,7 +267,7 @@ async function resolveTalker(input: string, quiet = false, nonInteractive = fals
 program
   .name('weflow-cli')
   .description('WeFlow CLI - 微信聊天记录命令行查询与导出工具')
-  .version('1.5.1')
+  .version(CLI_VERSION)
 
 program
   .command('capabilities')
@@ -256,7 +276,7 @@ program
   .action((opts) => {
     const data = {
       schema: 'weflow-capabilities/v1',
-      version: '1.5.1',
+      version: CLI_VERSION,
       read: {
         sessions: { cli: 'sessions --json', mcp: 'wechat.list_sessions' },
         messages: { cli: 'messages <talker> --json', mcp: 'wechat.export_messages' },
@@ -665,6 +685,8 @@ program
       console.log(chalk.gray('  尝试从 WeFlow 桌面版配置读取...'))
       let extractedKey = opts.testMissingKeys ? '' : tryReadWeFlowKey()
       let linuxNtKey = ''
+      /** 密钥是本次从 hook 捕获的, 还是沿用已有的 - 摘要要说准, 不能一律报"获取成功" */
+      let keyCaptured = false
 
       if (extractedKey) {
         console.log(chalk.green('  ✓ 从 WeFlow 配置读取到密钥'))
@@ -750,11 +772,17 @@ program
 
         if (keyResult.success && keyResult.key) {
           extractedKey = keyResult.key
+          keyCaptured = true
         } else {
-          // hook 只在登录瞬间触发; 微信已登录时捕获不到 → 回退到已配置的 passphrase
-          const fallback = configService.get('favPassphrase') || ''
+          // hook 只在登录瞬间触发; 微信已登录时捕获不到 → 回退到已有密钥。
+          // decryptKey 也必须算数: init 成功时写入的就是它, 而 favPassphrase
+          // 仅在收藏库存在且验证通过时才会被设置。只看 favPassphrase 会让
+          // `init --refresh` 在一把完全可用的密钥面前报「密钥提取失败」——
+          // 而那正是 CLI 自己在微信迁移后建议用户执行的命令。
+          const fallback = configService.get('favPassphrase') || configService.get('decryptKey') || ''
           if (fallback) {
-            console.log(chalk.gray('  Hook 未捕获到密钥 (微信已登录时不再触发密钥函数), 使用已配置的 passphrase 继续'))
+            console.log(chalk.gray('  Hook 未捕获到密钥 (微信已登录时不再触发密钥函数)'))
+            console.log(chalk.gray('  检测到已配置的密钥, 沿用它并重新验证各库...'))
             extractedKey = fallback
           } else {
             console.log(chalk.red(`\n✗ 密钥提取失败: ${keyResult.error}`))
@@ -769,7 +797,8 @@ program
 
       if (extractedKey) {
         configService.set('decryptKey', extractedKey)
-        console.log(chalk.green('\n✓ 密钥获取成功!'))
+        if (keyCaptured) console.log(chalk.green('\n✓ 密钥获取成功!'))
+        else console.log(chalk.green('\n✓ 已沿用配置中的密钥 (本次未重新捕获)'))
       } else {
         console.log(chalk.green('\n✓ NT 密钥配置完成!'))
       }
@@ -2499,14 +2528,26 @@ favCmd
       else console.log(chalk.red(`\n❌ 数据库连接失败: ${conn.error}\n`))
       process.exit(1)
     }
-    if (!chatService.isFavSupported()) {
+    const favReason = chatService.favUnavailableReason()
+    if (favReason) {
+      const detail = {
+        channel: '当前数据通道不支持收藏查询 (需 4.x NT 连接)',
+        path: '未找到收藏数据库 (favorite.db)，请确认微信已登录并产生过收藏',
+        key: '收藏数据库已找到，但缺少密钥',
+      }[favReason]
       if (opts.json) {
-        console.log(JSON.stringify({ success: false, code: 'FAVORITES_UNAVAILABLE', error: '当前数据通道不支持收藏查询' }))
+        console.log(JSON.stringify({ success: false, code: 'FAVORITES_UNAVAILABLE', reason: favReason, error: detail }))
         process.exit(1)
       }
-      console.log(chalk.red('\n❌ 当前数据通道不支持收藏查询 (需 4.x NT 连接)'))
-      console.log(chalk.gray('  请先配置收藏密钥: weflow-cli fav set-key <64位hex密钥>'))
-      console.log(chalk.gray('  或设置全库 passphrase: weflow-cli fav set-key --passphrase <64位hex>\n'))
+      console.log(chalk.red(`\n❌ ${detail}`))
+      if (favReason === 'key') {
+        console.log(chalk.gray('  请先配置收藏密钥: weflow-cli fav set-key <64位hex密钥>'))
+        console.log(chalk.gray('  或设置全库 passphrase: weflow-cli fav set-key --passphrase <64位hex>'))
+      }
+      if (favReason === 'path') {
+        console.log(chalk.gray('  可手动指定: weflow-cli config set favDbPath <favorite.db 路径>'))
+      }
+      console.log('')
       process.exit(1)
     }
 
@@ -5342,6 +5383,12 @@ program
           messageDatabase: !!configService.get('ntDbPath') && existsSync(configService.get('ntDbPath')),
           momentsDatabase: !!configService.get('snsDbPath') && existsSync(configService.get('snsDbPath')),
           favoritesDatabase: !!configService.get('favDbPath') && existsSync(configService.get('favDbPath')),
+          // `favoritesDatabase` only says the file is there. Reading it also
+          // needs a key, and a caller that took the former for "usable" would
+          // attempt favorites and always fail.
+          favoritesReady: !!configService.get('favDbPath')
+            && existsSync(configService.get('favDbPath'))
+            && (!!configService.get('favKey') || !!configService.get('favPassphrase')),
         },
         assistant: {
           engine,

package/dist/bin/weflow-cli.js

@@ -24,6 +24,25 @@ const program = new Command();
 function resolvePackageRoot() {
     return resolvePackageRootFrom(import.meta.url);
 }
+/**
+ * Version reported by `--version` and `capabilities`.
+ *
+ * Read from package.json instead of written here. A literal has to be updated
+ * by hand on every release, and when that is forgotten `--version` lies about
+ * what is installed - which is exactly what happened: the 1.6.0 package
+ * shipped a hardcoded `1.5.1`, so a user's bug report could not be told apart
+ * from a stale install, and diagnosing it needed a clean install to disprove.
+ */
+function resolveCliVersion() {
+    try {
+        const pkg = JSON.parse(readFileSync(join(resolvePackageRoot(), 'package.json'), 'utf8'));
+        return String(pkg.version || '0.0.0');
+    }
+    catch {
+        return '0.0.0';
+    }
+}
+const CLI_VERSION = resolveCliVersion();
 function pythonProcessEnv(apiKey, variable = 'DEEPSEEK_API_KEY') {
     return createPythonProcessEnv(apiKey ? { [variable]: apiKey } : {});
 }
@@ -231,7 +250,7 @@ async function resolveTalker(input, quiet = false, nonInteractive = false) {
 program
     .name('weflow-cli')
     .description('WeFlow CLI - 微信聊天记录命令行查询与导出工具')
-    .version('1.5.1');
+    .version(CLI_VERSION);
 program
     .command('capabilities')
     .description('输出 AI 可调用的功能能力清单')
@@ -239,7 +258,7 @@ program
     .action((opts) => {
     const data = {
         schema: 'weflow-capabilities/v1',
-        version: '1.5.1',
+        version: CLI_VERSION,
         read: {
             sessions: { cli: 'sessions --json', mcp: 'wechat.list_sessions' },
             messages: { cli: 'messages <talker> --json', mcp: 'wechat.export_messages' },
@@ -639,6 +658,8 @@ program
         console.log(chalk.gray('  尝试从 WeFlow 桌面版配置读取...'));
         let extractedKey = opts.testMissingKeys ? '' : tryReadWeFlowKey();
         let linuxNtKey = '';
+        /** 密钥是本次从 hook 捕获的, 还是沿用已有的 - 摘要要说准, 不能一律报"获取成功" */
+        let keyCaptured = false;
         if (extractedKey) {
             console.log(chalk.green('  ✓ 从 WeFlow 配置读取到密钥'));
         }
@@ -725,12 +746,18 @@ program
             });
             if (keyResult.success && keyResult.key) {
                 extractedKey = keyResult.key;
+                keyCaptured = true;
             }
             else {
-                // hook 只在登录瞬间触发; 微信已登录时捕获不到 → 回退到已配置的 passphrase
-                const fallback = configService.get('favPassphrase') || '';
+                // hook 只在登录瞬间触发; 微信已登录时捕获不到 → 回退到已有密钥。
+                // decryptKey 也必须算数: init 成功时写入的就是它, 而 favPassphrase
+                // 仅在收藏库存在且验证通过时才会被设置。只看 favPassphrase 会让
+                // `init --refresh` 在一把完全可用的密钥面前报「密钥提取失败」——
+                // 而那正是 CLI 自己在微信迁移后建议用户执行的命令。
+                const fallback = configService.get('favPassphrase') || configService.get('decryptKey') || '';
                 if (fallback) {
-                    console.log(chalk.gray('  Hook 未捕获到密钥 (微信已登录时不再触发密钥函数), 使用已配置的 passphrase 继续'));
+                    console.log(chalk.gray('  Hook 未捕获到密钥 (微信已登录时不再触发密钥函数)'));
+                    console.log(chalk.gray('  检测到已配置的密钥, 沿用它并重新验证各库...'));
                     extractedKey = fallback;
                 }
                 else {
@@ -745,7 +772,10 @@ program
         }
         if (extractedKey) {
             configService.set('decryptKey', extractedKey);
-            console.log(chalk.green('\n✓ 密钥获取成功!'));
+            if (keyCaptured)
+                console.log(chalk.green('\n✓ 密钥获取成功!'));
+            else
+                console.log(chalk.green('\n✓ 已沿用配置中的密钥 (本次未重新捕获)'));
         }
         else {
             console.log(chalk.green('\n✓ NT 密钥配置完成!'));
@@ -2569,14 +2599,26 @@ favCmd
             console.log(chalk.red(`\n❌ 数据库连接失败: ${conn.error}\n`));
         process.exit(1);
     }
-    if (!chatService.isFavSupported()) {
+    const favReason = chatService.favUnavailableReason();
+    if (favReason) {
+        const detail = {
+            channel: '当前数据通道不支持收藏查询 (需 4.x NT 连接)',
+            path: '未找到收藏数据库 (favorite.db)，请确认微信已登录并产生过收藏',
+            key: '收藏数据库已找到，但缺少密钥',
+        }[favReason];
         if (opts.json) {
-            console.log(JSON.stringify({ success: false, code: 'FAVORITES_UNAVAILABLE', error: '当前数据通道不支持收藏查询' }));
+            console.log(JSON.stringify({ success: false, code: 'FAVORITES_UNAVAILABLE', reason: favReason, error: detail }));
             process.exit(1);
         }
-        console.log(chalk.red('\n❌ 当前数据通道不支持收藏查询 (需 4.x NT 连接)'));
-        console.log(chalk.gray('  请先配置收藏密钥: weflow-cli fav set-key <64位hex密钥>'));
-        console.log(chalk.gray('  或设置全库 passphrase: weflow-cli fav set-key --passphrase <64位hex>\n'));
+        console.log(chalk.red(`\n❌ ${detail}`));
+        if (favReason === 'key') {
+            console.log(chalk.gray('  请先配置收藏密钥: weflow-cli fav set-key <64位hex密钥>'));
+            console.log(chalk.gray('  或设置全库 passphrase: weflow-cli fav set-key --passphrase <64位hex>'));
+        }
+        if (favReason === 'path') {
+            console.log(chalk.gray('  可手动指定: weflow-cli config set favDbPath <favorite.db 路径>'));
+        }
+        console.log('');
         process.exit(1);
     }
     let favType;
@@ -5544,6 +5586,12 @@ program
                 messageDatabase: !!configService.get('ntDbPath') && existsSync(configService.get('ntDbPath')),
                 momentsDatabase: !!configService.get('snsDbPath') && existsSync(configService.get('snsDbPath')),
                 favoritesDatabase: !!configService.get('favDbPath') && existsSync(configService.get('favDbPath')),
+                // `favoritesDatabase` only says the file is there. Reading it also
+                // needs a key, and a caller that took the former for "usable" would
+                // attempt favorites and always fail.
+                favoritesReady: !!configService.get('favDbPath')
+                    && existsSync(configService.get('favDbPath'))
+                    && (!!configService.get('favKey') || !!configService.get('favPassphrase')),
             },
             assistant: {
                 engine,