"CLI-Anything: Making ALL Software Agent-Native" -- CLI-Hub: https://clianything.cc/
Python
fix(joplin): remove BOMs and sync docs
27494539a-hub190bd89dc4a9
diff --git a/README.md b/README.mdindex 87e25797b..f80cf0ecb 100644--- a/README.md+++ b/README.md@@ -1,4 +1,4 @@-<h1 align="center"><img src="assets/icon.png" alt="" width="64" style="vertical-align: middle;"> CLI-Anything: Making ALL Software Agent-Native</h1>+<h1 align="center"><img src="assets/icon.png" alt="" width="64" style="vertical-align: middle;"> CLI-Anything: Making ALL Software Agent-Native</h1><div align="center"><a href="https://trendshift.io/repositories/22991" target="_blank"><img src="https://trendshift.io/api/badge/repositories/22991" alt="HKUDS%2FCLI-Anything | Trendshift" style="width: 250px; height: 55px;" width="250" height="55"/></a>@@ -906,7 +906,7 @@ Each application received complete, production-ready CLI interfaces — not demo<td>Note-taking & To-dos</td><td><code>cli-anything-joplin</code></td><td>Joplin terminal CLI subprocess</td>-<td align="center">✅ 131</td>+<td align="center">✅ 134</td></tr><tr><td align="center"><strong>📝 <a href="mubu/agent-harness/">Mubu</a></strong></td>@@ -1222,7 +1222,7 @@ cli-anything/├── 📧 mailchimp/agent-harness/ # Mailchimp Marketing API CLI (303 commands, 36 unit tests)├── 📚 zotero/agent-harness/ # Zotero CLI (new, write import support)├── 📖 calibre/agent-harness/ # Calibre CLI (58 tests: 38 unit + 20 E2E)-├── 📓 joplin/agent-harness/ # Joplin CLI (131 tests: 107 unit + 27 e2e)+├── 📓 joplin/agent-harness/ # Joplin CLI (134 tests: 107 unit + 27 e2e)├── 📝 mubu/agent-harness/ # Mubu CLI (96 tests)├── 📹 obs-studio/agent-harness/ # OBS Studio CLI (153 tests)├── 📱 nslogger/agent-harness/ # NSLogger CLI (139 tests)diff --git a/README_CN.md b/README_CN.mdindex 5e949257b..ffac02dd9 100644--- a/README_CN.md+++ b/README_CN.md@@ -1,4 +1,4 @@-<h1 align="center"><img src="assets/icon.png" alt="" width="64" style="vertical-align: middle;"> CLI-Anything: 让所有软件都能被 Agent 驱动</h1>+<h1 align="center"><img src="assets/icon.png" alt="" width="64" style="vertical-align: middle;"> CLI-Anything: 让所有软件都能被 Agent 驱动</h1><p align="center"><strong>今天的软件为人而生👨💻,明天的用户是 Agent🤖<br>@@ -643,7 +643,7 @@ CLI-Anything 适用于任何有代码库的软件 —— 不限领域,不限<td>笔记与待办</td><td><code>cli-anything-joplin</code></td><td>Joplin 终端 CLI 子进程</td>-<td align="center">✅ 131</td>+<td align="center">✅ 134</td></tr><tr><td align="center" colspan="4"><strong>合计</strong></td>@@ -747,7 +747,7 @@ cli-anything/├── 🎵 audacity/agent-harness/ # Audacity CLI(161 项测试)├── 📄 libreoffice/agent-harness/ # LibreOffice CLI(158 项测试)├── 📚 zotero/agent-harness/ # Zotero CLI(新增,支持文献导入)-├── 📓 joplin/agent-harness/ # Joplin CLI(131 测试:104 单元 + 27 e2e)+├── 📓 joplin/agent-harness/ # Joplin CLI(134 测试:107 单元 + 27 e2e)├── 📹 obs-studio/agent-harness/ # OBS Studio CLI(153 项测试)├── 🎞️ kdenlive/agent-harness/ # Kdenlive CLI(155 项测试)├── 🎬 shotcut/agent-harness/ # Shotcut CLI(154 项测试)diff --git a/README_JA.md b/README_JA.mdindex 033497018..eda2f7bb3 100644--- a/README_JA.md+++ b/README_JA.md@@ -557,12 +557,19 @@ CLI-Anythingはコードベースを持つあらゆるソフトウェアで動<td align="center">✅ 40</td></tr><tr>+<td align="center"><strong>📓 <a href="joplin/agent-harness/">Joplin</a></strong></td>+<td>ノートとToDo管理</td>+<td><code>cli-anything-joplin</code></td>+<td>Joplinターミナルクライアント(サブプロセス)</td>+<td align="center">✅ 134</td>+</tr>+<tr><td align="center" colspan="4"><strong>合計</strong></td>-<td align="center"><strong>✅ 1,547</strong></td>+<td align="center"><strong>✅ 1,681</strong></td></tr></table>-> **全1,547テストで100%パス** — 1,108ユニットテスト + 439エンドツーエンドテスト。+> **全1,681テストで100%パス** — 1,215ユニットテスト + 466エンドツーエンドテスト。---@@ -591,8 +598,9 @@ zoom 22 passed ✅ (22 unit + 0 e2e)drawio 138 passed ✅ (116 unit + 22 e2e)anygen 50 passed ✅ (40 unit + 10 e2e)nsight-graphics 40 passed ✅ (36 unit + 4 e2e)+joplin 134 passed ✅ (107 unit + 27 e2e, 1 skipped on Windows)──────────────────────────────────────────────────────────────────────────────-合計 1,547 passed ✅ 100% パス率+合計 1,681 passed ✅ 100% パス率```---@@ -652,7 +660,7 @@ cli-anything/├── 📞 zoom/agent-harness/ # Zoom CLI (22テスト)├── 📐 drawio/agent-harness/ # Draw.io CLI (138テスト)├── ✨ anygen/agent-harness/ # AnyGen CLI (50テスト)-├── 📓 joplin/agent-harness/ # Joplin CLI (118テスト、新規)+├── 📓 joplin/agent-harness/ # Joplin CLI (134テスト: 107 unit + 27 e2e, 新規)└── 🟩 nsight-graphics/agent-harness/ # Nsight Graphics CLI (40テスト)```diff --git a/joplin/agent-harness/JOPLIN.md b/joplin/agent-harness/JOPLIN.mdindex 2d0b94cd9..9c12cb457 100644--- a/joplin/agent-harness/JOPLIN.md+++ b/joplin/agent-harness/JOPLIN.md@@ -1,10 +1,10 @@-# JOPLIN Harness SOP+# JOPLIN Harness SOP## Overview`cli-anything-joplin` is a stateful CLI harness for Joplin automation backed bythe real `joplin` terminal binary. It is intended for command-driven-workflows, real-backend validation, and agent-style demo runs.+workflows, real-backend validation, and agent demo runs.## Requirementsdiff --git a/joplin/agent-harness/README.md b/joplin/agent-harness/README.mdindex b95b8297e..67d8668d7 100644--- a/joplin/agent-harness/README.md+++ b/joplin/agent-harness/README.md@@ -1,4 +1,4 @@-# Joplin Agent Harness+# Joplin Agent Harness`cli-anything-joplin` is a stateful CLI harness for the Joplin terminalapplication. It wraps the real `joplin` binary for backend operations and is@@ -12,7 +12,7 @@ demonstrations.status, config, backend utility, API server, and E2EE command groups- emits a stable JSON envelope (`ok`/`command`/`data`/`error`) for machineparsing-- supports one-shot mode and REPL mode+- supports one-shot and REPL modes- auto-saves the harness project on mutation; honors `--dry-run`## Requirementsdiff --git a/joplin/agent-harness/cli_anything/joplin/README.md b/joplin/agent-harness/cli_anything/joplin/README.mdindex dd3cb832a..eaf72160c 100644--- a/joplin/agent-harness/cli_anything/joplin/README.md+++ b/joplin/agent-harness/cli_anything/joplin/README.md@@ -1,7 +1,8 @@-# cli-anything-joplin+# cli-anything-joplin-`cli-anything-joplin` is a stateful CLI harness that wraps the real `joplin` terminal-binary, exposing every common Joplin workflow under a uniform JSON command envelope.+`cli-anything-joplin` is a stateful CLI harness that wraps the real `joplin`+terminal binary and exposes common Joplin workflows under a uniform JSON+command envelope.It supports:diff --git a/joplin/agent-harness/cli_anything/joplin/WORKFLOWS.md b/joplin/agent-harness/cli_anything/joplin/WORKFLOWS.mdindex 1a3ff263b..c5ab6804e 100644--- a/joplin/agent-harness/cli_anything/joplin/WORKFLOWS.md+++ b/joplin/agent-harness/cli_anything/joplin/WORKFLOWS.md@@ -8,20 +8,20 @@ has implemented and verified. It is intended as the single source of truth forThe harness covers 12 workflow categories:-1. CLI surface �?`--help`, every group's help, JSON envelope-2. Project lifecycle �?`new`, `open`, `info`, `json`, `save`, `status`,+1. CLI surface - `--help`, every group's help, JSON envelope+2. Project lifecycle - `new`, `open`, `info`, `json`, `save`, `status`,`session status/undo/redo/history`-3. Notebook lifecycle �?`list`, `create`, `use`, `remove`-4. Note lifecycle �?`list`, `create`, `set`, `get`, `remove`-5. Note organization �?`copy`, `move`, `rename`-6. To-do lifecycle �?`create`, `list`, `toggle`, `clear`, `done`, `undone`-7. Tag management �?`list`, `add`, `remove`, `notetags`, `tagnotes`-8. Search �?`run` (best-effort; some Joplin CLI builds gate this behind GUI mode)-9. Sync �?`run` (verified with the default no-target configuration)-10. Import / export �?`import` (md, jex, enex, raw, html, �?, `export`+3. Notebook lifecycle - `list`, `create`, `use`, `remove`+4. Note lifecycle - `list`, `create`, `set`, `get`, `remove`+5. Note organization - `copy`, `move`, `rename`+6. To-do lifecycle - `create`, `list`, `toggle`, `clear`, `done`, `undone`+7. Tag management - `list`, `add`, `remove`, `notetags`, `tagnotes`+8. Search - `run` (best-effort; some Joplin CLI builds gate this behind GUI mode)+9. Sync - `run` (verified with the default no-target configuration)+10. Import / export - `import` (md, jex, enex, raw, html), `export`(jex, md, raw, md_frontmatter)-11. Attachments and status �?`attach add`, `status show`, `status restore`-12. Backend utilities �?`version`, `dump`, `keymap`, `geoloc`,+11. Attachments and status - `attach add`, `status show`, `status restore`+12. Backend utilities - `version`, `dump`, `keymap`, `geoloc`,`export-sync-status`, `server`, and `e2ee`## 2. Workflow points (real-backend)@@ -29,25 +29,25 @@ The harness covers 12 workflow categories:The real-backend `TestBackendWorkflows` class executes the following shortscripts end-to-end:-- **Note lifecycle** �?create notebook �?use �?create note �?rename via `set`- �?get �?remove note �?remove notebook-- **Note organization** �?create source/target notebooks �?create note �?copy- to target �?rename source �?move renamed to target �?list target �?cleanup-- **Todo lifecycle** �?create todo �?list �?done �?undone �?toggle �?clear �?+- **Note lifecycle** - create notebook -> use -> create note -> rename via `set`+ -> get -> remove note -> remove notebook+- **Note organization** - create source/target notebooks -> create note -> copy+ to target -> rename source -> move renamed to target -> list target -> cleanup+- **Todo lifecycle** - create todo -> list -> done -> undone -> toggle -> clear ->cleanup-- **Tagging** �?create notebook/note �?add tag �?list tags �?notetags �?- tagnotes �?remove tag �?cleanup-- **Search** �?create notebook/note �?search (tolerates GUI-mode rejection)- �?cleanup-- **Sync** �?`sync run` returns a payload even when no target is configured-- **Export** �?JEX and Markdown for the same note set-- **Import** �?Markdown directory import into a fresh notebook-- **Attach** �?create notebook/note �?attach a real text file �?verbose get �?+- **Tagging** - create notebook/note -> add tag -> list tags -> notetags ->+ tagnotes -> remove tag -> cleanup+- **Search** - create notebook/note -> search (tolerates GUI-mode rejection)+ -> cleanup+- **Sync** - `sync run` returns a payload even when no target is configured+- **Export** - JEX and Markdown for the same note set+- **Import** - Markdown directory import into a fresh notebook+- **Attach** - create notebook/note -> attach a real text file -> verbose get ->cleanup-- **Unicode** �?`notebooks create/use/notes create/remove` with CJK + Greek+- **Unicode** - `notebooks create/use/notes create/remove` with CJK + Greekcharacters (skipped on Windows due to `cmd.exe` codepage truncation)-- **Session history persists** �?three mutating commands �?reload the saved- project �?assert every action is present in `history`+- **Session history persists** - three mutating commands -> reload the saved+ project -> assert every action is present in `history`## 3. Full end-to-end integration@@ -79,7 +79,7 @@ tag.add, tag.remove, attach.add, interop.export, note.remove, notebook.remove| Layer | File / class | Backend needed | Workflows ||--------------------------|--------------------------------------|----------------|---------------------------------|-| Unit + CLI contract | `test_core.py` | No | 91 tests |+| Unit + CLI contract | `test_core.py` | No | 107 tests || CLI subprocess | `TestCLISubprocess` | No | 10 tests || Real-backend commands | `TestBackendCommands` | Yes | 6 tests || Real-backend workflows | `TestBackendWorkflows` | Yes | 11 tests (1 skipped on Windows) |@@ -105,14 +105,15 @@ tag.add, tag.remove, attach.add, interop.export, note.remove, notebook.removenon-zero exit code is a real failure; they are not stripped from the returnedstreams (so multi-line note bodies and exports stay intact).- JSON error envelopes use the same `command` identifier as success responses- (`config.import_file`, `backend.export_sync_status`, `e2ee.decrypt_file`, ?.+ (`config.import_file`, `backend.export_sync_status`, `e2ee.decrypt_file`).+ Multi-word subcommands use a single dot between group and subcommand.## 7. Known limitations- `joplin search` is gated behind GUI mode on some Joplin CLI 3.x builds. Thesearch workflow accepts a clean `ok=false` JSON envelope with the originalerror message.-- Non-ASCII process arguments on Windows pass through `joplin.cmd` �?`cmd.exe`,+- Non-ASCII process arguments on Windows pass through `joplin.cmd` -> `cmd.exe`,which downgrades them to the active code page. The harness's JSON stateitself handles unicode correctly (see the unicode roundtrip in`test_core.py`); only the argv path is affected. The unicode workflow testdiff --git a/joplin/agent-harness/cli_anything/joplin/skills/SKILL.md b/joplin/agent-harness/cli_anything/joplin/skills/SKILL.mdindex fd6ffc1fd..4bf1edd84 100644--- a/joplin/agent-harness/cli_anything/joplin/skills/SKILL.md+++ b/joplin/agent-harness/cli_anything/joplin/skills/SKILL.md@@ -1,4 +1,4 @@----+---name: "cli-anything-joplin"description: "Command-line interface for Joplin workflows using the real joplin terminal backend"---@@ -82,7 +82,7 @@ When `--json` is enabled, commands return:- Backend `stdout`/`stderr` in command results are verbatim; do not assumewarnings were stripped from note bodies or exports.- On failure, parse `error` using the same `command` field as success- (`config.import_file`, `e2ee.decrypt_file`, ?. Multi-word subcommands use+ (`config.import_file`, `e2ee.decrypt_file`). Multi-word subcommands usea single dot between group and subcommand.## Test workflowdiff --git a/joplin/agent-harness/cli_anything/joplin/tests/TEST.md b/joplin/agent-harness/cli_anything/joplin/tests/TEST.mdindex d189bd0f7..58cc0fb27 100644--- a/joplin/agent-harness/cli_anything/joplin/tests/TEST.md+++ b/joplin/agent-harness/cli_anything/joplin/tests/TEST.md@@ -1,9 +1,9 @@-# Test Plan ???cli-anything-joplin+# Test Plan - cli-anything-joplinThe suite has two files:-- `test_core.py` ???pure unit + CLI-contract tests (no `joplin` binary required)-- `test_full_e2e.py` ???CLI subprocess tests + real-backend workflows + full+- `test_core.py` - pure unit + CLI-contract tests (no `joplin` binary required)+- `test_full_e2e.py` - CLI subprocess tests + real-backend workflows + fullend-to-end roundtripReal-backend classes are skipped automatically when `joplin` is not on `PATH`.@@ -16,7 +16,7 @@ a Joplin backend.Coverage areas:- Project schema, save/open roundtrip, unicode roundtrip, history shape-- Session lifecycle: set/get, snapshot, undo, redo, undo???redo chain,+- Session lifecycle: set/get, snapshot, undo, redo, undo->redo chain,redo cleared on new snapshot, save/save-without-path, `mark_dirty`- Session save regression: nested project path auto-creates missing parentdirectories before lock/write@@ -84,7 +84,7 @@ Coverage areas:- `project status` and `project save` errors when no project is loaded- Auto-save behavior: mutation auto-saves; `--dry-run` suppresses save- Todo and notebook-remove flows write the expected history actions-- `session save` keeps undo/redo depth consistent across save ???undo ???redo ???save+- `session save` keeps undo/redo depth consistent across save->undo->redo->save- Joplin source parity checks for `ls --format json`, `config --export`,`config --import-file`, `sync --upgrade/--use-lock`, `import --force`,`import --output-format`, `version`, `server`, and `e2ee` wrapper arguments@@ -139,23 +139,23 @@ Isolated real-backend command tests:Short backend flows:-- **Note lifecycle** ???create notebook ???use ???create note ???rename via `set`- ???get ???remove note ???remove notebook-- **Note organization** ???copy, rename (via `ren`), move (via `mv`) between+- **Note lifecycle** - create notebook -> use -> create note -> rename via `set`+ -> get -> remove note -> remove notebook+- **Note organization** - copy, rename (via `ren`), move (via `mv`) betweennotebooks-- **Todo lifecycle** ???create todo ???list ???done ???undone ???toggle ???clear-- **Tagging** ???add, list, notetags, tagnotes, remove-- **Search** ???best-effort; tolerates the GUI-mode restriction by checking the+- **Todo lifecycle** - create todo -> list -> done -> undone -> toggle -> clear+- **Tagging** - add, list, notetags, tagnotes, remove+- **Search** - best-effort; tolerates the GUI-mode restriction by checking theerror message when the backend rejects `search` outside the REPL-- **Sync (no target)** ???verifies `sync run` returns a payload even when no+- **Sync (no target)** - verifies `sync run` returns a payload even when notarget is configured-- **Export** ???JEX and Markdown-- **Import** ???Markdown directory import-- **Attach** ???attach file to note, then read it back-- **Unicode** ???skipped on Windows because `joplin.cmd` truncates non-ASCII+- **Export** - JEX and Markdown+- **Import** - Markdown directory import+- **Attach** - attach file to note, then read it back+- **Unicode** - skipped on Windows because `joplin.cmd` truncates non-ASCIIargs; the Python-only unicode roundtrip in `test_core.py` covers harnessencoding-- **Session history persists** ???verifies history actions land in the saved+- **Session history persists** - verifies history actions land in the savedproject file### `TestBackendIntegration` (1 test, backend required)@@ -175,7 +175,7 @@ Full end-to-end roundtrip used for agent demos and regression. Phases:After the run, the test verifies that the saved project's history containsevery expected action (`notebook.create`, `note.copy`, `note.move`,-`todo.toggle`, `tag.add`, `attach.add`, `interop.export`, ???.+`todo.toggle`, `tag.add`, `attach.add`, `interop.export`, and cleanup actions.## Forcing the installed console script@@ -197,7 +197,7 @@ CLI_ANYTHING_FORCE_INSTALLED=1 python -m pytest -v -s cli_anything/joplin/tests/(Windows shim / custom prefix), the parent's `lib/node_modules/joplin`(non-symlinked `<prefix>/bin/joplin`), or whatever `npm root -g` reports.The original error is included in `stderr`.-- Non-ASCII process arguments on Windows pass through `joplin.cmd` ???+- Non-ASCII process arguments on Windows pass through `joplin.cmd` ->`cmd.exe`, which drops to the active code page. The unicode workflow testis therefore skipped on Windows. The Python-level unicode handling in theharness (project JSON, history, REPL) is covered in `test_core.py`.diff --git a/skills/cli-anything-joplin/SKILL.md b/skills/cli-anything-joplin/SKILL.mdindex e4f28fefc..61e5f544d 100644--- a/skills/cli-anything-joplin/SKILL.md+++ b/skills/cli-anything-joplin/SKILL.md@@ -1,4 +1,4 @@----+---name: "cli-anything-joplin"description: "Command-line interface for Joplin workflows using the real joplin terminal backend"---@@ -83,7 +83,7 @@ When `--json` is enabled, commands return:- Backend `stdout`/`stderr` in command results are verbatim; do not assumewarnings were stripped from note bodies or exports.- On failure, parse `error` using the same `command` field as success- (`config.import_file`, `e2ee.decrypt_file`, ?. Multi-word subcommands use+ (`config.import_file`, `e2ee.decrypt_file`). Multi-word subcommands usea single dot between group and subcommand.## Recommended workflow