@qoder-ai/qmind-cli 1.1.2 → 3.0.0

package/CHANGELOG.md

@@ -1,5 +1,47 @@
 # @qoder-ai/qmind-cli
 
+English (default) | [简体中文](CHANGELOG.zh-CN.md)
+
+Published versions below describe the Global CLI/shared implementation, not historical CN releases. CN will join the shared history with the future joint release.
+
+## 3.0.0
+
+### Major Changes
+
+- 28508e5: Release QMind CLI as one shared-version Global/CN cohort. Keep `@qoder-ai/qmind-cli` / `qmind` for Qoder Global and introduce `@qodercn-ai/qmind-cli` / `qmind-cn` for Qoder China. Each distribution now has a build-time-fixed product identity and production target, isolated product/target file credentials, bilingual package documentation and changelog, and an immutable dual-distribution candidate that is published automatically after its Changeset reaches `main`. The CLI no longer reads legacy root state or OS Keyring entries; upgrade the Global package and sign in again, and install the CN package separately when it is published.
+
+### Changes without version bumps
+
+- Fix the CLI product at build time and isolate config, file credentials and sync mappings by product/target under `QMIND_HOME/cli/`. Use `--env` or paired `--sash`/`--dashboard` for debug targets and `QMIND_DEBUG_TOKEN` for debug tokens. Legacy address hints only warn when matching and fail before requests otherwise; old root files and `.qmind-env` are not read. Sign in again in the new partition. The shared major release delivers the CN package from the same versioned source.
+- Use the file credential vault exclusively; do not install, load, read, write, or delete OS Keyring entries. Device/refresh tokens remain plaintext files with existing permissions, atomic writes, locks, and compare-and-swap protection. No old authentication state is imported.
+- Remove obsolete CLI-internal Node Host forwarding/updater layers, harden Agent release evidence, and align package, security, and acceptance documentation with the current topology.
+
+- Settle CLI English and Chinese changelogs together from one Changeset and version, validate matching history and references, and include both files in settlement and local artifact checks. Keep publication deferred.
+- Add an opt-in frozen CLI candidate tag stage with strict annotated tag identity and tarball digest checks, immutable per-attempt evidence, and remote readback for retries. Keep production CI and npm publication unchanged.
+- Add the internal per-distribution publisher for frozen CLI candidates: reconcile exact versions, publish original tarballs under release tags, verify anonymously, and resume latest promotion without downgrading newer releases. Production publishing remains disconnected.
+- Prepare independently compiled Global/CN CLI tarballs from one version and dependency snapshot, with normal co-installation and fixed-product authentication checks. Defer formal candidate integration and publication to the joint major release.
+- Add opt-in dual CLI candidate preparation and read-only frozen artifact verification. Bind both distributions to one settled source and bilingual release, while keeping the existing publication pipeline disabled for the new candidate schema.
+- Prepare fixed CLI product routing, explicit debug targets, legacy-address diagnostics and partitioned file state. Keep shared Host defaults unchanged and defer versioning/publication to the joint Global/CN major release.
+- Archive schema 8 dual CLI candidates from main settlement and add an explicit production promotion pipeline with candidate-bound acceptance, tag, isolated Global/CN publisher, recovery, summary, and notification gates. No release is executed by this change.
+- Add opt-in anonymous exact-version verification for frozen Global/CN CLI candidates, including downloaded bytes, isolated npm installation, installed commands and immutable verification receipts. Keep production publishing and latest promotion unchanged.
+- Add a tokenless internal dual-release summary that validates Global/CN publisher evidence and anonymously rechecks current latest versions without mutating registry or Git state. Production release assembly remains disconnected.
+
+## 2.0.0
+
+### Major Changes
+
+- a317ae9: Tighten the QMind Client domain contract: remove the ineffective `userId` client option and the Node Host/CLI `userId`, `--user`, and `QMIND_USER_ID` configuration surface; accept real empty lists, zero pagination, and RepoWiki snake_case wire shapes; complete known Card facet and ChatMessage fields; and advertise only capabilities callable through the public interface. Export strict domain decoders for host routes not yet exposed by the Client. Add Fetch Transport stream connect/idle timeouts and make Zod a compatible host-provided peer to avoid duplicate schema type universes.
+
+## 1.1.3
+
+### Patch Changes
+
+- d2dcbb6: Add the QMind Agent Contract v1 Core, per-Query Qoder Agent SDK adapter, shared Node host, canonical Qoder Plugin runtime and deterministic Plugin artifact flow. The CLI now consumes the extracted Node host without changing its command surface.
+
+### Changes without version bumps
+
+- Enable Node.js module compile caching before loading the CLI application on supported runtimes while preserving Node 20 compatibility.
+
 ## 1.1.2
 
 ### Patch Changes

package/CHANGELOG.zh-CN.md

@@ -0,0 +1,70 @@
+# @qoder-ai/qmind-cli
+
+[English (default)](CHANGELOG.md) | 简体中文
+
+以下已发布版本属于 Global CLI / 共享实现，不代表 CN 曾发布过这些版本。CN 将在后续共同发行版加入同一历史。
+
+## 3.0.0
+
+### Major Changes
+
+- 28508e5: 将 QMind CLI 作为共享版本的 Global/CN 共同发行版发布：Qoder Global 继续使用 `@qoder-ai/qmind-cli` / `qmind`，Qoder 中国版新增 `@qodercn-ai/qmind-cli` / `qmind-cn`。每个发行版都具有构建时固定的产品身份与正式目标、按产品/目标隔离的文件凭证、中英文 package 文档与 changelog，以及一个在 Changeset 进入 `main` 后自动发布的双发行物不可变候选。CLI 不再读取旧根目录状态或 OS Keyring 项；Global 用户升级后需要重新登录，CN 包正式发布后需单独安装。
+
+### Changes without version bumps
+
+- 构建时固定 CLI 产品，config、文件凭证与同步映射按产品/目标隔离在 `QMIND_HOME/cli/` 下。调试使用 `--env` 或成对 `--sash`/`--dashboard`，Token 使用 `QMIND_DEBUG_TOKEN`。旧地址仅同值警告、冲突则在请求前停止；不读取旧根文件与 `.qmind-env`，请在新分区重新登录。共同 major 发行版从同一份版本化源码交付 CN 包。
+- 只使用文件 credential vault，不安装、加载、读取、写入或删除 OS Keyring 项。device/refresh token 仍为明文文件，保留现有权限、原子写、文件锁与 compare-and-swap 保护，不导入旧认证状态。
+- 移除过时的 CLI 内部 Node Host 转发及 updater 层，强化 Agent 发布证据，并使 package、安全和验收文档与当前结构一致。
+
+- 从同一 Changeset 与版本共同结算 CLI 中英文 changelog，校验历史及引用一致，并将两份文档纳入结算和本地制品检查。仍不触发发布。
+- 增加显式冻结 CLI 候选 tag 阶段，严格校验 annotated tag 身份和 tarball 摘要，逐次保留不可覆盖的尝试记录，并通过远端读回支持重试。生产 CI 与 npm 发布流程保持不变。
+- 增加冻结 CLI 候选的内部按发行物发布模块：精确版本对账、以 release 标签发布原始 tarball、匿名验证，以及不会降级新版的 latest 恢复。生产发布入口仍不接通。
+- 从同一版本与依赖快照分别编译 Global/CN CLI tarball，验证普通并装及固定产品认证。正式候选接入与发布留至共同 major 发行版。
+- 增加显式双 CLI 候选准备与冻结制品只读验证入口，将两种发行物绑定到同一已结算源码和双语版本；现有发布流水线仍不接受新的候选格式。
+- 准备固定的 CLI 产品路由、显式调试目标、旧地址诊断与分区文件状态。保持共享 Host 默认行为不变，版本升级与发布留至 Global/CN 共同 major 发行版。
+- 从 main 结算归档 schema 8 双 CLI 候选，并增加显式生产 promotion pipeline，串联候选绑定认证、tag、Global/CN 隔离 publisher、恢复、汇总与通知门禁。本改动不执行发布。
+- 增加冻结 Global/CN CLI 候选的显式匿名精确版本验证，覆盖下载字节、隔离 npm 安装、安装后命令与不可覆盖的验证回执。生产发布及 latest 推进保持不变。
+- 增加无 token 的内部双发行汇总：验证 Global/CN publisher 证据并匿名复核当前 latest，不修改 registry 或 Git 状态。生产发布装配仍未接通。
+
+## 2.0.0
+
+### Major Changes
+
+- a317ae9: 收紧 QMind Client 领域合同：移除无效的 `userId` client option，以及 Node Host / CLI 的 `userId`、`--user`、`QMIND_USER_ID` 配置面；兼容真实空列表、零分页与 RepoWiki snake_case wire shape，补齐 Card facet、ChatMessage 等已知字段，并让 capability 只声明当前公开 interface 可调用的领域能力。SDK 同时公开严格领域 decoder，供尚未进入 Client interface 的宿主 route 复用同一合同；官方 Fetch Transport 新增 stream connect/idle timeout，且将 Zod 改为由宿主提供的兼容 peer，避免 SDK 安装出第二套 schema 类型世界。
+
+## 1.1.3
+
+### Patch Changes
+
+- d2dcbb6: 新增 QMind Agent Contract v1 Core、按 Query 创建的 Qoder Agent SDK adapter、共享 Node Host、canonical Qoder Plugin runtime 和确定性的 Plugin artifact 流程。CLI 改用提取出的 Node Host，命令面不变。
+
+### Changes without version bumps
+
+- 在支持的 Node.js runtime 上，加载 CLI application 前启用 module compile cache，同时保持 Node 20 兼容性。
+
+## 1.1.2
+
+### Patch Changes
+
+- c3a3a0f: 从 CLI package README 中移除冗余的 module boundary 说明。
+
+## 1.1.1
+
+### Patch Changes
+
+- 711c3b9: 面向 package 使用者重写各包 README，将公共 QMind CLI 明确为 bin-only，移除原 workspace module exports。
+
+## 1.1.0
+
+### Minor Changes
+
+- 858c2f4: QMind CLI 以 `@qoder-ai/qmind-cli` 发布到 npm。使用 `npm install --global @qoder-ai/qmind-cli` 安装后，通过 `qmind` 登录、管理知识库和来源、检索知识、运行 RAG/编译流程和安全同步目录。支持适合自动化的 JSON/NDJSON 输出、稳定退出码以及 npm 管理的升级，适用于 macOS、Linux、Windows 和 Node.js 20.18.1 及以上版本。
+
+## 1.0.0
+
+### Initial release
+
+- 引入面向 QMind 知识工作流的 `qmind` 命令。
+- 新增浏览器登录与安全的本地凭证管理，支持自动化环境及 Token 配置。
+- 新增 notebook 创建/列表/读取/删除、card 列表/搜索、检索、RAG、编译、校验、source 创建/列表/读取/上传/下载/移动/内容/删除、网站导入、图片预签名与目录上传流程。
+- 新增人类可读的表格、JSON、agent、NDJSON 输出，以及结构化错误和适合脚本的退出码。

package/README.md

@@ -1,10 +1,14 @@
-# `@qoder-ai/qmind-cli`
+# QMind CLI for Qoder Global
 
-QMind 命令行工具，可用于登录、管理知识库和来源、检索内容、运行 RAG/编译任务，以及把本地目录同步到知识库。
+[简体中文](./README.zh-CN.md)
 
-## 安装
+The QMind command-line interface for Qoder Global lets you sign in, manage knowledge bases and sources, retrieve content, run RAG and compilation workflows, and synchronize local directories.
 
-需要 Node.js `>=20.18.1`：
+Package: `@qoder-ai/qmind-cli` · command: `qmind`
+
+## Install
+
+Node.js `>=20.18.1` is required.
 
 ```sh
 npm install --global @qoder-ai/qmind-cli
@@ -12,99 +16,76 @@ qmind version
 qmind --help
 ```
 
-升级和卸载也交给 npm：
+Upgrade and uninstall through npm. `qmind self-update` only prints the npm upgrade command and never modifies npm-managed files.
 
 ```sh
 npm update --global @qoder-ai/qmind-cli
 npm uninstall --global @qoder-ai/qmind-cli
 ```
 
-`qmind self-update` 仅用于提示 npm 升级方式，不会修改 npm 管理的文件。
-
-## 快速开始
-
-交互式登录会打开浏览器完成授权，并把凭证安全保存到本机：
+## Quick start
 
 ```sh
 qmind login
 qmind notebook list
 qmind source list --nb <notebook-id>
-qmind retrieve --nb <notebook-id> "部署流程是什么？"
+qmind retrieve --nb <notebook-id> "What must be checked before release?"
 ```
 
-CI 或 Agent 场景建议使用环境变量和结构化输出：
+Interactive login opens a browser and stores the session in a local file vault. For CI and agents, prefer an environment variable and structured output:
 
 ```sh
 export QMIND_TOKEN='<token>'
 qmind notebook list --non-interactive --format json
-qmind retrieve --nb <notebook-id> --format agent "发布前要检查什么？"
+qmind retrieve --nb <notebook-id> --format agent "What is the deployment process?"
 ```
 
-不要把 token 写进脚本参数、仓库或日志。使用完本机凭证后可执行：
+Do not put tokens in command arguments, repositories, or logs. Run `qmind logout` to remove the current local session.
 
-```sh
-qmind logout
-```
+## Commands
+
+| Command                     | Purpose                                  |
+| --------------------------- | ---------------------------------------- |
+| `login` / `logout`          | Sign in or remove local credentials      |
+| `notebook`                  | Manage knowledge bases                   |
+| `cards` / `list` / `search` | List or search cards                     |
+| `source`                    | Manage knowledge-base sources            |
+| `retrieve`                  | Retrieve context without invoking an LLM |
+| `rag`                       | Ask questions using a knowledge base     |
+| `compile` / `lint`          | Run compilation or validation workflows  |
+| `task`                      | Manage task runs                         |
+| `upload-folder` / `sync`    | Synchronize a local directory            |
+| `image`                     | Obtain image upload or access URLs       |
+| `version`                   | Print version and build information      |
 
-## 命令
+Run `qmind <command> --help` for complete options. Domain commands support formats such as `table`, `json`, `agent`, and `ndjson`. stdout contains results; progress and diagnostics go to stderr. Exit codes are `0` for success, `1` for runtime failure/partial success/cancellation, and `2` for invalid usage.
 
-| 命令                        | 用途                                   |
-| --------------------------- | -------------------------------------- |
-| `login` / `logout`          | 登录或清除本机凭证                     |
-| `notebook`                  | 创建、列出、查看、删除知识库           |
-| `cards` / `list` / `search` | 列出或搜索卡片                         |
-| `source`                    | 创建、上传、下载、移动、读取或删除来源 |
-| `retrieve`                  | 检索知识库上下文，不发起 LLM 调用      |
-| `rag`                       | 基于知识库提问                         |
-| `compile` / `lint`          | 启动编译或检查工作流                   |
-| `task`                      | 创建、查询或列出任务运行               |
-| `upload-folder` / `sync`    | 将本地目录同步到知识库                 |
-| `image`                     | 获取图片上传地址或访问地址             |
-| `version`                   | 查看版本和构建信息                     |
+## Directory synchronization
 
-使用 `qmind <command> --help` 查看完整参数。例如：
+Review the plan before allowing remote deletions:
 
 ```sh
-qmind source upload --help
-qmind upload-folder --help
+qmind upload-folder --nb <notebook-id> --dir ./docs --mode if-changed --dry-run
 ```
 
-## 输出与退出码
-
-领域命令支持 `table`、`json`、`agent`、`ndjson` 等输出格式；具体可用值以命令的 `--help` 为准。
-
-- stdout 只输出命令结果，进度与诊断信息输出到 stderr；
-- `0` 表示成功或正常显示帮助；
-- `1` 表示运行失败、部分成功或用户取消；
-- `2` 表示参数用法错误或 `INVALID_ARGUMENT`。
-
-JSON 错误使用稳定的 `error` envelope，包含 `code`、`message`，以及服务端提供时的 `status`、`errorCode`、`requestId` 和 `details`。
+Removing `--dry-run` enables writes. `--delete` treats the remote source root as a mirror of the local directory and removes extra remote entries. Concurrency must be between `1` and `10`.
 
-## 同步目录
+## Configuration and authentication
 
-先用 `--dry-run` 审阅计划，再决定是否执行删除：
+This package has a fixed Qoder Global identity. Renaming the executable, changing its install path, or setting product-selection environment variables cannot switch products. Production is the default; `--env test` and `--env daily` select supported debug presets. A custom target requires both `--sash` and `--dashboard` and cannot be combined with an explicit `--env`.
 
 ```sh
-qmind upload-folder \
-  --nb <notebook-id> \
-  --dir ./docs \
-  --mode if-changed \
-  --ignore '**/drafts/**' \
-  --dry-run
+qmind login --env test
+QMIND_DEBUG_TOKEN='<debug-token>' qmind notebook list --env test --non-interactive --format json
+qmind login --sash http://localhost:8080 --dashboard http://localhost:3000
 ```
 
-移除 `--dry-run` 后才会写入远端。`--delete` 会把知识库的来源根目录视为本地目录的镜像，并删除远端多余项；使用前请确认 dry-run 结果。并发范围为 `1..10`。
+Production token priority is `--token > QMIND_TOKEN > current production vault`. Debug token priority is `--token > QMIND_DEBUG_TOKEN > current debug vault`; credentials are never borrowed across targets.
 
-## 配置与网络
+State is stored under `<state-root>/cli/global/<target>/`, where the state root is `QMIND_HOME` or `~/.qmind`. The CLI does not install, load, or access the OS Keyring. Credential files are plaintext JSON, not encrypted storage. On POSIX, partition directories use mode `0700` and files use `0600`; these modes do not represent Windows ACLs. Writes use atomic replacement, file locking, and compare-and-swap protection for refreshes.
 
-常用环境变量：
+After upgrading from the legacy unpartitioned store, sign in again. Root-level config/credential files, `~/.qmind-env`, and old Keyring entries are not read, imported, or deleted automatically.
 
-- `QMIND_TOKEN`：非交互 token；
-- `QMIND_ENV`：`prod`、`daily` 或 `test`；
-- `QMIND_SASH_URL` / `QMIND_DASHBOARD_URL`：覆盖服务 origin；
-- `QMIND_HOME`：覆盖配置与凭证目录，默认 `~/.qmind`；
-- `QMIND_NON_INTERACTIVE=1`：禁止打开浏览器；
-- `QMIND_REQUEST_TIMEOUT_MS` / `QMIND_STREAM_IDLE_TIMEOUT_MS`：请求与流空闲超时；
-- `QMIND_TLS_CA_FILE`：私有 CA 文件。
+The shared 3.x Global/CN release is a breaking upgrade from Global 2.x. Upgrade this package with npm, then run `qmind login`; do not copy legacy credentials into the new partition. Existing versions before the shared release describe the Global/shared implementation only and do not imply a historical CN publication.
 
-CLI 支持 `HTTP_PROXY`、`HTTPS_PROXY` 和 `NO_PROXY`。TLS 默认严格校验；上传到签名对象地址时不会携带 QMind 的 Authorization、Cookie、CSRF 或代理凭证。
+Common variables include `QMIND_TOKEN`, `QMIND_DEBUG_TOKEN`, `QMIND_HOME`, `QMIND_CLIENT`, `QMIND_NON_INTERACTIVE`, `QMIND_REQUEST_TIMEOUT_MS`, `QMIND_STREAM_IDLE_TIMEOUT_MS`, and `QMIND_TLS_CA_FILE`. `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` are supported. TLS verification is strict by default, and credentials are not forwarded to signed object-storage URLs.

package/README.zh-CN.md

@@ -0,0 +1,91 @@
+# Qoder Global QMind CLI
+
+[English](./README.md)
+
+面向 Qoder Global 的 QMind 命令行工具，可用于登录、管理知识库和来源、检索内容、运行 RAG/编译任务，以及把本地目录同步到知识库。
+
+npm 包：`@qoder-ai/qmind-cli` · 命令：`qmind`
+
+## 安装
+
+需要 Node.js `>=20.18.1`。
+
+```sh
+npm install --global @qoder-ai/qmind-cli
+qmind version
+qmind --help
+```
+
+升级和卸载交给 npm。`qmind self-update` 只提示 npm 升级命令，不会修改 npm 管理的文件。
+
+```sh
+npm update --global @qoder-ai/qmind-cli
+npm uninstall --global @qoder-ai/qmind-cli
+```
+
+## 快速开始
+
+```sh
+qmind login
+qmind notebook list
+qmind source list --nb <notebook-id>
+qmind retrieve --nb <notebook-id> "发布前要检查什么？"
+```
+
+交互式登录会打开浏览器并把登录态保存到本机文件 vault。CI 或 Agent 场景建议使用环境变量和结构化输出：
+
+```sh
+export QMIND_TOKEN='<token>'
+qmind notebook list --non-interactive --format json
+qmind retrieve --nb <notebook-id> --format agent "部署流程是什么？"
+```
+
+不要把 token 写进命令参数、仓库或日志。使用完本机凭证后执行 `qmind logout`。
+
+## 命令
+
+| 命令                        | 用途                        |
+| --------------------------- | --------------------------- |
+| `login` / `logout`          | 登录或清除本机凭证          |
+| `notebook`                  | 管理知识库                  |
+| `cards` / `list` / `search` | 列出或搜索卡片              |
+| `source`                    | 管理知识库来源              |
+| `retrieve`                  | 检索上下文，不发起 LLM 调用 |
+| `rag`                       | 基于知识库提问              |
+| `compile` / `lint`          | 运行编译或检查工作流        |
+| `task`                      | 管理任务运行                |
+| `upload-folder` / `sync`    | 同步本地目录                |
+| `image`                     | 获取图片上传地址或访问地址  |
+| `version`                   | 查看版本和构建信息          |
+
+使用 `qmind <command> --help` 查看完整参数。领域命令支持 `table`、`json`、`agent`、`ndjson` 等输出格式。stdout 只输出结果，进度与诊断信息输出到 stderr。退出码 `0` 表示成功，`1` 表示运行失败、部分成功或取消，`2` 表示参数错误。
+
+## 同步目录
+
+先审阅计划，再决定是否执行远端删除：
+
+```sh
+qmind upload-folder --nb <notebook-id> --dir ./docs --mode if-changed --dry-run
+```
+
+移除 `--dry-run` 后才会写入远端。`--delete` 会把远端来源根目录视为本地目录镜像，并删除多余项。并发范围为 `1..10`。
+
+## 配置与认证
+
+本包固定为 Qoder Global 产品身份。不能通过改名、安装路径或产品选择环境变量切换产品。默认使用正式环境；`--env test` 和 `--env daily` 选择受支持的调试环境。自定义目标必须同时提供 `--sash` 与 `--dashboard`，且不能与显式 `--env` 组合。
+
+```sh
+qmind login --env test
+QMIND_DEBUG_TOKEN='<debug-token>' qmind notebook list --env test --non-interactive --format json
+qmind login --sash http://localhost:8080 --dashboard http://localhost:3000
+```
+
+正式环境 Token 优先级为 `--token > QMIND_TOKEN > 当前正式 vault`；调试环境为 `--token > QMIND_DEBUG_TOKEN > 当前调试 vault`，不会跨目标借用凭证。
+
+状态保存在 `<状态根>/cli/global/<目标>/`，状态根为 `QMIND_HOME` 或 `~/.qmind`。CLI 不安装、加载或访问 OS Keyring。凭证文件是明文 JSON，不是加密存储。POSIX 平台分区目录为 `0700`、文件为 `0600`；这些 mode 不代表 Windows ACL。写入使用原子替换、文件锁及 refresh compare-and-swap 保护。
+
+从旧版未分区存储升级后需要重新登录。旧根目录 config/credentials、`~/.qmind-env` 和旧 Keyring 项不会被读取、导入或自动删除。
+
+共享 3.x Global/CN 发行版相对 Global 2.x 是 breaking upgrade。通过 npm 升级本包后执行 `qmind login`，不要把旧凭证复制到新分区。共同发行版之前的历史版本只描述 Global/共享实现，不代表 CN 曾经发布。
+
+常用变量包括 `QMIND_TOKEN`、`QMIND_DEBUG_TOKEN`、`QMIND_HOME`、`QMIND_CLIENT`、`QMIND_NON_INTERACTIVE`、`QMIND_REQUEST_TIMEOUT_MS`、`QMIND_STREAM_IDLE_TIMEOUT_MS` 和 `QMIND_TLS_CA_FILE`。支持 `HTTP_PROXY`、`HTTPS_PROXY` 和 `NO_PROXY`。TLS 默认严格校验，访问签名对象存储地址时不会转发凭证。

package/bin/cli.js

@@ -1,3 +1,8 @@
 #!/usr/bin/env node
 
-import '../dist/qmind.js';
+import * as nodeModule from 'node:module';
+
+// Keep Node 20 compatibility while enabling the cache before the application graph is loaded.
+nodeModule.enableCompileCache?.();
+
+await import('../dist/qmind.js');

package/dist/cards-2J6ebaI0.js

@@ -0,0 +1,75 @@
+import { b as cardListSchema, d as pagination, h as stringList, m as requiredString, n as call, p as queryPath, u as optionalTrimmedString, v as batchMutationResultSchema, x as cardSchema } from "./shared-DwycozMA.js";
+//#region ../sdk/src/operations/cards.ts
+function createCardOperations(context) {
+	const listCards = async (notebookId, input = {}, options, featured = false) => {
+		const notebook = requiredString(notebookId, "notebookId");
+		const normalizedPage = pagination({
+			page: input.page ?? 1,
+			pageSize: input.pageSize ?? 20
+		});
+		const category = optionalTrimmedString(input.category, "category");
+		const query = optionalTrimmedString(input.query, "query");
+		const root = context.profile.apiPath(featured ? "featured-notebooks" : "notebooks", notebook, "cards");
+		const path = queryPath(root, [
+			["category", category],
+			["query", query],
+			["page", normalizedPage.page],
+			["page_size", normalizedPage.pageSize]
+		]);
+		return call(context, {
+			callOptions: options,
+			capability: featured ? "featuredNotebooks.read" : "cards.read",
+			idempotent: true,
+			method: "GET",
+			operation: featured ? "featuredCards.list" : "cards.list",
+			path,
+			schema: cardListSchema
+		});
+	};
+	return {
+		async batchDeleteCards(notebookId, cardIds, options) {
+			const notebook = requiredString(notebookId, "notebookId");
+			const ids = stringList(cardIds, "cardIds", { min: 1 });
+			return call(context, {
+				body: { cardIds: ids },
+				callOptions: options,
+				capability: "cards.write",
+				idempotent: false,
+				method: "POST",
+				operation: "cards.batchDelete",
+				path: context.profile.apiPath("notebooks", notebook, "cards", "batch-delete"),
+				schema: batchMutationResultSchema
+			});
+		},
+		async deleteCard(notebookId, cardId, options) {
+			const notebook = requiredString(notebookId, "notebookId");
+			const card = requiredString(cardId, "cardId");
+			return call(context, {
+				callOptions: options,
+				capability: "cards.write",
+				idempotent: false,
+				method: "DELETE",
+				operation: "cards.delete",
+				path: context.profile.apiPath("notebooks", notebook, "cards", card),
+				schema: batchMutationResultSchema
+			});
+		},
+		async getCard(notebookId, cardId, options) {
+			const notebook = requiredString(notebookId, "notebookId");
+			const card = requiredString(cardId, "cardId");
+			return call(context, {
+				callOptions: options,
+				capability: "cards.read",
+				idempotent: true,
+				method: "GET",
+				operation: "cards.get",
+				path: context.profile.apiPath("notebooks", notebook, "cards", card),
+				schema: cardSchema
+			});
+		},
+		listCards: (notebookId, input, options) => listCards(notebookId, input, options),
+		listFeaturedCards: (notebookId, input, options) => listCards(notebookId, input, options, true)
+	};
+}
+//#endregion
+export { createCardOperations };

package/dist/imports-Da88W09Q.js

@@ -0,0 +1,126 @@
+import { D as importProvidersSchema, Q as assertCapability, _ as aliDingImportRunSchema, a as invalidArgument, d as pagination, g as aliDingImportRunItemListSchema, m as requiredString, n as call, p as queryPath } from "./shared-DwycozMA.js";
+//#region ../sdk/src/operations/imports.ts
+const aliDingHost = "alidocs.dingtalk.com";
+const requestIdPattern = /^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$/u;
+/**
+* A canonical AliDing URL identifies exactly one node or knowledge base. Share links, short links,
+* query strings and fragments are aliases, so they are rejected rather than silently trimmed.
+*/
+function canonicalAliDingUrl(value, scope) {
+	const raw = requiredString(value, "url");
+	let url;
+	try {
+		url = new URL(raw);
+	} catch (cause) {
+		throw invalidArgument("url must be a canonical AliDing HTTPS URL", "url", { cause });
+	}
+	if (url.protocol !== "https:" || url.hostname !== aliDingHost) throw invalidArgument(`url must be an https://${aliDingHost} address`, "url");
+	if (url.search.length > 0 || url.hash.length > 0 || url.username.length > 0) throw invalidArgument("url must not carry a query, fragment or credentials", "url");
+	const prefix = scope === "nodeSubtree" ? "/i/nodes/" : "/i/spaces/";
+	if (!url.pathname.startsWith(prefix) || url.pathname === prefix) throw invalidArgument(`url must be an AliDing ${prefix} address for this import scope`, "url");
+	return url.toString();
+}
+function importRunBody(input, scope) {
+	const requestId = requiredString(input?.requestId, "requestId");
+	if (!requestIdPattern.test(requestId.toLowerCase())) throw invalidArgument("requestId must be a UUID", "requestId");
+	return {
+		requestId,
+		url: canonicalAliDingUrl(input?.url, scope)
+	};
+}
+function createImportOperations(context) {
+	return {
+		async getAliDingImportRun(notebookId, runId, options) {
+			const notebook = requiredString(notebookId, "notebookId");
+			const run = requiredString(runId, "runId");
+			assertCapability(context.profile, "imports.aliDing", "imports.aliDing.getRun");
+			return call(context, {
+				callOptions: options,
+				capability: "imports.aliDing",
+				idempotent: true,
+				method: "GET",
+				operation: "imports.aliDing.getRun",
+				path: context.profile.mindPath("notebooks", notebook, "aliding", "import-runs", run),
+				schema: aliDingImportRunSchema
+			});
+		},
+		async listAliDingImportRunItems(notebookId, runId, input = {}, options) {
+			const notebook = requiredString(notebookId, "notebookId");
+			const run = requiredString(runId, "runId");
+			const normalizedPage = pagination(input);
+			assertCapability(context.profile, "imports.aliDing", "imports.aliDing.listRunItems");
+			const base = context.profile.mindPath("notebooks", notebook, "aliding", "import-runs", run, "items");
+			return call(context, {
+				callOptions: options,
+				capability: "imports.aliDing",
+				idempotent: true,
+				method: "GET",
+				operation: "imports.aliDing.listRunItems",
+				path: queryPath(base, [
+					["pagination.currentPage", normalizedPage.page],
+					["pagination.pageSize", normalizedPage.pageSize],
+					["status", wireItemStatus(input.status)],
+					["contentStatus", wireContentStatus(input.contentStatus)],
+					["descendantsStatus", wireDescendantsStatus(input.descendantsStatus)]
+				]),
+				schema: aliDingImportRunItemListSchema
+			});
+		},
+		async listImportProviders(options) {
+			assertCapability(context.profile, "imports.discover", "imports.discover");
+			return call(context, {
+				callOptions: options,
+				capability: "imports.discover",
+				idempotent: true,
+				method: "GET",
+				operation: "imports.discover",
+				path: context.profile.mindPath("import-sources"),
+				schema: importProvidersSchema
+			});
+		},
+		async startAliDingKnowledgeBaseImport(notebookId, input, options) {
+			const notebook = requiredString(notebookId, "notebookId");
+			const body = importRunBody(input, "knowledgeBase");
+			assertCapability(context.profile, "imports.aliDing", "imports.aliDing.createKnowledgeBaseRun");
+			return call(context, {
+				body,
+				callOptions: options,
+				capability: "imports.aliDing",
+				idempotent: false,
+				method: "POST",
+				operation: "imports.aliDing.createKnowledgeBaseRun",
+				path: context.profile.mindPath("notebooks", notebook, "aliding", "knowledge-base-import-runs"),
+				schema: aliDingImportRunSchema
+			});
+		},
+		async startAliDingNodeSubtreeImport(notebookId, input, options) {
+			const notebook = requiredString(notebookId, "notebookId");
+			const body = importRunBody(input, "nodeSubtree");
+			assertCapability(context.profile, "imports.aliDing", "imports.aliDing.createNodeSubtreeRun");
+			return call(context, {
+				body,
+				callOptions: options,
+				capability: "imports.aliDing",
+				idempotent: false,
+				method: "POST",
+				operation: "imports.aliDing.createNodeSubtreeRun",
+				path: context.profile.mindPath("notebooks", notebook, "aliding", "node-subtree-import-runs"),
+				schema: aliDingImportRunSchema
+			});
+		}
+	};
+}
+function wireItemStatus(value) {
+	return value === void 0 ? void 0 : `ALI_DING_IMPORT_ITEM_STATUS_${screamingCase(value)}`;
+}
+function wireContentStatus(value) {
+	return value === void 0 ? void 0 : `ALI_DING_IMPORT_CONTENT_STATUS_${screamingCase(value)}`;
+}
+function wireDescendantsStatus(value) {
+	return value === void 0 ? void 0 : `ALI_DING_IMPORT_DESCENDANTS_STATUS_${screamingCase(value)}`;
+}
+function screamingCase(value) {
+	return value.replace(/([a-z0-9])([A-Z])/gu, "$1_$2").toUpperCase();
+}
+//#endregion
+export { createImportOperations };