The native adapter's route was named deepseek, colliding with pi-ai's catalog provider of the same name, so the two DeepSeek paths could never be mounted side by side. The web settings page needs both configurable at once. Compositions, fixtures, goldens, scaffolding defaults, and docs all move together (pre-release, no shim); TUI/session-query-spill/ missing-credential goldens re-recorded through their keyless refresh modes because provider-name length shifts box padding and spill truncation points.
29 lines
1.2 KiB
YAML
29 lines
1.2 KiB
YAML
# Keyless replay includes the live `cordis.yml`, disables the key-requiring
|
|
# DeepSeek adapter, and inserts `llm-replay` to serve recorded JSONL without a
|
|
# key or network; every other entry remains shared. The replay provider
|
|
# catalog claims the `deepseek-official` provider so the SDK server's `initialize`
|
|
# finds it owned and never mounts the real-adapter fallback. The SDK snapshot
|
|
# suite passes this path explicitly through `DSH_CORDIS_CONFIG` (the
|
|
# jsonrpc-demo bin performs no DSH_SNAPSHOT config swap of its own), and
|
|
# `llm-replay` reads `DSH_SNAPSHOT_FILE` / `DSH_SNAPSHOT_CHILD_FILES` from the
|
|
# harness. Stdout remains reserved for JSON-RPC frames.
|
|
- id: base
|
|
name: '@cordisjs/plugin-include'
|
|
config:
|
|
path: ./cordis.yml
|
|
patches:
|
|
# `name` asserts the target: a mismatch skips the patch and warns only
|
|
# when a logger exists.
|
|
- id: llm-deepseek
|
|
name: '@deepseek-ai/dsh-llm-deepseek'
|
|
disabled: true
|
|
- insert:
|
|
- id: llm-replay
|
|
name: '@deepseek-ai/dsh-llm-replay'
|
|
config:
|
|
providers:
|
|
- id: deepseek-official
|
|
name: DeepSeek
|
|
models:
|
|
- id: deepseek-v4-flash
|