Skip to content

dsh-workflow-boost 1.3.0

Choose a tag to compare

@SlumberMin SlumberMin released this 16 Nov 16:07
· 2 commits to main since this release

dsh-workflow-boost 1.3.0

Every module is now editable from the DSH plugin settings page. 1.2.0 only exposed one volatile section (stylePack); this release makes all 15 modules plus the master switch live-editable, with no changes to any module's config read sites.

Why the settings page was mostly empty

The host's plugin form is schema-derived and projects only fields declared .volatile() (packages/settings/settings/src/schema.ts :: volatileForm). Ordinary fields are edited from the profile YAML and never rendered. Official plugins such as bash-local mark each editable field individually and read it with .get(). Now this plugin does the same.

Added

  • Field-level volatile across all sections (lib/config.js): every direct scalar field of all 15 modules plus the master enabled switch is declared volatile, guarded for schemastery < 3.19. The real form projects 16 top-level entries / 100 editable fields (verified under schemastery 3.19.0).
  • lib/live-config.js: dereferences the stable .get() references into one plain snapshot and refreshes it IN PLACE on loader/volatile-update. Nested section objects keep their identity, so modules that cached config.<section> still see live values. No module read site changed.
  • lib/module-lifecycle.js: hot-mounts/unmounts modules when a settings-page edit flips an enabled switch; parameter-only edits never remount. Reconciliation is idempotent.
  • test/cases/live-config.mjs: 7 cases covering snapshotting, in-place refresh, plain-config fallback, lifecycle reconciliation and listener ordering.
  • test/verify-config.mjs is now a real settings-form gate: it mirrors the host's volatileForm() projection under the real schemastery package and asserts form coverage, field-level .get() references and in-place refresh. Verified on 3.19.0 and 3.18.2.

Fixed

  • The loader/volatile-update refresh listener is registered before any module is installed. stylePack listens to the same emit and reads the shared snapshot in its handler; Cordis dispatches in registration order, so registering the refresh afterwards made it re-register its prompt section with stale values.

Changed

  • Four array-of-object fields stay ordinary config and are still edited from the profile YAML: duplicateGuard.whitelist, editCheck.checks, goalGate.verifyCommands, hookBus.hooks. The generated form cannot reliably add/remove nested rows.
  • Unit suite 273 -> 280 assertions; checked sources 59 -> 62 files; wiring harness unchanged at 62; package 70 -> 73 files.

Install (DSH 0.2.x)

dsh plugin --profile <profile> add https://github.com/SlumberMin/dsh-workflow-boost/releases/download/v1.3.0/dsh-workflow-boost-1.3.0.tgz

or from git source: dsh plugin --profile <profile> add github:SlumberMin/dsh-workflow-boost.

Verify

node test/check.mjs            # 62 files
node test/unit.mjs             # 280 assertions
node test/verify-harness.mjs   # 62 wiring assertions
node test/verify-config.mjs    # real host: 3.19.0 + 3.18.2
node test/run-case.mjs test/cases/live-config.mjs

The release contains 73 files; SHA256SUMS.txt covers both archives.

Verification scope: checked against DSH 0.2.2-rc.1 source contracts and the real schemastery packages; no live interactive DSH session was run on this machine. After installing, edit one settings-page threshold and confirm the plugin log and behaviour follow it.