@huaweidevtools/aishell-dsh-llm 0.0.15 → 0.0.17

package/lib/index.js

@@ -1,5 +1,5 @@
 import { createCredentialsStore } from "@huaweidevtools/aishell-dsh-credentials-store";
-import { IMAGE_OFFLOAD_REQUIRED_CODE, LlmAdapter, LlmError, contentHasImage, offloadedImageText, projectOffloadedImages, requestImageHandleText, requiredImageOffload, resolveImageAttachmentAccess } from "@deepseek-ai/dsh-llm";
+import { IMAGE_OFFLOAD_REQUIRED_CODE, LlmAdapter, LlmError, contentHasImage, offloadedImageText, projectOffloadedImages, requestImageHandleText, requiredImageOffload, resolveImageAttachmentAccess, resolveRetryPolicy } from "@deepseek-ai/dsh-llm";
 import { requestImageDimensions } from "@deepseek-ai/dsh-attachment";
 import { brandString } from "@deepseek-ai/dsh-brand";
 import { EventSourceParserStream } from "eventsource-parser/stream";
@@ -977,9 +977,10 @@ function requireRequestImage(images, ref) {
 * Replace every offloaded occurrence with its placeholder text.
 *
 * The durable `offloaded` mark is a surface fact shared by all routes; only
-* the placeholder wording is route-owned. Request assembly does not do this
-* for adapters, so an adapter that skips it would send an image whose bytes
-* it deliberately never loaded.
+* the placeholder wording is route-owned. Request assembly leaves this to the
+* adapter, so skipping it would send an image whose bytes this route
+* deliberately never loaded — an empty `image_url` rather than the text that
+* explains where it went.
 *
 * @param messages - complete request history.
 * @param resolveAccess - execution-world path resolver, when one is available.
@@ -1179,20 +1180,34 @@ function contentFor(blocks, images, resolveAccess) {
 * target is for), so the version is the only description of the bytes actually
 * being sent.
 *
-* Encoded through `btoa` over the byte string rather than `Buffer`: this
-* package compiles host and browser halves in one project under `types: []`
-* with the DOM lib, so the Node global is neither declared nor reachable here.
-* `btoa` is a global in both Node 22+ and every browser, which is why it is
-* the one that typechecks in both halves.
+* Encoded through `btoa` over a byte string rather than `Buffer`: this package
+* compiles host and browser halves in one project under `types: []` with the
+* DOM lib, so the Node global is neither declared nor reachable here. `btoa` is
+* a global in both Node 22+ and every browser, which is why it is the one that
+* typechecks in both halves.
+*
+* The byte string is built in chunks. One `String.fromCharCode` per byte is
+* quadratic in the string's length on engines without rope concatenation, and
+* a request image may carry a megabyte; spreading a bounded chunk into the
+* call is linear and stays under the argument-count limit.
 *
 * @param version - prepared request version.
 * @returns a base64 data URL.
 */
 function dataUrl(version) {
-	let binary = "";
-	for (const byte of version.data) binary += String.fromCharCode(byte);
-	return `data:${version.mediaType};base64,${btoa(binary)}`;
+	const bytes = version.data;
+	const chunks = [];
+	for (let start = 0; start < bytes.length; start += BYTE_STRING_CHUNK) chunks.push(String.fromCharCode(...bytes.subarray(start, start + BYTE_STRING_CHUNK)));
+	return `data:${version.mediaType};base64,${btoa(chunks.join(""))}`;
 }
+/**
+* Bytes converted per `String.fromCharCode` call.
+*
+* A power of two below the argument-count ceiling every engine allows (the
+* lowest is 65535), chosen so the spread stays well clear of it rather than at
+* the edge.
+*/
+const BYTE_STRING_CHUNK = 32768;
 /** Type guard for tool-call blocks. */
 function isToolCallBlock(block) {
 	return block.type === "tool-call";
@@ -1390,6 +1405,7 @@ async function* translate(payloads) {
 		...reasoningBlock !== void 0 ? [reasoningBlock] : [],
 		...toolBlocks.values()
 	].sort((a, b) => a.index - b.index);
+	if (allBlocks.length === 0 && (pendingFinish === void 0 || pendingFinish.kind === "stop")) throw new LlmError("aishell-llm: gateway returned a stream with no content", "EMPTY_RESPONSE");
 	for (const block of allBlocks) yield {
 		type: "block-end",
 		index: block.index,
@@ -1427,6 +1443,40 @@ const PROVIDER_DISPLAY_NAME = "AI Shell";
 //#endregion
 //#region src/adapter.ts
 /**
+* Retries after the first attempt.
+*
+* Five, so a request is tried six times at most. Six requests is the point
+* where a rate limit that has not cleared is more likely to be a quota than a
+* burst, and the last delay alone is sixteen seconds.
+*/
+const RETRY_MAX_ATTEMPTS = 5;
+/**
+* First backoff delay. The ladder is this value doubled per attempt — 1, 2, 4,
+* 8, 16 seconds — so the cap below is what fixes the last rung.
+*/
+const RETRY_INITIAL_DELAY_MS = 1e3;
+/** Cap on one delay. Equal to the fifth rung, so the ladder is exact. */
+const RETRY_MAX_DELAY_MS = 16e3;
+/**
+* Failures worth another attempt.
+*
+* Transient by definition: a rate limit asks for a later attempt, a server
+* error and a timeout say nothing about the request, and `EMPTY_RESPONSE` is
+* documented as safe to repeat because the attempt left nothing durable.
+*
+* Absent on purpose: `PROVIDER_ERROR` (a 4xx that is not a rate limit is a
+* statement about the request — a bad model id, a malformed body — and
+* repeating it returns the same answer), and `MISSING_CREDENTIAL` /
+* `INVALID_CREDENTIAL` (a retry cannot conjure a credential).
+*/
+const RETRYABLE_CODES = [
+	"RATE_LIMIT",
+	"SERVER",
+	"TIMEOUT",
+	"TRANSPORT",
+	"EMPTY_RESPONSE"
+];
+/**
 * Whether a gateway error body reports an id the gateway does not carry.
 *
 * Both fields are accepted because the gateway emits them from one definition
@@ -1450,6 +1500,40 @@ function isModelNotFound(text) {
 	return typeof inner === "object" && inner !== null && inner.code === "model_not_found";
 }
 /**
+* Map an HTTP status onto the harness's retryable failure vocabulary.
+*
+* ## Why this matters
+*
+* `resolveRetryPolicy` decides whether to retry from the **error code**, not
+* from the status. An adapter that reports every non-2xx as one undifferentiated
+* code makes the retry policy blind: a 429 and a 401 would look identical, so
+* either every failure retries or none does.
+*
+* ## The mapping
+*
+*   - `429` — `RATE_LIMIT`. The one case where the gateway is explicitly
+*     asking for a later attempt.
+*   - `5xx` — `SERVER`. A transient upstream fault; the same request may
+*     succeed.
+*   - `408` — `TIMEOUT`. The gateway timed out waiting; nothing about the
+*     request is wrong.
+*   - everything else — `PROVIDER_ERROR`. A 4xx that is not a rate limit is a
+*     statement about the request itself (a bad model id, a malformed body, a
+*     rejected credential), and repeating it produces the same answer.
+*
+* `PROVIDER_ERROR` is not in the default retryable set, which is exactly the
+* intent: refusing to retry a request the provider already said was wrong.
+*
+* @param status - the HTTP status of the rejected request.
+* @returns the code to carry on the `LlmError`.
+*/
+function classifyHttpFailure(status) {
+	if (status === 429) return "RATE_LIMIT";
+	if (status === 408) return "TIMEOUT";
+	if (status >= 500 && status <= 599) return "SERVER";
+	return "PROVIDER_ERROR";
+}
+/**
 * Map the gateway's `modalities` array (e.g. `["text","image"]`) to DSH's
 * `ModelModality` vocabulary. DSH currently defines only `'text' | 'image'`;
 * other modalities (audio, video) are dropped — the gateway still accepts
@@ -1477,6 +1561,48 @@ var GatewayAdapter = class GatewayAdapter extends LlmAdapter {
 		};
 	}
 	/**
+	* The retry policy this route runs under.
+	*
+	* ## Why the adapter owns it
+	*
+	* The executor (`@deepseek-ai/dsh-llm-retry`, mounted by `dsh-base`) retries
+	* whatever a provider's policy says to retry, and it reads the policy from
+	* the provider registration. Declaring it here is what lets a 429 on this
+	* gateway be retried without retrying a 401 — the previous code reported
+	* every non-2xx as `PROVIDER_ERROR`, which put nothing in the retryable set
+	* and so retried nothing.
+	*
+	* ## The shape
+	*
+	* Five retries after the first attempt, so six requests at most. Delays are
+	* 1, 2, 4, 8 and 16 seconds: `localDelay` computes
+	* `initialDelayMs * 2 ** (retry - 1)` capped at `maxDelayMs`, so the caps and
+	* the initial delay together spell that exact ladder.
+	*
+	* `jitterRatio: 0` is deliberate. Jitter exists to spread a fleet's retries
+	* off one another; this adapter has one client per user, and the countdown
+	* the chat UI renders is the scheduled delay — jitter would make it disagree
+	* with the number the user is told.
+	*
+	* Eligible codes are the transient ones. `PROVIDER_ERROR` is deliberately
+	* absent: a 4xx that is not a rate limit is a statement about the request,
+	* and repeating it produces the same answer. `EMPTY_RESPONSE` is included
+	* because the harness documents it as safe to repeat — the attempt produced
+	* nothing durable.
+	*/
+	providerRetryPolicy(_provider) {
+		return resolveRetryPolicy({
+			mode: "normal",
+			maxRetries: RETRY_MAX_ATTEMPTS,
+			retryableCodes: [...RETRYABLE_CODES],
+			backoff: {
+				initialDelayMs: RETRY_INITIAL_DELAY_MS,
+				maxDelayMs: RETRY_MAX_DELAY_MS,
+				jitterRatio: 0
+			}
+		}, "aishell-llm: retry policy");
+	}
+	/**
 	* Fetch the raw wire models from `/models`, cached for a short TTL so
 	* `listModels` and `resolveModel` don't each sign a separate request.
 	* Returns `[]` on any failure (missing credentials, network, non-ok) so
@@ -1612,13 +1738,14 @@ var GatewayAdapter = class GatewayAdapter extends LlmAdapter {
 	* way.
 	*
 	* Deliberately the whole image pipeline and nothing else, so `stream` stays
-	* about transport. Ordering matters and mirrors the official adapters:
-	* resolve the attachment service, prepare one request version per retained
-	* image, fail the request if the budget is exceeded (handing
+	* about transport. The ordering is load-bearing and matches the official
+	* adapters: resolve the attachment service, prepare one request version per
+	* retained image, fail the request when the budget is exceeded (handing
 	* `dsh-compaction-image-offload` its decision), and only then project the
-	* offloaded occurrences to placeholder text — a mark set by an earlier
-	* request's offload decision, which serialization must replace rather than
-	* look up bytes for.
+	* offloaded occurrences to placeholder text. That projection has to come
+	* last: an offloaded occurrence is one an earlier request decided not to
+	* send, so serialization replaces it with text rather than looking up bytes
+	* that were deliberately never loaded.
 	*/
 	async buildBody(options) {
 		if (!historyHasImage(options.messages)) return JSON.stringify(serializeRequest(options, void 0, this.imageAccess));
@@ -1642,11 +1769,11 @@ var GatewayAdapter = class GatewayAdapter extends LlmAdapter {
 		} catch (error) {
 			if (options.signal?.aborted) throw error;
 			if (error instanceof LlmError) throw error;
-			throw new LlmError(`aishell-llm: request failed: ${error instanceof Error ? error.message : String(error)}`, "NETWORK_ERROR");
+			throw new LlmError(`aishell-llm: request failed: ${error instanceof Error ? error.message : String(error)}`, "TRANSPORT");
 		}
 		if (!response.ok) {
 			const text = await response.text().catch(() => "");
-			throw new LlmError(`aishell-llm: gateway returned ${response.status}: ${text}` + await this.unsupportedModelHint(text, options), "PROVIDER_ERROR", { status: response.status });
+			throw new LlmError(`aishell-llm: gateway returned ${response.status}: ${text}` + await this.unsupportedModelHint(text, options), classifyHttpFailure(response.status), { status: response.status });
 		}
 		if (!response.body) throw new LlmError("aishell-llm: gateway returned no body", "EMPTY_RESPONSE");
 		yield* translate(parseSse(response.body));

package/lib/types/adapter.d.ts

@@ -1,15 +1,15 @@
 /**
  * aishell LLM gateway adapter for DSH.
  *
- * Routes model calls through the aishell gateway using direct
- * AK/SK signing (SDK-HMAC-SHA256). No intermediate "config fetch" or API-key
- * exchange — every request (chat + model listing) is signed with the user's
- * AK/SK credentials read from the credential store.
+ * Routes model calls through the aishell gateway using direct AK/SK signing
+ * (SDK-HMAC-SHA256). Every request — chat and model listing alike — is signed
+ * with the user's AK/SK read from the credential store, so there is no API-key
+ * exchange and no separate config fetch between the credential and the call.
  *
  * @module @huaweidevtools/aishell-dsh-llm/adapter
  */
 import { LlmAdapter } from '@deepseek-ai/dsh-llm';
-import type { GenerateOptions, LlmModelInfo, LlmProviderInfo, LlmResolvedModelInfo, StreamChunk } from '@deepseek-ai/dsh-llm';
+import type { GenerateOptions, LlmModelInfo, LlmProviderInfo, LlmResolvedModelInfo, ResolvedRetryPolicy, StreamChunk } from '@deepseek-ai/dsh-llm';
 import type { AttachmentStore } from '@deepseek-ai/dsh-attachment';
 import type { CredentialsStore } from '@huaweidevtools/aishell-dsh-credentials-store';
 import { type ImageRequestBudget } from './images.ts';
@@ -18,14 +18,14 @@ export interface GatewayAdapterOptions {
     /**
      * Resolve the current chat API base URL (e.g. `https://openai.aishell.openbuildlab.com/v1`).
      *
-     * A reader, not a value, for the same reason `resolveAttachments` is: this
-     * plugin's whole Config is `Volatile`, so a settings edit is a
-     * volatile-only update. The loader commits such an update into the existing
+     * A reader, not a value, because this plugin's whole Config is `Volatile`: a
+     * settings edit is a volatile-only update that commits into the existing
      * references and returns without re-running `apply()`
-     * (`cordis-plugin-loader/lib/index.js:381-388`), which means the adapter
-     * instance outlives the value it was built with. A captured string would
-     * leave the settings surface showing the new endpoint while requests kept
-     * going to the old one — silently, and for the life of the process.
+     * (`cordis-plugin-loader/lib/index.js:381-388`). The adapter instance
+     * therefore outlives the values it was built with, and a captured string
+     * would leave the settings surface showing the new endpoint while requests
+     * kept going to the endpoint from construction — silently, for the life of
+     * the process.
      */
     readonly resolveBaseUrl: () => string;
     /** Credential store for reading AK/SK. */
@@ -55,6 +55,37 @@ export declare class GatewayAdapter extends LlmAdapter {
     private static readonly MODELS_TTL_MS;
     constructor(opts: GatewayAdapterOptions);
     providerInfo(provider: string): LlmProviderInfo;
+    /**
+     * The retry policy this route runs under.
+     *
+     * ## Why the adapter owns it
+     *
+     * The executor (`@deepseek-ai/dsh-llm-retry`, mounted by `dsh-base`) retries
+     * whatever a provider's policy says to retry, and it reads the policy from
+     * the provider registration. Declaring it here is what lets a 429 on this
+     * gateway be retried without retrying a 401 — the previous code reported
+     * every non-2xx as `PROVIDER_ERROR`, which put nothing in the retryable set
+     * and so retried nothing.
+     *
+     * ## The shape
+     *
+     * Five retries after the first attempt, so six requests at most. Delays are
+     * 1, 2, 4, 8 and 16 seconds: `localDelay` computes
+     * `initialDelayMs * 2 ** (retry - 1)` capped at `maxDelayMs`, so the caps and
+     * the initial delay together spell that exact ladder.
+     *
+     * `jitterRatio: 0` is deliberate. Jitter exists to spread a fleet's retries
+     * off one another; this adapter has one client per user, and the countdown
+     * the chat UI renders is the scheduled delay — jitter would make it disagree
+     * with the number the user is told.
+     *
+     * Eligible codes are the transient ones. `PROVIDER_ERROR` is deliberately
+     * absent: a 4xx that is not a rate limit is a statement about the request,
+     * and repeating it produces the same answer. `EMPTY_RESPONSE` is included
+     * because the harness documents it as safe to repeat — the attempt produced
+     * nothing durable.
+     */
+    providerRetryPolicy(_provider: string): ResolvedRetryPolicy;
     /**
      * Fetch the raw wire models from `/models`, cached for a short TTL so
      * `listModels` and `resolveModel` don't each sign a separate request.
@@ -130,13 +161,14 @@ export declare class GatewayAdapter extends LlmAdapter {
      * way.
      *
      * Deliberately the whole image pipeline and nothing else, so `stream` stays
-     * about transport. Ordering matters and mirrors the official adapters:
-     * resolve the attachment service, prepare one request version per retained
-     * image, fail the request if the budget is exceeded (handing
+     * about transport. The ordering is load-bearing and matches the official
+     * adapters: resolve the attachment service, prepare one request version per
+     * retained image, fail the request when the budget is exceeded (handing
      * `dsh-compaction-image-offload` its decision), and only then project the
-     * offloaded occurrences to placeholder text — a mark set by an earlier
-     * request's offload decision, which serialization must replace rather than
-     * look up bytes for.
+     * offloaded occurrences to placeholder text. That projection has to come
+     * last: an offloaded occurrence is one an earlier request decided not to
+     * send, so serialization replaces it with text rather than looking up bytes
+     * that were deliberately never loaded.
      */
     private buildBody;
     stream(options: GenerateOptions): AsyncIterable<StreamChunk>;

package/lib/types/client/index.d.ts

@@ -3,10 +3,9 @@
  *
  * The page's row for the aishell family is read-only: its profile has no
  * fields the host editor knows how to write, and its credentials are entered
- * through the credential form the `aishell-credentials` chips open. What the
- * row should tell the user is the one fact the old card extension distilled —
- * ready or not — so the browser half paints it as a status dot beside the
- * row's name and hides the header's Edit button (see
+ * through the credential form the `aishell-credentials` chips open. The one
+ * fact the row should carry is readiness, so the browser half paints it as a
+ * status dot beside the row's name and hides the header's Edit button (see
  * `client/provider-row-shadow.ts`).
  *
  * The readiness fact is read from the `aishell-client-credentials` settings

package/lib/types/client/provider-row-shadow.d.ts

@@ -2,23 +2,21 @@
  * Runtime shadow of the aishell provider's Models-page row.
  *
  * The Models page renders each configured provider as a row whose header
- * (`rowHead`) shows the display name followed by an Edit button the aishell
- * family has no use for: the profile has no fields the host editor knows how
- * to write (the old card extension said so itself), and the row's directory
- * entry names no api-key credential, so the host header also paints no status
- * dot. What the user actually needs from this row is the one fact the old
- * card distilled — ready or not — and that reads better beside the name than
- * in a card below the header.
+ * (`rowHead`) shows the display name followed by an Edit button this family
+ * has no use for: the profile has no fields the host editor knows how to
+ * write, and the row's directory entry names no api-key credential, so the
+ * host header paints no status dot either. What the row should carry is the
+ * one fact that matters — ready or not — and it reads better beside the name
+ * than in a card below the header.
  *
  * The header lives in ui-settings-models, digest-protected with no slot for
- * the identity half (the `settings.models.provider-card` seat extends the
- * area BELOW the header, which is exactly the part this family no longer
- * wants). The shadow therefore works the way aishell-brand's host residues
- * do: find the row, patch the DOM. The row is located by its rendered name
- * (the directory entry's displayName, `PROVIDER_DISPLAY_NAME` — a literal
- * both halves share); the class names beside it are CSS-module hashes, so
- * they are matched by the same `[class*="…"]` substring selectors the hero
- * patch already relies on.
+ * the identity half (the `settings.models.provider-card` seat extends the area
+ * BELOW the header, which is exactly the part this family does not want). The
+ * shadow therefore works the way aishell-brand's host residues do: find the
+ * row, patch the DOM. The row is located by its rendered name (the directory
+ * entry's displayName, `PROVIDER_DISPLAY_NAME` — a literal both halves share);
+ * the class names beside it are CSS-module hashes, so they are matched by the
+ * same `[class*="…"]` substring selectors the hero patch already relies on.
  *
  * What the shadow does to a found row:
  *

package/lib/types/images.d.ts

@@ -94,9 +94,10 @@ export declare function requireRequestImage(images: RequestImages, ref: ImageAtt
  * Replace every offloaded occurrence with its placeholder text.
  *
  * The durable `offloaded` mark is a surface fact shared by all routes; only
- * the placeholder wording is route-owned. Request assembly does not do this
- * for adapters, so an adapter that skips it would send an image whose bytes
- * it deliberately never loaded.
+ * the placeholder wording is route-owned. Request assembly leaves this to the
+ * adapter, so skipping it would send an image whose bytes this route
+ * deliberately never loaded — an empty `image_url` rather than the text that
+ * explains where it went.
  *
  * @param messages - complete request history.
  * @param resolveAccess - execution-world path resolver, when one is available.

package/lib/types/index.d.ts

@@ -3,9 +3,9 @@
  *
  * Registers the `aishell` provider route on `ctx.llm`, routing model calls
  * through the aishell gateway. Every request is signed directly with the
- * user's AK/SK (SDK-HMAC-SHA256) — no intermediate API-key exchange. AK/SK
- * are read from the credential store (OS keyring with memory fallback) via
- * `createCredentialsStore`.
+ * user's AK/SK (SDK-HMAC-SHA256), read from the credential store (OS keyring
+ * with memory fallback) via `createCredentialsStore` — there is no API-key
+ * exchange between the credential and the call.
  *
  * Credential management (settings namespace + watch → store transfer) lives
  * in `aishell-credentials`; this plugin only consumes the stored credentials.
@@ -14,8 +14,8 @@
  * directory (`registerConfigurableProviders`), which is what the Models page
  * joins with live routes — and it carries a Config schema, without which the
  * settings mirror (and therefore the Models row) never lists this namespace.
- * The row itself carries no card: the browser half replaces the page's
- * Edit-card extension with a status dot beside the row's name (see
+ * The row has no card of its own: the browser half paints a status dot beside
+ * the row's name and hides the Edit button, which has nothing to edit (see
  * `client/provider-row-shadow.ts`).
  *
  * @module @huaweidevtools/aishell-dsh-llm

package/lib/types/serialize.d.ts

@@ -1,11 +1,11 @@
 /**
  * Serialize harness {@link GenerateOptions} into an OpenAI-compatible wire request.
  *
- * Messages without images serialize to a plain string, exactly as before image
- * support existed. A message carrying an image serializes to an ordered part
- * list instead — a handle-text part naming the image, then the image itself as
- * a base64 data URL — which is the only shape an OpenAI-compatible endpoint
- * accepts image input in.
+ * A message without an image serializes to a plain string — the shape every
+ * OpenAI-compatible endpoint accepts for text. A message carrying one
+ * serializes to an ordered part list instead: a handle-text part naming the
+ * image, then the image itself as a base64 data URL, which is the only shape
+ * those endpoints accept image input in.
  *
  * Image bytes are not read here. The harness hands over durable references,
  * not bytes, so `prepareRequestImages` resolves them one step ahead of this

package/lib/types/translate.d.ts

@@ -2,8 +2,12 @@
  * Translate OpenAI-compatible SSE payloads into harness {@link StreamChunk}s.
  *
  * One stateful block per content, reasoning, or tool-call index. Finish reason
- * and usage are deferred until `[DONE]`, covering both finish-attached and
- * trailing usage-only shapes.
+ * and usage are deferred until `[DONE]`, which covers both shapes a
+ * compatible endpoint produces: usage attached to the finish chunk, and usage
+ * in a trailing chunk of its own.
+ *
+ * A stream that settles without producing any block is a failure rather than
+ * an empty turn — see the note on the check before the blocks close.
  *
  * @module @huaweidevtools/aishell-dsh-llm/translate
  */

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@huaweidevtools/aishell-dsh-llm",
   "description": "aishell LLM gateway adapter for DSH — OpenAI-compatible, Huawei Cloud AK/SK auth via credential store",
-  "version": "0.0.15",
+  "version": "0.0.17",
   "publishConfig": {
     "access": "public"
   },
@@ -33,7 +33,7 @@
   "license": "Apache-2.0",
   "dependencies": {
     "eventsource-parser": "^3.0.0",
-    "@huaweidevtools/aishell-dsh-credentials-store": "0.0.15"
+    "@huaweidevtools/aishell-dsh-credentials-store": "0.0.17"
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.4",