dsh-llm-fallbacks 0.6.13 → 0.7.0

package/dist/config.d.ts

@@ -94,7 +94,6 @@ export interface FallbacksConfig {
     cooldownMs: number;
     revertPolicy: RevertPolicy;
     maxSwitchesPerStep: number;
-    alwaysModeRetryCap: number;
     /**
      * Preset-role injection switch: `'bundled'` declares the 5 preset roles
      * (spec §9.2) as seed rows on apply; `'none'` disables declaration.
@@ -105,19 +104,6 @@ export interface FallbacksConfig {
      * every resolved config carries a value via the schema default.
      */
     presets?: 'bundled' | 'none';
-    /**
-     * Dispatch-time LLM role auto-match switch (plan fallbacks-role-automatch
-     * Task 1): when `true` (default), a subagent-origin request with no
-     * explicit/rules-resolved role may have the best-fit declared role picked
-     * by the LLM; `false` reproduces today's behavior exactly. Optional on
-     * purpose, mirroring `presets` — a required field would break library
-     * consumers that construct `FallbacksConfig` literals with the existing
-     * keys (additive, non-breaking). The value domain is guarded by the
-     * schema (`z.boolean().default(true)` in `src/schema.ts`), and the
-     * runtime reads it defensively as `config.roleAutoMatch ?? true` (safe
-     * for direct constructors that omit it).
-     */
-    roleAutoMatch?: boolean;
     /**
      * Extra time-slot rows (plan fallbacks-timeslots Task 1, P5): the FIRST
      * matching row's chain becomes the effective root chain at request time;
@@ -196,8 +182,10 @@ export declare function validateFallbacksConfig(config: FallbacksConfig, logger:
 /**
  * Detect legacy (two-block-era) leftovers in a config SOURCE — the composed
  * object `source()` returns, or a raw settings document. Recognizes the
- * removed `chains` key, the removed `roles.default` field, the removed
- * role-entity fields `roles.list[].label` / `roles.list[].description`
+ * removed `chains` key, the removed always-mode retry cap and dispatch
+ * role-auto-match keys (`alwaysModeRetryCap` / `roleAutoMatch` — direction
+ * C, virtual-chain-only fallback), the removed `roles.default` field, the
+ * removed role-entity fields `roles.list[].label` / `roles.list[].description`
  * (renamed to `persona`), and `roles.rules[].role` values that reference no
  * declared `roles.list` id and are not the built-in `'inherit'`. Returns
  * descriptive key/role names; the gateway attaches them as `get().legacyKeys`

package/dist/cooldown.d.ts

@@ -1,15 +1,11 @@
 /**
- * Cooldown store + per-step failure set (spec §5.1; plan Task 2).
+ * Cooldown store (spec §5.1; plan Task 2).
  *
  * `CooldownStore` maps `provider/model` keys to an expiry epoch ms with lazy
  * evaluation: expired entries are dropped on read. `revertPolicy: 'never'`
  * is expressed by suppressing with `Infinity` — the entry never expires
  * within the session.
  *
- * `StepFailureSet` is the step's failed-model set (spec §5.1 `failed`).
- * `switchCount` / `maxSwitchesPerStep` judgement belongs to the caller
- * (Task 3) — this task only provides the data structure.
- *
  * @module dsh-llm-fallbacks/cooldown
  */
 /**
@@ -45,13 +41,3 @@ export declare class CooldownStore {
         untilEpochMs: number;
     }>;
 }
-/**
- * The current step's failed-model set (`${provider}/${model}` keys).
- */
-export declare class StepFailureSet {
-    private keys;
-    get size(): number;
-    add(key: string): void;
-    has(key: string): boolean;
-    reset(): void;
-}

package/dist/events.d.ts

@@ -15,15 +15,15 @@
  * @module dsh-llm-fallbacks/events
  */
 /**
- * Why a switch was decided (spec §5.1 `PendingSwitch.reason`).
+ * Why a switch was decided — a **history and bookkeeping vocabulary** since
+ * direction C, not a set of live decision paths.
  *
- * `role-inject` is the dispatch-time reason (plan fallbacks-role-automatch
- * Task 4): a subagent-origin agent's first request was re-routed to its
- * resolved role's chain head. It is ADDITIVE to the failure-time reasons —
- * the event shape stays a superset of the pre-feature payload, and existing
- * renderers show unknown reasons raw (AC-5). Unlike `trigger-code` /
- * `always-cap`, a `role-inject` event is NOT a failure decision: it carries
- * no pending switch / cooldown / failure bookkeeping (no `commit()`).
+ * `trigger-code` is the only reason the current code produces (the walk's
+ * swallowed trigger failure, and the blocked-attempt record that mirrors it).
+ * `always-cap` (retired always-mode cap) and `role-inject` (retired
+ * dispatch-time request override) survive only so legacy `fallbacks/switch`
+ * events and their renderers keep a label; nothing writes them any more, and
+ * an unknown reason still renders raw (AC-5).
  */
 export type FallbackSwitchReason = 'trigger-code' | 'always-cap' | 'role-inject';
 /** Durable payload of one provider/model switch (spec §5 table). */

package/dist/gateway.d.ts

@@ -26,9 +26,9 @@
  * Data: `get` reads the `FallbacksSettingsBridge` source — the same live
  * composed config the runtime reads (schema defaults → plugin-row base →
  * profile patch). There is NO hard-gate resolver (unlike advisor's
- * `resolveAdvisorConfig`): the fallbacks decision path runs at
- * `agent/request` time in `src/index.ts`, so the gateway returns the raw
- * composed config. There is NO config-level `enabled` key on the contract
+ * `resolveAdvisorConfig`): the fallbacks decision path runs inside the
+ * virtual route's chain walk (`src/chain-walk.ts`), so the gateway returns
+ * the raw composed config. There is NO config-level `enabled` key on the contract
  * (plan fallbacks-web-ux-alignment T2): the Plugins-page row toggle is the
  * master switch, the runtime gates read content presence
  * (`isFallbackActive` in `src/config.ts`), and a stored `enabled:` line is
@@ -96,6 +96,8 @@ export type SubagentPolicyRoute = {
     provider: string;
     model: string;
 };
+/** Settings namespace of the host's subagent-model-selection policy. */
+export declare const SUBAGENT_POLICY_SETTINGS_NS = "subagent-model-selection-settings";
 /**
  * Additive `/api/fallbacks/get` host-policy snapshot (spec D4 / T5).
  * Omitted only when the snapshot is unwired (3-arg constructor) so older

package/dist/index.d.ts

@@ -1,6 +1,7 @@
 /**
- * dsh-llm-fallbacks host half (plan Task 3: settings + waterfall + state
- * machine + events).
+ * dsh-llm-fallbacks host half: settings, the virtual chain row, the dispatch
+ * seam, role seeds and the diagnostics surfaces (direction C, plan
+ * dsh-022-rc1-upgrade).
  *
  * Cordis function plugin mounted by the profile bundle patch row
  * `llm-fallbacks` (see `bundle/cordis.patch.yml`), composed AFTER llm-retry.
@@ -11,33 +12,25 @@
  *   `apply` reads the Loader's live config reference, and the
  *   `settings/document-updated` listener re-derives the runtime caches —
  *   the old `installSection` setSource/onChange contract, spec §4).
- * - `agent/request-error` waterfall: inactive config (`isFallbackActive`) /
- *   code ∉ `triggerCodes`
- *   (**always mode included**) → `next()`; otherwise resolve role + chain,
- *   and when a candidate survives the filter (current / cooldown /
- *   step-failed / `provider/*`-missing-id) write the pending switch +
- *   cooldown + failure bookkeeping, then return
- *   `{ kind: 'retry' }` (own recovery, no `next()`).
- * - `agent/request` waterfall: apply a pending switch after `await next()`
- *   (provider/model override; the inherited `reasoningEffort` follows the
- *   upstream routeChanged rule — dropped on a route change unless explicitly
- *   named, preserved on a same-route override; spec D3); a
- *   root-origin `FallbacksChain/Auto` seed is served UNCHANGED (plan
- *   model-change-notice-loop Task 1 — the route the loop serves and records
- *   must equal the session selection, otherwise the host `model-selection`
- *   notice is re-armed on every step; the virtual adapter's `stream()`
- *   delegate is what reaches the chain head); then the always-mode cap check
- *   (count `llm/retry` events for the current turn/step/provider; ≥
- *   `alwaysModeRetryCap` → same decision path, reason `always-cap` —
- *   ADR-2).
- * - Per-agent state (`FallbackStateStore`): `agent/disposed` removes it,
- *   `agent/status` idle prunes per-step state defensively, plugin dispose
- *   clears everything (spec §6 — no residual state).
+ * - The virtual `FallbacksChain/Auto` adapter is the ONLY fallback path: its
+ *   `stream()` WALKS the session's chain (`src/chain-walk.ts`). No
+ *   `agent/request` / `agent/request-error` listener is registered — rc.1
+ *   rejects a request that changes the captured selection, and a
+ *   request-error retry `continue`s with that captured selection, so the old
+ *   waterfall could not route a retried attempt at all. Real-model sessions
+ *   therefore have no plugin fallback; `llm-retry` owns their recovery.
+ * - Subagents: the dispatch seam (`src/subagents-seam.ts`) mounts an
+ *   inheriting child on the virtual row by stamping its creation options
+ *   (design §1.3) — creation-time only, so a resumed child's own durable
+ *   selection always wins.
+ * - Per-agent state (`FallbackStateStore`): `agent/disposed` removes it, plugin
+ *   dispose clears everything (spec §6 — no residual state). The cooldown /
+ *   recovery circuit is the cross-call memory the walk reads; per-request
+ *   bookkeeping lives inside one walk.
  *
  * @module dsh-llm-fallbacks
  */
 import type { Context } from '@deepseek-ai/cordis';
-import type { Session } from '@deepseek-ai/dsh-session';
 import { detectLegacyKeys, validateFallbacksConfig, type FallbacksConfig } from './config.ts';
 import { Config } from './schema.ts';
 import { resolveChain } from './chains.ts';
@@ -113,7 +106,7 @@ export { Config };
 /** The plugin's composition config — the `fallbacks` settings schema (spec §4). */
 export type Config = FallbacksConfig;
 export type { FallbackSwitchReason, FallbacksSwitchEventData } from './events.ts';
-export type { AgentFallbackState, BlockedSwitchAttempt, FallbackStateStore, PendingSwitch, StepFailures, SwitchScope } from './state.ts';
+export type { AgentFallbackState, BlockedSwitchAttempt, FallbackStateStore } from './state.ts';
 /** @internal T5 test-seam types (mirrors `BlockedSwitchAttempt`; not public API). */
 export type { ChainHeadSource, EffectiveChainHead } from './state.ts';
 export { resolveRole, type AgentLike, type Origin, } from './roles.ts';
@@ -147,20 +140,6 @@ export declare function blockedAttempts(ctx: Context): ReadonlyMap<string, Block
  * plugin is applied.
  */
 export declare function chainHeads(ctx: Context): ReadonlyMap<string, EffectiveChainHead> | undefined;
-/**
- * Count durable `llm/retry` events for the current (turn, step, provider) in
- * **always mode** (ADR-2; spec §2 clause 5). Normal-mode retries belong to
- * llm-retry's bounded budget and must not preempt the fallback, so only
- * `mode: 'always'` events count toward `alwaysModeRetryCap` (T3 review
- * Minor 2 — the real event carries the discriminator, llm-retry types.ts).
- *
- * Fast path (T3 review Minor 4): the session log is append-ordered, so the
- * scan runs backwards and stops at the first event older than the target
- * (turn, step) — a long session's earlier turns are never scanned.
- *
- * Exported for direct unit testing of the counting + fast path.
- */
-export declare function countRetryEvents(session: Session, turn: number, step: number, provider: string): number;
 /**
  * The live config reference the Loader hands `apply` for a
  * volatile Config schema: an identity-stable `{ get }` view (cosmokit's