cj-tauri 2.0.0 → 2.1.1

package/README.md

@@ -1,128 +1,145 @@
-# cj-tauri
-
-用[仓颉语言](https://cangjie-lang.cn)写桌面应用的脚手架 CLI——把 Tauri 的三件套带到仓颉：
-仓颉后端（静态编译）+ 系统 WebView 前端（HTML/CSS/JS），三件套与 Tauri 一致 ——
-WebView 宿主、IPC 双向桥（`invoke` / `resolve` / `event`）、能力安全模型（capability 白名单）。
-
-- 仓库与完整文档：<https://atomgit.com/qq8864/cj-tauri>
-- 当前版本：**2.0.0**（主版本：删除了已失效的 `setHostFactory` / `requireInjectedHost`，见文末「2.0.0 变更」）
-- 当前状态：**Windows（WebView2）、Linux（WebKitGTK）与鸿蒙 PC（ArkWeb）均已实机跑通**
-
-## 前置条件：仓颉 SDK
-
-**这个包不替代仓颉 SDK**。应用后端就是仓颉代码，`cj-tauri dev` / `build` 要调用 SDK 里的 `cjc` / `cjpm`
-把你的应用编译出来。所以请先装 SDK（验证版本 **1.2.0**，含 **stdx**），并让本包能找到它：
-
-```bash
-# Linux
-export CANGJIE_HOME=/opt/cangjie/cangjie
-
-# Windows cmd
-set CANGJIE_HOME=D:\Program Files (x86)\Cangjie
-```
-
-不设 `CANGJIE_HOME` 时，本包会探测常见安装位置（Windows `D:\Program Files (x86)\Cangjie`、
-Linux `/opt/cangjie/cangjie`）。另外两个变量视情况给：
-
-| 变量 | 什么时候需要 |
-|---|---|
-| `CJ_TAURI_ROOT` | 不在 cj-tauri 仓库内运行、又找不到框架根目录时（`create` 要把框架路径写进工程） |
-| `CANGJIE_STDX` | 应用的 `cjpm.toml` 用 `${CANGJIE_STDX}` 展开 stdx 路径；本包会从框架/工程的 toml 里探测，探不到就照此变量 |
-| `CANGJIE_STDX_OHOS` | 只在构建鸿蒙工程时用（鸿蒙版 stdx，`build-hap.sh` 按它找动态库） |
-
-装好后自检：
-
-```bash
-npx cj-tauri info        # 打印框架 / 项目 / stdx / SDK / cjpm / C 桥 的解析结果
-```
-
-没装 SDK 时本包会直接给出提示与安装说明，而不是抛一句 `cjpm: command not found`。
-另外 `npx cj-tauri --version` 不需要 SDK 也能查版本。
-
-## 用法
-
-```bash
-npx cj-tauri create myapp --template app     # 内联 HTML，零 Node（缺省模板）
-cd myapp
-npx cj-tauri sync                            # 按清单派生 targets/ 骨架（首次；重跑幂等）
-npx cj-tauri dev                             # 构建 C 桥 + cjpm build + 启动窗口
-
-npx cj-tauri create myapp-vue --template vue      # Vue 3 + Vite（前端工程在 assets/ui/）
-npx cj-tauri create myapp-react --template react  # React 18 + Vite
-
-npx cj-tauri create myohos --template ohos        # 鸿蒙 PC：同一份业务代码 + targets/ohos
-npx cj-tauri create myohos --template ohos --bundle com.example.myapp --label "我的应用"
-
-npm i -g cj-tauri                  # 也可以全局安装，之后直接用 cj-tauri <子命令>
-```
-
-**一份业务代码，骨架按目标派生**——`create` 只生成清单与业务侧，平台骨架是 `sync` 的产物：
-
-```
-myapp/
-├── cj-tauri.toml           # 应用清单——单一真相（id/version/窗口/资产/能力目录）
-├── cjpm.toml               # 业务包（static 库；骨架以 path 依赖引用）
-├── src/main.cj             # 业务装配点 build(): AppSpec（零平台知识）
-├── assets/
-│   ├── ui/index.html       # 前端页面（任意 Web 技术栈）
-│   └── capabilities/default.json   # 能力白名单（命令 / 事件 / 权限集）
-└── targets/                # cj-tauri sync 生成（勿手改；check 判漂移）
-    ├── desktop/            #   桌面可执行（launcher 调 build()）
-    └── ohos/               #   鸿蒙 hap 工程（DevEco + build-hap.sh）
-```
-
-| 子命令 | 作用 |
-|---|---|
-| `create <项目名> [--template app\|vue\|react\|ohos]` | 生成统一工程（清单 + `src/` + `assets/`）；`--bundle` / `--label` 只对 `ohos` 模板有意义，缺省由项目名推导 |
-| `sync [desktop\|ohos]` | 按清单派生 `targets/` 骨架（缺省两端都派生；幂等重跑） |
-| `dev` | 构建 C 桥 + `cjpm build` + 启动应用；Vite 模板会接管 dev server（HMR） |
-| `build` | 构建 C 桥 + `cjpm build`；鸿蒙端在 `targets/ohos` 里 `bash build-hap.sh` |
-| `run` | 运行已构建产物；鸿蒙端 `bash build-hap.sh --install`（构建 + 装机 + 拉起） |
-| `check` | 校验 `cj-tauri.toml`（id / 窗口 / 资产存在）+ `targets/` 骨架漂移 + 插件三方比对 |
-| `info [--json]` | 环境自检（排障先跑它）；`--json` 只输出插件清单，机器可读 |
-| `doctor` | 环境自检逐行给结论（每条自带「缺了就怎么办」） |
-| `help` | 帮助 |
-
-## 鸿蒙 PC（`--template ohos`）
-
-同一套框架换个宿主：桌面用 WebView2 / WebKitGTK，鸿蒙 PC 用 **ArkWeb**，上层页面、命令层、能力校验不用改。
-`--template ohos` 生成的仍是那种**统一工程**（`cj-tauri.toml` + `src/` + `assets/`），只是清单里带鸿蒙端信息
-（`[app] id` 就是 `bundleName`）；DevEco 工程是 `sync` 的产物，落在 `targets/ohos/`：
+# cj-tauri
+
+A scaffold CLI for building desktop apps in the [Cangjie language](https://cangjie-lang.cn) — it brings
+Tauri's trio to Cangjie: a Cangjie backend (statically compiled) plus a system WebView frontend
+(HTML/CSS/JS), with the same three pieces Tauri has — a WebView host, a bidirectional IPC bridge
+(`invoke` / `resolve` / `event`), and a capability-based security model (capability allowlists).
+
+- Repository and full documentation: <https://github.com/yangyongzhen/cj-tauri>
+- Current version: **2.1.1** (fixed in this release: sync now keeps the launcher on the framework path
+  the business package declares (no more cjpm module conflicts after editing the path), the desktop
+  launcher locates assets/ two levels up so it runs straight from targets/, and new **serial command
+  groups** — `TauriApp.registerSerial` — execute same-group commands strictly in arrival order, which
+  ai-chat's web-tab commands now use; plus the hello-world example and starter guide)
+- Current status: **Windows (WebView2), Linux (WebKitGTK) and HarmonyOS PC (ArkWeb) all run on real
+  hardware**; on the HarmonyOS side the menu capability bit and `fs` / `mqtt` / `redis` / `sqlite` /
+  `store` / `http` have been verified on a device
+
+## Prerequisite: the Cangjie SDK
+
+**This package does not replace the Cangjie SDK.** Your app backend is Cangjie code, and
+`cj-tauri dev` / `build` invoke the SDK's `cjc` / `cjpm` to compile it. So install the SDK first
+(verified with version **1.2.0**, including **stdx**) and make it discoverable:
+
+```bash
+# Linux
+export CANGJIE_HOME=/opt/cangjie/cangjie
+
+# Windows cmd
+set CANGJIE_HOME=D:\Program Files (x86)\Cangjie
+```
+
+When `CANGJIE_HOME` is unset, the package probes the usual install locations (Windows
+`D:\Program Files (x86)\Cangjie`, Linux `/opt/cangjie/cangjie`). Three more variables are needed
+in some situations:
+
+| Variable | When you need it |
+|---|---|
+| `CJ_TAURI_ROOT` | Running outside the cj-tauri repo when the framework root can't be located (`create` writes the framework path into your project) |
+| `CANGJIE_STDX` | Your app's `cjpm.toml` expands the stdx path via `${CANGJIE_STDX}`; the package probes the framework/project toml for it and falls back to this variable |
+| `CANGJIE_STDX_OHOS` | Only when building a HarmonyOS project (the HarmonyOS build of stdx; `build-hap.sh` locates its dynamic libraries through it) |
+
+Self-check once it's installed:
 
 ```bash
-npx cj-tauri create myohos --template ohos --bundle com.example.myapp --label "我的应用"
+npx cj-tauri info        # prints the resolved framework / project / stdx / SDK / cjpm / C bridge
+```
+
+Without the SDK the package prints a clear hint and install instructions instead of throwing
+`cjpm: command not found`. Note that `npx cj-tauri --version` works without the SDK.
+
+## Usage
+
+```bash
+npx cj-tauri create myapp --template app     # inline HTML, zero Node (the default template)
+cd myapp
+npx cj-tauri sync                            # derive the targets/ skeletons from the manifest (first run; idempotent)
+npx cj-tauri dev                             # build the C bridge + cjpm build + open the window
+
+npx cj-tauri create myapp-vue --template vue      # Vue 3 + Vite (frontend project under assets/ui/)
+npx cj-tauri create myapp-react --template react  # React 18 + Vite
+
+npx cj-tauri create myohos --template ohos        # HarmonyOS PC: same business code + targets/ohos
+npx cj-tauri create myohos --template ohos --bundle com.example.myapp --label "My App"
+
+npm i -g cj-tauri                  # or install globally and call cj-tauri <subcommand> directly
+```
+
+**One body of business code, skeletons derived per target** — `create` only generates the manifest and
+the business side; the platform skeletons are what `sync` produces:
+
+```
+myapp/
+├── cj-tauri.toml           # app manifest — the single source of truth (id/version/window/assets/capability dir)
+├── cjpm.toml               # business package (a static library; skeletons reference it by path)
+├── src/main.cj             # business assembly point build(): AppSpec (zero platform knowledge)
+├── assets/
+│   ├── ui/index.html       # frontend page (any web stack)
+│   └── capabilities/default.json   # capability allowlist (commands / events / permission sets)
+└── targets/                # generated by cj-tauri sync (don't hand-edit; check reports drift)
+    ├── desktop/            #   desktop executable (the launcher calls build())
+    └── ohos/               #   HarmonyOS hap project (DevEco + build-hap.sh)
+```
+
+| Subcommand | What it does |
+|---|---|
+| `create <name> [--template app\|vue\|react\|ohos]` | Generate the unified project (manifest + `src/` + `assets/`); `--bundle` / `--label` only matter for the `ohos` template, otherwise they're derived from the project name |
+| `sync [desktop\|ohos]` | Derive the `targets/` skeletons from the manifest (both ends by default; idempotent) |
+| `dev` | Build the C bridge + `cjpm build` + launch the app; Vite templates take over their dev server (HMR) |
+| `build` | Build the C bridge + `cjpm build`; on HarmonyOS run `bash build-hap.sh` inside `targets/ohos` |
+| `run` | Run the built artifact; on HarmonyOS `bash build-hap.sh --install` (build + install + launch) |
+| `check` | Validate `cj-tauri.toml` (id / window / assets present) + `targets/` skeleton drift + three-way plugin comparison |
+| `info [--json]` | Environment self-check (run this first when troubleshooting); `--json` prints only the plugin manifest, machine-readable |
+| `doctor` | Environment self-check with a verdict per line (each line says what to do if it's missing) |
+| `help` | Help |
+
+## HarmonyOS PC (`--template ohos`)
+
+The same framework with a different host: desktop uses WebView2 / WebKitGTK, HarmonyOS PC uses **ArkWeb**,
+while the page layer, the command layer and capability validation stay untouched. `--template ohos` still
+generates that **unified project** (`cj-tauri.toml` + `src/` + `assets/`), only the manifest carries the
+HarmonyOS side (`[app] id` is the `bundleName`); the DevEco project is a product of `sync`, landing in
+`targets/ohos/`:
+
+```bash
+npx cj-tauri create myohos --template ohos --bundle com.example.myapp --label "My App"
 cd myohos
-npx cj-tauri sync ohos             # 派生 targets/ohos（DevEco 骨架 + rawfile 里的页面与能力清单）
+npx cj-tauri sync ohos             # derive targets/ohos (DevEco skeleton + the page and capability manifest in rawfile)
 cd targets/ohos
-bash build-hap.sh --install        # 构建 hap + hdc 装机 + aa start
+bash build-hap.sh --install        # build the hap + install via hdc + aa start
 ```
 
-`targets/ohos/` 是标准 DevEco 工程（`entry/` + `AppScope/` + `build-profile.json5` + `hvigorfile.ts`），
-鸿蒙相关的那层很薄：
+`targets/ohos/` is a standard DevEco project (`entry/` + `AppScope/` + `build-profile.json5` +
+`hvigorfile.ts`), and the HarmonyOS-specific layer is thin:
 
-| 路径 | 作用 |
+| Path | Purpose |
 |---|---|
-| `entry/src/main/cangjie/main_ability.cj` | UIAbility：`ArkWebRuntime.configure(filesDir)` → 非 UI 线程 `spawn { run() }` → 等宿主登记再 `loadContent` |
-| `entry/src/main/cangjie/app_host.cj` | `@Component` 的 ArkWeb 宿主 + 双向桥（**必须住应用模块**，框架包引用 ArkUI 会启动即崩）；调你 `assets/` 里那份业务 `build()` |
-| `entry/src/main/resources/rawfile/` | `index.html` 与能力清单（从 `assets/` 拷进来的真文件） |
-| `build-hap.sh` | 唯一构建入口：探测 DevEco / stdx、`--no-daemon` 跑 hvigor、可选 `--install` |
+| `entry/src/main/cangjie/main_ability.cj` | UIAbility: `ArkWebRuntime.configure(filesDir)` → `spawn { run() }` off the UI thread → wait for the host to register, then `loadContent` |
+| `entry/src/main/cangjie/app_host.cj` | the `@Component` ArkWeb host + bidirectional bridge (**must live in the app module**; a framework package referencing ArkUI crashes at startup); calls the business `build()` in your `assets/` |
+| `entry/src/main/resources/rawfile/` | `index.html` and the capability manifest (real files copied in from `assets/`) |
+| `build-hap.sh` | the single build entry: probes DevEco / stdx, runs hvigor with `--no-daemon`, optional `--install` |
 
-前置两件事：
+Two prerequisites:
 
-- **DevEco Studio 6.1**（含仓颉插件）+ 已配好签名。`build-hap.sh` 用 `DEVECO_WIN` 找安装根
-  （默认 `D:\oh\DevEcoStudio`），用 `CANGJIE_STDX_OHOS` 找鸿蒙版 stdx 动态库；两者给不出时脚本会直接说清楚缺哪个。
-- 真机开着**开发者模式 + USB 调试**，`hdc` 能列到设备；`aa start` 需要**屏幕已解锁**。
+- **DevEco Studio 6.1** (with the Cangjie plugin) and signing already configured. `build-hap.sh` finds the
+  install root via `DEVECO_WIN` (default `D:\oh\DevEcoStudio`) and the HarmonyOS build of stdx's dynamic
+  libraries via `CANGJIE_STDX_OHOS`; when either is missing the script says exactly which one.
+- A device with **developer mode + USB debugging** on, so `hdc` lists it; `aa start` needs the **screen unlocked**.
 
-工程默认是桌面形态：`module.json5` 的 `deviceTypes` 写 `2in1`，并在 `entry/build-profile.json5` 里
-`cangjieOptions.checkDeviceTypes = false`（插件默认只放行 `phone` / `tablet`，写 `2in1` 会判 `01103012`）；
-窗口**不干预尺寸**，沿用系统给的默认矩形（实测本机 `2090×1394`，约屏宽 2/3 且居中）。
+The project defaults to desktop form factor: `deviceTypes` in `module.json5` is `2in1`, and
+`cangjieOptions.checkDeviceTypes = false` in `entry/build-profile.json5` (the plugin only allows
+`phone` / `tablet` by default, and writing `2in1` fails with `01103012`). The window **does not touch the
+size** and keeps the system default rectangle (measured at `2090×1394`, about two thirds of the screen
+width and centered).
 
-已知限制：签名要在 DevEco 里配（命令行不做自动签名，换 `bundleName` 需重新签）；同一份调试签名下两个
-工程会互相顶掉安装位；单窗口、暂无原生对话框（那两条能力位如实返回 0）；没有可用的 C 桥，
-`launchHidden` / 串口 / 托盘这类宿主能力在鸿蒙上不提供。改完 `assets/` 里的页面或能力清单要重跑
-`cj-tauri sync ohos`（`targets/` 是生成物，`check` 会报漂移）。
+Known limitations: signing is configured in DevEco (the command line does not auto-sign, and changing the
+`bundleName` requires re-signing); two projects under the same debug signature evict each other's install;
+single window with no native dialogs yet (those two capability bits honestly return 0); there is no usable
+C bridge, so host capabilities like `launchHidden` / serial / tray are not available on HarmonyOS. After
+editing pages or the capability manifest under `assets/`, re-run `cj-tauri sync ohos` (`targets/` is
+generated, and `check` reports it as drift).
 
-真机上怎么自证它通了（hilog，`CjTauri` tag）：
+How to prove it works on a device (hilog, `CjTauri` tag):
 
 ```
 host registered after N polls label=main
@@ -131,30 +148,80 @@ page begin label=main
 main window keeps system default 2090x1394 px at density 190% on screen 3120x2080
 ```
 
-## 这个包装层做了什么
-
-- **跨平台入口**：Windows / Linux / Git Bash 都是同一条 `cj-tauri` 命令，不再分 `.bat` 与 `.sh`；
-- **环境自检**：`cjpm` 与 SDK 运行时库的定位、`PATH` / `LD_LIBRARY_PATH` 的拼装都在这里完成；
-- **CLI 本体的获取**：优先用包内预编译二进制（`prebuilt/<平台-架构>/`），没有则把 CLI 源码拷到
-  `~/.cache/cj-tauri/<版本>/` 下用本机 `cjpm build` 一次并缓存 —— 不往安装目录写产物，避免全局安装只读；
-- **数据目录**：Linux 用 `$XDG_CACHE_HOME/cj-tauri`（默认 `~/.cache/cj-tauri`），Windows 用 `%LOCALAPPDATA%\cj-tauri`。
-
-已知限制：首次 `dev` / `build` 会把 C 桥构建到**框架目录的 `native/`** 下（应用 `cjpm.toml` 的
-链接参数指向那里），所以包安装目录需要可写；如果装在只读路径下，请改用仓库内运行方式。
-
-## 2.0.0 变更
-
-- **不兼容**：删除已失效的公开 API `setHostFactory` / `requireInjectedHost`（框架侧单槽宿主注入）。
-  源码里仍在调用它们的应用会编译失败——那些调用本来也不生效（`requireInjectedHost` 没有任何调用方）。
-  多宿主注入走 `registerHost(HostProvider)`（带优先级），鸿蒙宿主已内置。
-- **修复**：`sync` 生成的工程在 Windows 上编不过（TOML 路径保留反斜杠触发 `errLexEscape`、鸿蒙 entry 的
-  `compile-option` 内层引号未转义、生成源码里 `url=\"…\"` 少一层转义）；`cj-tauri check` 的三方比对在
-  Windows 上因产物名 `main.exe` 恒被跳过；示例 `modbus-poll` 缺串口插件 import。
-- **门禁**：版本校验从五处扩到六处（新增官网 `website/index.html`），并给与 `docs/` 同源的图片 / 图
-  加上了逐字节比对——官网是独立拷贝、此前不在门禁里，正是它漏更的根因。
-
-完整变更见仓库的 `CHANGELOG.md` 的 `[2.0.0] - 2026-10-23`。
-
-## License
-
-[MIT](https://atomgit.com/qq8864/cj-tauri/blob/main/LICENSE) © 2026 yangyongzhen
+## What this wrapper layer does
+
+- **One cross-platform entry point**: Windows / Linux / Git Bash all use the same `cj-tauri` command, with
+  no more separate `.bat` and `.sh`;
+- **Environment self-check**: locating `cjpm` and the SDK runtime libraries, and assembling `PATH` /
+  `LD_LIBRARY_PATH`, all happen here;
+- **Obtaining the CLI itself**: the packaged prebuilt binary is preferred (`prebuilt/<platform-arch>/`);
+  otherwise the CLI sources are copied to `~/.cache/cj-tauri/<version>/`, built once with the local
+  `cjpm build` and cached — nothing is written into the install directory, so a global install can stay
+  read-only;
+- **Data directories**: `$XDG_CACHE_HOME/cj-tauri` on Linux (default `~/.cache/cj-tauri`),
+  `%LOCALAPPDATA%\cj-tauri` on Windows.
+
+Known limitation: the first `dev` / `build` builds the C bridge into the **framework directory's `native/`**
+(that's where the app's `cjpm.toml` link options point), so the package install directory must be writable;
+if you installed under a read-only path, run from inside the repository instead.
+
+## Changes in 2.1.1
+
+- **Serial command groups** (issue #6-4): `IpcHub.registerSerial(cmd, handler, group)` /
+  `TauriApp.registerSerial` — commands in the same group execute strictly in **arrival order**,
+  while other groups and plain commands keep the concurrent semantics. Guaranteed by structure:
+  dispatch happens on the bridge's message-callback thread, so enqueue order is arrival order,
+  and each group has a single worker draining the queue under one lock. ai-chat's five web-tab
+  commands are enrolled in the `webtab` group (the front-end queue stays — page emission order
+  and host execution order are two halves of the same guarantee).
+- **sync keeps the launcher on the business package's framework path** (issue #6-1): the launcher's
+  `cjTauri` dependency now reads the path the business package declares in its own `cjpm.toml`
+  (relative paths absolutized against the project root), so editing that path no longer causes
+  a cjpm module conflict between two framework copies.
+- **The desktop launcher locates its assets** (issue #6-2/3): `assets/` and `capabilities/` are
+  found by walking up two levels, so running the binary straight from `targets/desktop/` no longer
+  dies with "asset not found"; sync's next-steps output names the runtime library path
+  (`<framework>/native` for `libcjtbridge.so`).
+- New `examples/hello-world` (smallest runnable app, generated by this CLI) and
+  `docs/hello-world-入门教程.md` — a starter guide written from an actual npx-create-to-window run.
+
+For the full list see `[2.1.1] - 2026-10-26` in the repository's `CHANGELOG.md`.
+
+## Changes in 2.1.0
+
+- **New**: in-window multi-WebView views (`webview:*` — several page views inside one window with an LRU
+  cap of 4, which is what drives ai-chat's nine web-version tabs); the four commands `fs:mkdir` /
+  `fs:rename` / `fs:copy` / `fs:stat` (with overwrite and two-path scope validation); the `http` plugin's
+  HarmonyOS transport layer (over the `ohos.net.http` system stack, which brings https back); `sqlite` /
+  `serial` landing on HarmonyOS; a `notification` capability bit in `system:host`; a pointer to the SDK
+  download in the CLI's `doctor`.
+- **Fixed**: the Linux C bridge `duplicate member 'h'` compile error (the embedded view's geometry field
+  collided with the host pointer), ai-chat's embedded view not following the widening after the sidebar
+  collapses, and the documented state of the HarmonyOS host capability bits (the menu bit is verified on a
+  device, so it's no longer all zeros).
+- Verified on a HarmonyOS device: `fs` / `mqtt` / `redis` / `sqlite` / `store` / `http` and the menu
+  capability bit.
+
+For the full list see `[2.1.0] - 2026-10-25` in the repository's `CHANGELOG.md`.
+
+## Changes in 2.0.0
+
+- **Breaking**: removed the dead public APIs `setHostFactory` / `requireInjectedHost` (the framework's
+  single-slot host injection). Apps still calling them will fail to compile — and those calls never took
+  effect anyway (`requireInjectedHost` had no callers at all). Multi-host injection goes through
+  `registerHost(HostProvider)` (with priorities); the HarmonyOS host is built in.
+- **Fixed**: projects generated by `sync` wouldn't compile on Windows (TOML paths keeping backslashes
+  triggered `errLexEscape`, the HarmonyOS entry's `compile-option` had unescaped inner quotes, and
+  `url=\"…\"` in the generated sources was one escape level short); `cj-tauri check`'s three-way
+  comparison was always skipped on Windows because of the `main.exe` artifact name; the `modbus-poll`
+  example was missing the serial plugin import.
+- **Gates**: version validation grew from five sites to six (adding the website's `website/index.html`),
+  and the images / diagrams that share a source with `docs/` now get a byte-for-byte comparison — the
+  website is an independent copy that previously sat outside the gate, which is exactly why it went stale.
+
+For the full list see `[2.0.0] - 2026-10-23` in the repository's `CHANGELOG.md`.
+
+## License
+
+[MIT](https://github.com/yangyongzhen/cj-tauri/blob/main/LICENSE) © 2026 yangyongzhen
+