Files
deepseek-harness/packages/experimental/personalized-recommendations
Turtle 38c7a9fbf4 feat(release): publish package source, declaration maps, and documentation (#5884)
* 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
2026-11-05 00:22:36 +08:00
..

description, kind
description kind
Enable personalized page proposals and built-in plugin recommendations below answers with one experimental bundle. package-bundle

@deepseek-ai/dsh-personalized-recommendations

English | 中文

Summary

Get an optional card below an answer for two kinds of need: a page or small tool you want to keep, and a built-in plugin that provides a capability you ask about. Nothing is built or enabled until you click Create or Enable on the card. Enable Personalized recommendations on the Web or Desktop Plugins page; shipped profiles leave it disabled. Its page lists both features and their card rows, each with its own switch.

Table of Contents


Use this package

Open Plugins → More → Experimental plugins and enable Personalized recommendations. Enabling pins it to the main Plugins list; disabling returns it to the secondary page only. While the bundle is on, its page lists six rows in this order, each with its own switch:

Row Package Contributes
Action cards action-cards The card tool, card state, user actions and status notices
Action card display client-ui-action-cards The card frame below answers
Personalized pages creation-recommendations Page proposals and their background creation
Personalized page cards client-ui-creation-recommendations The page card body
Plugin recommendations plugin-recommendations Built-in plugin recommendations and enabling
Plugin recommendation cards client-ui-plugin-recommendations The plugin card body

Switch off Personalized pages or Plugin recommendations to keep only the other feature: the switched-off feature withdraws its skill and card kind, and its earlier cards accept only Not now. Both features need the Action cards row; switching it off stops both until it is on again. Without a card body row, a card shows its proposal title and brief with Not now only. The Action cards row's queuedMessageLimit field sets how many queued next-turn messages make the card tool refuse the current turn's card. The Plugins page has no settings page for that row, so change the field with an id: action-cards override in the profile's cordis.patch.yml.


Understand the implementation

Maintainer details — click to expand

The static cordis.patch.yml inserts the six rows with their package-owned ids and no configuration. This bundle is the only layer that declares these ids, so the plugin manager addresses each row by its id and the Plugins page can switch it. Both feature plugins inject actionCards and register their card kinds with it; the three browser rows register the card frame and the two card bodies. src/index.ts exports nothing.


Further Exploration

Action cards · Personalized pages · Plugin recommendations · Plugin manager page


Model Experience

Indirectly, through the two features' skills, the shared propose_action tool and the card status notice, which the row packages document.

KV Cache effect

Enabling the bundle adds the two skills' catalog entries to requests; the card tool joins the declarations only after a card skill loads, as described on the action cards page.

Known Limitations and Deferred Work

  • The bundle page lists every row the patch inserts, including the four card rows that only support the two features; it cannot mark a row as supporting or hide it.
  • Each feature's own limitations are on its page: Personalized pages and Plugin recommendations.

Dev Note

Working context for maintainers — click to expand

None.