dsh-llm-fallbacks 0.6.13 → 0.8.0

package/dist/chains.d.ts

@@ -1,30 +1,13 @@
 /**
- * Fallback chain resolution (spec §7.2; plan fallbacks-role-runtime Task 1).
+ * Fallback chain resolution: candidate resolution over ONE chain's effective
+ * entries (named virtual chains, plan named-virtual-chains T2).
  *
- * `resolveChain` returns the ordered candidate list for a failing
- * (provider, model). Candidates come from the role's own chain plus
- * `rootChain` appended as an inherit-root fallback — **append-not-replace**:
- * `[...(roleDef.chain ?? []), ...(roleDef.fallback === 'none' ? [] :
- * rootChain)]` (role entries first, rootChain entries after). The reserved
- * built-in `inherit` id (INHERIT_ROLE_ID) resolves to `rootChain` silently —
- * it is the legal no-rule-match role, not a typo'd id. A truly undeclared
- * role id (defense) resolves to `rootChain` alone + one warn. Chain-key
- * specificity lookup (`exact` / `provider/*` / role / `default` keys) is
- * deleted — the two-block config model has no chain keys.
- *
- * Wildcard entries (`provider/*`) are resolved against the failing model —
- * keep the model id, swap only the provider; the "target provider has no
- * such model id" skip is judged by {@link resolveCandidate} (via
- * `modelExists`) or by the caller's filter.
- *
- * The concatenation itself lives in ONE helper — {@link buildRoleEntries}
- * (qc1 S-3 SSOT) — shared by {@link resolveChainViews} and
- * {@link hasWildcardEntry}, so the wildcard probe is exact (qc2 F-003:
- * `fallback: 'none'` excludes `rootChain`) and can never diverge from the
- * resolution. Defensive warns (unknown role / undeclared rule target) go
- * through an injected `warn` callback — the wiring passes the cordis
- * `logger.warn` (qc2 F-002 / qc3 S-3), with `console.warn` as the
- * direct-call default.
+ * `resolveChainViews` / `resolveChain` walk the chain's entries ONCE and
+ * resolve each against the failing (provider, model). Wildcard entries
+ * (`provider/*`) keep the model id and swap only the provider; the "target
+ * provider has no such model id" skip is judged by {@link resolveCandidate}
+ * (via `modelExists`) or by the caller's filter — applied to wildcard-origin
+ * candidates ONLY ({@link selectCandidates}).
  *
  * Cooldown / failed-set / same-as-current filtering is caller-side;
  * {@link createCandidateFilter} provides the ready-made predicate. A
@@ -33,10 +16,9 @@
  * than the failing model's cannot fit the request either
  * ({@link fitsContextWindow}; unknown windows keep the candidate).
  *
- * @module dsh-llm-fallbacks/chains
+ @module dsh-llm-fallbacks/chains
  */
-import { type FallbacksRole } from './config.ts';
-import type { CooldownStore, StepFailureSet } from './cooldown.ts';
+import type { CooldownStore } from './cooldown.ts';
 import { type Selector } from './selectors.ts';
 /** The model that just failed — the anchor for chain resolution. */
 export interface FailingModel {
@@ -56,25 +38,16 @@ export interface FailingModel {
  */
 export declare function resolveCandidate(entry: string, failing: FailingModel, modelExists?: (provider: string, model: string) => boolean): Selector | null;
 /**
- * Single-pass chain resolution for the decision path (T1 review Important
- * #2). Walks the role's concatenated entries ONCE and returns the unfiltered
- * view — `all` (every resolvable candidate, no filter and no existence
- * probe: the caller's early-exit / annotation view) — plus the parallel
- * `wildcard` provenance (`wildcard[i]` = candidate `all[i]` came from a
- * `provider/*` entry). The caller builds the existence probe from `all` and
- * then derives the surviving view with {@link selectCandidates}, so the
- * decision path never resolves the chain twice (and an unknown role warns
- * at most once per decision).
- *
- * The reserved built-in `inherit` id (INHERIT_ROLE_ID) is legal — it
- * resolves to `rootChain` silently (the no-rule-match role, not a typo'd
- * id). Only a truly undeclared id (∉ declared ids ∪ {'inherit'}) warns once
- * (defensive — never crashes) through `warn` (defaults to `console.warn`
- * for direct-call compatibility; the decision path injects the cordis
- * `logger.warn` — qc2 F-002 / qc3 S-3). Malformed entries never become
- * candidates.
+ * Single-pass chain resolution over one chain's entries. Walks `entries` ONCE
+ * and returns the unfiltered view — `all` (every resolvable candidate, no
+ * filter and no existence probe: the caller's early-exit / annotation view) —
+ * plus the parallel `wildcard` provenance (`wildcard[i]` = candidate `all[i]`
+ * came from a `provider/*` entry). The caller builds the existence probe from
+ * `all` and then derives the surviving view with {@link selectCandidates}, so
+ * the decision path never resolves the chain twice. Malformed entries never
+ * become candidates.
  */
-export declare function resolveChainViews(roles: readonly FallbacksRole[], rootChain: readonly string[], role: string, provider: string, model: string, warn?: (message: string) => void): {
+export declare function resolveChainViews(entries: readonly string[], provider: string, model: string, warn?: (message: string) => void): {
     all: Selector[];
     wildcard: boolean[];
 };
@@ -88,46 +61,24 @@ export declare function resolveChainViews(roles: readonly FallbacksRole[], rootC
  */
 export declare function selectCandidates(all: readonly Selector[], wildcard: readonly boolean[], filter?: (candidate: Selector) => boolean, modelExists?: (provider: string, model: string) => boolean): Selector[];
 /**
- * Ordered fallback candidates for the failing (provider, model).
- *
- * Candidates are the role's concatenated entries (spec §7.2, see
- * {@link buildRoleEntries} — the single concatenation SSOT): the declared
- * role's own `chain` followed by `rootChain` unless `fallback: 'none'`
- * (append-not-replace — role entries first, rootChain as the tail). The
- * reserved built-in `inherit` id resolves to `rootChain` silently; a truly
- * undeclared/unknown `role` id resolves to `rootChain` alone and warns once
- * (defensive — never crashes). `filter` optionally drops candidates — the
- * caller owns cooldown/failed-set/same-model filtering (see
- * {@link createCandidateFilter}). The `modelExists` existence probe is NOT
- * applied per entry here: {@link resolveChainViews} returns the parallel
- * `wildcard` provenance, and {@link selectCandidates} applies `modelExists`
- * to `provider/*`-origin candidates ONLY (qc1 S-2 — exact entries are never
- * existence-filtered, spec §2 clause 2 / T2 review Important #1
- * decision-path contract). `warn` forwards to {@link resolveChainViews}
- * (defaults to `console.warn`; the decision path injects `logger.warn`).
+ * Ordered fallback candidates for the failing (provider, model), over ONE
+ * chain's `entries`. `filter` optionally drops candidates — the caller owns
+ * cooldown/failed-set/same-model filtering (see {@link createCandidateFilter}).
+ * The `modelExists` existence probe is applied by {@link selectCandidates} to
+ * `provider/*`-origin candidates ONLY (exact entries are never
+ * existence-filtered). `warn` forwards to {@link resolveChainViews}.
  *
  * Single-pass: delegates to {@link resolveChainViews} + {@link selectCandidates}
- * (one concatenated-entry walk, warn at most once per call).
+ * (one entry walk).
  */
-export declare function resolveChain(roles: readonly FallbacksRole[], rootChain: readonly string[], role: string, provider: string, model: string, filter?: (candidate: Selector) => boolean, modelExists?: (provider: string, model: string) => boolean, warn?: (message: string) => void): Selector[];
+export declare function resolveChain(entries: readonly string[], provider: string, model: string, filter?: (candidate: Selector) => boolean, modelExists?: (provider: string, model: string) => boolean, warn?: (message: string) => void): Selector[];
 /**
- * Whether any entry of the role's concatenated candidates is a wildcard
- * (`provider/*`). F-002: {@link resolveChain} resolves wildcard entries to
- * concrete models, so the wildcard provenance is invisible on the resolved
- * candidate list — the decision path consults the same concatenation
- * `resolveChain` walks to decide whether the catalog existence probe is
- * needed at all.
- *
- * The probe walks {@link buildRoleEntries} — the SAME concatenation
- * {@link resolveChainViews} resolves (qc1 S-3 single SSOT) — so it is
- * exact, never an over-approximation (qc2 F-003 / qc3 S-1): for
- * `fallback: 'none'` roles `rootChain` is excluded, and a wildcard that can
- * never reach the candidate list never builds a catalog probe. No
- * false-negative is possible: any wildcard the resolution could reach is on
- * this concatenation by construction. Malformed entries never become
- * candidates and are skipped.
+ * Whether any entry of `entries` is a wildcard (`provider/*`). The decision
+ * path consults this to decide whether the catalog existence probe is needed
+ * at all — a wildcard that can never reach the candidate list never builds a
+ * catalog probe. Malformed entries never become candidates and are skipped.
  */
-export declare function hasWildcardEntry(roles: readonly FallbacksRole[], rootChain: readonly string[], role: string): boolean;
+export declare function hasWildcardEntry(entries: readonly string[]): boolean;
 /** Inputs for {@link createCandidateFilter}. */
 export interface CandidateFilterOptions {
     /** The currently active (failing) model — skipped as "same as current". */
@@ -135,7 +86,9 @@ export interface CandidateFilterOptions {
     /** Cooldown store: suppressed candidates are skipped (keyed `provider/model`). */
     cooldown: Pick<CooldownStore, 'isSuppressed'>;
     /** Failed-set for the current step: already-failed candidates are skipped. */
-    failed: Pick<StepFailureSet, 'has'>;
+    failed: {
+        has(key: string): boolean;
+    };
     /** Optional existence probe: candidates the target provider lacks are skipped. */
     modelExists?: (provider: string, model: string) => boolean;
     /**

package/dist/client/FallbacksCard.d.ts

@@ -1,83 +1,32 @@
 /**
- * Fallbacks settings card — the `fallbacks` plugin card on the web
- * Plugins page (spec §4). Registered into the `plugins.bundle.config` keyed
- * slot (key `dsh-llm-fallbacks`, the bundle package name, alongside
- * the upstream bash/agent-loop/web-search cards and the advisor card, in
- * registration order); owner props are empty and all data flows
- * through {@link FallbacksSettingsController}.
+ * Fallbacks settings card — the `fallbacks` plugin card on the web Plugins
+ * page (named virtual chains, plan named-virtual-chains T5; the FROZEN UI
+ * mockup `.mstar/design/named-virtual-chains/settings-mockup.html`).
  *
- * FLAT rebuild (plan fallbacks-web-ux-alignment T3, the advisor PR #98
- * pattern): the collapsible card chrome is gone — no header button, no
- * 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 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, 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
- * fallbacks skeleton stays the USABLE last-known form and saves are
- * attempted).
+ * Flat form vocabulary unchanged: fields at 12px vertical padding with 0.5px
+ * hairline separators, 34px inputs on the 0.5px l4 border, per-section
+ * Discard + Save pairs. The 虚拟链 group is TAB-PER-CHAIN: underline tabs on
+ * the 0.5px l2 hairline (active label = label-primary + 2px brand underline,
+ * dirty pip, error "!" mark), a "+" add affordance and a "⋯" chain menu
+ * (delete, ≥1 chain), WAI-ARIA tabs with roving tabindex.
+ * Each tab body carries 链名称 (the single label editor — the ⋯ menu binds to
+ * the same draft field) followed by the SHIPPED block order 分时槽设置 →
+ * 默认降级链 → 默认模型（链尾） plus a per-tab Discard/Save writing ONLY that
+ * chain (block ids per chain, error text under the owning block).
  *
- * The config-level `enabled` switch is REMOVED (T2, breaking): there is no
- * checkbox row and no `enabled.off` hiding — all fields render
- * unconditionally; the Plugins-page row toggle is the master switch and the
- * runtime gates read content presence (`isFallbackActive`).
+ * The 子代理 section is role cards: id + persona + 指定降级链 (a MANUAL
+ * named-chain pointer; 未指定（沿用 dsh 默认） = the plugin does not
+ * intervene). No rules, no per-role chain entries, no host-policy block.
+ * The 高级选项 group is unchanged; the 运行状态（只读） block and the
+ * General settings row are REMOVED with the client switch-history read.
  *
- * 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.
+ * Validation blocks the owning save only: chain id format/duplicates,
+ * missing label, per-chain slot guards, tail conformance, role id checks.
+ * A non-empty `state.legacyKeys` renders the migration banner at the top.
  *
- * 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
- * `rootChain` block (block 1 — the root agent's single chain, no key input),
- * and the roles block (block 2 — declared role entity cards from
- * `roles.list` plus the rule rows from `roles.rules`, whose role field is a
- * dropdown bound to the declared ids + the built-in `inherit`, same-page
- * live). Row-level disclosures that are CONTENT keep their expand/collapse:
- * 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
- * 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
- * config) block the write (the Save disabled gate) with per-section banners
- * + inline red borders / hints (never touching the store error path); a
- * non-empty `state.legacyKeys` renders the migration banner at the top.
- * The reset-to-defaults affordance is GONE from the card (PR #62 UX
- * round 3) — the gateway RPC `fallbacks/reset` and the store
- * `resetToDefaults()` stay as host APIs, only the card UI was removed.
- *
- * The AC-7 read-only status block (recent-switch summary, D-5) stays at the
- * bottom, flat.
- *
- * Presentation is ui-primitives-free (T4, advisor parity + reference §4
- * risk): Button/Tooltip and the five icon imports are replaced by
- * self-drawn styled elements — inline SVG icons (plus / trash / chevron /
- * grip) and the CSS `data-tip` tooltip bubble (the card's existing
- * icon-button pattern); every color resolves through a `--dsw-alias-*`
- * token so the card adapts to the light/dark theme.
+ * Presentation stays ui-primitives-free: inline SVG icons and the CSS
+ * `data-tip` tooltip bubble; every color resolves through a
+ * `--dsw-alias-*` token (light/dark parity).
  */
 import type { ReactNode } from 'react';
 import type { InjectFace, PropsLocale, PropsRuntime } from '@deepseek-ai/dsh-client-ui-slots';
@@ -94,10 +43,8 @@ export interface FallbacksCardInjected {
 /** Props delivered by the slot outlet: runtime share + locale seat + inject face. */
 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 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.
+ * Render the Fallbacks settings card inside the plugin-config section
+ * (named virtual chains): the 虚拟链 tab group, the 子代理 role cards and
+ * the 高级选项 group, flat under the page's plugin title/description.
  */
 export declare function FallbacksCard({ controller, useSnapshot, t }: FallbacksCardProps): ReactNode;