dsh-llm-fallbacks 0.6.2 → 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/FallbacksCard.d.ts

@@ -11,11 +11,13 @@
  * rotating chevron, no dirty "unsaved" pill, no card-local open state, no
  * bordered `<li>` box. The page already renders the plugin title/description
  * above the card (the `locale/*.json` meta files the host resolves per UI
- * language), so the notices, the form, and the footer tile directly beneath
- * it in the official flat settings-form language (reference §3): fields at
+ * language), so the notices, the form, and the section actions directly
+ * beneath it in the official flat settings-form language (reference §3):
+ * fields at
  * 12px vertical padding with 0.5px hairline separators, 34px inputs on the
- * 0.5px l4 border, one dark solid Save footer. The card is ALWAYS open —
- * nothing is hidden, so nothing needs disclosure state; the degraded /
+ * 0.5px l4 border, per-section Discard + Save pairs on the section
+ * headings. The card is ALWAYS open —
+ * nothing needs card-level disclosure state; the degraded /
  * error / read-only / migration notices render flat atop the form (the
  * unavailable notice stays always-visible per KD-G5 — the documented
  * divergence from the advisor, whose unavailable card renders nothing: the
@@ -27,19 +29,22 @@
  * unconditionally; the Plugins-page row toggle is the master switch and the
  * runtime gates read content presence (`isFallbackActive`).
  *
- * ONE Save replaces the per-section saves (T3): the per-section split
- * existed so one section's Save could not ride along another section's
- * unsaved edits (PR #62 UX round 3) — with ONE save over ONE document that
- * concern is moot. The footer's Save writes the whole validated draft
- * (disabled = `!dirty || invalid || saving || !writable` — `invalid` is the
- * LIVE whole-form `validateDraft` verdict plus the empty-rule-row check;
- * section bucketing survives for ERROR PLACEMENT only: each violation
- * renders under its owning section heading). Save additionally carries
- * `!writable` (W-1, qc2 fix wave: the dirty-implies-writable assumption
- * does not hold for this in-place-draft store). Discard is kept — our
- * staged edits survive refresh, the advisor's documented divergence from
- * the official no-discard form — a pure client-side revert of the WHOLE
- * draft to the last accepted config (`!dirty || saving`).
+ * PER-SECTION Save/Discard return beside each section heading (plan
+ * fallbacks-card-section-ux, the maintainer's live-host feedback reversing
+ * the flat plan's one-document model): the scroll-to-save cost of ONE
+ * bottom Save outweighed it. Each section's Save writes ONLY that section's
+ * fields (patch = the last ACCEPTED config with the section's fields
+ * replaced — the ride-along protection, PR #62 UX round 3), gated by that
+ * section's dirty term and validation bucket only (KD-U1: save =
+ * `!sectionDirty || saving || !writable`, discard = `!sectionDirty ||
+ * saving`; Save additionally carries `!writable` — W-1, qc2 fix wave: the
+ * dirty-implies-writable assumption does not hold for this in-place-draft
+ * store). Violations render live under their OWNING section heading, and a
+ * store write failure renders under the section whose Save was last
+ * clicked (`lastSaveSection`). Discard is kept — our staged edits survive
+ * refresh, the advisor's documented divergence from the official
+ * no-discard form — a pure client-side revert of THAT section's editors to
+ * the last accepted config.
  *
  * The form body is the two-block editing surface (spec §8): the 6 top-level
  * scalar fields (trigger codes / revert policy / three numeric fields), the
@@ -51,7 +56,9 @@
  * the time-slot row cards and the role entity cards (with the seeded
  * persona briefs) stay collapsible — a read-only view forces them open so
  * the configs stay reachable. The 主代理 / 子代理 / 高级选项 group labels
- * stay as flat, non-collapsible section headings.
+ * are semantic `<h2>` headings (T1); 高级选项 is a content-level disclosure
+ * collapsed by default (T3 — same expand/collapse contract as the rows, a
+ * read-only view forces it open).
  *
  * Validation: id format/reserved word/duplicates, undeclared rule role
  * references, illegal selectors, and a role with no chain entries (no model
@@ -88,8 +95,8 @@ export interface FallbacksCardInjected {
 export type FallbacksCardProps = PropsRuntime<'plugins.bundle.config'> & PropsLocale<'fallbacks'> & InjectFace<FallbacksCardInjected>;
 /**
  * Render the Fallbacks settings card inside the plugin-config section —
- * flat: the notices, the form, and the footer tile directly under the
- * page's plugin title/description, with no chrome of our own.
+ * flat: the notices, the form, and the section action pairs directly under
+ * the page's plugin title/description, with no chrome of our own.
  * @param props - slot-delivered injected dependencies and the synthesized t seat.
  * @returns the card.
  */

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