Turtle
a3480857dd
* 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
description, kind
| description | kind |
|---|---|
| The boot package group: how dsh app bins start — environment loading, profile and patch layers, clear startup failures, and app-owned command lines. | package-group |
boot/ — shared app-bin boot glue
English | 中文
Summary
The boot group launches profile applications and manages their installed composition. app-boot resolves configuration and starts the Loader, cmdline supplies application arguments, and plugin-manager exposes current-profile operations shared with the CLI. Each package README owns its details.
Table of Contents
Packages
| Package | Role | ctx key |
|---|---|---|
app-boot |
Boots a dsh app from a cordis.yml: loads .env, applies profile and patch layers, and reports startup failures clearly |
(library for the bins) |
cmdline |
Lets the app own its flags, --help, and exit code; passes everything after the launcher's flags through verbatim |
cmdlineArgs, appExit |
hmr |
Coordinates module and configuration reloads with package mutations | hmr |
config-editor |
Persists active profile configuration through Loader reconciliation | configEditor |
plugin-manager |
Manages current-profile plugins and bundle packages through shared CLI operations | pluginManager |
Related documentation
-
dsh app — the
dshbin that consumes these helpers for its boot sequence. -
Profile bundles — installable patch layers that
dsh --profilecompositions mount. -
dsh-home-paths — the harness-home resolver both packages build on.
-
dsh-cmdline — how an app owns its flag family instead of the launcher.
-
Profile management — service methods and result records.
Dev Note
None.