dsh-connect-trae 4.8.0 → 4.8.1

package/CHANGELOG.md

@@ -1,5 +1,33 @@
 # Changelog
 
+## 4.8.1 (2026-11-05)
+
+### 适配
+
+- **DSH 0.2.2-rc.1 同步**。宿主这一版随包换代到 `cordis@4.1.0`、`schemastery@3.19.0`、
+  `@earendil-works/pi-ai@1.3.0`，插件消费的 13 个宿主包里有 8 个带实质变化。
+  - **唯一的契约破坏**：`ResolvedPiAiProviderProfile` 新增两个必填字段
+    `maxRequestImages` / `imageOffloadCountQuantum`。本插件从实时目录手工构造这个 profile，
+    升级依赖后 `pnpm typecheck` 报 `TS2739`；已在 `REQUEST_IMAGE_BUDGETS` 补上宿主默认值
+    `50 / 10`（旧宿主忽略多余键，0.2.1 线仍类型通过）。
+  - **运行期无需适配**：4.8.0 在 0.2.2-rc.1 上照常工作——宿主只在配置解析路径给这两个字段
+    兜底，手写 profile 传 `undefined` 时 0.2.2 走「不限制张数」分支（本机实测：usage 路由
+    200、已登录）。本版把这两个字段显式声明，图像张数超限的流程才跟着宿主一起生效。
+  - **目录变化公告**：区域目录变化时按 provider 发一次 `llm/models-updated`（0.2.2 新增）。
+    `llm/adapters-updated` 只在路由拓扑变化时发，覆盖不到「同一路由换了 roster」；签名去重
+    保证一次设置写入重建出相同行时不会惊动选择器。旧宿主上这是无人监听的未知事件。
+  - **模型标签补回别人的 badge**：`conversation.input.model.label` 是 `single` 槽，本插件
+    占住后宿主的「名字 + `model.badge`」内置渲染对所有 provider 都不再生效。现在非 Trae 行
+    按宿主顺序补回 badge（trigger 在前、菜单在后）并做语言回退；本插件自己的行行为不变。
+  - 不采纳：新语言 ja/es/fr/de/ru/pt（只维护 zh/en）、`settings.section.icon`（不拥有
+    `settings.section`）、`llm-pi-ai/request-headers`、`supportsMidConvoEffort`。
+  - 三大价值（双区域供应商 / 用量积分 / 每日签到）不受影响，对应测试全绿。
+- **开发树同步**：13 个 `@deepseek-ai/dsh-*` devDependency → `0.2.2-rc.1`，`cordis` →
+  `^4.1.0`，`schemastery` → `3.19.0`（含 `pnpm-workspace.yaml` override），`pi-ai` →
+  `1.3.0`；`pnpm-lock.yaml` 重新生成。peerDependencies 零改动。
+- `tests/dsh-peer-range.spec.ts` 的 `MUST_ADMIT` 补入 `0.2.2-rc.1`；新增目录公告与
+  badge 渲染用例（103 文件 / 1335 用例全绿）。
+
 ## 4.8.0 (2026-11-05)
 
 > **从 npm 升级的用户，这一版把 v4.7.0 也一起带上了。** v4.7.0 的 tag 与 GitHub

package/README.en.md

@@ -197,7 +197,7 @@ Restart the DSH process after install/update/uninstall.
 ## DSH version compatibility
 
 **Requires DSH 0.1.7-rc.1 and up** (since 2.3.0 the plugin no longer targets hosts older than 0.1.7; the peer dependency ranges are narrowed accordingly).
-**The peer upper bound is `<0.3.0-0`, so both the 0.1.7 and the 0.2 line are supported (including 0.2.1-rc.5, verified).**
+**The peer upper bound is `<0.3.0-0`, so both the 0.1.7 and the 0.2 line are supported (including 0.2.2-rc.1, verified).**
 
 ### Both pi-ai context generations are supported (since 3.4.2)
 
@@ -257,6 +257,22 @@ For **this plugin**:
 
 Details: [section 11 of `docs/DSH_0.2.1_RC1_SYNC.md`](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.1_RC1_SYNC.md).
 
+### `0.2.2-rc.1` sync (since 4.8.1)
+
+The host moved to `0.2.2-rc.1`. This release is **not just version bumps**: the bundled dependencies move as a set (`cordis` 4.0.5 → **4.1.0**, `schemastery` 3.18.5 → **3.19.0**, `@earendil-works/pi-ai` 1.1.0 → **1.3.0**), and **8 of the 13 host packages** this plugin consumes carry real changes.
+
+For **this plugin**:
+
+- **One contract break**: `dsh-llm-pi-ai` added two **required** fields to `ResolvedPiAiProviderProfile` — `maxRequestImages` and `imageOffloadCountQuantum`. This plugin builds that profile **by hand** from the live catalog (it bypasses the host's config resolution), so `pnpm typecheck` fails with `TS2739` after the bump. Both are now declared in `REQUEST_IMAGE_BUDGETS` with the host's own defaults, `50 / 10`.
+- **Runtime was never broken**: the host only defaults those fields on its config-resolution path; a hand-built profile that omits them takes the "image count unchecked" branch on 0.2.2. That is why 4.8.0 keeps working there (verified on the desktop host: `GET /plugins/dsh-connect-trae/usage` → 200, `signed-in`).
+- **New capabilities adopted where they matter**: the plugin now emits `llm/models-updated(provider)` when a region's catalog changes (deduplicated by a signature, so a settings write that rebuilds identical rows does not wake every consumer). And because `conversation.input.model.label` is a `single` slot, holding it suppresses the host's built-in "name + `model.badge`" label for **every** provider — so the component now renders another provider's `model.badge` (with language fallback) instead of dropping it. Its own rows are unchanged.
+- **Deliberately not adopted**: the six new UI languages (this plugin keeps zh/en and falls back to English), `settings.section.icon` (it owns plugin cards, not a `settings.section`), `llm-pi-ai/request-headers` (no custom inference headers), `supportsMidConvoEffort` (not on the openai-completions route).
+- **The three core values are unaffected**: dual-region providers, usage/credits overview, daily check-in. Their tests are green; this change only touches the image budget, catalog announcements, and the model label.
+- The other six changed packages (`dsh-host-webserver` resource routes, `dsh-attachment` admission variants, the new languages in `dsh-client-locale` / `dsh-client-ui-settings-plugins`, the `dsh-client-ui-settings` icon slot, `dsh-client-ui-primitives` additions) are **additive**; this plugin either does not use them or already has an equivalent. The five unchanged packages (`dsh-atomic-write`, `dsh-client-ui-renderer`, `dsh-client-ui-slots`, `dsh-home-paths`, `dsh-settings`) are **byte-for-byte identical**, so every slot contract this plugin registers is unchanged.
+- The peer range **needs no change**: `0.2.2-rc.1` is admitted by `>=0.1.7-rc.1 <0.3.0-0`, and `MUST_ADMIT` in `tests/dsh-peer-range.spec.ts` now includes it.
+
+Details: [`docs/DSH_0.2.2_RC1_SYNC.md`](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.2_RC1_SYNC.md).
+
 
 ### Why the upper bound is not `<0.2.0`
 

package/README.md

@@ -216,7 +216,7 @@ npm install dsh-connect-trae
 ## DSH 版本兼容
 
 **要求 DSH 0.1.7-rc.1 及以上**（2.3.0 起不再支持 0.1.7 之前的宿主；peer 依赖范围已按此收窄）。
-**peer 上界为 `<0.3.0-0`：0.1.7 与 0.2 两条线均受支持（含 0.2.1-rc.5，已实测）。**
+**peer 上界为 `<0.3.0-0`：0.1.7 与 0.2 两条线均受支持（含 0.2.2-rc.1，已实测）。**
 
 ### 同时支持 pi-ai 的两代上下文（3.4.2 起）
 
@@ -317,6 +317,40 @@ stderr、View 标签的 tooltip 只在文字溢出时显示、More 菜单 toolti
 细节见 [`docs/DSH_0.2.1_RC1_SYNC.md`](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.1_RC1_SYNC.md) 第十一节。
 
 
+### `0.2.2-rc.1` 同步结论（4.8.1 起）
+
+宿主推进到 `0.2.2-rc.1`。这一版**不只是版本号**：随包依赖整体换代（`cordis` 4.0.5 →
+**4.1.0**、`schemastery` 3.18.5 → **3.19.0**、`@earendil-works/pi-ai` 1.1.0 → **1.3.0**），
+插件消费的 13 个宿主包里 **8 个有实质变化**。
+
+对**本插件**而言：
+
+- **唯一的契约破坏**：`dsh-llm-pi-ai` 给 `ResolvedPiAiProviderProfile` 新增了两个**必填**
+  字段 `maxRequestImages` / `imageOffloadCountQuantum`。本插件从实时目录**手工构造**这个
+  profile（不走宿主的配置解析），所以升级依赖后 `pnpm typecheck` 报 `TS2739`。已在
+  `REQUEST_IMAGE_BUDGETS` 补上宿主默认值 `50 / 10`。
+- **运行期原本就没坏**：宿主只在配置解析路径里给这两个字段兜底，手写 profile 传
+  `undefined` 时 0.2.2 走「不限制张数」，因此 4.8.0 在 0.2.2 上照常工作（本机实测：桌面端
+  0.2.2-rc.1 + 插件 4.8.0，`GET /plugins/dsh-connect-trae/usage` 返回 200 且 `signed-in`）。
+- **新增能力按需采纳**：目录变化时按 provider 发 `llm/models-updated`（签名去重，避免每次
+  设置写入都惊动选择器）；`conversation.input.model.label` 是 `single` 槽，本插件占住后会
+  压掉宿主的「名字 + `model.badge`」内置渲染，因此对**别的 provider** 的模型补回了 badge
+  （含语言回退），本插件自己的行行为不变。
+- **明确不采纳**：新语言 ja / es / fr / de / ru / pt（只维护 zh / en，其余回退英文）、
+  `settings.section.icon`（插件不拥有 `settings.section`）、`llm-pi-ai/request-headers`
+  （不需要额外请求头）、`supportsMidConvoEffort`（openai-completions 路线用不到）。
+- **三大价值不受影响**：双区域供应商、用量与积分概览、每日签到领取——对应测试全绿，本次
+  只碰图像预算、目录公告与模型标签三处。
+- 其余 6 个有变化的包（`dsh-host-webserver` 的资源路由、`dsh-attachment` 的准入类型扩展、
+  `dsh-client-locale` / `dsh-client-ui-settings-plugins` 的新语言、`dsh-client-ui-settings`
+  的 icon 槽位、`dsh-client-ui-primitives` 的新增属性）**全部是新增**，本插件未使用或已有
+  等价实现；`dsh-atomic-write` / `dsh-client-ui-renderer` / `dsh-client-ui-slots` /
+  `dsh-home-paths` / `dsh-settings` 这 5 个包**逐字节未变**，槽位契约不变。
+- peer 范围**无需改动**：`0.2.2-rc.1` 已被 `>=0.1.7-rc.1 <0.3.0-0` 放行，
+  `tests/dsh-peer-range.spec.ts` 的 `MUST_ADMIT` 已补入。
+
+细节见 [`docs/DSH_0.2.2_RC1_SYNC.md`](https://github.com/dingminhua/dsh-connect-trae/blob/main/docs/DSH_0.2.2_RC1_SYNC.md)。
+
 ### peer 上界为什么不写 `<0.2.0`
 
 2.3.1 曾写 `<0.2.0-0`，意图是「先不支持 0.2.0 正式版」。这个写法**是错的**：

package/lib/client.js

@@ -8611,8 +8611,9 @@ window.__ModuleLoader__.load({
 		*
 		* WHY THE HOST STILL OWNS THE NAME. The contract says to keep `model.name` as
 		* the text and render the addition beside it, so this component returns the name
-		* first — it never replaces it — and it renders nothing extra for a provider
-		* that is not ours.
+		* first — it never replaces it. For a provider that is not ours it reproduces
+		* the host's own label: the catalog name and, since 0.2.2, that model's optional
+		* `badge` (see {@link HostModelBadge}).
 		*
 		* @module dsh-connect-trae/client/TraeModelLabel
 		*/
@@ -8869,8 +8870,9 @@ window.__ModuleLoader__.load({
 		*
 		* WHAT WINNING/HOLDING COSTS. This cell is `single`, so the other registrants'
 		* decorations on the rows this plugin claims are not composed. That is the
-		* documented, accepted trade-off, and it is why the component returns the plain
-		* catalog name for any provider that is not ours — the slot's own minimum.
+		* documented, accepted trade-off, and it is why the component reproduces the
+		* host's own presentation — catalog name plus that model's optional badge — for
+		* any provider that is not ours.
 		*
 		* WHY A DISTINCT PRIORITY IS NOT ENOUGH ON ITS OWN. It removes the cross-plugin
 		* collision, but issue #74's error was a SECOND registration of THIS plugin
@@ -8883,10 +8885,88 @@ window.__ModuleLoader__.load({
 		* made the throw rarer and harder to read, not absent.
 		*/
 		const MODEL_LABEL_PRIORITY = -.25;
+		/** The tone colours, mapped onto the same theme tokens the host's Tag paints. */
+		const HOST_BADGE_TONES = {
+			neutral: {
+				color: "var(--dsw-alias-label-secondary)",
+				background: "var(--dsw-alias-bg-layer-2)",
+				border: "var(--dsw-alias-border-l2)"
+			},
+			info: {
+				color: "var(--dsw-alias-brand-primary)",
+				background: "var(--dsw-alias-bg-layer-2)",
+				border: "var(--dsw-alias-border-l2)"
+			},
+			success: {
+				color: "var(--dsw-alias-state-success-primary)",
+				background: "var(--dsw-alias-bg-layer-2)",
+				border: "var(--dsw-alias-border-l2)"
+			},
+			warning: {
+				color: "var(--dsw-alias-state-warn-secondary)",
+				background: "var(--dsw-alias-bg-layer-2)",
+				border: "var(--dsw-alias-border-l2)"
+			}
+		};
+		/**
+		* The one line a badge shows, in the reader's language.
+		*
+		* The host contract requires an English entry, so that is the last resort; the
+		* active language and its base tag (`de-DE` → `de`) come first, matching what
+		* the host's own resolver does. An empty string is treated as absent — a blank
+		* chip would be a decoration that says nothing.
+		*/
+		function resolveHostBadgeText(text) {
+			if (typeof text === "string") return text.trim() === "" ? void 0 : text;
+			const language = uiLanguage().toLowerCase();
+			const base = language.split("-")[0] ?? "";
+			const picked = text[language] ?? (base === "" ? void 0 : text[base]) ?? text.en;
+			return picked === void 0 || picked.trim() === "" ? void 0 : picked;
+		}
+		/** One provider-authored selector badge, drawn where the host's own label draws it. */
+		function HostBadge(props) {
+			const tone = HOST_BADGE_TONES[props.badge.tone] ?? HOST_BADGE_TONES.neutral;
+			return /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", {
+				className: "dsm-trae-model-label-host-badge",
+				style: {
+					flex: "none",
+					borderRadius: "999px",
+					padding: "0 6px",
+					fontSize: "10px",
+					fontWeight: 500,
+					lineHeight: "15px",
+					whiteSpace: "nowrap",
+					border: `1px solid ${tone.border}`,
+					color: tone.color,
+					background: tone.background,
+					maxWidth: "8em",
+					overflow: "hidden",
+					textOverflow: "ellipsis"
+				},
+				children: props.label
+			});
+		}
 		function TraeModelLabel(props) {
 			const { provider, model } = props;
 			const panel = panelOfProvider(provider.id);
-			if (panel === void 0) return /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", { children: model.name });
+			if (panel === void 0) {
+				const badgeInfo = model.badge;
+				const label = badgeInfo === void 0 ? void 0 : resolveHostBadgeText(badgeInfo.text);
+				if (badgeInfo === void 0 || label === void 0) return /* @__PURE__ */ (0, react_jsx_runtime.jsx)("span", { children: model.name });
+				const badge = /* @__PURE__ */ (0, react_jsx_runtime.jsx)(HostBadge, {
+					badge: badgeInfo,
+					label
+				});
+				return props.placement === "trigger" ? /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("span", { children: [
+					badge,
+					" ",
+					model.name
+				] }) : /* @__PURE__ */ (0, react_jsx_runtime.jsxs)("span", { children: [
+					model.name,
+					" ",
+					badge
+				] });
+			}
 			return /* @__PURE__ */ (0, react_jsx_runtime.jsx)(TraeModelLabelInner, {
 				modelId: model.id,
 				name: model.name,

package/lib/index.js

@@ -1034,10 +1034,33 @@ const INERT_AUTH = {
 		}
 	}
 };
+/**
+* The image-request policy this hand-built profile hands to `dsh-llm-pi-ai`.
+*
+* WHY THIS OBJECT IS SPELLED OUT. DSH's own config resolution (`resolveProfiles`
+* in `dsh-llm-pi-ai`) defaults every route-level image bound. This plugin never
+* runs that path: it builds `ResolvedPiAiProviderProfile` by hand from a live
+* Trae catalog, so every field the host expects has to be named here or the
+* bound silently does not apply.
+*
+* `maxRequestImages` / `imageOffloadCountQuantum` joined that contract in DSH
+* 0.2.2-rc.1 (the required fields on `ResolvedPiAiProviderProfile`). The count
+* bound is what turns a request carrying more images than a route accepts into
+* the host's `IMAGE_OFFLOAD_REQUIRED` flow instead of an upstream rejection, and
+* the quantum is how many of the oldest occurrences that flow offloads at once.
+* Without them the host treats the route as count-unbounded — the pre-0.2.2
+* behaviour, which is why 4.8.0 kept working — but the type contract no longer
+* compiles, so they are declared here with the host's own defaults (50 / 10).
+*
+* `imageOffloadCountQuantum` must be a positive integer no greater than
+* `maxRequestImages`; 10 ≤ 50 keeps the host's default ratio.
+*/
 const REQUEST_IMAGE_BUDGETS = {
 	maxRequestImageBytes: 20971520,
 	requestImagePixelBudget: 4194304,
-	requestImageMaxBytes: 1048576
+	requestImageMaxBytes: 1048576,
+	maxRequestImages: 50,
+	imageOffloadCountQuantum: 10
 };
 function toPiModel(info, baseUrl, providerId, withRate = true) {
 	return {
@@ -12190,6 +12213,64 @@ function apply(ctx, config) {
 		delete registration.cn.directory;
 	};
 	/**
+	* The last catalog announced to the host, per region.
+	*
+	* DSH 0.2.2-rc.1 added `llm/models-updated(provider)`: "a provider's advertised
+	* models or display metadata changed; consumers reload `listModels()`". The
+	* model picker listens for it next to the payload-free `llm/adapters-updated`
+	* — and the latter only fires when a route's TOPOLOGY changes, which is not
+	* the same event as "the models behind an unchanged route changed". The live
+	* directory this plugin refreshes from upstream is exactly the second kind:
+	* the same provider, a different roster.
+	*
+	* The map is the dedupe ledger. Every settings write rebuilds the catalog
+	* object even when the served rows are identical, so an unconditional emit
+	* would make every picker (and every other consumer) re-read the catalog on
+	* each card keystroke.
+	*/
+	const announcedCatalog = /* @__PURE__ */ new Map();
+	/**
+	* What a picker can tell apart about one catalog.
+	*
+	* Must cover every field the host exposes for a model — id, display name,
+	* context window, output cap, input modalities, reasoning tiers, and the
+	* credit multiplier the display name is derived from — or a refresh that
+	* changed only one of them would stay stale in the picker. Order and
+	* omission are both meaningful, so `null` marks an absent key instead of it
+	* collapsing into the empty string.
+	*/
+	function catalogSignature(models) {
+		return models.map((model) => JSON.stringify([
+			model.id,
+			model.name,
+			model.contextWindow ?? null,
+			model.maxTokens ?? null,
+			model.input ?? null,
+			model.reasoningEfforts ?? null,
+			model.creditMultiplier ?? null
+		])).join("\n");
+	}
+	/**
+	* Tell the host that one region's catalog changed, once per change.
+	*
+	* Called from `invalidateAdapter` — the single seam every `catalog.set` path
+	* already ends with (a settings write through `applySelection`, and the
+	* startup discovery) — so a new catalog-set path cannot forget to announce.
+	* A switched-off region advertises nothing: its route is withdrawn and
+	* `syncRegionRegistration` announces that topology change itself, so this
+	* only records the signature.
+	*
+	* Emitting on a host older than 0.2.2 is deliberately harmless: cordis
+	* dispatches events by name and simply has no listener for this one.
+	*/
+	function announceCatalog(panel) {
+		const signature = catalogSignature(stacks[panel].catalog.current());
+		if (announcedCatalog.get(panel) === signature) return;
+		announcedCatalog.set(panel, signature);
+		if (!regionEnabled(current(), panel)) return;
+		ctx.emit("llm/models-updated", providerOfPanel(panel));
+	}
+	/**
 	* Publish each region's on/off state to the harness (issue #11). Both swaps
 	* are single synchronous sections, so no request can observe a half-applied
 	* state, and `replace` announces itself through `llm/adapters-updated`, which
@@ -12355,6 +12436,7 @@ function apply(ctx, config) {
 				});
 				stack.invalidateAdapter = () => {
 					trae.invalidate();
+					announceCatalog(panel);
 				};
 				registration[panel].adapters.push({
 					provider,

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-connect-trae",
   "displayName": "DSH Connect Trae",
   "description": "把本机登录的 Trae 模型接入 DeepSeek Harness：国内版与国际版双供应商并行，提供用量/积分概览与每日签到领取。",
-  "version": "4.8.0",
+  "version": "4.8.1",
   "author": "dingminhua",
   "copyright": "Copyright (c) 2026 LaoDing",
   "license": "MIT",
@@ -100,22 +100,22 @@
     }
   },
   "devDependencies": {
-    "@deepseek-ai/cordis": "^4.0.5",
-    "@deepseek-ai/dsh-atomic-write": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-attachment": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-client-locale": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-client-ui-primitives": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-client-ui-renderer": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-client-ui-settings": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-client-ui-slots": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-home-paths": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-host-webserver": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-llm": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-llm-pi-ai": "0.2.1-rc.5",
-    "@deepseek-ai/dsh-settings": "0.2.1-rc.5",
-    "@deepseek-ai/schemastery": "3.18.5",
-    "@earendil-works/pi-ai": "1.1.0",
+    "@deepseek-ai/cordis": "^4.1.0",
+    "@deepseek-ai/dsh-atomic-write": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-attachment": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-client-locale": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-client-ui-primitives": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-client-ui-renderer": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings-plugins": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-client-ui-slots": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-home-paths": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-host-webserver": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-llm": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-llm-pi-ai": "0.2.2-rc.1",
+    "@deepseek-ai/dsh-settings": "0.2.2-rc.1",
+    "@deepseek-ai/schemastery": "3.19.0",
+    "@earendil-works/pi-ai": "1.3.0",
     "@testing-library/dom": "^10.4.2",
     "@testing-library/react": "^16.3.3",
     "@types/node": "^22.20.0",