Files
dsh-context/pnpm-workspace.yaml
T
bowenliang123 bc2544adfa feat(host): serve the preferences through the entry Config schema
The Config-form generation (dsh 0.1.7+) derives the Plugins page's live
form from each loader entry's own Config schema, so the entry schema must
be the schemastery one: cordis keeps validating the config: block through
its Standard Schema face, and the same schema now carries the six display
preferences as .volatile() fields (live-editable there, namespace = the
entry id). The fold bounds stay ordinary fields — their edit remounts the
entry, a preference edit commits volatile-only.

The .volatile() modifier ships only with the newer schemastery, so the
builder feature-detects it and the same bundle loads on the older lines
(3.18.2 predates the modifier). The devDependency bumps to 3.18.4 to
exercise the marked path in tests. Deliberate relaxations against the
replaced zod schema: unknown keys merge through, and integers are
expressed as min 1 + step 1.
2026-09-23 15:57:28 +08:00

26 lines
940 B
YAML

# The project is its own pnpm workspace root, so pnpm never walks up into a
# parent workspace (e.g. $HOME) when installing.
packages:
- .
# Allow esbuild's postinstall (binary bootstrap); everything else is pure JS.
allowBuilds:
esbuild: true
minimumReleaseAgeExclude:
- '@deepseek-ai/dsh-client-ui-primitives@0.1.2-rc.1'
- '@deepseek-ai/dsh-invariants@0.1.2-rc.1'
- '@deepseek-ai/dsh-scope@0.1.2-rc.1'
- '@deepseek-ai/dsh-session@0.1.2-rc.1'
- '@deepseek-ai/dsh-session-projection@0.1.2-rc.1'
- '@deepseek-ai/dsh-settings@0.1.2-rc.1'
- '@deepseek-ai/cosmokit@1.8.3 || 1.8.5'
- '@deepseek-ai/dsh-brand@0.1.2-rc.1'
- '@deepseek-ai/dsh-llm@0.1.2-rc.1'
- '@deepseek-ai/dsh-timeout@0.1.2-rc.1'
- '@deepseek-ai/dsh-typert-protocol@0.1.2-rc.1'
- '@deepseek-ai/dsh-util-crypto@0.1.2-rc.1'
- '@deepseek-ai/dsh-util-values@0.1.2-rc.1'
- '@deepseek-ai/schemastery@3.18.2 || 3.18.4'
- '@opencode-ai/models@0.0.72'