dsh-connect-trae 3.4.1 → 3.4.3

package/lib/index.d.ts

@@ -1,6 +1,7 @@
 import z from "@deepseek-ai/schemastery";
+import { Context, ProviderStreams } from "@earendil-works/pi-ai";
 import { PiAiAdapter } from "@deepseek-ai/dsh-llm-pi-ai";
-import { Context } from "@deepseek-ai/cordis";
+import { Context as Context$1 } from "@deepseek-ai/cordis";
 import { AttachmentStore } from "@deepseek-ai/dsh-attachment";
 //#region src/reasoning.d.ts
 declare const TRAE_REASONING_EFFORTS: readonly ["minimal", "low", "medium", "high", "xhigh"];
@@ -295,6 +296,113 @@ declare class TraeCatalog {
   set(models: readonly TraeModelInfo[]): void;
 }
 //#endregion
+//#region src/pi-ai-runtime.d.ts
+/**
+ * Which `@earendil-works/pi-ai` copy THIS plugin resolves at runtime, and which
+ * context shape that copy consumes (issue #27).
+ *
+ * WHY THIS EXISTS. The plugin declares pi-ai as a peer, so the module it
+ * imports is whatever the install provides — and the two generations consume
+ * DIFFERENT context shapes:
+ *
+ * - **modern** (0.86+): every public entry point calls `normalizeContext()`
+ *   once, so what reaches a provider is a normalized *transcript*:
+ *   `{ messages: [ { role: 'system', content, toolsAdded }, … ] }`. The system
+ *   prompt and the tool declarations live ONLY on that leading system message;
+ *   the top-level `systemPrompt` / `tools` fields are gone, and the api never
+ *   reads them back.
+ * - **legacy** (≤0.85): expects `{ systemPrompt, tools, messages }` and has no
+ *   branch for a `system` message inside `messages` at all. Its token estimator
+ *   crashes on one — `estimateMessageTokens` iterates the string `content`
+ *   character by character and reads `.name` off a character — and its wire
+ *   converter silently drops it.
+ *
+ * The mismatch is reachable in BOTH directions, because DSH itself spans both
+ * generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 declares `^0.85.1`; 0.2.0-rc.2 and
+ * later declare `^0.87.1`, 0.2.1-alpha.2 declares `^1.0.2`), while this plugin
+ * accepts the whole range (`>=0.1.7-rc.1 <0.3.0-0`). Whichever side is newer,
+ * the other one is wrong:
+ *
+ * | host | resolved api | outcome |
+ * |---|---|---|
+ * | legacy | legacy | fine |
+ * | legacy | modern | no crash, but prompt + tools silently LOST |
+ * | modern | legacy | CRASH: `Cannot read properties of undefined (reading 'length')` |
+ * | modern | modern | fine |
+ *
+ * THE BOUNDARY IS 0.86, NOT 0.87. Checked against the published tarballs:
+ * `dist/utils/transcript.js` — and with it `normalizeContext`, the
+ * `role === 'system'` estimator branch, and the switch away from reading
+ * `systemPrompt`/`tools` — first appears in **0.86.0**. A `>= 0.87` gate
+ * misclassifies 0.86.x as legacy and folds a context the modern api consumes
+ * natively, which deletes the only carrier of the prompt and the tools.
+ *
+ * HOW the generation is decided, in order:
+ *
+ * 1. **The manifest version** of the copy this plugin resolved. Numeric semver
+ *    comparison (`minor >= 86`), so `0.86.0` and the already-shipped `1.x` line
+ *    both land on modern, and `0.9.0` correctly sorts below `0.86.0`.
+ * 2. **The package's own layout**, when no version could be read: the transcript
+ *    module sits at `dist/utils/transcript.js` (the exports map's
+ *    `"./utils/*" → "./dist/utils/*.js"` convention is identical in every
+ *    published generation, 0.82 through 1.x).
+ *
+ * Both checks are deliberately resolver-independent. `import.meta.resolve()` is
+ * NOT used to answer this question: bundler-style resolvers (vite, and equally
+ * `vitest` under it) expand the `"./utils/*"` wildcard to a path and return it
+ * WITHOUT checking that the file exists, so a probe built on it answers "modern"
+ * for 0.85.1 — the exact false positive that would leave issue #27 unfixed while
+ * claiming to be capability-based. Reading the package directory cannot be
+ * fooled that way.
+ *
+ * The version is therefore the primary signal, and it also keeps the gate
+ * forward-compatible for free: a future 2.x needs no change here, whereas a
+ * file-name check alone would have to know about it.
+ *
+ * @module dsh-connect-trae/pi-ai-runtime
+ */
+/** The context generation a resolved pi-ai api module speaks. */
+type PiAiGeneration = 'legacy' | 'modern';
+/** What {@link piAiRuntimeInfo} reports about the resolved pi-ai copy. */
+interface PiAiRuntimeInfo {
+  /** `modern` (0.86+: consumes normalized transcripts) or `legacy` (≤0.85 shape). */
+  generation: PiAiGeneration;
+  /** Version of the resolved copy, when the manifest could be read. */
+  version: string | undefined;
+  /** Package directory of the resolved copy, when it could be located. */
+  resolvedFrom: string | undefined;
+  /**
+   * Whether the copy could be inspected at all. `false` means pi-ai does not
+   * resolve from this plugin — the normal state of a market install probed
+   * OUTSIDE the DSH host, where the host supplies the module at plugin runtime.
+   * Inside DSH the copy is always inspectable: a nested one shadows host
+   * injection, and without a nested one the host supplies its own.
+   */
+  inspected: boolean;
+}
+/** Resolve (once) which pi-ai copy this plugin runs against. */
+declare function piAiRuntimeInfo(): PiAiRuntimeInfo;
+/**
+ * The generation decision table, exported so every branch is pinned by tests
+ * rather than by a comment here — including the two this development tree can
+ * never reach (no local copy, and a copy with no readable version), which are
+ * exactly the states a market install founds its gate on.
+ *
+ * @param version - manifest version of the resolved copy, if readable.
+ * @param transcriptPresent - whether that copy actually ships
+ *   `dist/utils/transcript.js`; `undefined` when nothing was inspected.
+ */
+declare function decidePiAiGeneration(version: string | undefined, transcriptPresent: boolean | undefined): PiAiGeneration;
+/**
+ * The generation a version string belongs to, or `undefined` when the string
+ * cannot be read as a version at all.
+ *
+ * Only the minor of the `0.x` line matters for the boundary, and `major >= 1`
+ * is modern by definition (1.0.x is already in use by `dsh-llm-pi-ai@0.2.1-alpha.2`
+ * and consumes transcripts natively).
+ */
+declare function generationOf(version: string | undefined): PiAiGeneration | undefined;
+//#endregion
 //#region src/upstream.d.ts
 type TraeUpstreamErrorKind = 'authentication' | 'hard_credit' | 'soft_rate' | 'not_found' | 'server' | 'client' | 'unconfigured';
 type TraeChatResult = {
@@ -351,6 +459,67 @@ declare const TRAE_PROVIDER_DISPLAY_NAMES: Readonly<Record<TraeRegion, string>>;
 /** Region a provider route id belongs to. */
 declare function regionOfTraeProvider(provider: string): TraeRegion | undefined;
 declare const TRAE_STREAM_IDLE_TIMEOUT_MS = 300000;
+/**
+ * Fold a NORMALIZED transcript back into the `{ systemPrompt, tools, messages }`
+ * shape a LEGACY (≤0.85) api consumes — issue #27's crash and its two silent
+ * siblings.
+ *
+ * WHY (issue #27). 0.86+ normalizes at every public entry point, and DSH's host
+ * calls `Models.streamSimple()`, so on a modern host the context arriving here
+ * ALWAYS carries its prompt and its tool declarations on a leading system
+ * message — the top-level fields are gone. A legacy api has no branch for that
+ * message: `estimateMessageTokens` iterates the string `content` character by
+ * character and reads `.name` off a character, throwing
+ * `Cannot read properties of undefined (reading 'length')` before the request
+ * is even built. That is what surfaced as `PI_AI_ERROR` with all-zero usage.
+ *
+ * The fold must carry MORE than the prompt. `toolsAdded` is the ONLY remaining
+ * carrier of the tool declarations once `normalizeContext` has run, and a
+ * legacy api reads tools exclusively from `context.tools` — so lifting the text
+ * alone would trade a loud crash for a silent one: a model that can never emit
+ * a `toolCall` because the request declared no tools.
+ *
+ * Shape-guarded, not version-guarded: it asks "is there a system message inside
+ * `messages`?" rather than "which pi-ai is loaded?". A version test would be
+ * wrong the moment either side moves, and this predicate is an identity for the
+ * legacy shape, so the ordinary path stays byte-for-byte untouched. WHICH
+ * branch runs at all IS generation-gated — see {@link withContextAdaptation}.
+ *
+ * Returns the SAME object when there is nothing to fold, so a legacy host
+ * (which never normalizes) pays one `Array.some` and nothing else.
+ */
+declare function adaptLegacyPiAiContext(context: Context): Context;
+/**
+ * Lift the legacy `{ systemPrompt, tools, messages }` shape into the normalized
+ * transcript a MODERN (0.86+) api consumes — the reverse mismatch, and just as
+ * silent.
+ *
+ * WHY. DSH spans both generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 pins `^0.85.1`)
+ * while this plugin may resolve a newer copy than its host. A LEGACY host never
+ * normalizes, so it hands the api the legacy shape; a modern api reads the
+ * prompt from a leading system message and the tools from its `toolsAdded`, and
+ * never looks at the top-level fields — so both are dropped without a sound.
+ * Verified against the published tarballs: the request that reaches the wire
+ * carries no system turn and `tools: []`.
+ *
+ * Identity for anything already in transcript shape, and for a context with
+ * neither a prompt nor tools (pi-ai's own `createInitialSystemMessage` returns
+ * `undefined` there, keeping an empty transcript empty).
+ */
+declare function adaptModernPiAiContext(context: Context): Context;
+/**
+ * Wrap one pi-ai API module so BOTH stream entry points receive a context its
+ * own generation can consume.
+ *
+ * The gate is the copy THIS plugin resolved (see {@link piAiRuntimeInfo}) —
+ * what the host runs says nothing about it, because a nested copy on disk
+ * shadows host injection and vice versa. The wrapping is cheap and lazy: only
+ * `stream`/`streamSimple` are intercepted, the deferred-fetch entry points take
+ * no context and are passed through untouched, and each adapter function is an
+ * identity unless the context is actually the other generation's shape. So a
+ * healthy install does one `Array.some` per request.
+ */
+declare function withContextAdaptation(api: ProviderStreams, generation: PiAiGeneration): ProviderStreams;
 interface TraeAdapterOptions {
   shim: TraeShim;
   catalog: TraeCatalog;
@@ -359,6 +528,12 @@ interface TraeAdapterOptions {
   /** pi-ai provider name and profile display name; defaults to the CN name. */
   displayName?: string;
   resolveAttachments?: () => AttachmentStore | undefined;
+  /**
+   * Override the resolved pi-ai generation (see {@link withContextAdaptation});
+   * tests use it to exercise the combination this machine does not have
+   * installed.
+   */
+  piAiGeneration?: PiAiGeneration;
 }
 interface TraeAdapter {
   adapter: PiAiAdapter;
@@ -2116,7 +2291,7 @@ interface TraeUsageRouteOptions {
  */
 declare function traeWebUsage(deps: TraeUsageRouteOptions, region: TraeRegion): Promise<TraeWebUsage>;
 /** Mount the GET usage route on an optional webServer context. */
-declare function registerTraeUsageRoute(ctx: Context, deps: TraeUsageRouteOptions): void;
+declare function registerTraeUsageRoute(ctx: Context$1, deps: TraeUsageRouteOptions): void;
 //#endregion
 //#region src/model-probe.d.ts
 /** How one model answered. */
@@ -2333,6 +2508,6 @@ declare function regionEnabled(config: Config, region: TraeRegion): boolean;
  */
 declare function asVolatile<S>(schema: S): S;
 declare const Config: z<Config>;
-declare function apply(ctx: Context, config: Config): void;
+declare function apply(ctx: Context$1, config: Config): void;
 //#endregion
-export { Config, FALLBACK_TRAE_MODELS, FALLBACK_TRAE_MODELS_AI, REGION_GATEWAYS, type RawChatDelta, type RawChatMessage, type RawChatTool, SseDecoder, type SseEvent, TRAE_ACCOUNT_STATUS_PATH, TRAE_AI_PROVIDER, TRAE_CHECKIN_PATH, TRAE_CN_AGENT_TASK_PATH, TRAE_CN_TITLE_PATH, TRAE_MODELS_TEST_PATH, TRAE_MODEL_DETAIL_FUNCTIONS, TRAE_MODEL_DETAIL_PATH, TRAE_PAY_BASE, TRAE_PROBE_TIMEOUT_MS, TRAE_PROVIDER, TRAE_PROVIDERS, TRAE_PROVIDER_DISPLAY_NAMES, TRAE_RAW_CHAT_V1_PATH, TRAE_RAW_CHAT_V2_PATH, TRAE_REASONING_EFFORTS, TRAE_REGIONS, TRAE_REGION_PARAM, TRAE_SETTINGS_NS, TRAE_SOLO_CHAT_PATH, TRAE_SOLO_FUNCTION, TRAE_SOLO_MODELS_PATH, TRAE_SOLO_REMOTE_BASE, TRAE_STATE_DB_FILENAME, TRAE_STREAM_IDLE_TIMEOUT_MS, TRAE_USAGE_PATH, TRAE_VERSION_CODE_FALLBACK, type TraeActivityRule, type TraeAdapter, type TraeCachedModelConfig, TraeCatalog, type TraeChatResult, type TraeCheckinClaim, type TraeCheckinStatus, type TraeContextBudget, type TraeCredential, TraeCredentialStore, TraeDelegatingUpstreamClient, type TraeDiscoveredModel, type TraeDiscoveredReasoning, type TraeEdition, TraeFallbackUpstreamClient, type TraeFallbackUpstreamOptions, type TraeFusionRawChatEnvelope, TraeGatedUpstreamClient, type TraeGatedUpstreamOptions, type TraeIdentity, type TraeInputModality, type TraeModelDetailRequest, type TraeModelInfo, type TraeModelProbeVerdict, type TraeModelsTestResponse, type TraeObservedModelConfig, type TraeProbeResult, type TraeProbeVerdict, TraeRawCapabilityController, type TraeRawCapabilityControllerOptions, type TraeRawCapabilitySnapshot, TraeRawCapabilityState, type TraeRawChatBehaviorConfig, type TraeRawChatCapability, type TraeRawChatClientOptions, type TraeRawChatConfig, type TraeRawChatFailureReason, type TraeRawChatRuntimeConfig, TraeRawChatUpstreamClient, type TraeRawDiagnostic, type TraeRawDiagnosticState, type TraeRawGateway, type TraeRawGatewayOptions, type TraeRawResolverResult, type TraeReasoningCapability, type TraeReasoningEffort, type TraeRefreshDevice, type TraeRegion, type TraeRegionGateways, TraeRegionState, type TraeShim, TraeSoloBridge, type TraeSoloClientOptions, TraeSoloRemoteCatalogClient, type TraeSoloRemoteCatalogOptions, TraeSoloUpstreamClient, type TraeStorageCandidate, type TraeStreamEvent, type TraeUpstreamClient, TraeUsageClient, type TraeUsageOptions, type TraeUsagePack, type TraeUsageRouteOptions, type TraeUsageSnapshot, type TraeUsageSummary, type TraeUsageView, type TraeWebAccountState, type TraeWebActivity, type TraeWebAppLogin, type TraeWebCheckin, type TraeWebCheckinClaim, type TraeWebCredits, type TraeWebUsage, type TraeWireModel, UnconfiguredTraeUpstreamClient, apply, applyContextBudgets, applyImageSelection, applyReasoningEffort, asVolatile, bridgeTraeSoloStream, buildTraeAgentTaskBody, buildTraeCnHeaders, buildTraeFusionRawChatEnvelope, buildTraeModelDetailRequest, buildTraeRawChatDraft, buildTraeRawChatRuntimeConfig, classifyProbeError, classifyProbeResult, classifyTraeRawChatFailure, configuredAccountsOf, createTraeAdapter, createTraeRawGateway, createTraeShim, decodeRawChatChunk, decodeTraeEvent, decryptTraeStorageValue, deriveCatalog, describeIdShape, describeNameShape, discoveredCatalog, fallbackModelsFor, followAppLoginEnabled, hashTraeRawChatArg, identityHeaders, inject, legacyTraeOwnAuthPath, maskUserPath, mergeTraeModelSources, name, nextRegionEnabled, nextRegionSlots, normalizeTraeCredential, normalizeTraeVersionCode, parseObservedModelConfig, parseReasoningCapability, parseTraeAuthValue, parseTraeCachedModel, parseTraeModelExtraConfigLogLine, parseTraeRawChatBehaviorConfig, parseTraeRemoteModel, parseTraeStorageDocument, pickTraeStorageIdentity, prepareSoloBody, probeBody, probeModelsSequentially, probeOneModel, probeTraeRawChatCapability, rawCapabilityDiagnostic, rawCapabilityFingerprint, readTraeCachedModel, readTraeCliIdentity, readTraeIdentity, refreshTraeCredential, regionEnabled, regionEnabledOf, regionOfCredential, regionOfEdition, regionOfHost, regionOfTraeProvider, regionOfTraeStatusUrl, regionOfUserRegion, regionStateOf, registerTraeUsageRoute, resolveTraeIdentity, resolveTraeRawRuntime, sanitizeCatalog, settingsNamespaceOf, traeEndpoint, traeInputModalities, traeModelDisplayName, traeOwnAuthPath, traeRawChatExtraInfo, traeStateDatabaseCandidates, traeStorageCandidates, traeWebUsage, traeWindowsAppNames, unwrapVolatile, unwrapVolatileDeep, withTraeRegion };
+export { Config, FALLBACK_TRAE_MODELS, FALLBACK_TRAE_MODELS_AI, type PiAiGeneration, type PiAiRuntimeInfo, REGION_GATEWAYS, type RawChatDelta, type RawChatMessage, type RawChatTool, SseDecoder, type SseEvent, TRAE_ACCOUNT_STATUS_PATH, TRAE_AI_PROVIDER, TRAE_CHECKIN_PATH, TRAE_CN_AGENT_TASK_PATH, TRAE_CN_TITLE_PATH, TRAE_MODELS_TEST_PATH, TRAE_MODEL_DETAIL_FUNCTIONS, TRAE_MODEL_DETAIL_PATH, TRAE_PAY_BASE, TRAE_PROBE_TIMEOUT_MS, TRAE_PROVIDER, TRAE_PROVIDERS, TRAE_PROVIDER_DISPLAY_NAMES, TRAE_RAW_CHAT_V1_PATH, TRAE_RAW_CHAT_V2_PATH, TRAE_REASONING_EFFORTS, TRAE_REGIONS, TRAE_REGION_PARAM, TRAE_SETTINGS_NS, TRAE_SOLO_CHAT_PATH, TRAE_SOLO_FUNCTION, TRAE_SOLO_MODELS_PATH, TRAE_SOLO_REMOTE_BASE, TRAE_STATE_DB_FILENAME, TRAE_STREAM_IDLE_TIMEOUT_MS, TRAE_USAGE_PATH, TRAE_VERSION_CODE_FALLBACK, type TraeActivityRule, type TraeAdapter, type TraeCachedModelConfig, TraeCatalog, type TraeChatResult, type TraeCheckinClaim, type TraeCheckinStatus, type TraeContextBudget, type TraeCredential, TraeCredentialStore, TraeDelegatingUpstreamClient, type TraeDiscoveredModel, type TraeDiscoveredReasoning, type TraeEdition, TraeFallbackUpstreamClient, type TraeFallbackUpstreamOptions, type TraeFusionRawChatEnvelope, TraeGatedUpstreamClient, type TraeGatedUpstreamOptions, type TraeIdentity, type TraeInputModality, type TraeModelDetailRequest, type TraeModelInfo, type TraeModelProbeVerdict, type TraeModelsTestResponse, type TraeObservedModelConfig, type TraeProbeResult, type TraeProbeVerdict, TraeRawCapabilityController, type TraeRawCapabilityControllerOptions, type TraeRawCapabilitySnapshot, TraeRawCapabilityState, type TraeRawChatBehaviorConfig, type TraeRawChatCapability, type TraeRawChatClientOptions, type TraeRawChatConfig, type TraeRawChatFailureReason, type TraeRawChatRuntimeConfig, TraeRawChatUpstreamClient, type TraeRawDiagnostic, type TraeRawDiagnosticState, type TraeRawGateway, type TraeRawGatewayOptions, type TraeRawResolverResult, type TraeReasoningCapability, type TraeReasoningEffort, type TraeRefreshDevice, type TraeRegion, type TraeRegionGateways, TraeRegionState, type TraeShim, TraeSoloBridge, type TraeSoloClientOptions, TraeSoloRemoteCatalogClient, type TraeSoloRemoteCatalogOptions, TraeSoloUpstreamClient, type TraeStorageCandidate, type TraeStreamEvent, type TraeUpstreamClient, TraeUsageClient, type TraeUsageOptions, type TraeUsagePack, type TraeUsageRouteOptions, type TraeUsageSnapshot, type TraeUsageSummary, type TraeUsageView, type TraeWebAccountState, type TraeWebActivity, type TraeWebAppLogin, type TraeWebCheckin, type TraeWebCheckinClaim, type TraeWebCredits, type TraeWebUsage, type TraeWireModel, UnconfiguredTraeUpstreamClient, adaptLegacyPiAiContext, adaptModernPiAiContext, apply, applyContextBudgets, applyImageSelection, applyReasoningEffort, asVolatile, bridgeTraeSoloStream, buildTraeAgentTaskBody, buildTraeCnHeaders, buildTraeFusionRawChatEnvelope, buildTraeModelDetailRequest, buildTraeRawChatDraft, buildTraeRawChatRuntimeConfig, classifyProbeError, classifyProbeResult, classifyTraeRawChatFailure, configuredAccountsOf, createTraeAdapter, createTraeRawGateway, createTraeShim, decidePiAiGeneration, decodeRawChatChunk, decodeTraeEvent, decryptTraeStorageValue, deriveCatalog, describeIdShape, describeNameShape, discoveredCatalog, fallbackModelsFor, followAppLoginEnabled, generationOf, hashTraeRawChatArg, identityHeaders, inject, legacyTraeOwnAuthPath, maskUserPath, mergeTraeModelSources, name, nextRegionEnabled, nextRegionSlots, normalizeTraeCredential, normalizeTraeVersionCode, parseObservedModelConfig, parseReasoningCapability, parseTraeAuthValue, parseTraeCachedModel, parseTraeModelExtraConfigLogLine, parseTraeRawChatBehaviorConfig, parseTraeRemoteModel, parseTraeStorageDocument, piAiRuntimeInfo, pickTraeStorageIdentity, prepareSoloBody, probeBody, probeModelsSequentially, probeOneModel, probeTraeRawChatCapability, rawCapabilityDiagnostic, rawCapabilityFingerprint, readTraeCachedModel, readTraeCliIdentity, readTraeIdentity, refreshTraeCredential, regionEnabled, regionEnabledOf, regionOfCredential, regionOfEdition, regionOfHost, regionOfTraeProvider, regionOfTraeStatusUrl, regionOfUserRegion, regionStateOf, registerTraeUsageRoute, resolveTraeIdentity, resolveTraeRawRuntime, sanitizeCatalog, settingsNamespaceOf, traeEndpoint, traeInputModalities, traeModelDisplayName, traeOwnAuthPath, traeRawChatExtraInfo, traeStateDatabaseCandidates, traeStorageCandidates, traeWebUsage, traeWindowsAppNames, unwrapVolatile, unwrapVolatileDeep, withContextAdaptation, withTraeRegion };

package/lib/index.js

@@ -3,9 +3,11 @@ import { createProvider } from "@earendil-works/pi-ai";
 import { openAICompletionsApi } from "@earendil-works/pi-ai/api/openai-completions.lazy";
 import { resolveRetryPolicy } from "@deepseek-ai/dsh-llm";
 import { PiAiAdapter } from "@deepseek-ai/dsh-llm-pi-ai";
+import { existsSync, readFileSync } from "node:fs";
+import { dirname, join } from "node:path";
+import { fileURLToPath } from "node:url";
 import { readFile, rm, stat } from "node:fs/promises";
 import { createDecipheriv, createHash, randomBytes, randomUUID, sign, timingSafeEqual } from "node:crypto";
-import { dirname, join } from "node:path";
 import { withFileLock, writeFileAtomic } from "@deepseek-ai/dsh-atomic-write";
 import { resolveDshHome } from "@deepseek-ai/dsh-home-paths";
 import { cpus, homedir, hostname, release, userInfo } from "node:os";
@@ -13,7 +15,6 @@ import { createServer } from "node:http";
 import { Readable } from "node:stream";
 import { execFile } from "node:child_process";
 import { promisify } from "node:util";
-import { existsSync } from "node:fs";
 //#region src/catalog.ts
 /**
 * Bootstrap catalog: identity only where current Trae metadata has not been
@@ -322,6 +323,179 @@ var TraeCatalog = class {
 	}
 };
 //#endregion
+//#region src/pi-ai-runtime.ts
+/**
+* Which `@earendil-works/pi-ai` copy THIS plugin resolves at runtime, and which
+* context shape that copy consumes (issue #27).
+*
+* WHY THIS EXISTS. The plugin declares pi-ai as a peer, so the module it
+* imports is whatever the install provides — and the two generations consume
+* DIFFERENT context shapes:
+*
+* - **modern** (0.86+): every public entry point calls `normalizeContext()`
+*   once, so what reaches a provider is a normalized *transcript*:
+*   `{ messages: [ { role: 'system', content, toolsAdded }, … ] }`. The system
+*   prompt and the tool declarations live ONLY on that leading system message;
+*   the top-level `systemPrompt` / `tools` fields are gone, and the api never
+*   reads them back.
+* - **legacy** (≤0.85): expects `{ systemPrompt, tools, messages }` and has no
+*   branch for a `system` message inside `messages` at all. Its token estimator
+*   crashes on one — `estimateMessageTokens` iterates the string `content`
+*   character by character and reads `.name` off a character — and its wire
+*   converter silently drops it.
+*
+* The mismatch is reachable in BOTH directions, because DSH itself spans both
+* generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 declares `^0.85.1`; 0.2.0-rc.2 and
+* later declare `^0.87.1`, 0.2.1-alpha.2 declares `^1.0.2`), while this plugin
+* accepts the whole range (`>=0.1.7-rc.1 <0.3.0-0`). Whichever side is newer,
+* the other one is wrong:
+*
+* | host | resolved api | outcome |
+* |---|---|---|
+* | legacy | legacy | fine |
+* | legacy | modern | no crash, but prompt + tools silently LOST |
+* | modern | legacy | CRASH: `Cannot read properties of undefined (reading 'length')` |
+* | modern | modern | fine |
+*
+* THE BOUNDARY IS 0.86, NOT 0.87. Checked against the published tarballs:
+* `dist/utils/transcript.js` — and with it `normalizeContext`, the
+* `role === 'system'` estimator branch, and the switch away from reading
+* `systemPrompt`/`tools` — first appears in **0.86.0**. A `>= 0.87` gate
+* misclassifies 0.86.x as legacy and folds a context the modern api consumes
+* natively, which deletes the only carrier of the prompt and the tools.
+*
+* HOW the generation is decided, in order:
+*
+* 1. **The manifest version** of the copy this plugin resolved. Numeric semver
+*    comparison (`minor >= 86`), so `0.86.0` and the already-shipped `1.x` line
+*    both land on modern, and `0.9.0` correctly sorts below `0.86.0`.
+* 2. **The package's own layout**, when no version could be read: the transcript
+*    module sits at `dist/utils/transcript.js` (the exports map's
+*    `"./utils/*" → "./dist/utils/*.js"` convention is identical in every
+*    published generation, 0.82 through 1.x).
+*
+* Both checks are deliberately resolver-independent. `import.meta.resolve()` is
+* NOT used to answer this question: bundler-style resolvers (vite, and equally
+* `vitest` under it) expand the `"./utils/*"` wildcard to a path and return it
+* WITHOUT checking that the file exists, so a probe built on it answers "modern"
+* for 0.85.1 — the exact false positive that would leave issue #27 unfixed while
+* claiming to be capability-based. Reading the package directory cannot be
+* fooled that way.
+*
+* The version is therefore the primary signal, and it also keeps the gate
+* forward-compatible for free: a future 2.x needs no change here, whereas a
+* file-name check alone would have to know about it.
+*
+* @module dsh-connect-trae/pi-ai-runtime
+*/
+let cached;
+/** Resolve (once) which pi-ai copy this plugin runs against. */
+function piAiRuntimeInfo() {
+	cached ??= inspectResolvedPiAi();
+	return cached;
+}
+function inspectResolvedPiAi() {
+	const entry = resolveModuleFile();
+	const root = entry === void 0 ? void 0 : findPackageRoot(entry);
+	const version = root === void 0 ? void 0 : readVersion(root);
+	return {
+		generation: decidePiAiGeneration(version, root === void 0 ? void 0 : hasTranscriptModule(root)),
+		version,
+		resolvedFrom: root,
+		inspected: root !== void 0
+	};
+}
+/**
+* The generation decision table, exported so every branch is pinned by tests
+* rather than by a comment here — including the two this development tree can
+* never reach (no local copy, and a copy with no readable version), which are
+* exactly the states a market install founds its gate on.
+*
+* @param version - manifest version of the resolved copy, if readable.
+* @param transcriptPresent - whether that copy actually ships
+*   `dist/utils/transcript.js`; `undefined` when nothing was inspected.
+*/
+function decidePiAiGeneration(version, transcriptPresent) {
+	const byVersion = generationOf(version);
+	if (byVersion !== void 0) return byVersion;
+	if (transcriptPresent === true) return "modern";
+	if (transcriptPresent === false) return "legacy";
+	return "modern";
+}
+/**
+* The generation a version string belongs to, or `undefined` when the string
+* cannot be read as a version at all.
+*
+* Only the minor of the `0.x` line matters for the boundary, and `major >= 1`
+* is modern by definition (1.0.x is already in use by `dsh-llm-pi-ai@0.2.1-alpha.2`
+* and consumes transcripts natively).
+*/
+function generationOf(version) {
+	if (version === void 0) return void 0;
+	const match = /^(\d+)\.(\d+)\./u.exec(version);
+	if (match === null) return void 0;
+	const major = Number(match[1]);
+	const minor = Number(match[2]);
+	if (major > 0) return "modern";
+	return minor >= 86 ? "modern" : "legacy";
+}
+/**
+* Whether the resolved package actually contains the transcript module.
+*
+* `dist/utils/transcript.js` is the file every modern generation ships and no
+* legacy one has (checked: absent in 0.82.1 and 0.85.1; present in 0.86.0,
+* 0.86.1, 0.87.1 and 1.0.2). Landing on the file directly, rather than asking a
+* resolver to find it, is what keeps this honest under bundler-style resolution
+* — see the module docstring.
+*/
+function hasTranscriptModule(packageRoot) {
+	return existsSync(join(packageRoot, "dist", "utils", "transcript.js"));
+}
+/**
+* The file the main entry resolved to; undefined when resolution itself fails.
+*
+* `import.meta.resolve` (not `require.resolve`): pi-ai's exports map exposes
+* "." under the `import` condition only, so the CJS resolver refuses the bare
+* specifier outright — the ESM resolver is the one this plugin actually imports
+* with, so it is also the one whose answer is meaningful here. Only the package
+* LOCATION is taken from it; the generation question is answered from disk.
+*/
+function resolveModuleFile() {
+	try {
+		return fileURLToPath(import.meta.resolve("@earendil-works/pi-ai"));
+	} catch {
+		return;
+	}
+}
+/**
+* The package directory owning `moduleFile`: `dist/index.js` sits directly
+* inside the package, so walking up from the entry finds its manifest. The
+* manifest is claimed only when its `name` matches, so a same-named ancestor (a
+* pnpm virtual-store parent, for instance) cannot be misread.
+*/
+function findPackageRoot(moduleFile) {
+	let directory = dirname(moduleFile);
+	for (let depth = 0; depth < 4; depth++) {
+		if (readManifest(directory)?.name === "@earendil-works/pi-ai") return directory;
+		const parent = dirname(directory);
+		if (parent === directory) return void 0;
+		directory = parent;
+	}
+}
+/** Version from the manifest already located by {@link findPackageRoot}. */
+function readVersion(packageRoot) {
+	const version = readManifest(packageRoot)?.version;
+	return typeof version === "string" ? version : void 0;
+}
+function readManifest(directory) {
+	try {
+		const parsed = JSON.parse(readFileSync(join(directory, "package.json"), "utf8"));
+		return typeof parsed === "object" && parsed !== null ? parsed : void 0;
+	} catch {
+		return;
+	}
+}
+//#endregion
 //#region src/adapter.ts
 /** Provider route this bundle owns for the domestic (CN) gateway. */
 const TRAE_PROVIDER = "trae";
@@ -405,9 +579,172 @@ function toPiModel(info, baseUrl, providerId) {
 		compat: { supportsReasoningEffort: info.reasoningEfforts !== void 0 }
 	};
 }
+function isSystemMessage(message) {
+	return typeof message === "object" && message !== null && message.role === "system";
+}
+/**
+* The text of one system message: its `content` (a string, as
+* `normalizeContext` writes, or text blocks, which a provider may send back)
+* followed by its named `sections` — exactly the join pi-ai's own
+* `getSystemMessageText` performs.
+*
+* `sections` is not decoration: it is the modern transcript's second carrier of
+* prompt text ("named, ordered prompt sections rendered verbatim after
+* content"). Folding `content` alone would silently drop a prompt that arrives
+* section-shaped, which is the same asymmetric-loss failure this adapter exists
+* to prevent.
+*/
+function systemTextOf(message) {
+	const parts = [contentTextOf(message.content)];
+	const sections = message.sections;
+	if (typeof sections === "object" && sections !== null && !Array.isArray(sections)) {
+		for (const text of Object.values(sections)) if (typeof text === "string") parts.push(text);
+	}
+	return parts.filter((part) => part.length > 0).join("\n\n");
+}
+function contentTextOf(content) {
+	if (typeof content === "string") return content;
+	if (!Array.isArray(content)) return "";
+	const texts = [];
+	for (const block of content) {
+		if (typeof block !== "object" || block === null) continue;
+		const candidate = block;
+		if (candidate.type === "text" && typeof candidate.text === "string") texts.push(candidate.text);
+	}
+	return texts.join("\n\n");
+}
+/**
+* Replay one transcript system message's tool deltas into `state`, the same
+* merge pi-ai's own `getCurrentTools` performs: removals first, then additions,
+* keyed by name so a mid-conversation redeclaration replaces the original.
+*/
+function replayToolState(message, state) {
+	const removed = message.toolsRemoved;
+	if (Array.isArray(removed)) for (const tool of removed) {
+		const name = tool?.name;
+		if (typeof name === "string") state.delete(name);
+	}
+	const added = message.toolsAdded;
+	if (Array.isArray(added)) for (const tool of added) {
+		const name = tool?.name;
+		if (typeof name === "string") state.set(name, tool);
+	}
+}
+/**
+* Fold a NORMALIZED transcript back into the `{ systemPrompt, tools, messages }`
+* shape a LEGACY (≤0.85) api consumes — issue #27's crash and its two silent
+* siblings.
+*
+* WHY (issue #27). 0.86+ normalizes at every public entry point, and DSH's host
+* calls `Models.streamSimple()`, so on a modern host the context arriving here
+* ALWAYS carries its prompt and its tool declarations on a leading system
+* message — the top-level fields are gone. A legacy api has no branch for that
+* message: `estimateMessageTokens` iterates the string `content` character by
+* character and reads `.name` off a character, throwing
+* `Cannot read properties of undefined (reading 'length')` before the request
+* is even built. That is what surfaced as `PI_AI_ERROR` with all-zero usage.
+*
+* The fold must carry MORE than the prompt. `toolsAdded` is the ONLY remaining
+* carrier of the tool declarations once `normalizeContext` has run, and a
+* legacy api reads tools exclusively from `context.tools` — so lifting the text
+* alone would trade a loud crash for a silent one: a model that can never emit
+* a `toolCall` because the request declared no tools.
+*
+* Shape-guarded, not version-guarded: it asks "is there a system message inside
+* `messages`?" rather than "which pi-ai is loaded?". A version test would be
+* wrong the moment either side moves, and this predicate is an identity for the
+* legacy shape, so the ordinary path stays byte-for-byte untouched. WHICH
+* branch runs at all IS generation-gated — see {@link withContextAdaptation}.
+*
+* Returns the SAME object when there is nothing to fold, so a legacy host
+* (which never normalizes) pays one `Array.some` and nothing else.
+*/
+function adaptLegacyPiAiContext(context) {
+	if (context === null || typeof context !== "object") return context;
+	const messages = Array.isArray(context.messages) ? context.messages : void 0;
+	if (messages === void 0) return context;
+	if (!messages.some(isSystemMessage)) return context;
+	const systemTexts = [];
+	const rest = [];
+	const toolState = /* @__PURE__ */ new Map();
+	for (const message of messages) {
+		if (!isSystemMessage(message)) {
+			rest.push(message);
+			continue;
+		}
+		const text = systemTextOf(message);
+		if (text !== "") systemTexts.push(text);
+		replayToolState(message, toolState);
+	}
+	const texts = [...context.systemPrompt === void 0 || context.systemPrompt === "" ? [] : [context.systemPrompt], ...systemTexts];
+	const systemPrompt = texts.length > 0 ? texts.join("\n\n") : void 0;
+	const promoted = Array.isArray(context.tools) ? void 0 : [...toolState.values()];
+	return {
+		...context,
+		...systemPrompt === void 0 ? {} : { systemPrompt },
+		...promoted === void 0 || promoted.length === 0 ? {} : { tools: promoted },
+		messages: rest
+	};
+}
+/**
+* Lift the legacy `{ systemPrompt, tools, messages }` shape into the normalized
+* transcript a MODERN (0.86+) api consumes — the reverse mismatch, and just as
+* silent.
+*
+* WHY. DSH spans both generations (`dsh-llm-pi-ai` ≤0.2.0-rc.1 pins `^0.85.1`)
+* while this plugin may resolve a newer copy than its host. A LEGACY host never
+* normalizes, so it hands the api the legacy shape; a modern api reads the
+* prompt from a leading system message and the tools from its `toolsAdded`, and
+* never looks at the top-level fields — so both are dropped without a sound.
+* Verified against the published tarballs: the request that reaches the wire
+* carries no system turn and `tools: []`.
+*
+* Identity for anything already in transcript shape, and for a context with
+* neither a prompt nor tools (pi-ai's own `createInitialSystemMessage` returns
+* `undefined` there, keeping an empty transcript empty).
+*/
+function adaptModernPiAiContext(context) {
+	if (context === null || typeof context !== "object") return context;
+	const messages = Array.isArray(context.messages) ? context.messages : void 0;
+	if (messages === void 0) return context;
+	const prompt = context.systemPrompt;
+	const tools = Array.isArray(context.tools) && context.tools.length > 0 ? context.tools : void 0;
+	if (!(typeof prompt === "string" && prompt.length > 0) && tools === void 0) return context;
+	const head = {
+		role: "system",
+		content: prompt ?? "",
+		...tools === void 0 ? {} : { toolsAdded: tools }
+	};
+	const { systemPrompt: _lifted, tools: _liftedTools, ...rest } = context;
+	return {
+		...rest,
+		messages: [head, ...messages]
+	};
+}
+/**
+* Wrap one pi-ai API module so BOTH stream entry points receive a context its
+* own generation can consume.
+*
+* The gate is the copy THIS plugin resolved (see {@link piAiRuntimeInfo}) —
+* what the host runs says nothing about it, because a nested copy on disk
+* shadows host injection and vice versa. The wrapping is cheap and lazy: only
+* `stream`/`streamSimple` are intercepted, the deferred-fetch entry points take
+* no context and are passed through untouched, and each adapter function is an
+* identity unless the context is actually the other generation's shape. So a
+* healthy install does one `Array.some` per request.
+*/
+function withContextAdaptation(api, generation) {
+	const adapt = generation === "modern" ? adaptModernPiAiContext : adaptLegacyPiAiContext;
+	return {
+		...api,
+		stream: (model, context, options) => api.stream(model, adapt(context), options),
+		streamSimple: (model, context, options) => api.streamSimple(model, adapt(context), options)
+	};
+}
 function createTraeAdapter(options) {
 	const providerId = options.provider ?? "trae";
 	const providerName = options.displayName ?? "Trae";
+	const generation = options.piAiGeneration ?? piAiRuntimeInfo().generation;
 	const buildModels = () => options.catalog.current().map((info) => toPiModel(info, `${options.shim.baseUrl()}/v1`, providerId));
 	const provider = {
 		...createProvider({
@@ -424,7 +761,7 @@ function createTraeAdapter(options) {
 				}
 			} },
 			models: buildModels(),
-			api: openAICompletionsApi()
+			api: withContextAdaptation(openAICompletionsApi(), generation)
 		}),
 		getModels: () => buildModels()
 	};
@@ -5804,6 +6141,8 @@ function apply(ctx, config) {
 	Promise.all(REGION_KEYS.map((region) => stacks[region].shim.ready)).then(async () => {
 		if (stopped) return;
 		try {
+			const piAi = piAiRuntimeInfo();
+			ctx.logger.info(`dsh-connect-trae: pi-ai ${piAi.version ?? "unknown"} (${piAi.generation} generation)${piAi.inspected ? "" : " — not resolved locally, the host supplies it"}`);
 			for (const region of REGION_KEYS) {
 				const stack = stacks[region];
 				const trae = createTraeAdapter({
@@ -5877,4 +6216,4 @@ function apply(ctx, config) {
 	});
 }
 //#endregion
-export { Config, FALLBACK_TRAE_MODELS, FALLBACK_TRAE_MODELS_AI, REGION_GATEWAYS, SseDecoder, TRAE_ACCOUNT_STATUS_PATH, TRAE_AI_PROVIDER, TRAE_CHECKIN_PATH, TRAE_CN_AGENT_TASK_PATH, TRAE_CN_TITLE_PATH, TRAE_MODELS_TEST_PATH, TRAE_MODEL_DETAIL_FUNCTIONS, TRAE_MODEL_DETAIL_PATH, TRAE_PAY_BASE, TRAE_PROBE_TIMEOUT_MS, TRAE_PROVIDER, TRAE_PROVIDERS, TRAE_PROVIDER_DISPLAY_NAMES, TRAE_RAW_CHAT_V1_PATH, TRAE_RAW_CHAT_V2_PATH, TRAE_REASONING_EFFORTS, TRAE_REGIONS, TRAE_REGION_PARAM, TRAE_SETTINGS_NS, TRAE_SOLO_CHAT_PATH, TRAE_SOLO_FUNCTION, TRAE_SOLO_MODELS_PATH, TRAE_SOLO_REMOTE_BASE, TRAE_STATE_DB_FILENAME, TRAE_STREAM_IDLE_TIMEOUT_MS, TRAE_USAGE_PATH, TRAE_VERSION_CODE_FALLBACK, TraeCatalog, TraeCredentialStore, TraeDelegatingUpstreamClient, TraeFallbackUpstreamClient, TraeGatedUpstreamClient, TraeRawCapabilityController, TraeRawCapabilityState, TraeRawChatUpstreamClient, TraeSoloBridge, TraeSoloRemoteCatalogClient, TraeSoloUpstreamClient, TraeUsageClient, UnconfiguredTraeUpstreamClient, apply, applyContextBudgets, applyImageSelection, applyReasoningEffort, asVolatile, bridgeTraeSoloStream, buildTraeAgentTaskBody, buildTraeCnHeaders, buildTraeFusionRawChatEnvelope, buildTraeModelDetailRequest, buildTraeRawChatDraft, buildTraeRawChatRuntimeConfig, classifyProbeError, classifyProbeResult, classifyTraeRawChatFailure, configuredAccountsOf, createTraeAdapter, createTraeRawGateway, createTraeShim, decodeRawChatChunk, decodeTraeEvent, decryptTraeStorageValue, deriveCatalog, describeIdShape, describeNameShape, discoveredCatalog, fallbackModelsFor, followAppLoginEnabled, hashTraeRawChatArg, identityHeaders, inject, legacyTraeOwnAuthPath, maskUserPath, mergeTraeModelSources, name, nextRegionEnabled, nextRegionSlots, normalizeTraeCredential, normalizeTraeVersionCode, parseObservedModelConfig, parseReasoningCapability, parseTraeAuthValue, parseTraeCachedModel, parseTraeModelExtraConfigLogLine, parseTraeRawChatBehaviorConfig, parseTraeRemoteModel, parseTraeStorageDocument, pickTraeStorageIdentity, prepareSoloBody, probeBody, probeModelsSequentially, probeOneModel, probeTraeRawChatCapability, rawCapabilityDiagnostic, rawCapabilityFingerprint, readTraeCachedModel, readTraeCliIdentity, readTraeIdentity, refreshTraeCredential, regionEnabled, regionEnabledOf, regionOfCredential, regionOfEdition, regionOfHost, regionOfTraeProvider, regionOfTraeStatusUrl, regionOfUserRegion, regionStateOf, registerTraeUsageRoute, resolveTraeIdentity, resolveTraeRawRuntime, sanitizeCatalog, settingsNamespaceOf, traeEndpoint, traeInputModalities, traeModelDisplayName, traeOwnAuthPath, traeRawChatExtraInfo, traeStateDatabaseCandidates, traeStorageCandidates, traeWebUsage, traeWindowsAppNames, unwrapVolatile, unwrapVolatileDeep, withTraeRegion };
+export { Config, FALLBACK_TRAE_MODELS, FALLBACK_TRAE_MODELS_AI, REGION_GATEWAYS, SseDecoder, TRAE_ACCOUNT_STATUS_PATH, TRAE_AI_PROVIDER, TRAE_CHECKIN_PATH, TRAE_CN_AGENT_TASK_PATH, TRAE_CN_TITLE_PATH, TRAE_MODELS_TEST_PATH, TRAE_MODEL_DETAIL_FUNCTIONS, TRAE_MODEL_DETAIL_PATH, TRAE_PAY_BASE, TRAE_PROBE_TIMEOUT_MS, TRAE_PROVIDER, TRAE_PROVIDERS, TRAE_PROVIDER_DISPLAY_NAMES, TRAE_RAW_CHAT_V1_PATH, TRAE_RAW_CHAT_V2_PATH, TRAE_REASONING_EFFORTS, TRAE_REGIONS, TRAE_REGION_PARAM, TRAE_SETTINGS_NS, TRAE_SOLO_CHAT_PATH, TRAE_SOLO_FUNCTION, TRAE_SOLO_MODELS_PATH, TRAE_SOLO_REMOTE_BASE, TRAE_STATE_DB_FILENAME, TRAE_STREAM_IDLE_TIMEOUT_MS, TRAE_USAGE_PATH, TRAE_VERSION_CODE_FALLBACK, TraeCatalog, TraeCredentialStore, TraeDelegatingUpstreamClient, TraeFallbackUpstreamClient, TraeGatedUpstreamClient, TraeRawCapabilityController, TraeRawCapabilityState, TraeRawChatUpstreamClient, TraeSoloBridge, TraeSoloRemoteCatalogClient, TraeSoloUpstreamClient, TraeUsageClient, UnconfiguredTraeUpstreamClient, adaptLegacyPiAiContext, adaptModernPiAiContext, apply, applyContextBudgets, applyImageSelection, applyReasoningEffort, asVolatile, bridgeTraeSoloStream, buildTraeAgentTaskBody, buildTraeCnHeaders, buildTraeFusionRawChatEnvelope, buildTraeModelDetailRequest, buildTraeRawChatDraft, buildTraeRawChatRuntimeConfig, classifyProbeError, classifyProbeResult, classifyTraeRawChatFailure, configuredAccountsOf, createTraeAdapter, createTraeRawGateway, createTraeShim, decidePiAiGeneration, decodeRawChatChunk, decodeTraeEvent, decryptTraeStorageValue, deriveCatalog, describeIdShape, describeNameShape, discoveredCatalog, fallbackModelsFor, followAppLoginEnabled, generationOf, hashTraeRawChatArg, identityHeaders, inject, legacyTraeOwnAuthPath, maskUserPath, mergeTraeModelSources, name, nextRegionEnabled, nextRegionSlots, normalizeTraeCredential, normalizeTraeVersionCode, parseObservedModelConfig, parseReasoningCapability, parseTraeAuthValue, parseTraeCachedModel, parseTraeModelExtraConfigLogLine, parseTraeRawChatBehaviorConfig, parseTraeRemoteModel, parseTraeStorageDocument, piAiRuntimeInfo, pickTraeStorageIdentity, prepareSoloBody, probeBody, probeModelsSequentially, probeOneModel, probeTraeRawChatCapability, rawCapabilityDiagnostic, rawCapabilityFingerprint, readTraeCachedModel, readTraeCliIdentity, readTraeIdentity, refreshTraeCredential, regionEnabled, regionEnabledOf, regionOfCredential, regionOfEdition, regionOfHost, regionOfTraeProvider, regionOfTraeStatusUrl, regionOfUserRegion, regionStateOf, registerTraeUsageRoute, resolveTraeIdentity, resolveTraeRawRuntime, sanitizeCatalog, settingsNamespaceOf, traeEndpoint, traeInputModalities, traeModelDisplayName, traeOwnAuthPath, traeRawChatExtraInfo, traeStateDatabaseCandidates, traeStorageCandidates, traeWebUsage, traeWindowsAppNames, unwrapVolatile, unwrapVolatileDeep, withContextAdaptation, withTraeRegion };

package/package.json

@@ -2,7 +2,7 @@
   "name": "dsh-connect-trae",
   "displayName": "DSH Connect Trae",
   "description": "把本机登录的 Trae 模型接入 DeepSeek Harness：国内版与国际版双供应商并行，提供用量/积分概览与每日签到领取。",
-  "version": "3.4.1",
+  "version": "3.4.3",
   "author": "dingminhua",
   "copyright": "Copyright (c) 2026 LaoDing",
   "license": "MIT",