dsh-llm-fallbacks 0.6.3 → 0.6.4

package/README.md

@@ -7,7 +7,7 @@
 ![node](https://img.shields.io/badge/node-%3E%3D22-339933.svg)
 ![pnpm](https://img.shields.io/badge/pnpm-%3E%3D10-f69220.svg)
 ![dsh tui](https://img.shields.io/badge/dsh%20tui-compatible-4B32C3.svg)
-![dsh](https://img.shields.io/badge/DSH-0.1.7--rc.2-4B32C3.svg)
+![dsh](https://img.shields.io/badge/DSH-0.2.0--rc.1-4B32C3.svg)
 [![dshfind](https://dshfind.com/api/badge/omdsh-dev/dsh-llm-fallbacks?lang=en)](https://dshfind.com/zh/plugins/omdsh-dev/dsh-llm-fallbacks?ref=badge)
 
 Automatic provider/model fallback chains for dsh (DeepSeek Harness): when an agent's LLM requests keep failing — retries exhausted, auth errors, quota exceeded, rate limiting (429) — the plugin switches provider/model along the fallback chain for the current role, and the current step/turn continues on the target model: tasks are not interrupted by model problems.
@@ -94,7 +94,7 @@ Build the section up in four steps:
 
 **2. Set the all-day `rootChain`.** Leading entries are the fallback chain, walked first when a request fails; the **last** entry is the Default model.
 
-> **Conformance**: the last entry must be exactly one official model — `deepseek-official/deepseek-flash` or `deepseek-official/deepseek-v4-pro` (XOR). The settings card and gateway reject any other tail on save; a legacy non-official tail warns at startup and keeps working as a fallback-only walk, but cannot be saved as-is. The retired `deepseek-v4-flash` id is no longer a legal tail — a saved tail with it now warns, goes inert (slot rows + virtual picker), and blocks save until a legal tail is picked. The official Pro tail is catalog-served as `deepseek-official/deepseek-v4-pro` (dsh 0.1.7-rc.2; the claim re-verified against the rc.2 default catalog) and selectable in the card; a hand-written legacy `deepseek-official/deepseek-pro` tail — never catalog-served — reads back as non-conforming (no migration; re-pick the tail). The plugin does not probe catalog availability — a chain containing `deepseek-official/deepseek-v4-pro` dispatches to it like any other exact entry, and on the virtual route the `stream()` delegate serves the first dispatchable exact head of the effective chain, so a chain with a working entry before Pro still routes to that earlier entry.
+> **Conformance**: the last entry must be exactly one official model — `deepseek-official/deepseek-flash` or `deepseek-official/deepseek-v4-pro` (XOR). The settings card and gateway reject any other tail on save; a legacy non-official tail warns at startup and keeps working as a fallback-only walk, but cannot be saved as-is. The retired `deepseek-v4-flash` id is no longer a legal tail — a saved tail with it now warns, goes inert (slot rows + virtual picker), and blocks save until a legal tail is picked. The official Pro tail is catalog-served as `deepseek-official/deepseek-v4-pro` (dsh 0.2.0-rc.1; the claim re-verified against the rc.2 default catalog) and selectable in the card; a hand-written legacy `deepseek-official/deepseek-pro` tail — never catalog-served — reads back as non-conforming (no migration; re-pick the tail). The plugin does not probe catalog availability — a chain containing `deepseek-official/deepseek-v4-pro` dispatches to it like any other exact entry, and on the virtual route the `stream()` delegate serves the first dispatchable exact head of the effective chain, so a chain with a working entry before Pro still routes to that earlier entry.
 
 **3. Add `timeSlots` (optional).** Rows rotate the effective root chain by wall-clock windows. Preset rows use frozen UTC+8 windows (only their chain is editable; while a preset row exists, `tz` locks to `Asia/Shanghai`); custom rows take `start`/`end` (may wrap midnight) and an optional `days` list. The first row whose window contains the current moment wins; no match → the all-day `rootChain`. Rotation is a routing seed — it applies on the next root request and consumes no cooldown (see [Time slots](#time-slots)).
 

package/dist/client/ConversationFallbackSwitch.d.ts

@@ -10,7 +10,7 @@
  * so the `unknown-surface` fallback never picked it up and the transcript
  * showed nothing).
  *
- * Contract notes (dsh-private, 0.1.2 homes, verified 2026-08-28):
+ * Contract notes (dsh-private, current homes, verified 2026-08-28):
  * - D1 registry: `ConversationEventRegistry.register(definition)` — the
  *   client Context's `uiConversation.events` service seat
  *   (`ui-conversation conversation/event-registry.ts:17-25`); external

package/dist/client/fallbacks-store.d.ts

@@ -363,7 +363,7 @@ export declare function rulesToRows(rules: readonly FallbacksRoleRule[], catalog
 export declare function rowsToRules(rows: readonly RoleRuleRow[]): FallbacksRoleRule[];
 /**
  * The settings Remote namespace face the fallbacks store reads
- * (0.1.2 `ctx.remote.settings`; api-settings-controller `@Remote` methods).
+ * (`ctx.remote.settings`; api-settings-controller `@Remote` methods).
  */
 export interface FallbacksSettingsRemote {
     /** Redacted describe: provider writability plus the namespace directory. */
@@ -371,7 +371,7 @@ export interface FallbacksSettingsRemote {
 }
 /**
  * The llm Remote namespace face the fallbacks store reads
- * (0.1.2 `ctx.remote.llm`; dsh-llm `@Remote` methods).
+ * (`ctx.remote.llm`; dsh-llm `@Remote` methods).
  */
 export interface FallbacksLlmRemote {
     /** Declared configurable-provider directory, registered or dormant. */
@@ -379,7 +379,7 @@ export interface FallbacksLlmRemote {
 }
 /**
  * The session Remote namespace face the fallbacks store reads
- * (0.1.2 `ctx.remote.session`; api-session-controller `@Remote` methods).
+ * (`ctx.remote.session`; api-session-controller `@Remote` methods).
  */
 export interface FallbacksSessionRemote {
     /** Host-generation model catalog: provider groups plus per-provider failures. */
@@ -387,7 +387,7 @@ export interface FallbacksSessionRemote {
     /**
      * Live event stream for one durable session address; the opening snapshot
      * frame carries the tail page this store reads, then the stream is
-     * cancelled (0.1.2 successor of the apiproxy `sessions.history` unary —
+     * cancelled (successor of the apiproxy `sessions.history` unary —
      * `session/page` needs the follow opening frame's cursor, so a cold tail
      * read goes through the follow opening).
      */
@@ -479,7 +479,7 @@ export declare class FallbacksSettingsController {
     /**
      * Read the recent-switch summary for the current session (spec §2.5 D-5):
      * one tail page (`maxMessages` = {@link SWITCHES_HISTORY_PAGE}) read from
-     * the `session/follow` opening snapshot — 0.1.2 has no unary tail-page
+     * the `session/follow` opening snapshot — the host has no unary tail-page
      * read (`session/page` needs the follow opening frame's cursor), so the
      * stream is cancelled right after its first frame —
      * `fallbacks/switch` events extracted newest-first capped at

package/dist/client/index.d.ts

@@ -9,8 +9,8 @@
  *   config rides the plugin's gateway channel (`connection.rpc` →
  *   `/api/fallbacks/get|set|reset`), while `settings/describe` (writable +
  *   namespace directory), the provider/model catalog, and the switch-history
- *   tail page ride the typed `ctx.remote` namespaces (0.1.2:
- *   `ConnectionHandle` dropped `api`; see `fallbacks-store.ts`).
+ *   tail page ride the typed `ctx.remote` namespaces (`ConnectionHandle`
+ *   dropped `api`; see `fallbacks-store.ts`).
  * - Registers the `plugins.bundle.config` card `key: 'dsh-llm-fallbacks'`
  *   (bundle package name) with a business-only inject face
  *   ({@link FallbacksSettingsController} + hooks.snapshot); the old
@@ -48,7 +48,7 @@ export { FallbacksSettingsController, FALLBACKS_SETTINGS_NS } from './fallbacks-
  * (`setCurrentSession` never called, `loadSwitches` ready with an empty
  * array, which the store already supports).
  *
- * rc.1 dotted-namespace contract: each client Remote namespace is a
+ * The host's dotted-namespace contract: each client Remote namespace is a
  * child-fiber service named `remote.<ns>` (upstream `remoteServiceKey`), and
  * the traceable proxy forwards `ctx.remote.llm` / `.settings` / `.session`
  * to those context properties — consumers MUST declare the dotted names

package/dist/client/index.js

@@ -414,7 +414,7 @@ window.__ModuleLoader__.load({
 		* `deepseek-v4-flash` and the never-served legacy
 		* `deepseek-official/deepseek-pro` included) keeps slot rows inert and
 		* refuses the virtual-row
-		* delegate; the v0.2.2 failure walk over the raw chain stays
+		* delegate; the legacy failure walk over the raw chain stays
 		* verbatim.
 		*/
 		function isAllDayConforming(chain) {
@@ -432,7 +432,7 @@ window.__ModuleLoader__.load({
 		* (`isAllDayConforming(config.rootChain)`) the winner is ALWAYS `'all-day'`
 		* — a legacy multi-model (or empty) chain earns no slot rows, so every
 		* surface fed by this resolver reports the inert state and routing stays on
-		* the raw `rootChain` (the v0.2.2 walk verbatim).
+		* the raw `rootChain` (the legacy walk verbatim).
 		*/
 		function resolveSlotState(config, now, tz) {
 			if (!isAllDayConforming(config.rootChain)) return {
@@ -1109,7 +1109,7 @@ window.__ModuleLoader__.load({
 			/**
 			* Read the recent-switch summary for the current session (spec §2.5 D-5):
 			* one tail page (`maxMessages` = {@link SWITCHES_HISTORY_PAGE}) read from
-			* the `session/follow` opening snapshot — 0.1.2 has no unary tail-page
+			* the `session/follow` opening snapshot — the host has no unary tail-page
 			* read (`session/page` needs the follow opening frame's cursor), so the
 			* stream is cancelled right after its first frame —
 			* `fallbacks/switch` events extracted newest-first capped at
@@ -4458,7 +4458,7 @@ window.__ModuleLoader__.load({
 		* (`setCurrentSession` never called, `loadSwitches` ready with an empty
 		* array, which the store already supports).
 		*
-		* rc.1 dotted-namespace contract: each client Remote namespace is a
+		* The host's dotted-namespace contract: each client Remote namespace is a
 		* child-fiber service named `remote.<ns>` (upstream `remoteServiceKey`), and
 		* the traceable proxy forwards `ctx.remote.llm` / `.settings` / `.session`
 		* to those context properties — consumers MUST declare the dotted names
@@ -4477,7 +4477,7 @@ window.__ModuleLoader__.load({
 		];
 		/**
 		* The session the client is LOOKING at, derived from the sessions-list
-		* snapshot. 0.1.7-rc.1 moved view ownership out of `SessionListState` (the
+		* snapshot. The host moved view ownership out of `SessionListState` (the
 		* `current` field is gone — "navigation belongs to view owners"): the viewed
 		* session is the one the shell retains under the `mainView` reference source,
 		* surfaced as a positive `retainedBy.mainView` count on the row

package/dist/gateway.d.ts

@@ -38,7 +38,7 @@
  * rejection unchanged — the settings service itself is non-strict and would
  * merge the unknown key through), then writes the plugin's profile-entry
  * section in-process via `ctx.settings.update` (the `SettingsForms` form
- * service; 0.1.7-rc.1 replaced the namespace registry — the write lands in
+ * service; the host replaced the namespace registry — the write lands in
  * the active profile's patch under {@link FALLBACKS_PROFILE_ENTRY} and the
  * Loader commits it into the plugin's live config reference), and returns
  * the new composed value. `reset` (fallbacks-specific third method —
@@ -74,14 +74,14 @@ import type { FallbacksSeedManager, SeedRevertOutcome, SeedsWireStatus } from '.
 /**
  * The `fallbacks` service/typert namespace identity (`fallbacks`): the cordis
  * service key, the typert namespace under `/api/fallbacks/*`, and the settings
- * identity under the pre-0.1.6 dsh API. 0.1.7-rc.1 settings writes target the
+ * identity under the legacy dsh API. Current settings writes target the
  * PROFILE ENTRY id instead (see {@link FALLBACKS_PROFILE_ENTRY}); the branded
  * `SettingsNamespace` type the old service APIs constrained on survives as the
  * type this constant carries.
  */
 export declare const FALLBACKS_SETTINGS_NAMESPACE: SettingsNamespace;
 /**
- * The plugin's profile ENTRY id — the settings-write target on dsh 0.1.7-rc.1:
+ * The plugin's profile ENTRY id — the settings-write target on the current dsh host:
  * `SettingsForms` keys every form and write by the Loader entry id
  * (`entry.options.id`), and this plugin's bundle row ships `id: llm-fallbacks`
  * (`bundle/cordis.patch.yml`), so `settings.update('llm-fallbacks', …)` edits

package/dist/index.d.ts

@@ -6,7 +6,7 @@
  * `llm-fallbacks` (see `bundle/cordis.patch.yml`), composed AFTER llm-retry.
  *
  * Wiring:
- * - `fallbacks` settings via the Loader entry Config (0.1.7-rc.1: the
+ * - `fallbacks` settings via the Loader entry Config (the current host contract: the
  *   volatile `Config` schema in `src/schema.ts` IS the settings section;
  *   `apply` reads the Loader's live config reference, and the
  *   `settings/document-updated` listener re-derives the runtime caches —
@@ -142,7 +142,7 @@ export declare function chainHeads(ctx: Context): ReadonlyMap<string, EffectiveC
  */
 export declare function countRetryEvents(session: Session, turn: number, step: number, provider: string): number;
 /**
- * The live config reference the 0.1.7-rc.1 Loader hands `apply` for a
+ * The live config reference the Loader hands `apply` for a
  * volatile Config schema: an identity-stable `{ get }` view (cosmokit's
  * `Volatile` protocol) whose snapshot the Loader re-commits on every form
  * save, so reading `.get()` per call is the authoritative live composed

package/dist/role-notice.d.ts

@@ -29,7 +29,7 @@
  * Session-write contract (plan Global Constraints, hard): the row is a
  * `user/message` built with `createUserMessage` and the producer-declared
  * source `{ kind: 'llm-fallbacks-role-notice', form: 'notice', summary: … }`.
- * 0.1.7-rc.1 removed the shared `plugin` kind: `MessageSourceMap` is
+ * The host removed the shared `plugin` kind: `MessageSourceMap` is
  * producer-declared now ("each producer declares its own `kind` in its own
  * module; there is no shared catch-all `plugin` kind" — dsh-llm message.d.ts),
  * so this module merges its own kind and stamps `form: 'notice'` + the bound
@@ -81,7 +81,7 @@ declare module '@deepseek-ai/dsh-llm' {
     }
 }
 /**
- * The provenance label this plugin's notice rows carried under the pre-0.1.7
+ * The provenance label this plugin's notice rows carried under the legacy
  * `kind: 'plugin'` source API. The durable rows survive as data: the V3→V4
  * session-format edge rewrites every unlisted V3 plugin source to
  * `kind: 'plugin:<plugin>'`, so pre-upgrade child sessions carry
@@ -91,7 +91,7 @@ declare module '@deepseek-ai/dsh-llm' {
  */
 export declare const ROLE_NOTICE_PLUGIN = "dsh-llm-fallbacks";
 /**
- * The message source KIND the notice rides. 0.1.7-rc.1 removed the shared
+ * The message source KIND the notice rides. The host removed the shared
  * `plugin` kind (`MessageSourceMap` is producer-declared now — each producer
  * declares its own `kind` in its own module, the upstream `model-selection`
  * precedent), so this module declares `llm-fallbacks-role-notice` above and
@@ -102,7 +102,7 @@ export declare const ROLE_NOTICE_PLUGIN = "dsh-llm-fallbacks";
 export declare const ROLE_NOTICE_SOURCE_KIND = "llm-fallbacks-role-notice";
 /**
  * The source kinds the role projection must ALSO accept besides
- * {@link ROLE_NOTICE_SOURCE_KIND}: the V4-migrated form of the pre-0.1.7
+ * {@link ROLE_NOTICE_SOURCE_KIND}: the V4-migrated form of the legacy
  * `kind: 'plugin', plugin: 'dsh-llm-fallbacks'` rows (see
  * {@link ROLE_NOTICE_PLUGIN}).
  */

package/dist/role-projection.d.ts

@@ -6,7 +6,7 @@
  * Data source = Task 3's notice row, the plugin's single write primitive: the
  * fold reads the child's committed `user/message` events, keeps the one whose
  * provenance is ours (`source.kind` is the producer-declared
- * ROLE_NOTICE_SOURCE_KIND, or the V3→V4-migrated form of a pre-0.1.7 row —
+ * ROLE_NOTICE_SOURCE_KIND, or the V3→V4-migrated form of a legacy row —
  * `ROLE_NOTICE_LEGACY_SOURCE_KINDS`), and parses the role out of its
  * **content text** (`[role: <id>]`). No second write path, no new event type,
  * no plugin-owned store: the projection is a pure READ of the log, and the
@@ -33,7 +33,7 @@
  * The runtime shape relied on — `register({ key, stateSchema, init, apply,
  * wire: { viewSchema, view }, stateVersion })` → unregister disposer — is the
  * documented `ProjectionDefinition` contract of
- * `@deepseek-ai/dsh-session-projection@0.1.7-rc.1`
+ * `@deepseek-ai/dsh-session-projection`
  * (`lib/types/index.d.ts:38-80,150-152`); only `.parse` is ever called on the
  * schemas (`lib/index.js:255,305,422`).
  *

package/dist/schema.d.ts

@@ -19,17 +19,17 @@
  * `roles.default`) on the composed object at startup (warn + gateway
  * `legacyKeys`, see `src/index.ts` apply()).
  *
- * 0.1.7-rc.1 adoption: the whole schema is marked `volatile` (dsh 0.1.6
+ * Current host contract: the whole schema is marked `volatile` (the host
  * retired `installSection` — the Loader entry Config IS the settings
  * section now, and `SettingsForms.update` only accepts volatile paths, so
  * the marker is what keeps the gateway/card write path legal). One marker
  * on the ROOT object makes every field live-editable and hands `apply` a
  * single identity-stable config reference the Loader commits saves into
  * (no remount per save). The marker rides the generic `.extra()` writer —
- * the exact bytes `.volatile()` (schemastery ≥3.18.4) writes — because the
+ * the exact bytes `.volatile()` writes in newer schemastery — because the
  * dev-time schemastery resolved from the lockfile can predate that sugar;
- * the `Meta` augmentation below declares the field the ^3.18.2 peer range
- * admits at its upper end.
+ * the `Meta` augmentation below declares the field the peer range admits
+ * at its upper end.
  *
  * @module dsh-llm-fallbacks/schema
  */
@@ -38,7 +38,7 @@ import type { FallbacksConfig } from './config.ts';
 declare module '@deepseek-ai/schemastery' {
     namespace Schemastery {
         interface Meta {
-            /** Live-editable marker read by the Loader / `SettingsForms` (dsh 0.1.6+). */
+            /** Live-editable marker read by the Loader / `SettingsForms`. */
             volatile?: boolean;
         }
     }

package/dist/state.d.ts

@@ -67,14 +67,14 @@ export interface PendingSwitch {
 /**
  * One plugin-originated subagent switch the host allowlist blocked (plan
  * dsh-012-subagent-routing T3; spec D1). The intersection of the resolved
- * candidates with the effective allowlist was empty while the 0.3.5 walk
+ * candidates with the effective allowlist was empty while the unconstrained walk
  * would have switched — the attempt is recorded in-memory only (issue #52:
  * no durable session write) for the Subagents card warning (spec D4/T5).
  */
 export interface BlockedSwitchAttempt {
     /** Epoch ms when the switch was blocked. */
     at: number;
-    /** The route the 0.3.5 walk would have switched to (exact provider+model). */
+    /** The route the unconstrained walk would have switched to (exact provider+model). */
     route: {
         provider: string;
         model: string;

package/dist/subagent-policy.d.ts

@@ -46,7 +46,7 @@ export type PolicyRoute = {
  * Effective subagent routing policy for one session.
  *
  * - `disabled`: host policy off or absent — selection matches pre-policy
- *   (0.3.5) behavior.
+ *   behavior.
  * - `enabled`: an allowlist is proven; plugin-originated routes must stay
  *   inside it.
  * - `unprovable`: the policy is on but unreadable (malformed event payload,

package/dist/subagents-seam.d.ts

@@ -3,7 +3,7 @@
  * role-based-subagent-adoption Task 1).
  *
  * The seam is the documented cordis service-read waterfall
- * (`Events['internal/get']`, `@deepseek-ai/cordis` 4.0.2
+ * (`Events['internal/get']`, `@deepseek-ai/cordis`
  * `lib/types/events.d.ts`): a listener wraps the `subagents` service VALUE on
  * read and returns a prototype-delegating wrapper whose `start` /
  * `startContinuable` resolve the dispatch role from the incoming request
@@ -46,7 +46,7 @@
  * `chain: []` role gets its persona exactly like a chained one (no routing
  * state is read). Both native start surfaces are covered, with the gate each
  * one's fail-loud contract needs (measured on the installed
- * `@deepseek-ai/dsh-subagent` `0.1.7-rc.1`): the one-shot `start` REJECTS a
+ * `@deepseek-ai/dsh-subagent`): the one-shot `start` REJECTS a
  * request carrying `persona` for a provider whose
  * `getProvider(name).capabilities.persona` is not `true` (`lib/index.js:3284,3340-3363`,
  * `assertCapabilities`), so the merge pre-checks that flag; the continuable

package/dist/time-slots.d.ts

@@ -10,16 +10,15 @@
  * throw: they warn ONCE per row instance (through `console.warn` — the
  * resolver's 3-argument contract has no logger parameter) and are
  * skipped; a legacy non-empty non-conforming `rootChain` keeps the
- * v0.2.2 failure walk verbatim (P6).
+ * legacy failure walk verbatim (P6).
  *
  * @module dsh-llm-fallbacks/time-slots
  */
 import type { FallbacksConfig } from './config.ts';
 /** Official all-day selectors — the ONLY legal tails (length 1, XOR):
  * Flash (the current official default) and Pro, both selectable. The Pro
- * tail id is the catalog id verbatim: 0.1.7-rc.2's official default catalog
- * still serves `deepseek-v4-pro` alongside `deepseek-flash` — re-verified
- * at rc.2 (rc.1 re-introduced it), so the card's Pro radio is selectable. `deepseek-v4-flash` stays retired (dropped
+ * tail id is the catalog id verbatim: the official default catalog
+ * still serves `deepseek-v4-pro` alongside `deepseek-flash`, so the card's Pro radio is selectable. `deepseek-v4-flash` stays retired (dropped
  * from the catalog); a hand-written legacy `deepseek-official/deepseek-pro`
  * tail — never catalog-served nor selectable — is just a non-legal tail
  * that degrades through the existing nonconforming walk. */
@@ -83,7 +82,7 @@ export declare const PRESETS: Record<PresetId, PresetDefinition>;
  * `deepseek-v4-flash` and the never-served legacy
  * `deepseek-official/deepseek-pro` included) keeps slot rows inert and
  * refuses the virtual-row
- * delegate; the v0.2.2 failure walk over the raw chain stays
+ * delegate; the legacy failure walk over the raw chain stays
  * verbatim.
  */
 export declare function isAllDayConforming(chain: readonly string[]): boolean;
@@ -111,7 +110,7 @@ export declare function resolveEffectiveChain(config: FallbacksConfig, now: Date
  * (`isAllDayConforming(config.rootChain)`) the winner is ALWAYS `'all-day'`
  * — a legacy multi-model (or empty) chain earns no slot rows, so every
  * surface fed by this resolver reports the inert state and routing stays on
- * the raw `rootChain` (the v0.2.2 walk verbatim).
+ * the raw `rootChain` (the legacy walk verbatim).
  */
 export declare function resolveSlotState(config: FallbacksConfig, now: Date, tz: string): {
     winner: SlotRowConfig | 'all-day';

package/dist/virtual-adapter.d.ts

@@ -146,7 +146,7 @@ export declare class FallbacksChainAdapter extends LlmAdapter {
      */
     providerRetryPolicy(_provider: string): ResolvedRetryPolicy | undefined;
     /**
-     * Route-accurate image pricing (0.1.2 adoption): the virtual row has no
+     * Route-accurate image pricing: the virtual row has no
      * pricing of its own — the virtual `provider`/`model` arguments are
      * intentionally ignored. Resolves the SAME effective head `stream()`
      * dispatches and delegates through the runtime lookup, so the token

package/package.json

@@ -5,7 +5,7 @@
     "dsh",
     "dsh-plugin"
   ],
-  "version": "0.6.3",
+  "version": "0.6.4",
   "type": "module",
   "main": "./dist/index.js",
   "types": "./dist/index.d.ts",
@@ -65,28 +65,28 @@
   },
   "peerDependencies": {
     "@deepseek-ai/cordis": "^4.0.2",
-    "@deepseek-ai/dsh-agent": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-api-gateway": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-api-remotes": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-api-session-controller": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-connection": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-locale": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-store": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-ui-chat": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-ui-conversation": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-ui-plugin-manager": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-ui-renderer": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-ui-settings": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-client-ui-slots": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-commands": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-llm": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-llm-retry": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-session": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-session-projection": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-settings": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-tool-subagent": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-typert-protocol": "^0.1.7-rc.2",
-    "@deepseek-ai/dsh-typert-registry": "^0.1.7-rc.2",
+    "@deepseek-ai/dsh-agent": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-api-gateway": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-api-remotes": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-api-session-controller": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-connection": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-locale": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-store": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-chat": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-conversation": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-plugin-manager": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-renderer": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-settings": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-client-ui-slots": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-commands": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-llm": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-llm-retry": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-session": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-session-projection": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-settings": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-tool-subagent": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-typert-protocol": "^0.2.0-rc.1",
+    "@deepseek-ai/dsh-typert-registry": "^0.2.0-rc.1",
     "@deepseek-ai/schemastery": "^3.18.2",
     "react": "^18.2.0"
   },