Coder/deepseek-harness
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

refactor(web-e2e): rename harness -> scaffold; add interaction coverage

Browse Source 
The shared test module was named harness.ts inside a repo whose product
IS a harness — hopelessly ambiguous. Renamed to scaffold.ts with
launchWebScaffold/WebScaffold; tsconfig plane-split entries, the seam
JSDoc/README mentions, and both Agent Note languages updated.

Both scenarios gain a Playwright interaction step over the settled
transcript (after the golden capture, so committed aria surfaces stay
untouched): replay-round-trip clicks the reasoning fold open/closed over
wire-delivered state; seeded-history expands a read tool row rebuilt from
the cold log and asserts the recorded result text appears (read rows are
expand-in-place — rowExpands routes the click to the inline fold, not the
details column). test:web 30 passed | 1 skipped.
This commit is contained in:
Tianyi Cui
2026-07-24 22:18:19 +08:00
parent 8f97f95d7b
commit 6d3c25f494
9 changed files with 91 additions and 60 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
packages/host/runtime/README.md
View File

@@ -2,7 +2,7 @@
Host runtime assembly for `dsh`: `bootHost` composes the core plugin spine (LLM service + DeepSeek adapter, sessions with JSONL persistence and immediate fallback titles, optional first-message model summaries, system prompt, tools, agents, agent loop, workspace instructions, local bash, and the provider-neutral user-interaction service), `createApiProxy` implements the [`dsh-host-apiproxy`](../apiproxy/README.md) contract over that composition, and `startHost` is the one-step shell seam returning `{ api, handler, defaults, ctx, dispose }`.
Which plugins mount and with what defaults is decided only here — shells must not `ctx.plugin` to alter the assembly. `RunningHost.ctx` is a formal seam with exactly three sanctioned uses: mounting protocol front-door plugins (e.g. a future `dsh acp`), headless session-event subscription, and filling a capability seam the boot options deliberately left open (`llm: false` → the embedder installs its own LLM backend, e.g. the keyless web e2e harness's replay); consuming clients must not bypass `api` through it.
Which plugins mount and with what defaults is decided only here — shells must not `ctx.plugin` to alter the assembly. `RunningHost.ctx` is a formal seam with exactly three sanctioned uses: mounting protocol front-door plugins (e.g. a future `dsh acp`), headless session-event subscription, and filling a capability seam the boot options deliberately left open (`llm: false` → the embedder installs its own LLM backend, e.g. the keyless web e2e scaffold's replay); consuming clients must not bypass `api` through it.
## Configuration

2
packages/host/runtime/src/boot.ts
View File

@@ -69,7 +69,7 @@ export interface BootHostOptions {
* LLM adapter selection: `'deepseek'` (default) mounts the DeepSeek adapter
* (requires an API key at load), `false` mounts no adapter and leaves the
* `llm` capability seam open for the embedder to fill on the returned ctx
* (e.g. the keyless web e2e harness installing a replay backend). With
* (e.g. the keyless web e2e scaffold installing a replay backend). With
* `false` and nothing filled, the first stream fails loud with NO_ADAPTER —
* the earliest resolvable point for an open capability seam.
*/