Repository navigation
v0.1.3
v0.1.3 — dsh 0.1.2 host compatibility
modelspoke now loads and serves its routes when your dsh installation is updated
to 0.1.2 (previously it failed to load after the dsh update). 0.1.1 is
still supported — one build works on both.
What changed for you
- Works on a dsh 0.1.2 host. Two dsh 0.1.2 API changes had made modelspoke
fail to load; a small version-tolerant shim (src/dsh/compat.ts) now handles
both, resolving to the 0.1.1 symbols on a 0.1.1 host and the 0.1.2 ones on a
0.1.2 host:- dsh-llm renamed its tool-call-id brand
CallId→ToolCallId. This was
a link-time break — the named import threw before any code ran. - dsh-settings dropped the
installSettingsSection/settingsNamespace
free functions in favor of actx.inject(["settings"], …)service seam, and
moveddeepEqualJsonoff the main entry.
- dsh-llm renamed its tool-call-id brand
- Verified end-to-end on 0.1.2-rc.1 (a task routed through a modelspoke
route served a real model response) and regression-checked on 0.1.1.
Also in this release
- Completed the 0.1.2 changelog header (the shipped 0.1.2 work had been left
under "Unreleased").
One known follow-up
- The settings card (web UI) is the one surface not yet web-verified on a
live 0.1.2 host — it is unchanged from the 0.1.1 release and has no
dsh-client-*runtime dependency, so its risk is limited to core
service-interface stability. The routes it configures work regardless.