@oneinitai/dsh-settings-plus

LIMITATIONS

Known limitations

Stated honestly: - **Deferred to v2** (by plan): the aggregated settings page, per-namespace rejection lists, export/import, and the required-secret save fix. - **Host wire surface in honest degraded state**: T16's distribution smoke test verified plugin install/load and service mounting; the host wire surface (the browser catalog data channel, a real `ctx.fs` adapter, and the Fabric patch end-to-end) still awaits verification after a host upgrade. Today this is an honest degraded state: catalog empty source, Fabric no-op, file writes riding the local `FsLike` channel. - **Fabric dependency posture**: `cordis-fabric` is loaded optionally from the host context at binding time. No facade mounted → safe no-op (the stub row stays disabled, the gateway keeps its default allowlist); facade mounted but malformed → loud error. - **Write scope of `updateComposition`**: only ids that are registered settings namespaces are writable through the service; plain `cordis.yml` composition rows fail loudly and must be edited through the file surface or `cordis.patch.yml`. ### Roadmap (follow-ups) - **L2 browser RPC integration**: wire the client catalog to a real host data channel so it moves off the empty local source. - **L3 external HTTP API**: expose the settings service over HTTP on demand. - **Host version range lock**: keep the compatible host range pinned (see `peerDependencies`) and re-verify the wire surface after the host upgrade.