dsh-autotier 0.1.0 → 0.2.0

package/AGENTS.md

@@ -21,9 +21,28 @@ records repo-local decisions.
 - `src/service.ts` — `ctx.autotier` (`status()` and the live settings scope).
 - `src/types.ts` — shared vocabulary (tier ids, effort ids, routing modes,
   scenarios, route/status shapes).
+- `src/wire.ts` — the `tier` Remote wire vocabulary: `TierStatus` (the public
+  `AutotierStatus` plus an additive `session` view), `TierCatalog`, their zod v4
+  codecs, and the three invocation descriptors shared verbatim by the host
+  manifest and the client contribution.
+- `src/typert.host.ts` — the hand-written host Typert manifest exported as
+  `./typert`; the harness's typert-loader registers the `tier` invocations from
+  it when the plugin mounts.
+- `src/tier-remote.ts` — `TierRemoteService` (`TypertRemoteService`, namespace
+  `tier`): `status(agentId?)` / `catalog()` / `setMode(mode, agentId?)`. The
+  override it writes is the same per-agent `RouteState.override` the router and
+  `/tier` read; `agents` is read optionally through the injected resolver.
+- `src/client/` — browser half: `$mount`s the Remote contribution, registers the
+  composer pill into `conversation.input.left` (id `tier-pill`) and the Settings
+  card into `settings.plugins.tab` (id `autotier`), with a pure presenter
+  (`present.ts`), inline scoped stylesheet (`styles.ts`), and en/zh dictionaries
+  (`locales.ts`). The slot registry is read through a local structural
+  `SlotsFace` (its owning package differs across host lines).
 - `tests/` — vitest over the REAL published `0.1.2-rc.1` host packages
   (`Context`, `SessionStore`, `SystemPrompt`, `ToolRuntime`, `CommandRuntime`,
-  in-memory `SettingsProvider`) plus one real Loader composition.
+  in-memory `SettingsProvider`) plus one real Loader composition. The browser
+  half is covered through its pure units (wire codecs, presenter, dictionaries)
+  and the `tier` service through a real mount with a scripted `agents` face.
 
 ## Hard rules applied here
 
@@ -63,8 +82,12 @@ table.
 `typescript` + `tsdown` are regular `dependencies` (the git channel's `prepare`
 builds with production dependencies alone). `scripts/prepare.mjs` wipes `lib/`,
 emits tsc declarations into `lib/types`, then runs tsdown (tsdown `clean` stays
-OFF so the declarations survive). `pnpm-workspace.yaml` declares
-`allowBuilds: { esbuild: true }`.
+OFF so the declarations survive). Two build faces: the node half
+(`lib/index.js` + `lib/typert.host.js`) and the browser half (`lib/client.js`),
+whose CJS factory is wrapped in `window.__ModuleLoader__.load({ id, factory })`
+with the shell's platform modules (`react`, `react/jsx-runtime`, the
+`@deepseek-ai/dsh-client-*` singletons) left external and zod inlined.
+`pnpm-workspace.yaml` declares `allowBuilds: { esbuild: true }`.
 
 ## Checks
 

package/CHANGELOG.md

@@ -5,6 +5,65 @@ All notable changes to this project are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.2.0] - 2026-09-09
+
+### Added
+
+- **Browser half: a Settings card and a composer tier pill.** The plugin now
+  ships a `tier` Typert Remote service (`tier/status`, `tier/catalog`,
+  `tier/setMode`) behind a hand-written `./typert` host manifest, and a client
+  bundle that registers the composer pill into `conversation.input.left`
+  (id `tier-pill`) and the autotier card into the Plugins settings section
+  (`settings.plugins.tab`, id `autotier`). The pill shows the session's effective
+  mode (`AUTO` / `STRONG` / `CHEAP` / `OFF`) with an escalation badge and cycles
+  the session override on click; the card offers the full
+  `auto | strong | cheap | delegated | off` selector, the read-only tier
+  landings, the live session state, and a model-catalog dropdown fed by the live
+  `ctx.llm` registry. Copy ships in English and Simplified Chinese.
+- `TierStatus` extends the public `AutotierStatus` additively with a `session`
+  view (override, effective mode, applied tier and source, escalation, plan
+  mode, guard denials); the host still serves `ctx.autotier.status()` unchanged.
+- `zod` is now a runtime dependency (the strict wire codecs on both faces) and
+  the client peers (`dsh-api-remotes`, `dsh-client-connection`,
+  `dsh-client-locale`, `dsh-client-ui-conversation`, `dsh-client-ui-settings`,
+  `dsh-client-ui-slots`, `dsh-typert-protocol`) are declared as optional peers.
+
+### Notes
+
+- The session override stays runtime-only: `auto` clears it, and a plugin reload
+  restores the `cordis.yml` routing mode. Nothing is persisted.
+- `pnpm run verify:artifacts` now asserts the two new shipped faces
+  (`lib/typert.host.js` with its manifest shape, `lib/client.js` with its
+  ModuleLoader handshake and external platform modules).
+- The five-language READMEs are not updated in this change; the client copy is
+  English + Simplified Chinese only.
+
+## [0.1.1] - 2026-09-09
+
+### Added
+
+- **Route pre-flight against the live registry.** Before a tier landing is
+  written into the request configuration, the plugin now checks the two facts
+  that would fail the request outright: the provider route must be registered,
+  and the target model must declare the configured reasoning effort. An
+  unregistered provider redirects to a registered fallback chain entry; an
+  unsupported effort is dropped so the adapter default applies; an adapter that
+  cannot answer is treated leniently. Both answers are cached per
+  `provider/model`, and each degradation is logged once.
+- Compat workflow now runs its profile job over a matrix of both published
+  harness lines (`0.1.2-rc.1` and `0.1.5-alpha.1`), so drift in either is caught
+  automatically.
+
+### Changed
+
+- Peer ranges name both published lines explicitly
+  (`>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1 <0.2.0`): a semver range whose only
+  prerelease comparator sits on an earlier version tuple does not admit a later
+  alpha, so the previous range left `0.1.5-alpha.1` unsatisfied.
+- `dsh.compatibility.dshReleases` and the five READMEs now declare
+  `0.1.5-alpha.1` compatible after an end-to-end verification (real profile
+  install, `--dump-config` row, keyless headless smoke).
+
 ## [0.1.0] - 2026-09-09
 
 ### Added

package/README.es.md

@@ -19,10 +19,14 @@ strong con un TTL de retorno.
 
 | Harness | Estado |
 |---|---|
-| `@deepseek-ai/dsh` `0.1.2-rc.1` | compatible (es lo que CI verifica y lo que instala el flujo compat) |
-| `0.1.5-alpha.1` (la línea actual del checkout) | verificado por tipos contra sus caras publicadas; el smoke de extremo a extremo corre en `0.1.2-rc.1` |
+| `@deepseek-ai/dsh` `0.1.2-rc.1` | compatible; el flujo compat instala esta línea de extremo a extremo |
+| `@deepseek-ai/dsh` `0.1.5-alpha.1` | compatible; verificada de extremo a extremo (perfil real, fila en `--dump-config`, smoke keyless) y en la matriz compat |
 | `@deepseek-ai/cordis` `^4.0.2`, `@deepseek-ai/schemastery` `^3.18.2` | base de peers |
 
+Los rangos de peers nombran ambas líneas publicadas (`>=0.1.2-rc.1 <0.2.0 ||
+>=0.1.5-alpha.1 <0.2.0`), porque un rango cuyo único comparador de prerelease
+está en una tupla anterior no admite un alpha posterior. Se refrescan por ola.
+
 El plugin vive solo en el plano host y no necesita un preset propio: la fila host
 se aplica a todas las sesiones. Una sección de prompt en *tu* preset es opcional
 y solo hace visibles las decisiones al modelo (véase [Instalación y desinstalación](#instalación-y-desinstalación)).

package/README.hi.md

@@ -17,10 +17,15 @@ DeepSeek Harness के लिए स्वचालित मॉडल-स्
 
 | Harness | स्थिति |
 |---|---|
-| `@deepseek-ai/dsh` `0.1.2-rc.1` | संगत (CI इसी की जाँच करता है और compat वर्कफ़्लो इसे इंस्टॉल करता है) |
-| `0.1.5-alpha.1` (वर्तमान checkout लाइन) | इसके प्रकाशित type faces के विरुद्ध टाइप-जाँच; end-to-end smoke `0.1.2-rc.1` पर चलता है |
+| `@deepseek-ai/dsh` `0.1.2-rc.1` | संगत; compat वर्कफ़्लो इस लाइन को end-to-end इंस्टॉल करता है |
+| `@deepseek-ai/dsh` `0.1.5-alpha.1` | संगत; end-to-end सत्यापित (वास्तविक profile, `--dump-config` पंक्ति, keyless smoke) और compat मैट्रिक्स में |
 | `@deepseek-ai/cordis` `^4.0.2`, `@deepseek-ai/schemastery` `^3.18.2` | peer आधार |
 
+peer ranges दोनों प्रकाशित लाइनें स्पष्ट रूप से लिखती हैं (`>=0.1.2-rc.1 <0.2.0
+|| >=0.1.5-alpha.1 <0.2.0`), क्योंकि जिस range का एकमात्र prerelease comparator
+पुराने tuple पर हो वह बाद के alpha को स्वीकार नहीं करता। हर प्रकाशन-लहर पर
+रिफ़्रेश होता है।
+
 यह प्लगइन केवल host plane पर रहता है और अपना preset नहीं माँगता: host पंक्ति
 हर सत्र पर लागू होती है। *आपके* preset में एक प्रॉम्प्ट खंड वैकल्पिक है और
 केवल मॉडल को निर्णय दिखाता है ([इंस्टॉल और अनइंस्टॉल](#इंस्टॉल-और-अनइंस्टॉल) देखें)।

package/README.md

@@ -17,10 +17,15 @@ escalate to the strong tier with a TTL fallback.
 
 | Harness | Status |
 |---|---|
-| `@deepseek-ai/dsh` `0.1.2-rc.1` | compatible (this is what CI type-checks and the compat workflow installs) |
-| `0.1.5-alpha.1` (the current harness checkout line) | type-checked against its published type faces; the end-to-end smoke runs on `0.1.2-rc.1` |
+| `@deepseek-ai/dsh` `0.1.2-rc.1` | compatible; the compat workflow installs this line end-to-end |
+| `@deepseek-ai/dsh` `0.1.5-alpha.1` | compatible; verified end-to-end (real profile install, `--dump-config` row, keyless headless smoke) and in the compat matrix |
 | `@deepseek-ai/cordis` `^4.0.2`, `@deepseek-ai/schemastery` `^3.18.2` | peer baseline |
 
+Peer ranges name both published lines explicitly (`>=0.1.2-rc.1 <0.2.0 ||
+>=0.1.5-alpha.1 <0.2.0`), because a semver range whose only prerelease
+comparator sits on an earlier version tuple does not admit a later alpha.
+They are refreshed per published wave.
+
 The plugin is host-plane only. It needs no agent preset of its own: the host
 row applies to every session. A one-line prompt section in *your* preset is
 optional and only makes the router's decisions visible to the model (see

package/README.pt.md

@@ -18,10 +18,14 @@ retorno.
 
 | Harness | Estado |
 |---|---|
-| `@deepseek-ai/dsh` `0.1.2-rc.1` | compatível (é o que a CI verifica e o que o fluxo compat instala) |
-| `0.1.5-alpha.1` (a linha atual do checkout) | verificado por tipos contra suas faces publicadas; o smoke ponta a ponta roda em `0.1.2-rc.1` |
+| `@deepseek-ai/dsh` `0.1.2-rc.1` | compatível; o fluxo compat instala esta linha ponta a ponta |
+| `@deepseek-ai/dsh` `0.1.5-alpha.1` | compatível; verificada ponta a ponta (perfil real, linha no `--dump-config`, smoke keyless) e na matriz compat |
 | `@deepseek-ai/cordis` `^4.0.2`, `@deepseek-ai/schemastery` `^3.18.2` | base de peers |
 
+Os ranges de peers nomeiam as duas linhas publicadas (`>=0.1.2-rc.1 <0.2.0 ||
+>=0.1.5-alpha.1 <0.2.0`), porque um range cujo único comparador de prerelease
+está numa tupla anterior não admite um alpha posterior. São atualizados por onda.
+
 O plugin vive apenas no plano host e não precisa de preset próprio: a linha host
 vale para todas as sessões. Uma seção de prompt no *seu* preset é opcional e
 apenas torna as decisões visíveis ao modelo (veja [Instalação e desinstalação](#instalação-e-desinstalação)).

package/README.zh.md

@@ -14,10 +14,14 @@ DeepSeek Harness 的自动模型分档路由：一条用户指令进来，一个
 
 | Harness | 状态 |
 |---|---|
-| `@deepseek-ai/dsh` `0.1.2-rc.1` | 兼容（CI 的类型检查与 compat 工作流安装的就是它） |
-| `0.1.5-alpha.1`（当前宿主 checkout 线） | 对照其已发布类型面做类型检查；端到端冒烟跑在 `0.1.2-rc.1` 上 |
+| `@deepseek-ai/dsh` `0.1.2-rc.1` | 兼容；compat 工作流对该线做端到端安装验证 |
+| `@deepseek-ai/dsh` `0.1.5-alpha.1` | 兼容；已端到端实测（真实 profile 安装、`--dump-config` 行、keyless headless 冒烟）并纳入 compat 矩阵 |
 | `@deepseek-ai/cordis` `^4.0.2`、`@deepseek-ai/schemastery` `^3.18.2` | peer 基线 |
 
+peer 范围显式列出两条已发布线（`>=0.1.2-rc.1 <0.2.0 || >=0.1.5-alpha.1
+<0.2.0`）——因为仅含较早版本元组预发布比较符的 semver 范围无法接纳更晚的 alpha；
+每次发布波同步刷新。
+
 本插件只驻留 host 平面，不需要自带 agent preset：host 行对所有会话生效。
 在你的 preset 中加一段提示是可选项，仅用于让模型看见路由决策
 （见[安装与卸载](#安装与卸载)）。

package/THIRD_PARTY_NOTICES.md

@@ -1,5 +1,36 @@
 # Third-party notices
 
+## zod (https://github.com/colinhacks/zod)
+
+The `tier` Remote wire codecs (`src/wire.ts`) are zod v4 schemas. `zod` is a
+declared runtime dependency (MIT) and its library code is inlined into the built
+`lib/index.js`, `lib/typert.host.js` and `lib/client.js` bundles; no zod source
+is modified.
+
+```
+MIT License
+
+Copyright (c) 2020 Colin McDonnell
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+```
+
 ## dsh-tier-router (`lib/pure.js`)
 
 The high-risk command guard in `src/guard-rules.ts` is a port of the rule table

package/docs/roadmap-v0.2.md

@@ -0,0 +1,114 @@
+# v0.2 roadmap: concrete designs for the deferred items
+
+This file records the researched, decision-ready design for every capability
+that is deliberately **not** in 0.1.x. Each entry states the goal, the exact
+mechanism, the acceptance criteria, and why it is not enabled yet. Nothing here
+is speculation: the seams named below were read in the harness checkout
+(`dsh-v0.1.5-alpha.1-13`).
+
+## 1. Browser half (Settings card + composer pill)
+
+**Status:** implemented on the `v0.2.0` line (client bundle + Typert Remote
+`tier/status|setMode|catalog`); see `src/client/`, `src/wire.ts`,
+`src/typert.host.ts`.
+
+**Why it was deferred:** the host surface was complete first (`ctx.autotier`),
+and the client half needs the browser bundle pipeline (tsdown CJS face wrapped
+in `window.__ModuleLoader__.load`), which is a packaging change rather than a
+routing change.
+
+## 2. Fingerprint posterior persistence
+
+**Goal:** a restarted harness keeps the per-shape cheap/strong win rates instead
+of re-learning from the judge's cold start.
+
+**Mechanism (chosen):** a dedicated settings namespace, not the user-facing
+`autotier` one:
+
+```ts
+ctx.settings.register('autotier-fingerprints', FingerprintSchema, { applies: 'live' })
+```
+
+- `FingerprintSchema` = `{ version: 1, entries: [{ key, cheapOK, cheapN, strongOK, strongN, observations, lastSeen }] }`, capped at the same LRU 2000.
+- Writes are **debounced** (≥30 s between flushes and one final flush on
+  `ctx.effect` disposal) and use `replace()` on the whole section, so a user
+  editing the document cannot produce a partial merge.
+- On mount, `PosteriorTable.hydrate(section)` validates and loads; a
+  `stateVersion`/`version` mismatch discards the section (the same rule the
+  session-projection cache uses).
+- A namespace that is absent (a deployment without settings) degrades to the
+  current in-memory behaviour — the plugin never depends on persistence.
+
+**Why not the `autotier` namespace:** it is user-facing; writing a large learned
+table into it would surface in the Settings card and collide with the user's
+revision on every flush. A separate namespace keeps the two concerns apart.
+
+**Acceptance:** a unit test proving hydrate → record → flush → hydrate is
+idempotent; an integration test proving a refused settings write leaves the
+in-memory table intact.
+
+**Why not enabled yet:** it adds a write path to a plugin whose current promise
+is "writes only the `autotier` namespace", and the benefit only appears after a
+long enough session history that the cold-start fallback has already paid for
+itself. Ship it behind `persistence.fingerprints: false` default.
+
+## 3. Attempt-first middle band (default on)
+
+**Goal:** start ambiguous turns on the cheap tier and escalate on a signal,
+which the cascade literature shows is cheaper *and* faster than deciding up
+front.
+
+**What is missing is calibration, not code:** the band, its `tauLow`, the
+verify-once review, and the effort-first ladder are implemented and tested; the
+shipped default is `intent.attemptBand.enabled: false` because the thresholds
+have never been measured on real traffic.
+
+**Mechanism:** `scripts/calibrate.mjs` + a 90-case labelled corpus:
+
+- Corpus: `fixtures/intent-corpus.jsonl`, one `{ text, expectedTier, hard }` per
+  line, balanced across the eight scenarios (11–12 each) plus 10 adversarial
+  "looks simple, is complex" cases.
+- The script replays the corpus through the *shipped* classifier (no LLM), then
+  sweeps `ruleThreshold`/`tauLow` and prints a table of PGR, APGR, CPT(50 %),
+  CPT(80 %), strong-call % and rule-layer hit rate — the same metrics RouteLLM's
+  `calibrate_threshold` reports.
+- CI gate (a vitest suite over the same corpus): **CPT(80 %) ≤ 40 %**,
+  **APGR ≥ 0.7**, routing quality ≥ 95 % of an always-strong oracle, rule-layer
+  zero-token hit ≥ 60 %.
+- Only when the gate is green does the shipped default flip to
+  `attemptBand.enabled: true`.
+
+**Why not enabled yet:** enabling an uncalibrated band would spend strong calls
+on turns the rules already classify correctly, which is exactly the cost the
+plugin exists to avoid.
+
+## 4. Long-context lane
+
+**Goal:** route very long sessions (est. tokens ≥ 30 k) to a model whose context
+window actually fits, instead of failing or compacting mid-turn.
+
+**Mechanism:** the same pre-flight module already answers "does this route
+exist"; extend it with `ctx.llm.resolveModelInfo(...).context?.contextWindow`:
+
+- When the assembled request's estimated tokens exceed the target route's
+  `contextWindow`, pick the first fallback entry (or the other tier) whose
+  window fits, and log the substitution once.
+- If nothing fits, leave the route alone — compaction owns that case, and a
+  router must not silently drop the user's context.
+
+**Why not yet:** `LlmCallConfig` carries no message payload at the request
+waterfall, so the estimate must come from the session's derived history; the
+read is cheap but it is a new dependency on `session.deriveMessages()`, and the
+harness's own compaction is the primary owner of this problem.
+
+## 5. Multi-router coexistence
+
+**Status:** implemented in 0.1.2 — a foreign `provider/model` at the request
+waterfall is detected, logged once per session, and surfaced by `/tier status`
+and `tier_status`.
+
+## 6. Explicit user selection
+
+**Status:** implemented in 0.1.2 — the applied tier is mirrored into the
+`agent-default-model` document, and an external change to that document moves
+every live session to `delegated` until `/tier auto`.