weflow-cli 1.11.0 → 1.11.1

package/CHANGELOG.md

@@ -17,6 +17,44 @@ purpose** - a hand-written "latest is X" is exactly the claim that goes stale he
 
 All notable user-facing changes are recorded here. This project follows [Semantic Versioning](https://semver.org/).
 
+## 1.11.1
+
+- **Five defects in 1.11.0's document export, all found by looking at a real export instead of the code.**
+  Re-exporting one 1,914-message conversation (29 documents on disk) and asking whether what got written can
+  actually be **opened** turned up two files that would have been unopenable in the reader's own editor:
+
+  1. A document whose name contains a half-width parenthesis - `…开题报告(2).pdf` - landed in the link target
+     as-is, and **every markdown renderer ends a target at the first `)`**, so the link stopped at `…报告(2`
+     and opened nothing. A space breaks it the same way (the target ends at whitespace). Targets are now
+     percent-encoded per path segment (`%282%29`, `%20`) while the link text stays the original name and
+     Chinese characters stay literal - `%E5%…` would be correct but unreadable.
+  2. The 80-character filename limit was applied to the whole name, so a long title lost its **extension**:
+     one file landed as `Chang 等 - 2022 - Environmental Justice Assessment of Fine Particles, Ozone, and`
+     with no `.pdf`, leaving the OS and every editor without a clue how to open it. The limit now applies to
+     the stem, with the extension kept.
+
+  Both were **invisible to the code and to the existing tests** - the first pass "worked" and produced a
+  complete-looking asset directory. Hunting for the rest of that class turned up three more:
+
+  3. **A filename containing a control character killed the whole export at the last step.** A tab in a message
+     title makes `open()` raise `OSError: Invalid argument` on Windows, and nothing caught it - minutes of
+     parsing and image extraction were thrown away by one bad name. Copy failures (bad name, path too long,
+     target locked) are now counted as `unavailable` instead. Control characters are also stripped from the
+     on-disk name, the link text, and `sanitize_filename` generally.
+  4. **Windows reserved device names** (`CON.pdf`, `NUL.txt`, `aux.docx`) cannot be created at all; they are now
+     prefixed with `_`. Checked alongside: 200-character titles, `[草稿]` brackets, `#`, `%`, quotes, emoji,
+     trailing dots, `|*?` - a battery of 21 real-world names, with every resulting link asserted to *resolve*.
+  5. **A narrower export silently erased a wider one's manifest.** The manifest lives in the shared
+     `<talker>_assets/` directory, so exporting the whole conversation and then running
+     `json --media --limit 600` into the same folder overwrote 585 entries with 150 - the wider run's documents
+     kept their links in the markdown but vanished from the manifest, and neither side reported anything. The
+     manifest is now **merged** with the existing one (entries whose file is gone are dropped), and it records
+     both `copied` (this run) and `exported` (present in the directory), because those were being conflated.
+
+  One more, not a defect but the same "silent" shape: `--media` together with `html` did nothing at all (HTML
+  writes no document bodies by design, so that is not a missing feature) and said nothing, which reads as a
+  broken switch. The CLI now names the reason and points at `md` / `json --media`.
+
 ## 1.11.0
 
 - **Documents now travel with the export — all five formats, bodies included.** The same user report that asked

package/OPERATIONS.md

@@ -101,7 +101,13 @@ weflow-cli export "联系人A" json --output ./output
 `msg/file/YYYY-MM/` 下，按 `(归一化名, 字节数)` 对上，同名多份时用 md5 定。本机实测 1,855 条文件消息里
 **1,643 条对得上（88.6%）**，其余 212 条本地确实没有那份文件（没下载过或已清理）—— 这些消息仍是
 `[文件] 名字` 的标签，不清单里凑数、也不猜。导出的计数里 `exported` 是"这份文档在 assets 里"，
-`written` 才是"这次新拷了几个"，别把后者当成前者的成绩。
+`written`（清单里叫 `documents.copied`）才是"这次新拷了几个"，别把后者当成前者的成绩。
+另外 `--media` 配 `html` 不生效（HTML 不写文档本体），CLI 会提示一句而不是静默忽略。
+
+md 里指向文档的链接**把路径里的空格、括号等字符做了百分号编码**（如 `报告%282%29.pdf`），链接文字仍是原名。
+这不是洁癖：文档名里带半角括号时（`报告(2).pdf` 这种），链接目标会被任何 markdown 渲染器在**第一个 `)`
+处截断**，点开是空的（2026-10-13 重导时实测到；同一批里还有一份超长标题被 80 字符上限连 `.pdf` 一起截掉，
+落成一个没有扩展名的文件——那条也修了）。
 
 **HTML 导出（含 `--full-images`）不写文件本体**：HTML 的用法是"单文件可分享"，把几 MB 的 PDF 内嵌成
 base64 既没人打得开、也把网页撑大。要在文件本体上要文档，用 `md` 或 `json|txt|excel --media`。

package/bin/weflow-cli.ts

@@ -1881,6 +1881,13 @@ program
         else console.log(chalk.red(`✗ 媒体抽取失败: ${media.error}`))
         process.exit(1)
       }
+    } else if (opts.media && format === 'html') {
+      // HTML 的用法是"单文件可分享"，所以它不写文档本体（把几 MB 的 PDF 内嵌进网页，既打不开也把文件撑大）。
+      // 静默忽略这个开关会让人以为它生效了 —— 明说一句，并给出该用哪个格式。
+      if (!opts.json) {
+        console.error(chalk.gray('  提示：HTML 导出不含文档本体（单文件分享的用法），--media 对它不生效；'))
+        console.error(chalk.gray('        要连文档一起导出请用 md，或 json|txt|excel --media。'))
+      }
     }
     switch (format) {
       case 'json':

package/dist/bin/weflow-cli.js

@@ -1912,6 +1912,14 @@ program
             process.exit(1);
         }
     }
+    else if (opts.media && format === 'html') {
+        // HTML 的用法是"单文件可分享"，所以它不写文档本体（把几 MB 的 PDF 内嵌进网页，既打不开也把文件撑大）。
+        // 静默忽略这个开关会让人以为它生效了 —— 明说一句，并给出该用哪个格式。
+        if (!opts.json) {
+            console.error(chalk.gray('  提示：HTML 导出不含文档本体（单文件分享的用法），--media 对它不生效；'));
+            console.error(chalk.gray('        要连文档一起导出请用 md，或 json|txt|excel --media。'));
+        }
+    }
     switch (format) {
         case 'json':
             result = await exportService.exportJson(talker, opts.output, limit, from, to, opts.contract);