@linxin666/dsh-client-ui-skin-center

Configuration

• Enable switch: turns the whole card (try-on / apply / background controls) on or off; persisted in the v2 active-state document.
• Background sliders: occlusion (0–100%), two backdrop blur radii, input-card blur (0–20 px), and bubble opacity (0–100%); persisted in the same v2 document.
• Background persistence (remote-capable): background values live in the v2 active-state document ($DSH_HOME/skin-center-active.json, the background section) and are read/written through GET|POST /api/skin-center/v2/active, so paired remote desktops — where the settings surface is loopback-only — load and keep them across sessions. The skin-background section of the plugin's own configuration stays as the settings page's input face: a customized section is migrated into the v2 store once at boot, and later page edits are forwarded by the client. Card edits do not write back to that page, so it may show stale values until its next edit.
• Wallpaper panel: library folders, selection, render mode (live / static frame), dim, blur, pause-on-hidden, sound toggle and volume; persisted in the skin-wallpaper section of the plugin's own configuration.
• Custom theme: light/dark accent, background, foreground and contrast profiles plus the applied marker; persisted as a versioned contract in the skin-custom-theme section of the plugin's own configuration. Wallpaper selection and rendering remain owned by skin-wallpaper.
• Where these settings live: the three sections are one plugin configuration — the profile entry's own Config. The Host derives that entry's settings page from the schema in the GUI, and the card writes the same values; there is no separate settings document.
• User skin directory: $DSH_HOME/skins//; override precedence is DSH_SKINS_HOME, then DSH_SKINS_DIR, then $DSH_HOME/skins.