[BUG] Running the latest dsh built from source fails to boot the web

[ckqqqq]

Bug Report

 Running the latest dsh built from source fails to boot the `web`                                                                                                                          
 profile: two installed plugins (`dsh-better-sidebar`, `dshmarket`)                                                                                                                        
 crash at loader time because they import `settingsNamespace` and                                                                                                                          
 `installSettingsSection` from `@deepseek-ai/dsh-settings`, which no                                                                                                                       
 longer export them (removed in f4e49ccf8f "refactor(services): move                                                                                                                       
 shared values behind service APIs").                                                                                                                                                      
                                                                                                                                                                                           
 Environment                                                                                                                                                                           
 - dsh: 0.1.2-rc.1, built from source, commit 76fda729 (master)                                                                                                                            
 - OS: macOS 15.7.3 (24G419)                                                                                                                                                               
 - Node.js: v24.19.0                                                                                                                                                                       
 - pnpm: 11.7.0                                                                                                                                                                            
 - Plugins: dsh-better-sidebar, dshmarket (installed under                                                                                                                                 
   ~/.dsh/profiles/web/node_modules)                                                                                                                                                       
                                                                                                                                                                                           
 Steps to reproduce                                                                                                                                                                    
 1. Install dsh-better-sidebar / dshmarket into the web profile                                                                                                                            
 2. `pnpm dsh web`                                                                                                                                                                         
                                                                                                                                                                                           
 Expected behavior                                                                                                                                                                     
 Profile boots; or the loader reports a clear version-compatibility                                                                                                                        
 error for the stale plugins.                                                                                                                                                              
                                                                                                                                                                                           
 Actual behavior                                                                                                                                                                       
 Boot aborts with `plugin tree failed to load` → SyntaxError:                                                                                                                              
 "The requested module '@deepseek-ai/dsh-settings' does not provide                                                                                                                        
 an export named 'settingsNamespace' / 'installSettingsSection'".  

[argszero]

Confirmed — this is a clean, fully-attributable contract drift, and both settingsNamespace and installSettingsSection were removed in the commit you cite.

Source-verified. f4e49ccf8f ("refactor(services): move shared values behind service APIs") is the commit that removed both symbols from the @deepseek-ai/dsh-settings runtime export surface. The current packages/settings/settings/src/index.ts exports redactSecrets, the types SettingsNamespace/SettingsUpdateSource, and the SettingsProvider service — there is no settingsNamespace() function and no installSettingsSection export anymore. So dsh-better-sidebar and dshmarket crashing at loader time is exactly the "plugin imports a removed core export" shape.

The migration path is the settings service API that replaced those helpers. Instead of a standalone installSettingsSection(...), a plugin now registers its namespace schema through the ctx.settings service:

const scope = ctx.settings.register(
  'my-plugin',          // lowercase hyphenated namespace
  schema,               // schemastery schema resolving this namespace
  { base, applies },    // optional composition base + apply timing
)
// scope.get() / scope.watch(cb) / scope.update(patch) / scope.replace(section)

register returns the owner SettingsScope for reads, observation, and updates (see the service definition at packages/settings/settings/src/index.ts:419-458 — it's a registration effect on the plugin's fiber, so disposing the fiber unregisters the namespace and its observers). The namespace must be a lowercase hyphenated identifier (the pattern at index.ts:20).

For settingsNamespace, the was-a-standalone-function form is now register(...).get()-style access plus the namespace type; the type SettingsNamespace is still exported.

Two concrete points worth noting for the plugin authors:

• The migration is a code change on the plugin side, not a downstream codeload to patch. This is the harness's pre-release stance ("foundation over blast radius" — no compatibility shims retained). The right fix is to update dsh-better-sidebar/dshmarket to call ctx.settings.register(...) and pin a peer dependency on @deepseek-ai/dsh-settings >=0.1.2-alpha.2, so a fresh install that matches this build registers correctly.
• This is the same root cause as a related failure I've seen: settingsNamespace removal alone already broke other plugins (e.g. dsh-univer-office). This is a one-family drift: core API moved behind service APIs, old helper exports gone. If you have other installed plugins doing the same, they'll need the same migration.

One diagnostic that would confirm it's purely export-removal (and not a second issue): check <your prefix>'s settings usage — if the plugins only used settingsNamespace/installSettingsSection as helpers (not as a formally typed API), the fix is the ctx.settings.register(...) swap above. If they were dereferencing these at module scope (top-level import), that's the loader crash you're seeing.

Happy to review the actual dsh-better-sidebar/dshmarket diff if you point me at the changed lines — the migration is mechanical but there's a typing subtlety (the namespace must be validated against the lowercase-hyphenated pattern).