* feat(experimental): ship every experimental capability as an optional bundle dsh-base mounts the registration-only browser-use and computer-use services; the Playwright MCP, Chrome DevTools MCP, native and MCP Cua Driver providers, Auto review, and the Inspector become one-row bundles listed in OPTIONAL_BUNDLES with an icon and locale display metadata. verify-default-product-isolation requires both for every optional bundle. Python PTC and Stagehand stay explicit compositions. * feat(experimental): keep optional bundles inside the install closure Drop the Playwright MCP, Chrome DevTools MCP, and native Cua Driver bundles: each is a runtime dependency of every install and would add about 85 MB of provider runtimes whether or not enabled. dsh-browser-use leaves dsh-base with them. The three packages keep their locale display metadata for component rows. * feat(experimental): drop the Cua Driver MCP bundle and leave dsh-base untouched * test(web): refresh Official-group goldens for the four optional bundles * fix(plugins): use an uninstalled bundle as the install example and pin optional-bundle metadata The install guide's example is now @deepseek-ai/dsh-subagent-codex, a published bundle no shipped profile carries, since Auto review is an installed optional bundle. The optional-bundle spec guards its corpus and pins each bundle's title, description, and icon in both languages; the Inspector's Loader test mounts its real bundle patch, its Client names the reload a hot-enabled page needs, and its description states the loopback DevTools endpoint's reach. * test(web): refresh GitHub install recovery placeholder snapshot
apps/web browser e2e
English | 中文
These tests boot the real web composition in-process and drive it with real browsers over real HTTP. Chromium runs the full lane; the model and reasoning picker scenario also runs in WebKit to cover native mouse focus behavior. The lane's mechanics — modes, fixtures, goldens, and the deliberate composition divergences from dsh web — are documented in scaffold.ts and the browser e2e Agent Note.
After installing workspace dependencies, install the browsers and their system dependencies from the repository root:
pnpm --filter @deepseek-ai/dsh-web-frontend exec playwright install --with-deps chromium webkit
On Linux, --with-deps installs dependencies through the system package manager. The persistent CI VM must provide these dependencies through image maintenance; CI installs only the browser binaries, as required by the failover runbook.
Ordinary scenarios begin with no registered Workspace or Session and a durable marker recording a removed default Workspace, so explicit folder-selection scenarios retain control of their cwd. launchWebScaffold({ firstUse: true }) leaves initialization eligible for startup scenarios.
Completion observations
State-sensitive cases use Workspace, admission, attachment, and model-stream barriers to separate visible intermediate states from completed operations. Details close waits for frame transitions; archive verification assigns an explicit title to the seeded Session and follows that identity across reload. See the CI fixture synchronization decision.
Explicit scrolling uses scrollIntoView from support.ts: it resolves the locator again when its old element detaches and checks connection in the same browser task as native scrolling. Scenarios retain their visibility and geometry assertions after scrolling.
These are Host-face tests
They type-check in the root tsconfig.host.json, not in the Client aggregate, because they read Host services directly: ctx.connection, the Host SessionStore, and ctx.sessionProjectionCache. Driving a browser at runtime does not make a file part of the Client program — the two faces merge Cordis Context under the same keys with different services, so one program cannot see both. Moving these files into the Client aggregate makes every Host-service access fail to compile.
Do not import @deepseek-ai/dsh-client-* here
Importing a Client package — a value or a type — pulls its whole TypeScript project, and every project it references, into the Host build graph. That has bitten this lane once already: four Client consumer packages reference api/remotes' Client face, which cannot compile until Host tsdown has generated @deepseek-ai/dsh-goal/remote, so the Host build phase ended up waiting on an artifact it produces itself.
When a scenario needs a Client-owned constant or pure function, mirror it here instead, next to the commented-out import that names the source module. A drift then surfaces as a missed selector or a stale mirrored value — a loud failure, never a silent pass. scaffold.ts follows this rule for the welcome-notice namespace, acknowledgement field, version, and asserted Chinese copy.
The built-client harness is the exception. assembled-boot.ts imports AppWebEntry, the boot-manifest type, and RemoteMock; assembled-remote.ts imports the Client test runtime's default responses and RemoteMock. These packages are explicit project references for booting the real shell against a test-owned carrier. The chat scenarios mirror conversationContextKey in support.ts instead of importing its Client owner.
Nothing mechanically enforces this rule; keep it in review.