v0.5.2: Atomic Starter Disable and Independent Releases

v0.5.2 fixes the v0.5 Starter lifecycle regression reported in Issue #185. It also completes the one-time transition from coordinated package versions to independently versioned Source, Strategy, and Provider releases.

#Fix

The existing mnemon Entry remains the public configuration target and is again the lifecycle switch for the complete Starter:

- id: mnemon
  disabled: true

This override now disables the Core/Host, Runtime, Documents, Memory Spaces, the default three-tier Strategy, and all three optional Strategy enhancements together. DSH no longer leaves four dependent Entries pending on a missing mnemonMemory service, so the Host and WebUI can start normally with Mnemon disabled.

All existing Entry ids and configuration targets remain valid. Disabling the Starter does not uninstall any package, invoke a Provider, migrate storage, or delete memory data. Remove the override, or change it to false, and restart DSH to enable the complete Starter again. PR #186.

#Independent package releases

This release publishes dsh-mnemon and all sixteen official plugins once at 0.5.2. The one-time full release is required because the independent-version transition changes every package's published dependency metadata.

After v0.5.2, a package advances only when its own published artifact changes. dsh-mnemon remains the aggregate Starter and exact tested bill of materials, so it also advances whenever one of its pinned plugin versions changes. The release workflow computes that selection from the previous release, publishes selected plugin dependency layers with bounded concurrency, verifies Registry read-back, and publishes the Starter last. PR #181.

#Upgrade and compatibility

Install the exact stable release in the owning DSH profile and restart it:

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

Use headless instead of web for a Headless profile. The v0.5.2 Starter pins the verified 0.5.2 composition of all sixteen official plugins; normal users do not install them individually. The stable npm channel remains latest.

There is no RPC-authority, credential, storage-path, memory-format, Document-format, Provider-data, or extension-contract migration. Existing v0.5.x profiles and data remain valid. As before any upgrade, stop writers and back up the effective memory root, workspace Documents, DSH profile/configuration, and separately managed Provider data.

#Verification

The reported failure was reproduced from a retained disabled: true profile on DSH 0.1.2-rc.1 with Node.js 22.23.2. Before the fix, Runtime, Documents, Memory Spaces, and the default Strategy remained pending on mnemonMemory; the same profile appeared harmless with the monolithic v0.4.7 Entry.

The corrected build passed complete workspace verification, all package builds, type checks and tests, deterministic output, public-entry and package checks, real DSH Headless activation, and an isolated Linux Node.js 22.23.2 run. A disposable real WebUI profile started normally and showed all eight Mnemon Entries disabled, with no browser errors and no Mnemon tools exposed to the model. The implementation PR retains the screenshot and exact regression fixture.

The release workflow additionally freezes and verifies the selected artifacts, independently installs every plugin, compiles an external SDK consumer, verifies the real Starter composition, reads all packages back from npm, and smoke-tests a Registry-backed upgrade from v0.4.7.

#Rollback

Reinstall dsh-mnemon@0.5.1 in the same profile and restart DSH. No data conversion is required. If the profile keeps id: mnemon disabled after rollback, the v0.5.1 pending-Entry failure can return; remove that override or explicitly disable all four dependent Source/Strategy Entries before starting the older Host.

Previous release: v0.5.1.