dsh-openrouter-plus 0.0.0-stage → 0.1.1

package/CHANGELOG.md

@@ -0,0 +1,56 @@
+# Changelog
+
+Notable changes to `dsh-openrouter-plus`. Format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions follow
+[SemVer](https://semver.org/), and the project stays below 1.0 while the routing presets and
+the config keys can still change.
+
+## [Unreleased]
+
+Nothing yet.
+
+## [0.1.1] — 2026-10-27
+
+### Changed
+
+- The UI says **preset** everywhere. The recent-requests column header read `Tier`, the provider
+  row hint and the empty state said "service tier", and the Chinese strings said 服务等级; the
+  rename to presets had missed all five.
+- README gains screenshots of the provider switch, both halves of the settings page, and the
+  composer chip — the four states worth seeing before installing.
+
+## [0.1.0] — 2026-10-26
+
+First release: a loopback relay that applies an OpenRouter **routing preset** to a request at
+send time, chosen per Session from the composer.
+
+### Added
+
+- **Nine routing presets**, each a named wire effect rather than a price promise: *No pin*,
+  Standard (`service_tier: "default"`), Fastest · any price (`provider.sort: "throughput"`),
+  Fastest · standard price, Cheapest (`provider.sort: "price"`), Flex
+  (`service_tier: "flex"`), Priority (`service_tier: "priority"`), Ultra
+  (`service_tier: "ultrafast"`), Floor (the `:floor` model variant).
+- **A preset chip in the composer**, next to the model selector: the choice applies to one
+  Session, is never written to a provider row, and the first entry returns the Session to the
+  profile default.
+- **OpenRouter Plus settings page**: relay state and origin, one pinned base URL per preset with
+  a copy button, live request/token counters per tier, the measured effective multiplier, recent
+  requests, and a provider-route switch that repoints one existing row at the relay.
+- **Pinned base URLs** (`/v1`, `/default/v1`, `/flex/v1`, `/priority/v1`, `/ultrafast/v1`) for the
+  case a per-Session choice cannot cover: a route pinned this way keeps its preset for every
+  Session on it and across restarts.
+- **`defaultPreset`** — the preset an unchosen Session inherits, edited on the settings page.
+- **A relay control API** on loopback only: `status`, `targets`, `tier`, `traffic`, plus the
+  route attach/detach/repair endpoints the settings page drives.
+- **Reasoning-effort fill** for relay-routed models, so a route that points at the relay keeps the
+  thinking-level selector.
+
+### Notes on the wire
+
+- No preset is ever sent as `provider.sort` together with `service_tier: "flex"`, and `default`
+  is only written when the preset asks for it, never as a default for an unset choice.
+- `ultrafast` is OpenAI-only and needs `max_tokens`; the relay warns when a Session sets it
+  without one and never injects the field.
+- A `provider` block on the request is merged, not replaced, so `provider.only`, `provider.order`
+  and `provider.ignore` survive every preset.

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 dsh-openrouter-plus contributors
+
+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.

package/README.md

@@ -1,3 +1,421 @@
-# Temporary Holding Version
+# dsh-openrouter-plus
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+[![npm](https://img.shields.io/npm/v/dsh-openrouter-plus.svg)](https://www.npmjs.com/package/dsh-openrouter-plus)
+[![license](https://img.shields.io/npm/l/dsh-openrouter-plus.svg)](LICENSE)
+
+**Service-tier routing for OpenRouter — as a DeepSeek Harness plugin, with no patched packages.**
+
+OpenRouter lets you steer where a request is served from: `flex` endpoints bill half price on a
+slower pool, `priority` endpoints bill a multiplier for lower latency, and the throughput or price
+comparators reorder the pool in between. In `@deepseek-ai/dsh-llm-pi-ai` none of that is reachable —
+provider profiles expose `baseURL` and `headers`, but no request-body fields
+([discussion #9787](https://github.com/deepseek-ai/deepseek-harness/discussions/9787)).
+
+This plugin reaches the same wire result from the outside. It runs a **loopback relay**; a provider
+route points at it, and the relay writes the routing fields into the request body on the way
+upstream — `service_tier`, `provider.sort`, or the `:floor` model variant, depending on the
+**preset** you picked. Because it only uses schema fields the profile already has, it survives
+`bun install -g` upgrades and never touches `~/.bun/install/global`.
+
+The preset is chosen **per session, at request time**. One provider row keeps serving every preset, so
+switching never mints a provider, a route or a model list.
+
+```
+  composer chip: this session runs on «priority»
+      │
+      ▼
+  dsh-llm-pi-ai ──►  dsh-openrouter-plus relay  ──►  https://openrouter.ai/api/v1
+      baseURL =           │ reads the session from x-session-id / prompt_cache_key,
+  127.0.0.1:8791/t/<id>/v1  │ applies that session's preset to the body
+                            └── /__openrouter-plus/* ──► OpenRouter Plus settings page
+```
+
+## What you get
+
+- **One provider row, any preset.** A routed provider keeps its key, protocol and models and gains
+  one thing: a composable **preset** that the relay applies to each request. No per-preset provider
+  copies, no sibling route per preset, no model list duplicated nine times.
+- **Pinned base URLs** for what a chip cannot cover — `/v1` (no pin), `/default/v1` (Standard),
+  `/flex/v1` (Flex), `/priority/v1` (Priority), `/ultrafast/v1` (Ultra). Paste one into an
+  OpenAI-compatible provider route and that preset applies to *every* Session on the route,
+  subagents included, and survives a restart. The relay still serves the older names
+  (`/auto/v1`, `/fast/v1`, `/scale/v1`); the settings page lists one mount per preset so it never
+  offers the same choice twice.
+- **Its own settings page** (Settings → OpenRouter Plus) showing relay state, one pinned base URL
+  per preset with a copy button, live request/token counters per preset, the measured effective
+  multiplier, and recent requests.
+- **A preset chip in the composer** — next to the model selector, a compact chip shows the preset
+  this Session will actually apply and switches it in one click. The switch is **per session**: it
+  changes what the next request from *this* conversation carries, so two conversations can sit on
+  `Flex` and `Priority` at the same time. It shows up on a brand-new Session too — before the first
+  message the chip reads the profile default, so a preset can be picked *before* you start typing.
+  The reasoning effort you chose stays put: switching a preset touches no provider row and no model
+  list.
+- **A switch on every provider row** — in Settings → Models, each `llm-pi-ai` provider gets a
+  **Route through OpenRouter Plus** checkbox. Tick it and that provider's traffic flows through the
+  relay to the endpoint you already gave it; untick it and the endpoint comes back. Your provider
+  entry, protocol, key and models are left exactly as they were.
+- **A default preset for the profile** — the settings page sets what an unchosen Session inherits
+  (and explains what every preset sends), and the composer chip's `Profile default (…)` entry hands
+  a Session back to it.
+- **Zero risk to your existing setup** — the relay holds no API key, forwards your `Authorization`
+  header verbatim, binds only to loopback, and the only profile changes it makes are reversible by
+  construction.
+
+## Screenshots
+
+The switch lives on the provider you already use, in Settings → Models. Ticking it moves that
+row's traffic onto the relay and changes nothing else:
+
+![Route through OpenRouter Plus ticked on a provider row](docs/images/models-route.jpg)
+
+The settings page — relay state, one pinned base URL per preset, the counters, and what each
+preset actually sends:
+
+![OpenRouter Plus settings: relay state, pinned base URLs, spend impact](docs/images/settings-overview.jpg)
+
+![OpenRouter Plus settings: preset catalogue, provider routes, recent requests](docs/images/settings-presets.jpg)
+
+The composer chip, which switches the preset for one Session without touching any provider row:
+
+![Composer chip showing a per-session preset next to the model selector](docs/images/composer-chip.jpg)
+
+## Install
+
+`--profile` is not optional — `dsh plugin` manages the plugins of one named profile, so pass the
+one you actually boot (`web` for `dsh web`, `default` for a bare `dsh`). Without it the CLI stops
+with `required option '--profile <name>' not specified`.
+
+```bash
+dsh plugin --profile web add dsh-openrouter-plus                              # from npm
+dsh plugin --profile web add github:GnaneshKunal/dsh-openrouter-plus#v0.1.0   # or a pinned tag
+```
+
+From a clone, which is what development uses:
+
+```bash
+git clone https://github.com/GnaneshKunal/dsh-openrouter-plus
+dsh plugin --profile web add ./dsh-openrouter-plus     # or, from a session:
+#   plugin_manager { action: install_bundle, target: "./dsh-openrouter-plus" }
+```
+
+The manifest declares `engines.dsh`, so the plugin manager refuses a harness older than the build
+it was tested against instead of mounting something that cannot work.
+
+The plugin adds one entry to Settings navigation: **OpenRouter Plus**, directly after *Models*. If
+the relay is up, the page shows the origin (`http://127.0.0.1:8791`) and its mounts.
+
+## Releasing
+
+`.github/workflows/ci.yml` runs `npm run check`, `npm test` and `npm pack --dry-run` on every push
+and pull request. `.github/workflows/release.yml` turns a tag into a release:
+
+```bash
+$EDITOR package.json CHANGELOG.md      # version 0.2.0, and a "## [0.2.0] — 2026-11-02" section
+git commit -am "chore: 0.2.0" && git push
+git tag v0.2.0 && git push origin v0.2.0
+```
+
+The job refuses a tag that disagrees with `package.json`, runs the suite, publishes to npm, and
+opens the GitHub Release with the matching `CHANGELOG.md` section as its notes. It fails rather
+than skipping when npm already has that version: a release is a new version, never a re-upload.
+
+npm needs the package to exist before it can trust a publisher, so `0.1.0` went up by hand, once,
+from a logged-in machine:
+
+```bash
+npm login
+npm publish --access public
+npm trust github dsh-openrouter-plus --file release.yml \
+  --repo GnaneshKunal/dsh-openrouter-plus --env release --allow-publish
+```
+
+Every version after it is a tag, and nothing else. The tag does everything: the workflow run's OIDC identity is accepted, npm attaches a
+provenance attestation linking the tarball to the commit and run that built it, and no
+`NPM_TOKEN` exists in the repository. `npm trust list dsh-openrouter-plus` shows the grant.
+
+Publishing to npm is optional for users: `dsh plugin --profile web add github:…` installs the same code from a
+tag, which is how most of the community ships.
+
+## Use it
+
+### Two clicks: tick the provider, pick the preset
+
+1. **Settings → Models** → tick **Route through OpenRouter Plus** on the provider you already use
+   (for example `openrouter-custom`). That provider's traffic now flows through the relay; its
+   `api`, `apiKeyEnv`, headers and models are untouched.
+2. Open the composer of any Session and pick a preset in the chip next to the model selector. Every
+   request that Session sends now applies that preset.
+
+Nothing else to create, and nothing to clean up: the provider row is the only row that ever existed,
+and the preset is a per-Session choice rather than a provider.
+
+The settings page manages the profile-level **Service tier for new sessions** — with a short table
+of what each preset sends — and lists the routes that currently point at this relay (with **Remove**
+for the ones you no longer want).
+
+### From a provider row (the switch)
+
+In **Settings → Models**, every `llm-pi-ai` provider row carries a compact strip added by this
+plugin: a **Route through OpenRouter Plus** checkbox.
+
+Ticking it does three things, all through the control API:
+
+1. records the endpoint that row currently points at (that is your real base URL) as a *target* in
+   this plugin's own config;
+2. gives that target a mount — `http://127.0.0.1:8791/t/<targetId>/v1` — which *mounts* the
+   endpoint without pinning a service tier: the presets come from the Sessions that call it;
+3. repoints **only** that provider row's `baseURL` at the mount. `api`, `apiKeyEnv`, headers and
+   models are not touched, and no plugin bookkeeping is written into the provider entry (it is
+   schema-validated, so it stays clean).
+
+**The first attach reloads the plugin.** Recording a new target is a write to this plugin's own
+config, so the Loader re-applies the Host row and the listener rebinds — which can cut the HTTP
+response to that very request. It is not a failure: the strip re-probes `/health`, re-reads
+`/targets` and shows the truth, and every write here is idempotent, so a retry lands cleanly. Later
+attaches (a detach, a re-attach of a known endpoint) reuse the target row and do not reload anything.
+**A preset switch never writes anything**, so it never reloads anything either.
+
+What happens to a request: the relay strips the mount prefix, appends the rest of the path to your
+recorded endpoint, resolves the preset the Session carrying that request chose, and applies it to the
+JSON body. `No pin` sends neither a tier nor a comparator — and a `service_tier` the client put there
+itself is removed, so a Session that pinned nothing stays unpinned rather than inheriting whatever a
+UI happened to send.
+
+Untick it (**Detach**) and the row's `baseURL` goes back to the endpoint recorded for that target;
+the mount stays until you remove the target. Everything is idempotent: the same endpoint always maps
+to the same target id, so ticking the box twice cannot fork the table or repoint anything twice.
+
+> **Why the switch is on the row and not inside the add-provider form.** The obvious place for this
+> checkbox is the "Custom model API" form itself. A plugin cannot put it there: the
+> `settings.models.provider-card` extension slot hands an extension `{provider, configured,
+> keyConfigured}` and no setter, the draft Base URL lives in a private `useState` inside the editor,
+> and that card dispatches no extension at all before the provider is saved. The saved row is the
+> earliest surface a plugin can reach — same page, one save later. The same class of limitation is
+> why a re-picked model loses hand-declared fields (tracked upstream as
+> [discussion #11097](https://github.com/deepseek-ai/deepseek-harness/discussions/11097)).
+
+### By hand
+
+Point any OpenAI-compatible provider route's `baseURL` at a mount:
+
+```yaml
+- id: llm-pi-ai
+  config:
+    providers:
+      my-flex-route:
+        api: openai-responses
+        apiKeyEnv: OPENROUTER_API_KEY
+        baseURL: http://127.0.0.1:8791/flex/v1
+        models:
+          - id: deepseek/deepseek-v4.1-flash
+            # Optional but recommended — see "Reasoning effort" below.
+            reasoningEfforts:
+              off: null
+              low: low
+              medium: medium
+              high: high
+              max: max
+```
+
+Or route a provider to its own endpoint through a target mount — no provider config needed beyond
+the base URL:
+
+```yaml
+- id: llm-pi-ai
+  config:
+    providers:
+      acme-gateway:
+        api: openai-completions
+        apiKeyEnv: ACME_API_KEY
+        baseURL: http://127.0.0.1:8791/t/acme-gw-9f3a/flex/v1
+        models:
+          - id: acme-large
+```
+
+`/t/<targetId>/v1` is the shape the switch writes: it mounts the endpoint and pins nothing, so each
+Session's chip decides. `/t/<targetId>/<tier>/v1` is the older pinned shape and still works — useful
+when a row must sit on one tier regardless of who calls it. The target's endpoint is declared once,
+in the plugin's config (see `targets` below), so one listener can front any number of OpenAI- or
+Anthropic-style endpoints.
+
+### Reasoning effort on a relay route
+
+A relay route is a provider key the installed catalog has never seen, so
+`@deepseek-ai/dsh-llm-pi-ai` cannot inherit a model's reasoning capability for it. Without an
+explicit `reasoningEfforts` the model materializes as `reasoning: false` and the composer shows
+**"This model provides no reasoning effort levels."** — no effort selector, no error, nothing in the
+log. The relay itself is not involved; it never touches reasoning fields.
+
+The plugin fills that gap when it creates a route, from the best evidence available:
+
+1. a capability the model already declares (in the source route), kept byte-identical;
+2. a declaration for another variant of the same id — `google/gemini-4-argon:flex` teaches the
+   plugin about `google/gemini-4-argon`;
+3. the configured `reasoningEfforts` map, as a fallback for everything else.
+
+Set `reasoningEfforts: false` to switch filling off, or omit it to fill only from evidence 1–2.
+A model that declares `reasoningEfforts: false` is itself opted out: the fill leaves it alone.
+
+**The fill also re-applies itself.** Re-picking a model in Settings → Models rebuilds that row from
+the catalog — `id`, `name`, context window, max tokens — and drops `reasoningEfforts` along with
+every other hand-declared field. That is the shape of this bug: the effort selector works, you touch
+the model list afterwards, and it is gone. The cause is upstream rather than here (`adopt()` in
+`@deepseek-ai/dsh-client-ui-settings-models` copies a fixed field list), so the plugin watches the
+profile instead: a debounced pass runs on every config settle and restores the capability a moment
+after the edit lands. Set `autoRepairReasoning: false` to keep the plugin out of your config
+entirely, and use **Add reasoning to N models** in the settings page (or
+`POST /__openrouter-plus/routes/repair`) when you want the fill on demand.
+
+Either way it only ever touches routes whose `baseURL` points at the relay, never overwrites a
+declared map, never resurrects an explicit `false`, and writes nothing when there is nothing to do.
+
+## Presets
+
+A service tier is not one field. OpenRouter exposes three levers — `service_tier` (which pools may
+serve, and in what order), `provider.sort` (the comparator over that pool) and two slug suffixes
+(`:nitro`, `:floor`) that mix the two — and each preset is a combination the API actually defines:
+
+| Preset | Sends | What it does |
+| --- | --- | --- |
+| **No pin** | nothing | OpenRouter's own routing. |
+| **Standard** | `service_tier: "default"` | The standard tier only; priority endpoints are excluded. |
+| **Fastest · any price** | `provider.sort: "throughput"` | The whole eligible pool sorted by throughput. On an open-weight model this *is* nitro — its priority endpoints already compete in default routing. On a closed-weight one it stops short, because those endpoints are opt-in. |
+| **Fastest · standard price** | `sort: "throughput"` + `service_tier: "default"` | The same race over the standard pool only, so the priority premium is unreachable. |
+| **Cheapest** | `provider.sort: "price"` | Lowest price over the standard pool — usually a quantized version of the model. It never admits a flex endpoint, so it cannot reach a flex rate. |
+| **Flex** | `service_tier: "flex"` | Flex endpoints only, at flex rates. Not necessarily the cheapest, and a flex capacity error surfaces instead of falling back to standard. |
+| **Priority** | `service_tier: "priority"` | Priority endpoints serve first, then standard. OpenAI calls this Fast mode. The premium is charged only when a priority endpoint actually serves, and within each group endpoints sort by throughput unless you set a comparator. |
+| **Ultra** | `service_tier: "ultrafast"` | ultrafast, then priority, then standard. OpenAI models only, and it needs `max_tokens` to hold — without one it silently degrades to priority. |
+| **Floor** | `model: "…:floor"` | A blind price sort across the standard **and** flex pools. No parameter form exists for this, which is why it is a slug. `:nitro` is deliberately not offered separately: for the models where it changes the outcome, **Fastest · any price** is the same race. |
+
+Two rows sit between "no tier" and "priority" for a reason: `provider.sort` and `service_tier`
+decide different things. Sorting by throughput reorders whatever pool the tier admitted; pinning
+`service_tier: "default"` is what keeps the premium out of it. Neither one alone can say
+"fastest, and never at a premium".
+
+### From the composer (the preset chip)
+
+Once a provider row is routed, a compact chip appears in the composer next to the model selector,
+showing the preset the next request will apply. Picking another one there does **not** rewrite any
+config and does **not** mint a provider: the Host records the choice for this Session in memory, and
+the relay applies it to the request body on the way out.
+
+The menu carries labels only — `Fastest · any price`, `Cheapest`, `Flex`, `Priority`, … — and the
+long explanation of what each one sends lives on the settings page, where it is read once. The first
+entry, **Profile default (…)**, stops choosing for this Session and shows which preset it will
+inherit.
+
+That is why it is per session: two conversations can be on `Flex` and `Priority` at the same time,
+neither of them rewrites the other's provider row, and the reasoning effort you selected survives
+the switch because the selection itself never changes.
+
+The choice lives in the Host's memory — it is runtime state, like the effort level — so it survives
+the whole Session but not a Host restart (a default-preset write reloads the plugin, which drops
+those choices too). Want a preset that outlives every restart? Either set the profile **Service tier
+for new sessions** or point a provider at a pinned mount by hand (`/flex/v1`).
+
+The chip only appears when the Session's current provider is routed through a mount
+(`/t/<targetId>/…`). Elsewhere the Models-page switch is the control: it is the one that moves the
+provider itself.
+
+## Control API
+
+Served on the same loopback listener, outside the proxy path space:
+
+| Endpoint | Purpose |
+| --- | --- |
+| `GET /__openrouter-plus/health` | liveness |
+| `GET /__openrouter-plus/status` | address, upstream, mounts, metrics |
+| `GET /__openrouter-plus/targets` | source routes, routes on this relay, the `targets` table, and the preset table (`{ default, presets }`) |
+| `GET /__openrouter-plus/tier?session=<id>` | what that Session would apply now: `preset`, `wire`, `chosen`, `default`, `presets` |
+| `POST /__openrouter-plus/tier` | `{ session, preset }` — choose this Session's preset; `preset: null` hands it back to the profile default. **Memory only, never a config write** |
+| `POST /__openrouter-plus/tier/default` | `{ preset }` — the preset an unchosen Session inherits; omit it (or send `none`) to pin nothing |
+| `POST /__openrouter-plus/routes/remove` | `{ name }` |
+| `POST /__openrouter-plus/routes/repair` | adds missing `reasoningEfforts` to the routes this plugin owns |
+| `POST /__openrouter-plus/routes/attach` | `{ route, upstream }` — record the endpoint and point that provider at the relay |
+| `POST /__openrouter-plus/routes/detach` | `{ route, id }` — put that provider back on its own endpoint |
+| `POST /__openrouter-plus/targets/register` | `{ upstream, tier?, id? }` — record an endpoint without touching a provider |
+| `POST /__openrouter-plus/targets/remove` | `{ id }` — refuse while a provider still routes through it |
+
+`attach`/`detach` are what the Models-page switch calls; both are idempotent and report
+`changed: false` when the row is already in the requested state. A rejected request answers `400`
+with `{ error: { message } }` — for example a body that is not an http(s) URL, or one that points
+back at the relay. `POST /tier` answers `400` for an unknown preset (`turbo`) or a missing
+`session`, and accepts `preset: null` (or no `preset` at all) to clear. The tier-era body shape is still
+read: `tier: "fast"` maps onto the `priority` preset, and any other legacy name maps onto the preset
+that sends the same field.
+
+Everything in `/tier` is deliberately write-free: a config write would re-apply this plugin row and
+restart the listener, which is not something a mid-conversation click should risk. Only
+`/tier/default` writes, because it is a preference rather than one Session's state.
+
+`POST` requires `x-oorp-client: web`. CORS is reflected only for loopback GUI origins.
+
+```bash
+curl -s http://127.0.0.1:8791/__openrouter-plus/status | jq .metrics.byTier
+```
+
+## Configuration
+
+`cordis.patch.yml` ships the defaults; override them in your profile's patch layer:
+
+| Key | Default | Meaning |
+| --- | --- | --- |
+| `enabled` | `true` | `false` keeps the plugin installed but binds nothing |
+| `host` | `127.0.0.1` | bind address — loopback only, deliberately |
+| `port` | `8791` | preferred port |
+| `portFallback` | `true` | fall forward to the next free port (the page probes 8791–8794) |
+| `upstream` | `https://openrouter.ai/api/v1` | where requests are forwarded, no trailing slash |
+| `routes` | tier mounts | mount path → tier, for pinned URLs (`/flex/v1`); `null` tier is a pure passthrough. Accepted names are `default`, `flex`, `priority`, `ultrafast`, and the aliases `auto`/`scale` (both mean *no pin*) and `fast` (= `priority`). The per-session design needs only `/v1` |
+| `upstreamTimeoutMs` | `0` | `0` disables the upstream timeout (long SSE completions) |
+| `reasoningEfforts` | `false`-able map | levels written onto relay routes' models; `false` disables, omit for evidence-only |
+| `autoRepairReasoning` | boolean, default `true` | re-apply that fill whenever the profile changes, so editing a route's models cannot silently strip the effort selector |
+| `defaultPreset` | `none` | the preset an unchosen Session inherits; `none` pins nothing. A tier-era `defaultTier` is read forward onto the equivalent preset. Written by **Service tier for new sessions** on the settings page |
+| `targets` | `{}` | extra endpoints served from `/t/<id>/…` mounts: `{ "<id>": { upstream } }`. Written by the switch; edit by hand only if you want one without a provider row |
+
+## Security model
+
+- **Loopback only.** The relay forwards the caller's `Authorization` verbatim and stores no key.
+  Do not bind a routable interface.
+- **Read-only telemetry.** The status API exposes counts and token sums, never prompts or keys.
+- **Reversible by construction.** The plugin only ever adds a provider route whose `baseURL` points
+  at its own origin, and only removes routes that pass that same test. The switch is the same idea
+  one level down: the endpoint it took over is recorded in the plugin's config, and **Detach** —
+  or deleting the target — puts it back, so a provider is never left pointing at a dead mount.
+
+## Troubleshooting
+
+| Symptom | Cause and fix |
+| --- | --- |
+| Card says *relay offline* | The port range is busy, or the row is `enabled: false`. Check the Host log for `[openrouter-plus]`; set a fixed `port`. |
+| A model errors after disabling the plugin | That model belongs to a route pointing at the relay. Re-enable the plugin or remove the route on the OpenRouter Plus page. |
+| Requests work but nothing is steered | The Session is on **No pin** (or the profile default is), the mount is a bare `/v1` passthrough, or the request is not `POST` with a JSON body. |
+| The chip shows a preset, but another Session still bills full price | Every preset is per Session by design. Set it in that Session's composer, or set a profile **Service tier for new sessions**. |
+| The chip disappeared after a Host restart | Choices are runtime state and the memory table is dropped on restart (and on a default-preset write, which reloads the plugin). Re-pick it, or set the profile default. |
+| `Flex` still bills full price | The provider decides which endpoint served; a preset only decides which ones may be asked. Confirm the served endpoint with `usage` or the OpenRouter dashboard. |
+| `Fastest · any price` did not get faster | The comparator only reorders the pool the tier admitted. On a closed-weight model the fastest endpoints are priority-only, so use **Priority** — or compare against the `:nitro` slug in the OpenRouter dashboard. |
+| `Ultra` behaves like `Priority` | `ultrafast` only holds on OpenAI models that receive a `max_tokens` limit; without one the API degrades to priority. The relay never invents a limit, so set one on the model row. |
+| The page says *failed to render*, and switching the chip says *the relay did not confirm the change* | The tab is running the browser half from before the update against the restarted Host. Reload the page (or reopen the app window); only a document reload re-fetches the client bundle, and a Host restart alone keeps the old module in memory. |
+| No effort selector for a relay route's model | The model has no `reasoningEfforts` — usually because the model list was edited in Settings → Models afterwards. It is restored automatically; if `autoRepairReasoning` is off, press **Add reasoning to N models** on the OpenRouter Plus page. See "Reasoning effort on a relay route". |
+
+## Uninstall
+
+Remove the route(s) in Settings → Models, then:
+
+```bash
+dsh plugin --profile web remove dsh-openrouter-plus
+```
+
+## Development
+
+```bash
+node --check index.js && node --check client.js
+node --test            # 99 tests, no network, no profile writes
+```
+
+See [`docs/ARCHITECTURE.md`](docs/ARCHITECTURE.md) for the module contract, and
+`docs/DESIGN.md` for the design rationale against the upstream discussion.
+
+MIT.
+
+[![](https://img.shields.io/badge/powered_by-dsh-4D6BFE?style=flat-square&logo=deepseek&logoColor=white)](https://github.com/deepseek-ai/deepseek-harness)