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 |
|---|---|
| Automation-only ACP stdio application profile for users and maintainers launching persistent harness agents. | package-bundle |
@deepseek-ai/dsh-acp-app
English | 中文
Summary
The automation-only ACP stdio application as a dsh profile bundle over dsh-base. It inherits the base's disabled module-HMR policy; its patch sets the coding-agent persona and default model route, mounts an app-owned zero-option command provider, and starts dsh-acp only after that provider accepts the invocation. dsh --profile acp --help therefore writes help and exits without claiming stdin or stdout.
Table of Contents
- Use this package
- Standard automation workflow
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
The startup provider binds stdin EOF to the launcher's bounded successful shutdown. ACP connection close, SIGINT, and SIGTERM drain the bridge-owned agents and the root profile tree before exit. Stdout is reserved for newline-delimited ACP JSON-RPC frames. The bundle disables model-generated session titles because ACP exposes no title surface; deterministic fallback titles remain durable without an auxiliary model request. The inherited projection cache checkpoints ACP-created sessions for later consumers; its durability barrier flushes each covered log prefix before publishing the cache row and may split otherwise coalesced JSONL runs. A deployment selects a different complete composition through profile bundles and patch files, not another app bin.
The shipped row creates sessions with deepseek-official and deepseek-v4-flash; a later patch can replace that row's complete config. The base profile owns adapters, tools, persistence, policy, settings, credentials, and the per-session workspace supplied by the ACP client.
Standard automation workflow
An ACP v1 SDK client initializes dsh --profile acp, creates a session with an absolute cwd and optional standard stdio/HTTP MCP declarations, chooses an advertised model or reasoning_effort, prompts while observing standard semantic updates, then calls session/close. Another process can use session/list and session/resume against the same profile persistence root; resume reconnects the MCP declarations supplied by that request and does not replay history.
The complete supported method matrix, MCP trust model, update mapping, and stop reasons live in the dsh-acp protocol contract. This profile adds no private method, capability, _meta, environment variable, or transport field. The keyless control-surface conformance test drives the real profile through the public ACP SDK.
Model Experience
ACP coding-agent persona
What the model sees
The profile supplies You are a coding agent powered by the {{model}} model. before first-party guidance; the ACP route resolves {{model}}. Each Session receives its current directory in required user-role context from dsh-working-directory.
Token effect
One short stable persona plus the data-dependent base prompt sections and selected tool schemas.
KV Cache effect
Stable for a fixed profile, provider, model, and tool roster. Profile changes take effect on the next process because the shipped ACP profile uses startup-only patches.
Known Limitations and Deferred Work
- A profile can omit the ACP bridge — a custom ACP launch profile must retain this bundle or another
dsh-acprow; otherwise no peer answers the client. - User plugins can violate stdout purity — profile and per-launch patches are trusted application composition. The shipped bundle writes no non-protocol stdout, but it cannot contain an arbitrary inserted plugin.
- Configuration changes require restart — the
acp-appbundle disables HMR in YAML so one stdio connection never observes a replacement bridge or Agent dependency.
Dev Note
Working context for maintainers — click to expand
None.