llm-relay 0.70.0 → 0.72.0

package/dist/config.d.ts

@@ -1,107 +1,6 @@
-import { type ProviderLimitsConfig } from "./configured-limits.js";
-import { type CredentialSlot, type ProviderCredentialConfig } from "./credential-fleet.js";
 import { type KeystoreOptions } from "./keystore.js";
-export type Mode = "detect" | "repair" | "strict";
-export type AuthHeader = "x-api-key" | "authorization";
-export type Kind = "anthropic" | "openai";
-export type ProviderTierType = "free" | "mixed" | "subscription";
-/**
- * The effort bands, WEAKEST FIRST — one declaration, and the type is derived from it rather than
- * the other way round.
- *
- * ⚠ Order is load-bearing: `dynamic-pools.ts` derives the degrade tail from this array's index, so
- * a band inserted out of order silently reorders which weaker members an exhausted pool falls back
- * to.
- *
- * ⚠ Why an ordered tuple and not four hand-lists: the member list stood restated in four places
- * across three modules, and only ONE of them was exhaustiveness-checked. `new Set<EffortLevel>([…])`
- * and `EffortLevel[]` both accept a SUBSET, and `cli.ts` validated against a bare `string[]` with
- * no link to the type at all — so a fifth band would have compiled everywhere and silently failed
- * in three of the four. `Record<EffortLevel, …>` (`EFFORT_FLOORS` in `benchmarks.ts`) is the shape
- * that already caught it, and is why that one is left as it is.
- */
-export declare const EFFORT_LEVELS: readonly ["low", "medium", "high", "xhigh"];
-/** Requested reasoning/capability band for an automatically discovered pool. */
-export type EffortLevel = (typeof EFFORT_LEVELS)[number];
-export declare const CLAUDE_TIER_NAMES: readonly ["opus", "sonnet", "haiku", "fable"];
-export type ClaudeTierName = (typeof CLAUDE_TIER_NAMES)[number];
-/** Which requests a client-specific offload rule may reroute. */
-export type OffloadScope = "subagents" | "all";
-/** One independently controlled offload rule. */
-export interface OffloadRule {
-    enabled: boolean;
-    scope: OffloadScope;
-    /**
-     * Refuse — loudly — rather than let this client's rerouted traffic reach a deployment that
-     * is not assessed `free` (see `assessCost`; `unknown` counts as paid on purpose). Applies to
-     * everything `subagentSpec` reroutes for this client, INCLUDING a per-call `@relay:` directive:
-     * the flag is the owner's standing "this lane never spends money", and a subagent prompt must
-     * not be able to out-rank it. The Anthropic passthrough is primary quota and is never free.
-     */
-    freeOnly?: boolean;
-}
-/**
- * `false`/`true` is the backwards-compatible global switch. The object form is keyed by
- * originating harness (`claude`, `codex`, or a future client name), with `default` available as
- * an explicit catch-all for a client that has not got a dedicated rule yet.
- */
-export type OffloadConfig = boolean | Record<string, OffloadRule>;
-export interface ReshaperConfig {
-    base: string;
-    model: string;
-    /** "anthropic": call /v1/messages. "openai": call /chat/completions (NIM/vLLM). */
-    kind: Kind;
-    /** Provider name for provider-aware credential resolution (auth alias + passthrough rules). */
-    provider?: string;
-    authEnv?: string;
-    authHeader: AuthHeader;
-    timeoutMs: number;
-}
-/**
- * What happens to the CALLER's own `Authorization`/`x-api-key` at a provider that declares no
- * `authEnv` of its own. See `buildForwardHeaders`.
- */
-export type CredentialMode = "passthrough" | "contained";
-/**
- * What shape a provider's own validator demands of the tool-call ids the relay puts on the wire.
- *
- *  - `"preserve"` — forward the caller's ids verbatim. The default everywhere, and what the relay
- *    did for its whole life before 2026-08-23: an id is linkage, so not touching it is the safest
- *    thing a translation can do.
- *  - `"strict9"` — rewrite every outbound `tool_calls[].id` / `tool_call_id` to mistral's stated
- *    `^[a-zA-Z0-9]{9}$` shape. Mistral's `mistral-common` validator enforces it on BOTH halves of
- *    the pair (and, from v13, linkage and uniqueness on top), so an Anthropic `toolu_01…` id is a
- *    hard 400 there — see `src/openai-request.ts`.
- */
-export type ToolCallIdMode = "preserve" | "strict9";
-/**
- * Whether a replayed assistant tool call must carry gemini 3.x's `thought_signature` field.
- *
- *  - `"none"` — emit nothing. The default everywhere, and byte for byte what this relay put on the
- *    wire before 2026-08-23.
- *  - `"sentinel"` — stamp Google's own documented opt-out token,
- *    `skip_thought_signature_validator`, at `tool_calls[].extra_content.google.thought_signature`
- *    on every replayed tool call. See `src/openai-request.ts` for the 400 that states the rule and
- *    for why echoing a REAL signature is not an option here.
- */
-export type ThoughtSignatureMode = "none" | "sentinel";
-/**
- * Per-provider WIRE-SHAPE quirks — things a specific host's request validator demands that the
- * protocol itself does not. Deliberately not routing configuration and deliberately not a
- * per-provider switch in `src/`: a labelled provider fact may live in code only while config can
- * override it (see the "Provider knowledge is data" invariant), which is exactly the shape here —
- * a base-host default that any explicit value beats in both directions.
- *
- * Two keys today, one per vendor rule the relay has first-party evidence for. An unknown key or
- * value is a HARD load error naming it: the `configured-limits` precedent — an ignored typo
- * silently no-ops while reading like a declaration that took effect.
- */
-export interface ProviderCompatConfig {
-    /** Absent ⇒ resolved from the base host by `resolveToolCallIdMode`. */
-    toolCallIds?: ToolCallIdMode;
-    /** Absent ⇒ resolved from the base host by `resolveThoughtSignatureMode`. */
-    thoughtSignature?: ThoughtSignatureMode;
-}
+import { type OffloadRule, type OffloadConfig, type ReshaperConfig, type ToolCallIdMode, type ThoughtSignatureMode, type ProviderCompatConfig, type RequestHeaders, type ResolvedTarget, type Config, type LaneProbeSettings } from "./config-types.js";
+export { EFFORT_LEVELS, CLAUDE_TIER_NAMES, type Mode, type AuthHeader, type Kind, type ProviderTierType, type EffortLevel, type ClaudeTierName, type OffloadScope, type OffloadRule, type OffloadConfig, type ReshaperConfig, type CredentialMode, type ToolCallIdMode, type ThoughtSignatureMode, type ProviderCompatConfig, type ProviderConfig, type Routing, type StickyRoutingConfig, type StickyConfig, type QuotaEnforcementConfig, type LatencyDemotionConfig, type HedgeConfig, type CliLaneTemplate, type PoolPolicy, type LadderRung, type RequestHeaders, type ResolvedTarget, type Config, type LaneProbeSettings, type McpSettings, } from "./config-types.js";
 /**
  * The resolved outbound tool-call-id shape for one provider.
  *
@@ -129,352 +28,10 @@ export declare function resolveThoughtSignatureMode(p: {
     base: string;
     compat?: ProviderCompatConfig;
 }): ThoughtSignatureMode;
-/** One HTTP backend provider in the registry (NIM, OpenRouter, Gemini API, …). */
-export interface ProviderConfig {
-    base: string;
-    /**
-     * "anthropic": provider speaks Anthropic Messages; forward as-is.
-     * "openai": provider is OpenAI-compatible (NIM/vLLM/OpenRouter/Gemini-openai);
-     * the proxy translates request+response via llm-bridge.
-     */
-    kind: Kind;
-    authEnv?: string;
-    /** Explicit multi-key declarations. Presence of an empty array means an empty fleet. */
-    credentials?: ProviderCredentialConfig[];
-    /**
-     * What to do with the caller's own credential when this provider declares no `authEnv`:
-     *  - `"passthrough"` — forward it. This is the declaration that makes an Anthropic
-     *    passthrough deliberate rather than a side effect of leaving `authEnv` out.
-     *  - `"contained"` — strip it and send none. The right answer for a keyless backend that
-     *    is not the caller's own vendor: a local daemon, a second relay, someone else's
-     *    Anthropic-format endpoint.
-     *
-     * Omitting it still forwards, so existing configs keep working, but config load warns for an
-     * `anthropic`-kind provider. "This backend needs no key of its own" and "send this host the
-     * user's subscription credential" are different intentions, and only the first one should be
-     * inferable from an omission. Illegal together with `authEnv` — that pair states both at once.
-     */
-    credentialMode?: CredentialMode;
-    /** Maximum concurrent requests for this provider credential domain; null/omitted is unlimited. */
-    maxConcurrent?: number | null;
-    /** Which header to inject the provider key into. Default: authorization (openai) / x-api-key (anthropic). */
-    authHeader: AuthHeader;
-    /** Backend request deadline in ms. Default 120000. */
-    timeoutMs: number;
-    /**
-     * Inter-byte stall watchdog for STREAMED responses, in ms. Once a stream is being served, the
-     * total `timeoutMs` deadline disarms — one flat deadline kills a healthy long generation at
-     * minute two while letting a dead stream hang until the same minute two — and this watchdog
-     * aborts only when NO byte arrives for this long. 0 keeps the old single-deadline behavior.
-     * Default 90000 (fork-validated in freellmapi). Adoption review §1.2.
-     */
-    stallTimeoutMs?: number;
-    /** "free": wholly free/free-tier catalog. "mixed": catalog contains free and paid models. */
-    tierType?: ProviderTierType;
-    /**
-     * Operator-asserted rate limits (spec §4 rung 3, basis "configured"). The provider-level block
-     * is the default for every credential of this provider; a slot's own `limits` overrides it per
-     * credential; a `models` entry overrides per deployment — each axis independently. See
-     * `src/configured-limits.ts`. These never refuse a request by themselves; they feed the
-     * availability/headroom surfaces.
-     */
-    limits?: ProviderLimitsConfig;
-    /**
-     * Wire-shape quirks this host's own request validator enforces. Absent keys fall back to a
-     * labelled base-host default (`resolveToolCallIdMode`, `resolveThoughtSignatureMode`); an
-     * explicit value always wins.
-     */
-    compat?: ProviderCompatConfig;
-    /** Web URL where users can sign up or obtain API keys. */
-    signupUrl?: string;
-}
-/**
- * How an inbound request's `model` maps to a provider + backend model.
- *  - `default`: fallback "provider/model" spec (string or array of target specs) when nothing else matches.
- *  - `tiers`: Claude tier name ("opus"/"sonnet"/"haiku"/"fable") → "provider/model" spec or array.
- *  - `pools`: named candidate list addressed as "pool/<name>" — the ranked, discovery-friendly
- *    alternative to pinning one model. A pool resolves to ALL its specs, so `benchmarkSort` ranks
- *    them and the existing failover walks them in order. This is the only routing form that lets a
- *    caller say "the best available coding model" instead of naming one; a bare namespaced spec is
- *    deliberately verbatim and never ranked.
- * A request may also address a provider directly with a namespaced model id
- * ("nim/z-ai/glm-5.2") — the prefix picks the provider, the rest is the model.
- */
-export interface Routing {
-    default: string | string[];
-    tiers: Record<string, string | string[]>;
-    pools?: Record<string, string[]>;
-    /** Dynamic pool policies are normalized separately from their materialized target arrays. */
-    poolPolicies?: Record<string, PoolPolicy>;
-    /**
-     * Pool → the specs in its DEGRADE TAIL: live members below the pool's effort band, appended so
-     * an exhausted band still has somewhere to go.
-     *
-     * Materialized alongside `pools`, never written to config.json — it is derived state, and the
-     * same refresh that rebuilds a pool rebuilds this. It exists so a served response can say the
-     * answer came from below the requested band: degrading automatically is only acceptable if it is
-     * never silent, since a capability downgrade that reads as an ordinary success is indistinguishable
-     * from having got what you asked for.
-     */
-    poolDegraded?: Record<string, string[]>;
-    /**
-     * Tier → spec for SUBAGENT requests only (`cc_is_subagent=true`). Lets the dispatcher pick a
-     * destination with the one per-call knob it actually has — the Agent tool's `model` enum
-     * (sonnet|opus|haiku|fable) — without writing an agent file. `default` catches anything that
-     * matches no tier. Main-conversation requests never consult this, which is what keeps
-     * `routing.tiers` free to stay on an Anthropic passthrough.
-     */
-    subagents?: Record<string, string>;
-    /**
-     * Offload admission. The legacy boolean is a global subagent-only switch. The object form is
-     * independently keyed by originating client (`claude`, `codex`, or a future name), and each
-     * rule chooses whether it applies to marked subagents only or to every conversation from that
-     * client. **Default false** in either form.
-     */
-    offload?: OffloadConfig;
-    benchmarkSort?: boolean;
-    /** Ephemeral session affinity. Boolean shorthand uses the 30m/1,000-entry defaults. */
-    sticky?: StickyConfig;
-    /**
-     * Quota-as-demotion enforcement (spec §5.4 / Gap 12). `enforce` (default true) lets a SPENT
-     * quota demote a candidate to the cooling band — provider-stated observations and
-     * operator-declared limits only. `enforceLearned` (default false) additionally admits limits
-     * LEARNED from vendor prose (decision M2): display-only until this is set to true.
-     *
-     * A demotion never drops and never refuses — it only reorders, expiring at the resetsAt the
-     * evidence stated. Unknown quota has no effect whatsoever.
-     */
-    quota?: QuotaEnforcementConfig;
-    /**
-     * Sustained MEASURED latency as a demotion term (owner decision 2026-08-30). **Default ON** —
-     * absent means enabled with the tunable defaults in `src/latency-demotion.ts`. `false` is the
-     * shorthand for `{ enabled: false }` and restores the pre-2026-08-30 behaviour exactly.
-     *
-     * Like quota, it only ever REORDERS: never drops, never refuses, and unmeasured latency has no
-     * effect whatsoever.
-     */
-    latency?: LatencyDemotionConfig;
-    /**
-     * Hedged attempts (owner proposal + decisions 2026-08-30,
-     * docs/hedged-attempts-design-2026-08-30.md §7). **Default ON**, and confined to deployments
-     * `assessCost()` calls FREE.
-     *
-     * ⚠ This is the FIRST behaviour here that does not merely reorder — it DUPLICATES a request onto
-     * a second candidate. The `CLAUDE.md` invariant reads "Acting on counts is optional, always
-     * announced, and may only reorder"; the owner amended it for this feature on 2026-08-30 and
-     * bounded the duplication three ways: free deployments only (D1), the loser aborted the moment a
-     * winner commits, and the response announcing it (`x-llm-relay-hedged`).
-     *
-     * `false` is the shorthand for `{ enabled: false }` and restores the pre-hedge behaviour exactly.
-     */
-    hedge?: HedgeConfig;
-    /**
-     * Background lane re-probing (owner decision 2026-08-29,
-     * docs/quota-reprobe-design-2026-08-29.md): keeping lane metadata fresh is the relay's own
-     * job, the way the ping loop already does for HTTP. **Default ON** — catalog probes are
-     * metadata commands that spend no quota, and quota probes fire only for buckets carrying an
-     * ACTIVE recorded death (an alive lane is re-tested by real use for free). Boolean shorthand
-     * toggles `enabled` with the default intervals. Absent on a hand-built `Config` means the
-     * defaults too — the cadence resolves absence itself.
-     */
-    laneProbe?: LaneProbeSettings;
-    /**
-     * Settings for `llm-relay mcp`, the stdio MCP server that exposes the dispatch verb to any MCP
-     * host. Read ONLY by that server — the daemon never consults this block, because the daemon
-     * never serves MCP and never spawns a lane for an HTTP turn.
-     *
-     * Absent means every default: the lane runs in the MCP server's own working directory unless the
-     * caller names another, and any existing directory is accepted.
-     */
-    mcp?: McpSettings;
-    /**
-     * Ordered dispatch ladder consulted by `/dispatch` — which LANE a host agent should hand a
-     * whole delegated task to, and in what order to fall back. Distinct from `subagents`, which
-     * routes one HTTP turn: a ladder rung may be an agent CLI that never traverses this proxy,
-     * because its quota is client-bound and only the vendor's own binary can spend it.
-     *
-     * Absent means the relay expresses no opinion and dispatch order stays the host's to choose.
-     */
-    ladder?: LadderRung[];
-    /** Tier-specific dispatch ladders. `dispatch --tier <name>` selects one. */
-    ladders?: Record<string, LadderRung[]>;
-    /**
-     * How to reach a `relay` rung's spec by SHELLING OUT, for a host whose own traffic does not
-     * reach this relay (see `src/host-routing.ts`). `/dispatch` substitutes the rung's spec into
-     * `{spec}` and the task into `{task}`, and hands back an ordinary `cli` invoke.
-     *
-     * Declared, never invented: the relay must not learn what a `claude` binary is or how to
-     * address one — that is the provider/model-agnostic invariant applied to lane rendering. Absent
-     * means no transposition is possible, and such rungs are reported unreachable rather than
-     * quietly replaced with something the operator never authorised.
-     */
-    cliLane?: CliLaneTemplate;
-}
-export interface StickyRoutingConfig {
-    enabled: boolean;
-    ttlMs?: number;
-    maxSessions?: number;
-}
-export type StickyConfig = boolean | StickyRoutingConfig;
-/**
- * `routing.quota`. Both keys are optional booleans with deliberate defaults: enforcement of
- * provider-stated/derived-from-configured figures is ON unless switched off (decision M1), and
- * learned prose parses stay display-only unless explicitly admitted (decision M2). An object with
- * neither key is legal and means exactly the defaults — writing it down is documentation, not a
- * behaviour change.
- *
- * G2 adds `hardCaps` (default true): an operator who wrote a `hard` block inside a `limits`
- * declaration meant it, so the refusal ceilings are live unless this switch turns every one of
- * them into a soft limit. false demotes nothing per request and logs nothing.
- */
-export interface QuotaEnforcementConfig {
-    /** Default true. false disables quota demotion entirely. */
-    enforce?: boolean;
-    /** Default false. true additionally lets `derived:learned` figures gate routing. */
-    enforceLearned?: boolean;
-    /** Default true. false treats every `hard` cap as an ordinary (soft) configured limit. */
-    hardCaps?: boolean;
-}
-/**
- * `routing.latency` — sustained MEASURED latency as a demotion term (owner decision 2026-08-30).
- *
- * **Default ON.** A candidate whose measured p95 exceeds `p95Ms`, over at least `minSamples`
- * measurable samples, joins the cooling band instead of leading the walk. It is a demotion, so the
- * worst case is a reorder: nothing is dropped and nothing is refused.
- *
- * `false` is the documented shorthand for `{ enabled: false }` and restores the pre-2026-08-30
- * behaviour exactly. An object with no keys is legal and means the defaults — writing it down is
- * documentation, not a behaviour change.
- *
- * The thresholds live in `src/latency-demotion.ts` beside the measurement that calibrated them.
- */
-export interface LatencyDemotionConfig {
-    /** Default true. false disables latency demotion entirely. */
-    enabled?: boolean;
-    /** Fallback ceiling: measured absolute p95 in ms. Above it, the candidate is demoted. */
-    p95Ms?: number;
-    /**
-     * PRIMARY ceiling: measured p95 latency per OUTPUT TOKEN, in ms.
-     *
-     * Absolute latency cannot compare a probe with a generation - a probe asks for one token, a real
-     * request may produce hundreds and amortise the same fixed overhead. The per-token rate is the
-     * fair figure, so it is tested first, over real request samples only.
-     */
-    msPerToken?: number;
-    /** Minimum measurable samples before latency may demote anything at all. */
-    minSamples?: number;
-}
-/**
- * `routing.hedge` — start the NEXT candidate beside a slow in-flight attempt, instead of after it
- * (owner proposal 2026-08-30; the four decisions are in
- * `docs/hedged-attempts-design-2026-08-30.md` §7).
- *
- * **Default ON, free deployments only.** That is owner decision D1, taken against the
- * recommendation of off-by-default. `assessCost()` treats an UNKNOWN price as paid, so the rule is
- * fail-safe in the only direction that matters: a duplicate can never land on a deployment whose
- * price this relay cannot establish. The stated cost is that hedging silently does not fire on many
- * members whose prices are simply unpublished.
- *
- * ⚠ **Hedging DUPLICATES; every other term here only reorders.** `false` is the documented
- * shorthand for `{ enabled: false }` and restores the pre-hedge behaviour exactly, byte for byte.
- * An object with no keys is legal and means the defaults.
- *
- * The thresholds live in `src/hedge-trigger.ts`. ⚠ `margin` and `minSamples` are still PLACEHOLDERS
- * awaiting calibration and say so at their definition — do not quote them as measurements.
- * `msPerInputToken` IS calibrated (`scripts/calibrate-hedge-floor.mjs`, 2026-09-04) — see its own
- * doc comment in `hedge-trigger.ts` for why the fit came back out of range and what shipped instead.
- */
-export interface HedgeConfig {
-    /** Default true. false disables hedging entirely. */
-    enabled?: boolean;
-    /**
-     * The floor's flat component, in ms. Owner direction 2026-09-04: the floor is no longer flat on
-     * its own — see `msPerInputToken` — but this still bounds the SMALL-prompt case, where the
-     * size-scaled component is negligible. Without it a deployment with a tiny p90 is hedged on
-     * ordinary noise, and a fast pool duplicates almost every request.
-     */
-    minFloorMs?: number;
-    /**
-     * LEGACY alias of `minFloorMs`, kept for backward compatibility — an operator config written
-     * before 2026-09-04 (`{"floorMs": 8000}`) keeps loading and keeps meaning exactly what it always
-     * meant: the floor never drops below 8000 ms. Honoured only when `minFloorMs` itself is absent;
-     * `resolveHedgeSettings` in `hedge-trigger.ts` is the ONE place that resolves the alias, so a new
-     * caller of that function can never re-decide the precedence.
-     */
-    floorMs?: number;
-    /**
-     * The floor's size-scaled component, in ms per estimated INPUT token
-     * (`estimateRequestTokens` in `metadata.ts`). Without it a large prompt is hedged against the
-     * time it simply takes a healthy deployment to read the prompt, not against real slowness.
-     */
-    msPerInputToken?: number;
-    /** How far past the expected time an attempt must run before a hedge starts. */
-    margin?: number;
-    /** Minimum samples before a measured statistic may set the bar instead of the floor. */
-    minSamples?: number;
-}
-/**
- * Template for rendering a `relay` rung as a shelled-out CLI command.
- *
- * Same executable shape as a `cli` rung — the host runs `command` with `args`, applying `env`
- * (string sets, `null` unsets) — with one extra placeholder: `{spec}`, replaced by the rung's
- * routing spec so ONE template serves every pool and pinned model in the ladder.
- */
-export interface CliLaneTemplate {
-    command: string;
-    /** Must contain `{spec}`; `{task}` too, on the same reasoning as a cli rung's args. */
-    args: string[];
-    /** Applied by the host when spawning. Placeholders are never substituted here. */
-    env?: Record<string, string | null>;
-}
-/** A fixed configured prefix followed by automatically discovered free models. */
-export interface PoolPolicy {
-    preferred: string[];
-    include: "free";
-    /** Permanent user tombstones, applied to both the fixed prefix and discovered tail. */
-    exclude?: string[];
-    /** Optional evidence-aware effort band for the discovered tail. */
-    effort?: EffortLevel;
-}
-/**
- * One rung of `routing.ladder`.
- *
- * `cli` rungs are executed by the HOST (the relay never spawns a process — it is a proxy, not a
- * process supervisor); `relay` rungs are addressed through this proxy in the ordinary way.
- * `quota` names the balance a rung draws on so that rungs sharing one are cooled down together
- * and rungs that merely share a binary are not: one CLI can meter two model families against
- * two independent balances, and treating those as one bucket would skip a live lane.
- */
-export interface LadderRung {
-    id: string;
-    kind: "cli" | "relay";
-    /** Parked rungs stay visible in the ladder but are never auto-selected. Default true. */
-    enabled: boolean;
-    quota?: string;
-    note?: string;
-    /** cli rungs: the binary to run, and its args — one of which must contain the task placeholder. */
-    command?: string;
-    args?: string[];
-    /**
-     * cli rungs: environment the HOST applies when spawning the command. A string value sets the
-     * variable; `null` unsets an inherited one. Both directions are load-bearing for the lane this
-     * exists for — a `claude -p` child routed through this proxy: `ANTHROPIC_BASE_URL` must be SET
-     * (a terminal-spawned `claude` honours it even though Claude Desktop pins its own sessions to
-     * api.anthropic.com), and `CLAUDECODE`/`CLAUDE_CODE_SSE_PORT`/`CLAUDE_CODE_ENTRYPOINT`/
-     * `ANTHROPIC_API_KEY` must be UNSET or a child spawned from inside a Claude session inherits
-     * the parent's harness wiring and refuses to start cleanly. The task placeholder is never
-     * substituted here — env values are operator-authored routing, not task content.
-     */
-    env?: Record<string, string | null>;
-    /** relay rungs: the spec to address (`pool/<name>`, `<provider>/<model>`, a provider name). */
-    spec?: string;
-}
 /** Reserved provider-namespace prefix for `pool/<name>` routing. */
 export declare const POOL_PREFIX = "pool";
 /** Reserved model name for auto-dispatch to the ladder's first ready relay rung. */
 export declare const AUTO_MODEL = "auto";
-/** The request headers needed for protocol-specific subagent markers. */
-export type RequestHeaders = Readonly<Record<string, string | string[] | undefined>>;
 /** True when this request is a marked Claude Code or local Codex child turn. */
 export declare function isSubagentRequest(reqJson: unknown, headers?: RequestHeaders): boolean;
 /**
@@ -533,95 +90,6 @@ export declare function anyOffloadEnabled(cfg: Pick<Config, "routing">): boolean
  * fail and name what IS configured.
  */
 export declare function subagentSpec(reqJson: unknown, model: string | null, cfg: Config, headers?: RequestHeaders, client?: string): string | null;
-/** A request routed to a concrete provider + backend model. */
-export interface ResolvedTarget {
-    provider: string;
-    base: string;
-    kind: Kind;
-    /** Real backend model id (required for openai; absent = anthropic passthrough). */
-    model?: string;
-    authEnv?: string;
-    /** Normalized non-secret credential slots for this provider. */
-    credentialSlots?: readonly CredentialSlot[];
-    /** Carried from the provider: whether the caller's own credential may travel to this target. */
-    credentialMode?: CredentialMode;
-    authHeader: AuthHeader;
-    timeoutMs: number;
-    /** Carried from the provider: inter-byte stall watchdog for streamed responses. */
-    stallTimeoutMs?: number;
-    /**
-     * RESOLVED outbound tool-call-id shape (`resolveToolCallIdMode`) — an explicit
-     * `compat.toolCallIds` or the labelled base-host default. Resolved here so the request mapper
-     * is handed a mode and never a provider identity to re-derive one from. Absent (a hand-built
-     * target) reads as `"preserve"`, which is the pre-2026-08-23 behaviour byte for byte.
-     */
-    toolCallIds?: ToolCallIdMode;
-    /**
-     * RESOLVED thought-signature mode (`resolveThoughtSignatureMode`) — an explicit
-     * `compat.thoughtSignature` or the labelled base-host default. Resolved here for the same reason
-     * as `toolCallIds`: the request mapper is handed a mode, never a provider identity to sniff one
-     * from. Absent (a hand-built target) reads as `"none"` — the pre-2026-08-23 bytes exactly.
-     */
-    thoughtSignature?: ThoughtSignatureMode;
-}
-export interface Config {
-    host: string;
-    port: number;
-    providers: Record<string, ProviderConfig>;
-    routing: Routing;
-    mode: Mode;
-    /** Explicit global reshaper override; otherwise repair reshapes on the resolved target itself. */
-    reshaper?: ReshaperConfig;
-    /**
-     * Ranked reshaper candidates, from `reshaper: { pool: "<name>" }`. Tried in order, so a single
-     * de-listed model cannot take repair down with it — the whole point of not pinning one model.
-     * `reshaper` is candidates[0] so every existing single-reshaper path keeps working unchanged.
-     */
-    reshaperCandidates?: ReshaperConfig[];
-    /** Dynamic reshaper pool resolved lazily after its catalog-backed tail is materialized. */
-    reshaperPool?: {
-        name: string;
-        timeoutMs?: number;
-    };
-    repair: {
-        maxAttempts: number;
-        destructiveTools: string[];
-    };
-    /**
-     * Wall-clock ceiling (ms) on STARTING further failover attempts within one request's pool
-     * walk. The first two attempts are always allowed and an attempt already in flight is never
-     * aborted — the budget bounds the walk, not the answer. 0 disables. Absent ⇒ the server's
-     * DEFAULT_WALK_BUDGET_MS (45s).
-     */
-    walkBudgetMs?: number;
-    /** Maximum inbound request-body size in bytes. Absent ⇒ 36 MiB. */
-    maxBodyBytes?: number;
-    log: {
-        level: "metadata" | "silent";
-        file: string | null;
-        maxBytes?: number;
-    };
-    /**
-     * Providers the onboarding nudge must stop asking about (`leave_me_alone` in config.json).
-     *
-     * Scope is deliberately narrow: it silences the "❌ Missing Key / 👉 get one here" prompt in
-     * `llm-relay onboard`, and nothing else. Suppressed providers still appear in `llm-relay keys`,
-     * in `/registry` and in every status surface — silencing a nudge is not hiding state, and a
-     * provider that vanished from the status commands would be undebuggable later.
-     *
-     * Names that match no known provider are legal (see `parseLeaveMeAlone`).
-     */
-    leaveMeAlone?: string[];
-    /** Path this config was loaded from. Set by `loadConfig`; absent for hand-built test configs.
-     *  Only consumer is the runtime offload toggle, which persists back to the same file. */
-    sourcePath?: string;
-    /**
-     * Non-fatal load-time problems (a provider disabled for an unset `${ENV}`, a pool member
-     * dropped with it). Present so startup can print them — a degraded config that boots
-     * silently is how you end up running on one provider without noticing.
-     */
-    warnings?: string[];
-}
 /**
  * Tools a repaired call is never allowed to name. THE single definition — the
  * shipped config template, config.example.json and the docs all derive from or
@@ -674,26 +142,6 @@ export interface ConfigOverrides {
 }
 /** Load + validate a config file, failing loudly on anything unusable. */
 export declare function loadConfig(path: string, overrides?: ConfigOverrides, keystoreOptions?: KeystoreOptions): Config;
-/** `llm-relay mcp` settings — see the `mcp` field doc on `Routing`. */
-export interface McpSettings {
-    /**
-     * Directories a caller-supplied `cwd` must sit under. Absent or empty ⇒ no bound beyond the
-     * directory existing.
-     *
-     * ⚠ Offered, never imposed. The MCP caller is already a trusted agent on the operator's own
-     * machine, and defaulting to a bound would make the tool useless for its stated purpose. Whether
-     * to narrow it is the operator's decision to record here, not this file's to assume.
-     */
-    allowedRoots?: string[];
-}
-/** Background lane re-probing settings — see the `laneProbe` field doc on `Routing`. */
-export interface LaneProbeSettings {
-    enabled: boolean;
-    /** Gate between quota probes of ONE dead bucket. A probe spends that lane's quota. */
-    quotaIntervalMs: number;
-    /** Gate between catalog re-probes of ONE lane. Metadata commands, no quota spent. */
-    catalogIntervalMs: number;
-}
 export declare const DEFAULT_LANE_PROBE: LaneProbeSettings;
 /** Parse the legacy global switch or the independently keyed client-rule form. */
 export declare function parseOffload(raw: unknown): OffloadConfig;

package/dist/config.js

@@ -5,8 +5,8 @@ import { CREDENTIAL_LABEL_PATTERN, makeCredentialId } from "./credential-id.js";
 import { parseConfiguredLimits } from "./configured-limits.js";
 import { providerCredentialSlots, resolveCredentialSlot, } from "./credential-fleet.js";
 import { createKeystoreResolutionWalk, keystoreStatus, listEntries, } from "./keystore.js";
-export const EFFORT_LEVELS = ["low", "medium", "high", "xhigh"];
-export const CLAUDE_TIER_NAMES = ["opus", "sonnet", "haiku", "fable"];
+import { EFFORT_LEVELS, CLAUDE_TIER_NAMES, } from "./config-types.js";
+export { EFFORT_LEVELS, CLAUDE_TIER_NAMES, } from "./config-types.js";
 const EFFORT_LEVEL_SET = new Set(EFFORT_LEVELS);
 const COMPAT_KEYS = ["toolCallIds", "thoughtSignature"];
 const TOOL_CALL_ID_MODES = ["preserve", "strict9"];