Turtle
38c7a9fbf4
* feat(release): publish package source, declaration maps, and documentation Every release member publishes its TypeScript source and the declaration maps that resolve into it, and @deepseek-ai/dsh publishes the repository Markdown documentation staged from docs/ at prepack time. The ./src/* export most members already declared now resolves for an installed consumer, and a consumer editor follows a declaration to the implementation. Bundled JavaScript maps stay unpublished; the vendored family and the Desktop runtime file policy are unchanged. Rationale: .agents/notes/implemented/process/2026-10-08-published-source-and-docs.md * feat(release): publish JavaScript maps and compress bundles Every emitted JavaScript map ships beside the bundle it describes, and the workspace build and the client preset compress bundles without mangling identifiers. The documentation payload now mirrors the website publication manifest and is removed again by `postpack`; Desktop and the Python executable exclude the published source, documentation, and maps; `clean` removes a staged copy. Typert's publication contract gains the Remote declaration map. * fix(release): keep node bundles readable for the worker image The browser worker image lowers `yield*` only as a whole statement and rewrites `for await` loops by their source layout, so compressed node-side entries either fail that lowering or lower to unparseable code. Only the browser bundles keep compression, which removes about a third of their text. The bundle-purity assertion now matches the module-loader call regardless of the quote style compression picks, and the release-pack fixture exercises the installed package's new documentation requirement. * feat(release): publish the whole documentation tree `@deepseek-ai/dsh` copies `docs/` in full instead of the website's page set: the maintainer documents, the generated migration records, the translation guidelines, and the `*.i18n.yaml` consistency records ship with the installed package, so the documentation's own links resolve without a checkout. * feat(release): publish the upgrade guides with the documentation The staged documentation keeps the website's page set and adds every `docs/upgrade-guide/` document, which is what an installed reader consults when a released change breaks something. The rest of the maintainer tree stays out. * test(release): expect source and maps in master's new payload cases * feat(release): keep installed docs and source readable in Desktop Desktop keeps the published src/ and docs/ trees inside app.asar, and every model shell call receives DSH_INSTALL_DIR and DSH_NODE_EXECUTABLE so an agent can read them through Electron's Node mode. Staging also generates docs/upgrade-guide/README.md, an index of the upgrade guides grouped by the release they upgrade from. Minified client bundles print string literals with backticks: the worker image packer now recognizes those chunk requests, client license banners are prepended after minification so their text survives, and the affected artifact tests accept either quote. * test(desktop): read archived docs through the Windows PowerShell form Regenerate the config catalog for the shifted shell-env source line. * test(desktop): wait for the GUI-subsystem Electron process from PowerShell * build(release): publish source and maps from the message-quotes package * build(release): publish source and maps from packages new on master * build(release): publish source and maps from the tool-office package
description, kind
| description | kind |
|---|---|
| The shell executor's settings page on the dsh web client's Plugins page: the command timeout and the per-stream output cap of the shell namespace. | package-reference |
@deepseek-ai/dsh-client-ui-settings-shell
English | 中文
Summary
Open Plugins in the sidebar and select Shell in the Official group to set how long one command may run and how much of each output stream stays in memory. The page stages what is typed and writes it only on save, marks the values the user overrode, and offers to reset each back to the deployment's default. The page exists while the Host serves the shell namespace, so a deployment without a local shell executor shows no trace of it.
Table of Contents
- Use this package
- Understand the implementation
- Further Exploration
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
The Shell card in the Official group opens the page. Command timeout (ms) ends a command that runs longer; Output cap per stream (bytes) spills output beyond it to a temporary file. Both render the effective value — the user's override over the composed default — and a field the user overrode carries an Overridden badge with Reset to default beside it. Nothing is written until Save; leaving the page drops the drafts, an empty field saves as a reset, and text that is not a number blocks the save and says so under the field.
Understand the implementation
Implementation internals — click to expand
The Host half is an empty apply, present only so the package holds a Loader row the client module system serves the browser half for. The browser half binds the composed shell executor entry (bash-sandbox off Windows, pwsh-sandbox on it) through ctx.configForms.get, keeps the staged form in ShellCardController over the shared SettingsFormModel of ui-primitives, and registers ShellCard into the Plugins page's plugins.item slot through ctx.configForms.whileServed, which registers while the Host serves either entry and withdraws when it stops. The page's copy lives in this package's settings.shell dictionary; the SettingsForm frame takes its copy as props.
Further Exploration
- ui-plugin-manager — the Plugins page and the
plugins.itemslot the page registers into. - ui-settings — the settings scope and the served-namespace watch the page rides.
- ui-primitives — the settings form model and fields the page renders.
- bash-local — the executor that registers the
shellnamespace.
Model Experience
None, as the package is a browser-side settings surface that registers no model surface.
KV Cache effect
None; this package neither assembles nor sends a provider request.
Known Limitations and Deferred Work
- The page follows the composed executor — the POSIX and PowerShell executor families share the
shellnamespace because a host composes exactly one of them, so the served schema differs by platform (PowerShell addspwshPath) while the page edits the same two fields on both.
Dev Note
Working context for maintainers — click to expand
None.