* 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 |
|---|---|
| Offer plugin browsing and a Creator draft in three navigation regions. | package-reference |
@deepseek-ai/dsh-client-ui-entry-customization
English | 中文
Desktop product events use the optional product analytics service; ordinary Web interactions are excluded.
Summary
Browse plugins and prepare a reviewable Creator draft from the More menus of the left sidebar, Conversation View tabs, and right-sidebar guide. The Web app loads this package by default. Each region draws its own More button; this package stores nothing.
Table of Contents
- Use this package
- Understand the implementation
- Model Experience
- Known Limitations and Deferred Work
- Dev Note
Use this package
The @deepseek-ai/dsh-web-app bundle loads this package by default; it needs no Plugins switch or profile selection. A region shows its More button only while its actions slot has a registration, so unloading this package removes all three buttons.
Open More beneath the left navigation entries, More conversation views after the Conversation View tabs, or More tools after the right-sidebar guide cards. All three menus offer Browse other plugins (when available) and Create your plugin. The left-sidebar menu lists only unpinned sidebar entries, each with its registered panel icon, before those actions: opening an entry does not pin it, while its separate pin icon returns it to the sidebar and dismisses the menu. Plugins stays fixed in the sidebar. Sidebar and menu entries retain the same registration order; pinning does not reorder them. The current sidebar entry shows a right-aligned check that is replaced in place by the pin action on row hover or keyboard focus. Hovering the pin changes only its color and keeps the whole row highlighted; non-hover devices show the pin action directly. Its tooltip says “Pin to left sidebar”. The Conversation menu also lists folded Views before those actions and marks the active View with a check on the right. Guide and Conversation menus provide no pin controls; none of the menus provide sorting.
Browse other plugins opens the Plugins main list without opening an installation dialog. Create your plugin opens a new or reusable blank Session with the Creator preset and adds a short localized request for a plugin in that region to its draft: an empty draft takes the request as its text, and an existing draft keeps its text, references, and attachments with the request appended as a new paragraph. It never sends a message. Review and send the draft yourself. Creation remains available regardless of the region’s entries; a separator appears only between unpinned sidebar entries or folded Views and the actions, before browsing when available or before creation otherwise.
On Desktop, Browse other plugins and Create your plugin report more_menu_item_click before they act, with action=browse_plugins or action=create_plugin and the menu's region: sidebar for More, conversation for More conversation views, and rightbar for More tools. The menus report no exposure events. Without the analytics service, both actions behave the same and report nothing.
The browse-plugins row appears only while the pluginNavigation service is present; the plugin starts without it. Its absence removes only browsing, not More buttons, unpinned sidebar entries, folded Views, or creation.
Understand the implementation
Implementation internals — click to expand
apply registers EntryMenuContent under id entry-customization into sidebar.panellist.actions, conversation.session.header.views.actions, and sidebar.right.tab.guide.actions through ctx.slots.inject, so each registration follows its region's declaration lifetime. The regions render these slots inside their own Menu; the rows call onDismiss before browsing or creating. The sidebar menu consumes its owner’s unpinned entries and navigation and pin callbacks; the Conversation menu consumes its owner’s folded entry list and navigation callback.
Each registration's inject supplies its region and two callbacks. Each callback first calls ctx.get('productAnalytics')?.track('more_menu_item_click', { region, action }). Browsing then calls ctx.get('pluginNavigation')?.openList(); ui-plugin-manager provides that service only while the Plugins page has access, so this package reads it optionally and never lists it in inject. Creation then calls uiWorkspace.startSession(undefined, { agentPreset: 'cordis', prompt, whenDraftExists: 'append' }) with the region's localized prompt; it does not go through ui-agent-preset, so the preset chip plays no introduction. The dsh-web-app bundle patch mounts the browser plugin.
Model Experience
None, as the package manages browser launchers and prepares an unsent, reviewable draft; only user submission sends its text to the model.
KV Cache effect
None; the package neither assembles nor sends model requests.
Known Limitations and Deferred Work
- Only the left sidebar provides pin controls: its rows unpin, and its More menu pins. Pin choices remain in memory in the region owner; plugin reload restores defaults.
- Legacy pin values in localStorage are neither read nor written.
- Create your plugin does not check whether the Creator preset exists. Without it, Session creation fails, the Workspace shows its creation-failure notice, and no draft is prepared. Draft preparation also requires a resolvable Workspace; without one, the existing flow reports that a Workspace is required.
- Conversation owns the estimated tab split; these menus provide no sorting.
- Conversation controls follow the existing nonblank-Session header and Coding Tools eligibility. Right-sidebar controls require a selected Session and appear on its guide page.
- The menus do not list plugins; use the browsing action to open the Plugins page.
Dev Note
Working context for maintainers — click to expand
None.