dsh-maestro-config

Across the dsh-maestro plugin suite, several plugins often need to read and write the same user preferences, yet typically each one manages its own file. Settings end up scattered, writes silently overwrite each other, and no plugin can learn that a neighbor just changed a value. dsh-maestro-config solves this by collapsing all shared settings into a single namespaced store at ~/.dsh/maestro/settings.json (locked to 600), partitioned by domain so that each plugin owns only its own slice.

The core surface is intentionally small: listDomains enumerates registered config domains; get retrieves a domain's full or partial fields; set applies a patch-merge write so you update only what changed without clobbering siblings. Whenever any domain is modified, subscribed onChange callbacks fire, letting other plugins react in real time. A loopback RPC channel (maestro.config) exposes list, get, and set for lightweight cross-process or cross-profile integration.

This plugin is aimed at developers building or maintaining dsh-maestro suite plugins who want a shared, conflict-free settings layer without hand-rolling JSON I/O and file-watching logic. It is designed as an optional layer: every plugin bundles dsh-maestro-config-lib internally, so the suite keeps working standalone—installing this package simply promotes the shared logic into a first-class service with domain ownership and change notification.