Yichen Jiang
93e67201dd
Each official settings page now lives in a client package of its own: `ui-settings-shell`, `ui-settings-agent-loop`, `ui-settings-subagent` and `ui-settings-web-search` register into `plugins.item` while the Host serves their namespaces, through the new `settingsScope.whileServed` watch, each with its own dictionary and styles. The form model, the fields and the form move to `ui-primitives` as the shared settings kit, so a community package's browser half builds a page the same way. `ui-settings-plugins` keeps only the Built-in plugins section shell around the inventory tab. The companions hold Loader rows in `web-app` behind the section; the client catalog, config catalog and module graph regenerate; the settings-card cookbook walks through a companion package.
11 lines
490 B
TypeScript
11 lines
490 B
TypeScript
/**
|
|
* Agent loop settings page, node half. The empty apply exists so the plugin
|
|
* appears in the host cordis.yml / Loader; the browser half owns the page
|
|
* through exports["./client"], discovered from the package.json dsh.client
|
|
* declaration. The `agent-loop` namespace the page edits is registered by the
|
|
* agent loop, so this package registers no namespace of its own.
|
|
*/
|
|
|
|
/** Host plugin body — no host-side behavior for this surface plugin. */
|
|
export function apply(): void {}
|