dsh-d365-kit 0.34.1 → 0.34.3

package/INSTALL.md

@@ -1,94 +1,94 @@
-# Install (for colleagues)
-
-**English** | [简体中文](INSTALL.zh-CN.md)
-
-`dsh-d365-kit` is a DeepSeek Harness bundle (host plugin + settings page). Once installed you get 15 `d365_*` tools and a "Settings → D365 Toolkit" page.
-
-For the complete steps, see [docs/en/installation.md](docs/en/installation.md).
-
-## Prerequisites
-
-- DSH desktop app, able to open the Web GUI;
-- the machine can reach your Dataverse environment (`*.dynamics.com` or the regional domain);
-- an **application user** (ClientId + secret) granted permission in the environment to read metadata,
-  read solutions (`prvReadSolution`) and read the layer table (`prvReadmsdyn_componentlayer`). Read-only is
-  enough; add the relevant permissions when you need writes.
-
-## Install
-
-### Option 1: Install from npm (shortest, upgradeable)
-
-```
-plugin_manager install_bundle target="dsh-d365-kit@0.34.1"
-```
-
-This needs the package to be published to the registry pnpm uses — public npm or an internal mirror. The name has no scope, so no scope mapping is required.
-
-> Publishing to GitHub does not put the package in a registry: with only a GitHub repo, use option 2 (or `npm install github:<user>/<repo>#<tag>`). Pushing a `v*` tag publishes automatically once the `NPM_TOKEN` secret exists (`.github/workflows/publish.yml`).
-
-### Option 2: Install from Git (no registry needed)
-
-```
-plugin_manager install_bundle target="git+https://<your Git>/<group>/dsh-d365-kit.git#v0.34.1"
-```
-
-### Option 3: Install from a local directory
-
-Put the whole repository directory anywhere on the machine:
-
-```
-plugin_manager install_bundle target="D:\path\to\dsh-d365-kit"
-```
-
-This is a `link:` install: code changes take effect immediately, but upgrading is your own `git pull`.
-
-All paths are the same: **restart DSH once after installing**, so the Web client loads the settings page code into the module graph.
-
-## First-time configuration
-
-1. Settings → D365 Toolkit → Environments → Add environment: key (e.g. `dev`), URL, tenant ID, ClientId, client secret;
-2. Click "Test connection"; if you see a version number, the credentials are fine;
-3. On the "Permissions" tab, tick what this machine is allowed to do (one block per environment, separated by a rule):
-   - "Read metadata" — already ticked by default; untick it and tables, fields and views become unreadable too;
-   - "Read business data" — without it the records in tables are unreadable;
-   - write capabilities are all off by default, and even when ticked every execution still needs a person to confirm it in the conversation;
-4. Click "Save".
-
-By default the configuration is written to `<your DSH workspace>/d365.config.json`, and the secret is stored separately in `d365.secrets.json` in the same directory
-(plain text, don't commit it). If your workspace isn't in the default location, set the `D365_CONFIG_FILE` environment variable, or point `configFile` at an absolute path in the profile's
-`cordis.patch.yml`.
-
-## Verify
-
-```
-d365_envs check=true
-d365_metadata resource=entities top=3
-```
-
-If both return content, you're connected. The first `d365_sync` pulls the full metadata (about 125 MB, three minutes or so); if you don't want to spend the disk space, you can skip it for now.
-
-### The troubleshooting skill comes with the plugin
-
-The package ships an agent skill at `skills/d365-troubleshooting/SKILL.md` (how to work a plug-in failure: trace level → signature → one full call → registration → reproduce). The plugin registers it into the Host skill registry when it loads, so installing the bundle is all you have to do — nothing to copy, and the agent picks it up by description without anyone invoking it by name.
-
-To change it, edit the file in the installed package (or in your clone, when you installed from source) and reload the plugin; edits made anywhere else are not read.
-
-## Upgrade
-
-```
-plugin_manager remove_bundle target=dsh-d365-kit
-plugin_manager install_bundle target="...<new version>..."
-```
-
-You must remove before installing: when the package already exists the installer only returns `already-installed` and does not replace the code. Restart DSH after upgrading.
-
-## FAQ
-
-- **Tools don't appear**: run `plugin_manager list_plugins` and check whether `include:dsh-d365-kit` is `active`; a fresh install needs a restart.
-- **No "D365 Toolkit" on the settings page**: the client plugin didn't make it into the module graph — restart; if it's still missing, check whether the module id in `client.js` matches the package name.
-- **Save reports "writes can only be started from the settings page"**: that's the CSRF guard — only save from the settings page; rejections are logged to `.d365/write-guard.log`.
-- **Reading business data reports `data-read-forbidden`**: tick "Read business data" on the Permissions tab.
-- **A write is rejected with `environment-busy`**: the environment is importing or publishing; wait for it to finish and retry.
-- **GitLab 403**: the token's user needs at least the Reporter role in that project.
-
-For other error codes, see [docs/en/troubleshooting.md](docs/en/troubleshooting.md).
+# Install (for colleagues)
+
+**English** | [简体中文](INSTALL.zh-CN.md)
+
+`dsh-d365-kit` is a DeepSeek Harness bundle (host plugin + settings page). Once installed you get 19 `d365_*` tools and a "Settings → D365 Toolkit" page.
+
+For the complete steps, see [docs/en/installation.md](docs/en/installation.md).
+
+## Prerequisites
+
+- DSH desktop app, able to open the Web GUI;
+- the machine can reach your Dataverse environment (`*.dynamics.com` or the regional domain);
+- an **application user** (ClientId + secret) granted permission in the environment to read metadata,
+  read solutions (`prvReadSolution`) and read the layer table (`prvReadmsdyn_componentlayer`). Read-only is
+  enough; add the relevant permissions when you need writes.
+
+## Install
+
+### Option 1: Install from npm (shortest, upgradeable)
+
+```
+plugin_manager install_bundle target="dsh-d365-kit@0.34.3"
+```
+
+This needs the package to be published to the registry pnpm uses — public npm or an internal mirror. The name has no scope, so no scope mapping is required.
+
+> Publishing to GitHub does not put the package in a registry: with only a GitHub repo, use option 2 (or `npm install github:<user>/<repo>#<tag>`). `.github/workflows/publish.yml` publishes on every push to `main` whose `package.json` version is not on npm yet, once either the `NPM_TRUSTED_PUBLISHING` variable (trusted publishing) or the `NPM_TOKEN` secret exists.
+
+### Option 2: Install from Git (no registry needed)
+
+```
+plugin_manager install_bundle target="git+https://<your Git>/<group>/dsh-d365-kit.git#v0.34.3"
+```
+
+### Option 3: Install from a local directory
+
+Put the whole repository directory anywhere on the machine:
+
+```
+plugin_manager install_bundle target="D:\path\to\dsh-d365-kit"
+```
+
+This is a `link:` install: code changes take effect immediately, but upgrading is your own `git pull`.
+
+All paths are the same: **restart DSH once after installing**, so the Web client loads the settings page code into the module graph.
+
+## First-time configuration
+
+1. Settings → D365 Toolkit → Environments → Add environment: key (e.g. `dev`), URL, tenant ID, ClientId, client secret;
+2. Click "Test connection"; if you see a version number, the credentials are fine;
+3. On the "Permissions" tab, tick what this machine is allowed to do (one block per environment, separated by a rule):
+   - "Read metadata" — already ticked by default; untick it and tables, fields and views become unreadable too;
+   - "Read business data" — without it the records in tables are unreadable;
+   - write capabilities are all off by default, and even when ticked every execution still needs a person to confirm it in the conversation;
+4. Click "Save".
+
+By default the configuration is written to `<your DSH workspace>/d365.config.json`, and the secret is stored separately in `d365.secrets.json` in the same directory
+(plain text, don't commit it). If your workspace isn't in the default location, set the `D365_CONFIG_FILE` environment variable, or point `configFile` at an absolute path in the profile's
+`cordis.patch.yml`.
+
+## Verify
+
+```
+d365_envs check=true
+d365_metadata resource=entities top=3
+```
+
+If both return content, you're connected. The first `d365_sync` pulls the full metadata (about 125 MB, three minutes or so); if you don't want to spend the disk space, you can skip it for now.
+
+### The troubleshooting skill comes with the plugin
+
+The package ships an agent skill at `skills/d365-troubleshooting/SKILL.md` (how to work a plug-in failure: trace level → signature → one full call → registration → reproduce). The plugin registers it into the Host skill registry when it loads, so installing the bundle is all you have to do — nothing to copy, and the agent picks it up by description without anyone invoking it by name.
+
+To change it, edit the file in the installed package (or in your clone, when you installed from source) and reload the plugin; edits made anywhere else are not read.
+
+## Upgrade
+
+```
+plugin_manager remove_bundle target=dsh-d365-kit
+plugin_manager install_bundle target="...<new version>..."
+```
+
+You must remove before installing: when the package already exists the installer only returns `already-installed` and does not replace the code. Restart DSH after upgrading.
+
+## FAQ
+
+- **Tools don't appear**: run `plugin_manager list_plugins` and check whether `include:dsh-d365-kit` is `active`; a fresh install needs a restart.
+- **No "D365 Toolkit" on the settings page**: the client plugin didn't make it into the module graph — restart; if it's still missing, check whether the module id in `client.js` matches the package name.
+- **Save reports "writes can only be started from the settings page"**: that's the CSRF guard — only save from the settings page; rejections are logged to `.d365/write-guard.log`.
+- **Reading business data reports `data-read-forbidden`**: tick "Read business data" on the Permissions tab.
+- **A write is rejected with `environment-busy`**: the environment is importing or publishing; wait for it to finish and retry.
+- **GitLab 403**: the token's user needs at least the Reporter role in that project.
+
+For other error codes, see [docs/en/troubleshooting.md](docs/en/troubleshooting.md).

package/INSTALL.zh-CN.md

@@ -1,93 +1,93 @@
-# 安装（给同事）
-
-**[English](INSTALL.md)** | 简体中文
-
-`dsh-d365-kit` 是 DeepSeek Harness 的 bundle（Host 插件 + 设置页）。装完会有 16 个 `d365_*` 工具和「设置 → D365 工具箱」页面。
-
-更完整的步骤见 [docs/installation.md](docs/zh/installation.md)。
-
-## 前置
-
-- DSH 桌面版，能打开 Web GUI；
-- 机器能访问你的 Dataverse 环境（`*.dynamics.com` 或对应区域域名）；
-- 一个**应用用户**（ClientId + 密钥），在环境里给了读元数据、读解决方案（`prvReadSolution`）、
-  读层表（`prvReadmsdyn_componentlayer`）的权限。只读就够用；要写入再加相应权限。
-
-## 安装
-
-### 方式一：从 npm 装（最短，可升级）
-
-```
-plugin_manager install_bundle target="dsh-d365-kit@0.34.1"
-```
-
-前提是包已经发到 pnpm 用的那个 registry——公网 npm 或公司内网镜像都行。包名没有 scope，不需要配 scope 映射。
-
-> 只推 GitHub 不等于进了 registry：只有 GitHub 仓库时用方式二（或 `npm install github:<user>/<repo>#<tag>`）。配好 `NPM_TOKEN` secret 后推 `v*` tag 会自动发布（`.github/workflows/publish.yml`）。
-
-### 方式二：从 Git 装（不需要 registry）
-
-```
-plugin_manager install_bundle target="git+https://<你的 Git>/<group>/dsh-d365-kit.git#v0.34.1"
-```
-
-### 方式三：从本地目录装
-
-把整个仓库目录放到本机任意位置：
-
-```
-plugin_manager install_bundle target="D:\path\to\dsh-d365-kit"
-```
-
-这是 `link:` 安装：改代码立刻生效，但升级要自己 `git pull`。
-
-三条路一样：**装完重启一次 DSH**，Web 客户端才会把设置页代码加载进模块图。
-
-## 首次配置
-
-1. 设置 → D365 工具箱 → 环境 → 添加环境：key（如 `dev`）、URL、租户 ID、ClientId、客户端密钥；
-2. 点「测试连接」，看到版本号说明凭据没问题；
-3. 到「权限」标签勾选这台机器允许做什么（每个环境单独一块，用分隔线隔开）：
-   - 「读取元数据」——默认就是勾上的；不勾连表、字段、视图都查不到；
-   - 「读取业务数据」——不勾就读不到表里的记录；
-   - 写入类能力默认全关，勾了之后每次执行仍要人在对话里确认；
-4. 点「保存」。
-
-配置默认写到 `<你的 DSH 工作区>/d365.config.json`，密钥单独存同目录的 `d365.secrets.json`
-（明文，别提交）。工作区不在默认位置时，设环境变量 `D365_CONFIG_FILE`，或在 profile 的
-`cordis.patch.yml` 里给 `configFile` 写绝对路径。
-
-## 验证
-
-```
-d365_envs check=true
-d365_metadata resource=entities top=3
-```
-
-都有内容就说明通了。第一次 `d365_sync` 会拉全量元数据（约 125 MB、三分钟左右），不想占盘可以先不做。
-
-### 排查 skill 随插件一起装
-
-包里带了一个 agent skill：`skills/d365-troubleshooting/SKILL.md`（插件失败怎么查：跟踪级别 → 归并签名 → 取一条完整调用 → 看步骤注册 → 复现）。插件加载时会把它注册进 Host 的 skill 注册表，所以装完 bundle 就有了——不需要复制文件，也不用谁按名字手动调用，agent 按描述就会自己用。
-
-要改就直接改装好的包里的这一份（源码安装就改克隆里的那份），然后重载插件；写在别处的副本不会被读到。
-
-## 升级
-
-```
-plugin_manager remove_bundle target=dsh-d365-kit
-plugin_manager install_bundle target="...新版本..."
-```
-
-必须先 remove 再 install：包已存在时安装器只返回 `already-installed`，不会替换代码。升级后重启 DSH。
-
-## 常见问题
-
-- **工具没出现**：`plugin_manager list_plugins` 看 `include:dsh-d365-kit` 是否 `active`；刚装完要重启。
-- **设置页没有「D365 工具箱」**：客户端插件未进模块图，重启；仍没有就查 `client.js` 的模块 id 是否与包名一致。
-- **保存报「写入只能从设置页发起」**：CSRF 守卫，只在设置页里保存；被拒记录在 `.d365/write-guard.log`。
-- **读业务数据报 `data-read-forbidden`**：到权限标签勾「读取业务数据」。
-- **写入被拒 `environment-busy`**：环境正在导入或发布，等结束再试。
-- **GitLab 403**：令牌用户在该项目里至少要有 Reporter 角色。
-
-其余错误码见 [docs/troubleshooting.md](docs/zh/troubleshooting.md)。
+# 安装（给同事）
+
+**[English](INSTALL.md)** | 简体中文
+
+`dsh-d365-kit` 是 DeepSeek Harness 的 bundle（Host 插件 + 设置页）。装完会有 19 个 `d365_*` 工具和「设置 → D365 工具箱」页面。
+
+更完整的步骤见 [docs/installation.md](docs/zh/installation.md)。
+
+## 前置
+
+- DSH 桌面版，能打开 Web GUI；
+- 机器能访问你的 Dataverse 环境（`*.dynamics.com` 或对应区域域名）；
+- 一个**应用用户**（ClientId + 密钥），在环境里给了读元数据、读解决方案（`prvReadSolution`）、
+  读层表（`prvReadmsdyn_componentlayer`）的权限。只读就够用；要写入再加相应权限。
+
+## 安装
+
+### 方式一：从 npm 装（最短，可升级）
+
+```
+plugin_manager install_bundle target="dsh-d365-kit@0.34.3"
+```
+
+前提是包已经发到 pnpm 用的那个 registry——公网 npm 或公司内网镜像都行。包名没有 scope，不需要配 scope 映射。
+
+> 只推 GitHub 不等于进了 registry：只有 GitHub 仓库时用方式二（或 `npm install github:<user>/<repo>#<tag>`）。`.github/workflows/publish.yml` 会在每次推 `main` 且 `package.json` 版本还没上架时自动发布 —— 前提是配了 `NPM_TRUSTED_PUBLISHING` 变量（trusted publishing）或 `NPM_TOKEN` secret。
+
+### 方式二：从 Git 装（不需要 registry）
+
+```
+plugin_manager install_bundle target="git+https://<你的 Git>/<group>/dsh-d365-kit.git#v0.34.3"
+```
+
+### 方式三：从本地目录装
+
+把整个仓库目录放到本机任意位置：
+
+```
+plugin_manager install_bundle target="D:\path\to\dsh-d365-kit"
+```
+
+这是 `link:` 安装：改代码立刻生效，但升级要自己 `git pull`。
+
+三条路一样：**装完重启一次 DSH**，Web 客户端才会把设置页代码加载进模块图。
+
+## 首次配置
+
+1. 设置 → D365 工具箱 → 环境 → 添加环境：key（如 `dev`）、URL、租户 ID、ClientId、客户端密钥；
+2. 点「测试连接」，看到版本号说明凭据没问题；
+3. 到「权限」标签勾选这台机器允许做什么（每个环境单独一块，用分隔线隔开）：
+   - 「读取元数据」——默认就是勾上的；不勾连表、字段、视图都查不到；
+   - 「读取业务数据」——不勾就读不到表里的记录；
+   - 写入类能力默认全关，勾了之后每次执行仍要人在对话里确认；
+4. 点「保存」。
+
+配置默认写到 `<你的 DSH 工作区>/d365.config.json`，密钥单独存同目录的 `d365.secrets.json`
+（明文，别提交）。工作区不在默认位置时，设环境变量 `D365_CONFIG_FILE`，或在 profile 的
+`cordis.patch.yml` 里给 `configFile` 写绝对路径。
+
+## 验证
+
+```
+d365_envs check=true
+d365_metadata resource=entities top=3
+```
+
+都有内容就说明通了。第一次 `d365_sync` 会拉全量元数据（约 125 MB、三分钟左右），不想占盘可以先不做。
+
+### 排查 skill 随插件一起装
+
+包里带了一个 agent skill：`skills/d365-troubleshooting/SKILL.md`（插件失败怎么查：跟踪级别 → 归并签名 → 取一条完整调用 → 看步骤注册 → 复现）。插件加载时会把它注册进 Host 的 skill 注册表，所以装完 bundle 就有了——不需要复制文件，也不用谁按名字手动调用，agent 按描述就会自己用。
+
+要改就直接改装好的包里的这一份（源码安装就改克隆里的那份），然后重载插件；写在别处的副本不会被读到。
+
+## 升级
+
+```
+plugin_manager remove_bundle target=dsh-d365-kit
+plugin_manager install_bundle target="...新版本..."
+```
+
+必须先 remove 再 install：包已存在时安装器只返回 `already-installed`，不会替换代码。升级后重启 DSH。
+
+## 常见问题
+
+- **工具没出现**：`plugin_manager list_plugins` 看 `include:dsh-d365-kit` 是否 `active`；刚装完要重启。
+- **设置页没有「D365 工具箱」**：客户端插件未进模块图，重启；仍没有就查 `client.js` 的模块 id 是否与包名一致。
+- **保存报「写入只能从设置页发起」**：CSRF 守卫，只在设置页里保存；被拒记录在 `.d365/write-guard.log`。
+- **读业务数据报 `data-read-forbidden`**：到权限标签勾「读取业务数据」。
+- **写入被拒 `environment-busy`**：环境正在导入或发布，等结束再试。
+- **GitLab 403**：令牌用户在该项目里至少要有 Reporter 角色。
+
+其余错误码见 [docs/troubleshooting.md](docs/zh/troubleshooting.md)。

package/LICENSE

@@ -1,21 +1,21 @@
-MIT License
-
-Copyright (c) 2026 iTanzhao
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+MIT License
+
+Copyright (c) 2026 iTanzhao
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.