lefarcen
f9c07517b7
* fix deepseek harness cancellation lifecycle * fix DeepSeek canceled status rendering * fix DeepSeek cancellation handshake race * feat support reasoning selection in composer * test DeepSeek pre-execute cancellation protocol * test reasoning selector visual surface
@open-design/dsh-runtime
Profile bundle that lets Open Design drive a user-installed DeepSeek Harness
through a strict JSONL stdio protocol. It does not ship the dsh executable,
Node.js, credentials, or provider configuration.
Install DeepSeek Harness first. Packaged Open Design builds carry an exact,
integrity-checked tarball of this component. When the DeepSeek Harness card
reports that the connection component is required, selecting the card asks for
confirmation and then invokes the user's own dsh to install that tarball into
the open-design profile. Open Design does not download or install dsh.
Repository developers can perform the equivalent operation manually:
pnpm --filter @open-design/dsh-runtime build
pnpm -C packages/dsh-runtime pack --pack-destination <temporary-directory>
dsh plugin --profile open-design add <temporary-directory>/open-design-dsh-runtime-0.1.0.tgz
dsh --profile open-design --probe
dsh --profile open-design --models
The daemon and od agent setup deepseek-harness --json use the same setup
endpoint as the UI. Setup is always explicit on the first incompatible
selection; cancelling does not select the agent or mutate the Harness profile.
The probe prints exactly one JSON object. Open Design starts one short-lived
dsh --profile open-design --stdio process per run; Harness session storage
provides cold resume across later processes.
The models command prints the provider-qualified catalog assembled by the user's Harness profile. Open Design refreshes this read-only catalog during agent detection; credentials and secret values are never included.