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 |
|---|---|
| React and Slot adapters for Session Controller lists, interaction state, and per-session context. | package-reference |
@deepseek-ai/dsh-client-ui-session
English | 中文
Summary
Use this package to expose Session catalog, retain information, and unified UI status through standard Slot hooks. It materializes per-SessionBinding hooks and props, while SessionProvider can inherit an outer binding or bind an explicit SessionReference. It owns process-local pending-interaction and completion-reminder policy without owning Controller transport, history, or references.
Running status comes from Host list baselines or status events. Subagent catalog rows and retained subagent fallback rows do not establish running status; main view references still acknowledge completions.
Table of Contents
Access Hooks
The package injects the Client remoteAccess service and publishes Session access Hooks over its source(): the root useSessionAccess(sessionId, action) answers on one Session resource, and the Session-scope useAccess(action) answers on the bound Session's resource; the global resource's answer is a different Hook, useRemoteAccess(action), so neither shadows the other. ctx.uiSession.whenAccess(sessionId, action, callback) is the JS counterpart of useSessionAccess: it keeps the callback's effects installed while the current Peer may call action on that Session, with the semantics of ctx.remoteAccess.whenAccess. The SessionMaybe-scope useAccess(action) returns undefined while no Session is bound, which callers treat as not allowed; a decision on the global resource reads useRemoteAccess instead. Snapshot semantics belong to dsh-api-remote-access.
Model Experience
None, as this package adapts browser-side Session state and registers nothing model-facing.
KV Cache effect
None; Session selectors and Slot scopes do not assemble model requests.
Known Limitations and Deferred Work
- Pending interactions are process-local projections — the owning Remote waterfall must replay an outstanding request after a browser reconnect.
Dev Note
Working context for maintainers — click to expand
None.