v0.5.20: No Separate Starter Switch

This patch release contains the three pull requests merged after v0.5.19:

• The Starter's readiness is part of its component group (#314): 0.5.18 and 0.5.19 listed a separate readiness row, dsh-mnemon/starter, on the Plugins page, and the component group waited for it. Turning that row off, for example to silence an error after an update, left every component waiting for mnemonStarterReady: dsh web started without the Memory System, and the desktop app failed its start and offered to remove the plugin. The group, mnemon-bundle, now names dsh-mnemon/bundle, which prepares the Starter's dependency resolution itself and then mounts the components with DSH's own cordis:group. Enable now still works without a restart, the row is gone, and a profile stuck in that state recovers after the update and a restart.
• Recovery after updates (#313, #315): the installation guide covers ERR_PACKAGE_PATH_NOT_EXPORTED after an update without a restart, waiting for service: mnemonStarterReady with the desktop app's recovery page, and pnpm's one-day window falling back more than one release.

#Upgrade and compatibility

Supported hosts are unchanged: DSH 0.1.7-rc.2 (npm latest) and DSH 0.2.0-rc.1 (npm next). Complete profiles require Node ^22.19.0 || >=24.0.0. Older hosts should retain v0.5.16.

Install dsh-mnemon@0.5.20 through Plugins → Add plugin, then choose Enable now. The CLI alternative is:

dsh plugin --profile web add dsh-mnemon@0.5.20

Include the version for the first 24 hours after publication. pnpm 11 does not pick a version published less than a day ago, and until 17:31 UTC on 2026-09-29 it falls back to 0.5.17, because 0.5.18 and 0.5.19 were both published on 2026-09-28; DSH 0.2 refuses 0.5.17. A versioned install pins the version; upgrade it later with dsh plugin --profile web update --latest dsh-mnemon.

• Existing installations: for the first 24 hours run dsh plugin --profile web add dsh-mnemon@0.5.20, because until then pnpm 11 keeps update and update --latest on the installed version; afterwards dsh plugin --profile web update dsh-mnemon (update --latest for a versioned install) works. Then restart DSH. Desktop users update from the app's Plugins page and then quit and reopen the app. Until that restart, an update from 0.5.18 or 0.5.19 reports mnemon-bundle (dsh-mnemon/bundle): pending (waiting for service: mnemonStarterReady), because the running Loader keeps the old group.
• A leftover - id: mnemon-starter row in a profile patch matches nothing and is ignored. The desktop app logs patch: entry "mnemon-starter" not found; the two lines can be deleted. dsh-mnemon/starter stays exported for compositions that still insert it.
• The container row on the Plugins page reads dsh-mnemon/bundle instead of cordis:group, and as before it shows Off (upstream #649).
• DSH's config schema export (dsh web --dump-config-schema) walks only native groups, so it now reports mnemon-bundle as an unrecognized carrier and leaves out Mnemon's component schemas, as it does for DSH's own agent presets. Runtime configuration and profile patches are unaffected.

No memory storage or configuration migration is required.

#Changed packages

The Starter still pins 17 component packages, all unchanged.

#Verification

The versioned release acceptance installs the release package through Add plugin on both supported hosts. The component group evidence compares the Plugins page before and after. The cold start and upgrade record covers the web, the command line, Headless and the desktop layout, and updates from 0.5.16 through 0.5.19. Publication verifies the complete pinned composition, the Registry installation and the real upgrade before creating the GitHub release.

Previous release: v0.5.19.