dsh-background-by-model 0.8.2 → 0.9.0

package/lib/client.js

@@ -4,8 +4,8 @@ window.__ModuleLoader__.load({
 		var module = { exports: {} };
 		var exports = module.exports;
 		Object.defineProperty(exports, Symbol.toStringTag, { value: "Module" });
-		let react = require("react");
 		let react_jsx_runtime = require("react/jsx-runtime");
+		let react = require("react");
 		let react_dom = require("react-dom");
 		//#region src/client/runtime.ts
 		function resolveStore() {
@@ -16,384 +16,39 @@ window.__ModuleLoader__.load({
 		}
 		const defineStore = resolveStore().defineStore;
 		//#endregion
-		//#region src/client/i18n.ts
-		const NS = "settings.anyBg";
-		const zh = {
-			nav: "模型背景",
-			brandTag: "按模型换背景",
-			pageInterface: "界面",
-			pageModelBg: "模型背景",
-			pageProfile: "配置",
-			descInterface: "为主界面的各个区域单独调节透明度，营造空间层次感。这里的设置对所有模型生效",
-			descModelBg: "每条规则 = 一个匹配串 + 一组背景图与外观。切换模型时，从上往下找第一条匹配串出现在模型名里的规则；都没中就使用第 1 条。一条规则可以放多张图，按你设的节奏轮换",
-			descProfile: "调整壁纸切换效果，并把当前全部规则连同图片导出备份，或从文件一键恢复",
-			uiTitle: "主界面",
-			uiOpacity: "透明度",
-			uiOpacityBg: "主背景",
-			uiOpacitySide: "左侧栏",
-			uiOpacityCard: "卡片与菜单面板",
-			uiOpacityCode: "代码块",
-			uiOpacityInput: "输入框与控件",
-			uiSop: "设置界面透明度",
-			uiChatRegion: "对话文本框",
-			uiTrajectory: "轨迹页",
-			uiPage: "插件页面",
-			uiPreview: "右侧栏",
-			statusUnknownHint: "检测不到时一律使用第 1 条可用规则；切换一次模型或稍等片刻会自动重试",
-			statusSourceDefaultHint: "只读到宿主默认模型，它不是本会话当前选择的模型；本会话的模型选择可用后会自动纠正",
-			statusNoteNoService: "仍未拿到会话服务（会话控制器晚于本插件加载），正在自动重试",
-			statusNoteNoSession: "会话服务已就绪，但还没有当前会话 id",
-			statusNoteNoProjection: "拿不到本会话的模型选择投影（binding / projections 不可用）",
-			statusNoteEmptySelection: "本会话的模型选择投影还没有值（切一次模型即可写入）",
-			hostStaleHint: "检测到 DSH 主进程仍在运行旧版插件：新版配置格式它还读不懂，为避免丢规则，本次只改界面不写入配置。重启 DSH 后多图与轮换即可正常保存",
-			tryoutTitle: "匹配试跑",
-			tryoutPlaceholder: "输入模型名，如 deepseek-flash",
-			tryoutUseCurrent: "填入当前模型",
-			tryoutHit: "命中规则",
-			tryoutFallback: "无匹配 · 走兜底规则",
-			tryoutNone: "没有可用规则（规则需要启用，并且有图片或主题色）",
-			tryoutEmpty: "输入模型名即可试跑",
-			autoExtract: "选图后自动取主题色",
-			ruleAdd: "新增规则",
-			ruleNoneHint: "还没有规则，点上面的「新增规则」新建一条",
-			ruleFallbackBadge: "兜底",
-			ruleMatchPlaceholder: "如 flash / glm（忽略大小写，留空则不参与匹配）",
-			ruleEnabled: "启用",
-			ruleUp: "上移",
-			ruleDown: "下移",
-			ruleRemove: "删除规则",
-			tabListLabel: "规则",
-			tabPick: "选择规则",
-			tabMore: "更多规则",
-			tabUnnamed: "未命名规则",
-			tabLive: "正在使用",
-			tabRotating: "轮换中",
-			tabOff: "已停用",
-			ruleRemoveConfirm: "再点一次删除",
-			ruleNoImage: "尚未选择图片",
-			ruleFromUrl: "从网址",
-			ruleUrlPlaceholder: "粘贴图片网址 https://…",
-			ruleUrlApply: "应用",
-			ruleUrlCancel: "取消",
-			ruleUrlApplying: "加载中…",
-			ruleUrlBadHttp: "仅支持 http/https 图片网址",
-			ruleUrlFail: "获取图片失败",
-			ruleImageRemove: "移除",
-			ruleEmptyHint: "这条规则还没有图片，也没有自己的主题色：没有可显示的内容，匹配和兜底都会跳过它",
-			ruleColorOnlyHint: "这条规则还没有图片：不会铺壁纸，界面只用这个主题色",
-			ruleImagePendingHint: "这张图片还没有取到内容，稍后会自己出现（也可以直接替换它）",
-			ruleColor: "主题色",
-			ruleColorNone: "跟随系统主题",
-			ruleColorNoneHint: "未设颜色时跟随系统主题：界面用宿主的配色，壁纸与各部位的透明度照旧生效",
-			ruleColorPick: "自定义颜色",
-			ruleColorPickHint: "优先从本图取色，取不到就用默认色",
-			ruleColorNoImageHint: "这条规则还没有图片，取不到色：选一个颜色可以只铺主题色，或先添加图片",
-			ruleColorPendingImageHint: "这张图片还没有取到内容，暂时取不了色：可以直接选一个颜色，或等它加载完",
-			ruleColorExtract: "从本图提取",
-			ruleColorTargetImage: "作用于选中的图片：",
-			ruleColorTargetRule: "作用于本规则（它还没有图片）",
-			ruleLayout: "布局模式",
-			ruleLayoutNoImage: "添加图片后可分别设置每张图的布局模式",
-			ruleFramingEdit: "编辑位置",
-			ruleOpacity: "背景透明度",
-			ruleBrightness: "背景亮度",
-			ruleBlur: "背景模糊",
-			ruleBlurHint: "这三条滑块都作用于壁纸层；界面页里的透明度作用于界面各区域，两者互不影响",
-			rotTitle: "多图轮换",
-			rotEnable: "轮换这组图",
-			rotNeedTwo: "至少两张图才能轮换",
-			rotEvery: "每张停留",
-			rotCustom: "自定义秒数",
-			rotSeconds: "秒",
-			rotOrder: "换图顺序",
-			rotOrderSeq: "按顺序",
-			rotOrderShuffle: "随机",
-			rotOnSwitch: "切换模型时也换一张",
-			rotNext: "下一张",
-			rotNextInactive: "只有正在生效的规则能换画面上的图",
-			rotPos: "第",
-			rotShowing: "正在显示",
-			rotAddImage: "添加",
-			rotReplaceImage: "替换",
-			rotDragHint: "拖动排序",
-			rotDblHint: "双击切换",
-			rotEvery10s: "10 秒",
-			rotEvery30s: "30 秒",
-			rotEvery1m: "1 分钟",
-			rotEvery5m: "5 分钟",
-			rotEvery30m: "30 分钟",
-			bgModeFit: "适应",
-			bgModeFill: "填充",
-			bgModeStretch: "拉伸",
-			bgModeTile: "平铺",
-			bgModeCenter: "居中",
-			editorTitle: "背景编辑器",
-			editorHint: "拖动移动画面，滚轮缩放大小",
-			editorCommit: "确认",
-			editorCancel: "取消",
-			editorReset: "重置",
-			extracting: "取色中…",
-			extractDone: "已应用图片配色",
-			extractFail: "未在这张图里找到鲜明的颜色，请换一张",
-			eyedropper: "从图片取色",
-			pickerTitle: "从图片取色",
-			pickerHint: "移动鼠标预览颜色，点击图片选取为主题色",
-			pickerClose: "关闭",
-			crashTitle: "界面渲染出错",
-			crashDesc: "设置面板遇到问题，点击下方按钮重置后重试",
-			crashReset: "重置面板",
-			exportTheme: "导出配置",
-			importTheme: "导入配置",
-			exportCardTitle: "导出配置",
-			exportCardDesc: "把全部规则、每条规则的颜色/布局/透明度/模糊与图片打包为 dsh-background-by-model-theme.json",
-			importCardTitle: "导入配置",
-			importCardDesc: "从之前导出的 JSON 文件一键恢复全部规则（会覆盖当前规则与图片）",
-			toastExportDone: "配置文件已开始下载",
-			importDone: "已导入配置",
-			importFail: "导入失败，文件格式不正确",
-			recCardTitle: "推荐配置",
-			recCardDesc: "从项目素材库下载作者维护的一整套配置（规则、壁纸与接口设置），一键替换当前的全部内容",
-			recAdopt: "采用推荐配置",
-			recBusy: "正在下载",
-			recConfirmTitle: "替换当前的全部配置？",
-			recConfirmBody: "会先删除你现在的全部规则与壁纸，再写入这份推荐配置。删除的文件无法恢复。",
-			recStatRules: "条规则",
-			recStatImages: "张壁纸",
-			recConfirmOk: "删除并替换",
-			recConfirmCancel: "取消",
-			recDone: "已采用推荐配置",
-			recFailNetwork: "推荐配置下载失败，请检查网络后重试",
-			recFailNotProfile: "素材库返回的内容不是配置，请稍后重试",
-			recFailNewer: "这份推荐配置需要更新的插件版本，未做任何改动",
-			recFailTooMany: "这份推荐配置列出的图片数量超出限制，未做任何改动",
-			recFailTooLarge: "这份推荐配置体积过大，未做任何改动",
-			recFailImage: "这张壁纸没拿到（素材库里缺这个文件）：",
-			recFailApply: "未能写入推荐配置，你原来的配置没有被改动",
-			footerTag: "按模型换背景插件",
-			repoLink: "在 GitHub 上打开仓库",
-			holidayTitle: "节日特殊背景",
-			holidayEnable: "启用节日特殊背景（中秋当天、国庆 10 月 1–7 日）",
-			trTitle: "切换效果",
-			trEffect: "切换方式",
-			trEffectFade: "淡入淡出",
-			trEffectNone: "直接切换",
-			trEffectZoom: "缩放淡入",
-			trEffectSlide: "平移推入",
-			trEasing: "缓动",
-			trEasingEase: "标准",
-			trEasingLinear: "匀速",
-			trEasingOut: "先快后慢",
-			trEasingInOut: "两端慢",
-			trDuration: "切换时长",
-			trPreview: "试放",
-			trHint: "效果对所有换图生效：切模型、轮换、手动下一张、节日。「直接切换」和 0 秒一样是硬切",
-			trReducedHint: "系统开启了「减少动态效果」，实际切换不会播放动画"
-		};
-		const en = {
-			nav: "Model background",
-			brandTag: "Per-model wallpaper",
-			pageInterface: "Interface",
-			pageModelBg: "Model background",
-			pageProfile: "Profile",
-			descInterface: "Tune opacity per surface to build depth. These settings are global and apply to every model",
-			descModelBg: "Each rule is a match string plus a set of wallpapers and one look. On a model switch the list is scanned top-down for the first match string contained in the model name; if nothing hits, rule 1 is used. A rule can hold several images and rotate through them on a rhythm you set",
-			descProfile: "Tune how the wallpaper switches, and back up every rule together with its image — or restore one from a file",
-			uiTitle: "Interface",
-			uiOpacity: "Opacity",
-			uiOpacityBg: "Main background",
-			uiOpacitySide: "Left panel",
-			uiOpacityCard: "Cards & menus",
-			uiOpacityCode: "Code blocks",
-			uiOpacityInput: "Input & controls",
-			uiSop: "Settings interface opacity",
-			uiChatRegion: "Conversation text frame",
-			uiTrajectory: "Trajectory view",
-			uiPage: "Plugin pages",
-			uiPreview: "Right panel",
-			statusUnknownHint: "Without a detected model rule 1 is always used; switching the model once or waiting a moment retries automatically",
-			statusSourceDefaultHint: "Only the host-wide default model could be read — that is not necessarily this session's selection. It self-corrects once this session's model selection is available.",
-			statusNoteNoService: "The sessions service is not available yet (the session controller loads after this plugin); retrying automatically",
-			statusNoteNoSession: "The sessions service is up but reports no current session yet",
-			statusNoteNoProjection: "This session's model-selection projection is unreachable (no binding / projections)",
-			statusNoteEmptySelection: "The model-selection projection exists but carries no value yet (selecting a model once writes it)",
-			hostStaleHint: "The DSH host process is still running the older plugin, which cannot read the new config shape. To avoid dropping rules, this session changes the interface but holds every config write — restart DSH and multi-image plus rotation will save normally",
-			tryoutTitle: "Match test",
-			tryoutPlaceholder: "Type a model name, e.g. deepseek-flash",
-			tryoutUseCurrent: "Use current model",
-			tryoutHit: "matches rule",
-			tryoutFallback: "no match · fallback rule",
-			tryoutNone: "No usable rule (a rule needs to be enabled and carry an image or a theme color)",
-			tryoutEmpty: "Type a model name to test the list",
-			autoExtract: "Extract the theme color when an image is chosen",
-			ruleAdd: "Add rule",
-			ruleNoneHint: "No rules yet — use “Add rule” in the tab strip above",
-			ruleFallbackBadge: "fallback",
-			ruleMatchPlaceholder: "e.g. flash / glm (case-insensitive, empty never matches)",
-			ruleEnabled: "Enabled",
-			ruleUp: "Move up",
-			ruleDown: "Move down",
-			ruleRemove: "Remove rule",
-			tabListLabel: "Rules",
-			tabPick: "Pick a rule",
-			tabMore: "More rules",
-			tabUnnamed: "Unnamed rule",
-			tabLive: "In use",
-			tabRotating: "Rotating",
-			tabOff: "Disabled",
-			ruleRemoveConfirm: "Click again to delete",
-			ruleNoImage: "No image yet",
-			ruleFromUrl: "From URL",
-			ruleUrlPlaceholder: "Paste an image URL https://…",
-			ruleUrlApply: "Apply",
-			ruleUrlCancel: "Cancel",
-			ruleUrlApplying: "Loading…",
-			ruleUrlBadHttp: "Only http/https image URLs are supported",
-			ruleUrlFail: "Could not fetch the image",
-			ruleImageRemove: "Remove",
-			ruleEmptyHint: "This rule has no image and no theme color of its own: it has nothing to show, so matching and the fallback both skip it",
-			ruleColorOnlyHint: "No image in this rule yet: no wallpaper is shown, and the interface is painted from this theme color alone",
-			ruleImagePendingHint: "This image has no content yet — it appears once it loads; you can also replace it",
-			ruleColor: "Theme color",
-			ruleColorNone: "Follow system theme",
-			ruleColorNoneHint: "Without a color this rule follows the system theme: the host palette paints the interface while the wallpaper and every opacity slider keep working",
-			ruleColorPick: "Custom color",
-			ruleColorPickHint: "Extracts from this image when it can, otherwise uses a default color",
-			ruleColorNoImageHint: "This rule has no image to take a color from: pick a color to tint the interface alone, or add an image first",
-			ruleColorPendingImageHint: "This image has no content yet, so there is nothing to extract from: pick a color directly, or wait for it to load",
-			ruleColorTargetImage: "Applies to the selected image:",
-			ruleColorTargetRule: "Applies to this rule (it has no image yet)",
-			ruleColorExtract: "Extract from image",
-			ruleLayout: "Layout mode",
-			ruleLayoutNoImage: "Add an image to give each one its own layout mode",
-			ruleFramingEdit: "Edit position",
-			ruleOpacity: "Background opacity",
-			ruleBrightness: "Background brightness",
-			ruleBlur: "Background blur",
-			ruleBlurHint: "These three sliders all treat the wallpaper layer; the opacity on the Interface page affects interface surfaces — they are independent",
-			rotTitle: "Image rotation",
-			rotEnable: "Rotate these images",
-			rotNeedTwo: "At least two images are needed to rotate",
-			rotEvery: "Dwell time per image",
-			rotCustom: "Custom seconds",
-			rotSeconds: "s",
-			rotOrder: "Order",
-			rotOrderSeq: "In order",
-			rotOrderShuffle: "Shuffle",
-			rotOnSwitch: "Also step on a model switch",
-			rotNext: "Next image",
-			rotNextInactive: "Only the active rule can step the background",
-			rotPos: "Image",
-			rotShowing: "On screen",
-			rotAddImage: "Add",
-			rotReplaceImage: "Replace",
-			rotDragHint: "drag to reorder",
-			rotDblHint: "double-click to show",
-			rotEvery10s: "10 s",
-			rotEvery30s: "30 s",
-			rotEvery1m: "1 min",
-			rotEvery5m: "5 min",
-			rotEvery30m: "30 min",
-			bgModeFit: "Fit",
-			bgModeFill: "Fill",
-			bgModeStretch: "Stretch",
-			bgModeTile: "Tile",
-			bgModeCenter: "Center",
-			editorTitle: "Background editor",
-			editorHint: "Drag to move, scroll to zoom",
-			editorCommit: "Confirm",
-			editorCancel: "Cancel",
-			editorReset: "Reset",
-			extracting: "Extracting…",
-			extractDone: "Image colors applied",
-			extractFail: "No vivid color found in this image, try another",
-			eyedropper: "Eyedropper",
-			pickerTitle: "Pick from image",
-			pickerHint: "Hover to preview, click to pick as the theme color",
-			pickerClose: "Close",
-			crashTitle: "Section crashed",
-			crashDesc: "The panel hit an error. Reset below to recover.",
-			crashReset: "Reset panel",
-			exportTheme: "Export",
-			importTheme: "Import",
-			exportCardTitle: "Export profile",
-			exportCardDesc: "Bundle every rule — color, layout, opacity, blur — and its image into dsh-background-by-model-theme.json",
-			importCardTitle: "Import profile",
-			importCardDesc: "Restore every rule and image from a previously exported JSON file (replaces the current set)",
-			toastExportDone: "Export started",
-			importDone: "Profile imported",
-			importFail: "Import failed — invalid file",
-			recCardTitle: "Recommended profile",
-			recCardDesc: "Download the author's own full setup — rules, wallpapers and interface settings — and replace everything with it",
-			recAdopt: "Use recommended profile",
-			recBusy: "Downloading",
-			recConfirmTitle: "Replace your entire profile?",
-			recConfirmBody: "Every rule and wallpaper you have is deleted first, then this profile is written in its place. Deleted files cannot be recovered.",
-			recStatRules: "rules",
-			recStatImages: "wallpapers",
-			recConfirmOk: "Delete and replace",
-			recConfirmCancel: "Cancel",
-			recDone: "Recommended profile applied",
-			recFailNetwork: "Could not download the recommended profile — check your connection and retry",
-			recFailNotProfile: "The asset host answered with something that is not a profile — try again later",
-			recFailNewer: "This profile needs a newer plugin version. Nothing was changed.",
-			recFailTooMany: "The recommended profile names more images than the plugin will fetch. Nothing was changed.",
-			recFailTooLarge: "The recommended profile is too large. Nothing was changed.",
-			recFailImage: "Could not fetch this wallpaper — the asset host has no such file:",
-			recFailApply: "Could not write the recommended profile — your own is untouched",
-			footerTag: "Per-model wallpaper plugin",
-			repoLink: "Open the repository on GitHub",
-			holidayTitle: "Holiday backgrounds",
-			holidayEnable: "Enable holiday backgrounds (Mid-Autumn day, Oct 1–7)",
-			trTitle: "Switch effect",
-			trEffect: "Transition",
-			trEffectFade: "Cross-fade",
-			trEffectNone: "Instant",
-			trEffectZoom: "Zoom in",
-			trEffectSlide: "Slide in",
-			trEasing: "Easing",
-			trEasingEase: "Standard",
-			trEasingLinear: "Linear",
-			trEasingOut: "Ease out",
-			trEasingInOut: "Ease in-out",
-			trDuration: "Duration",
-			trPreview: "Preview",
-			trHint: "The effect applies to every change: model switch, rotation, manual next, holidays. “Instant” and 0 s are the same hard cut",
-			trReducedHint: "Your system asks for reduced motion, so a real switch will not animate"
-		};
-		//#endregion
-		//#region src/client/transition.ts
-		/**
-		* Resolve the duration one switch uses, in ms (`0` = a hard cut).
-		*
-		*   1. `effect: 'none'` is a hard cut whatever the duration says — asking for no
-		*      animation and asking for 0 ms are the same request, and the effect is the
-		*      more explicit of the two;
-		*   2. otherwise the global `durationMs` decides, because a rule has no notion of
-		*      a transition and there is exactly one duration for every switch.
-		*
-		* A non-finite or negative value answers `0` (a hard cut) rather than a default:
-		* animating for an unknown length is the one answer that cannot be right. The
-		* input is already clamped by the shared sanitizer (`./schema`), so this is a
-		* guard against a hand-edited config, not a second clamp.
-		*/
-		function resolveFadeMs(transition) {
-			if (transition.effect === "none") return 0;
-			return Number.isFinite(transition.durationMs) && transition.durationMs > 0 ? transition.durationMs : 0;
-		}
-		/**
-		* The transform the incoming layer starts from, per effect.
-		*
-		* `zoom` starts ABOVE 1 and settles back to exactly `none`, never below or past
-		* it: the wallpaper would otherwise be left larger than the viewport, cropping a
-		* `fit` framing the user committed by hand. `slide` is a small push because a
-		* full-width travel of a full-bleed wallpaper reads as two wallpapers, not one
-		* transition.
-		*/
-		const START_TRANSFORM = {
-			fade: "none",
-			none: "none",
-			zoom: "scale(1.06)",
-			slide: "translateX(6%)"
+		//#region src/client/transition.ts
+		/**
+		* Resolve the duration one switch uses, in ms (`0` = a hard cut).
+		*
+		*   1. `effect: 'none'` is a hard cut whatever the duration says — asking for no
+		*      animation and asking for 0 ms are the same request, and the effect is the
+		*      more explicit of the two;
+		*   2. otherwise the global `durationMs` decides, because a rule has no notion of
+		*      a transition and there is exactly one duration for every switch.
+		*
+		* A non-finite or negative value answers `0` (a hard cut) rather than a default:
+		* animating for an unknown length is the one answer that cannot be right. The
+		* input is already clamped by the shared sanitizer (`./schema`), so this is a
+		* guard against a hand-edited config, not a second clamp.
+		*/
+		function resolveFadeMs(transition) {
+			if (transition.effect === "none") return 0;
+			return Number.isFinite(transition.durationMs) && transition.durationMs > 0 ? transition.durationMs : 0;
+		}
+		/**
+		* The transform the incoming layer starts from, per effect.
+		*
+		* `zoom` starts ABOVE 1 and settles back to exactly `none`, never below or past
+		* it: the wallpaper would otherwise be left larger than the viewport, cropping a
+		* `fit` framing the user committed by hand. `slide` is a small push because a
+		* full-width travel of a full-bleed wallpaper reads as two wallpapers, not one
+		* transition.
+		*/
+		const START_TRANSFORM = {
+			fade: "none",
+			none: "none",
+			zoom: "scale(1.06)",
+			slide: "translateX(6%)"
 		};
 		/** The properties one effect actually animates — an unchanged property must not
 		*  be put on the transition list, or `fade` would stop being byte-for-byte the
@@ -582,23 +237,16 @@ window.__ModuleLoader__.load({
 		/**
 		* The persisted configuration shape — declared exactly ONCE, for both halves.
 		*
-		* This shape used to be written out twice: the node half owns persistence and
-		* sanitizes every write, the browser half owns the UI and its own reading of the
-		* same file. A field added to only one side was silently dropped by the other
-		* side's sanitizer — the matching slider stayed live in memory, `writeConfig`
-		* wrote a config without it, and the next load fell back to the default.
-		* `blurs.rightbar` / `rightbarOpacity` in 0.3.2 was exactly that bug, and the key
-		* lists were duplicated 6 times across the two halves, so it was due to happen.
-		*
-		* The types, the key lists, the defaults and the pure normalizers therefore live
-		* here and both halves import them: adding a field means editing this file, and
-		* the two halves cannot disagree about the shape. The host additionally logs one
-		* warning per unknown key while sanitizing a write (see `warnUnknownConfigKeys`
-		* in `src/index.ts`), so a field that reaches the node half without being
-		* declared here shows up in the host log instead of quietly disappearing.
+		* The types, the key lists, the defaults and the pure normalizers live here and
+		* both halves import them, so adding a field means editing this file and the two
+		* halves cannot disagree about the shape. (This was written twice until 0.3.2,
+		* when a field declared on one side was silently dropped by the other side's
+		* sanitizer.) The host also logs one warning per unknown key while sanitizing a
+		* write (`warnUnknownConfigKeys` in `src/index.ts`), so a field that reaches the
+		* node half without being declared here shows up in the log.
 		*
-		* Nothing in this module may touch the DOM, Node or the Cordis context: it is
-		* imported by the browser bundle and by the node half alike.
+		* Nothing here may touch the DOM, Node or the Cordis context: it is imported by
+		* the browser bundle and by the node half alike.
 		*/
 		const DEFAULT_BG_STATE = {
 			zoom: 1,
@@ -633,14 +281,14 @@ window.__ModuleLoader__.load({
 			return { ...DEFAULT_ROTATION };
 		}
 		/**
-		* Main interface opacities (0..1), global (Interface page):
-		*   `bg`      main background (`--dsw-alias-bg-base`)
-		*   `sidebar` sidebar (`--dsw-specific-sidebar-fill`)
-		*   `card`    cards/panels (`--dsw-alias-bg-layer-1/2/3`, `--dsw-specific-menu`
-		*             and its 0.1.7 alias `--dsw-menu-surface-fill`)
-		*   `code`    code blocks, banner included (`--dsw-alias-markdown-code-block`,
-		*             `--dsw-alias-markdown-code-block-banner`)
-		*   `input`   input/control surfaces (`--dsw-specific-input-major`)
+		* Main interface opacities (0..1), global (Interface page) — each part is the token
+		* set it owns:
+		*   `bg`       `--dsw-alias-bg-base`
+		*   `sidebar`  `--dsw-specific-sidebar-fill`
+		*   `card`     `--dsw-alias-bg-layer-1/2/3`, `--dsw-specific-menu` (and its alias
+		*              `--dsw-menu-surface-fill`)
+		*   `code`     `--dsw-alias-markdown-code-block`, `…-banner`
+		*   `input`    `--dsw-specific-input-major`
 		*/
 		const PART_OPACITY_KEYS = [
 			"bg",
@@ -688,27 +336,17 @@ window.__ModuleLoader__.load({
 			return rule.images.map((i) => i.slot);
 		}
 		/**
-		* Whether a rule has anything to show at all: an image, or a theme color of its
+		* Whether a rule has anything to show at all: an image, or a theme colour of its
 		* own. Used by matching (`usable` in ./client/modelbg) and by the panel's copy.
 		*
-		* An image is the obvious way a rule paints, and until 0.7 it was the ONLY one —
-		* which stopped being true the moment the last image became removable. A
-		* rule-level theme color is the second: it recolors the interface through the
-		* token palette with no wallpaper involved, so a rule whose pictures were all
-		* removed still paints, and treating it as unusable made every control left on
-		* its card (the wheel, the swatches, the clear-to-system-theme button) dead — the
-		* one state where the panel was confidently showing a lie. It also silently
-		* handed the model to the NEXT rule, so clearing the default rule's images put
-		* another model's wallpaper on the screen.
+		* The rule's own colour counts because it recolours the interface with no
+		* wallpaper involved: a rule whose pictures were all removed still paints, and
+		* treating it as unusable handed the model to the NEXT rule (another model's
+		* wallpaper on screen) while every control left on its card went dead. Per-image
+		* colours do not enter the question at all — an image is already enough.
 		*
-		* Note that a per-image color (0.7.1) does not enter this question at all: an
-		* image is already enough, so the answer here is about the IMAGE LIST being
-		* non-empty, never about what those images are painted in.
-		*
-		* A rule with no image and no color of its own paints nothing: the system theme
-		* is not a paint of this rule's own, so such a rule is skipped by matching, which
-		* is what makes a freshly added rule (empty, colorless) invisible until the user
-		* gives it something.
+		* A rule with neither paints nothing, so matching skips it: a freshly added rule
+		* stays invisible until the user gives it something.
 		*/
 		function ruleCanPaint(rule) {
 			return rule.enabled && (ruleSlots(rule).length > 0 || rule.color !== null);
@@ -718,12 +356,10 @@ window.__ModuleLoader__.load({
 		const DEFAULT_RIGHTBAR_OPACITY = .45;
 		/**
 		* `#RRGGBB` → the `[h, s, l]` triple every rule stores (`s` and `l` in 0..1), or
-		* null when the string is not a hex color.
+		* null when the string is not a hex colour.
 		*
-		* A holiday names its color as hex because that is how a color is quoted, and a
-		* hand-converted triple is a magic number nothing downstream can check. The
-		* conversion lives here rather than in ./holiday because `[h, s, l]` is this
-		* module's own rule shape.
+		* Holidays name their colour as hex (`HOLIDAYS`) because a hand-converted triple
+		* is a magic number nothing downstream can check.
 		*/
 		function hexToHsl(hex) {
 			const m = /^#?([0-9a-f]{6})$/i.exec(hex.trim());
@@ -756,11 +392,8 @@ window.__ModuleLoader__.load({
 		/**
 		* One holiday's appearance, untouched.
 		*
-		* Holidays default to `fill` rather than a rule's `fit`: these are full-bleed
-		* festival wallpapers, and `fit` would letterbox them on every aspect ratio the
-		* art was not cut for. The mode now lives on the IMAGE (see `BgImage.bgMode`), so
-		* that default is written there — and `fill` is what a holiday's read-back
-		* sanitizer refuses to lose (see `normalizeHolidayRule`).
+		* The mode is `fill` rather than a rule's `fit`: full-bleed festival art would be
+		* letterboxed by `fit` on every aspect ratio it was not cut for.
 		*/
 		function defaultHolidayRule(def) {
 			const color = hexToHsl(def.color);
@@ -786,21 +419,13 @@ window.__ModuleLoader__.load({
 			return HOLIDAYS.map(defaultHolidayRule);
 		}
 		/**
-		* A rule with nothing in it yet: no picture, no match string, no color.
-		*
-		* Two states need this factory and they are the same state — a fresh install
-		* (see `freshThemeConfig` and `normalizeConfig`), and the "add rule" tile one
-		* entry further down the list.
+		* A rule with nothing in it yet: no picture, no match string, no colour — a fresh
+		* install's rule 1 and the "add rule" tile alike.
 		*
-		* Such a rule is deliberately valid rather than half-built: it is skipped by
-		* matching until it has something of its own to paint (`ruleCanPaint` — a picture,
-		* or a theme color), which is what makes a rule nobody has filled in yet invisible
-		* instead of letting an empty background steal the fallback from rule 1.
-		*
-		* It used to be born with an allocated slot and an empty image entry, which is
-		* what put a blank tile at position 1 of a new rule's strip — and, worse, stopped
-		* the picture the user added next from being the first one (a rule paints its
-		* FIRST image). The slot is allocated when the first picture arrives.
+		* Valid rather than half-built: `ruleCanPaint` skips it until it has something of
+		* its own, so it cannot steal the fallback from rule 1. It deliberately carries NO
+		* image entry: a rule paints its FIRST image, and a placeholder slot left the
+		* picture the user added next in position 2. The slot is allocated on arrival.
 		*/
 		function blankRule(id) {
 			return {
@@ -816,14 +441,11 @@ window.__ModuleLoader__.load({
 			};
 		}
 		/**
-		* A default config with independent nested objects (never hand out the shared ones).
+		* A default config with independent nested objects (never the shared ones).
 		*
-		* The rule list is seeded with one blank rule rather than left empty: "no rules at
-		* all" is not a state the panel should ever open in, because the first thing a new
-		* user has to do is name a match string and drop a picture in — and the drop target
-		* for that is the rule card, which an empty list has no way to show. The empty
-		* state is still reachable (deleting the last rule is a thing the user can mean),
-		* and is described by `ruleNoneHint`.
+		* Seeded with one blank rule: an empty list has no rule card, and the card is the
+		* only drop target a first picture has. Deleting every rule is still reachable and
+		* is described by `ruleNoneHint`.
 		*/
 		function freshThemeConfig() {
 			return {
@@ -843,7 +465,7 @@ window.__ModuleLoader__.load({
 			};
 		}
 		/** Slot names reach the filesystem, so they are strictly whitelisted. */
-		const SLOT_RE = /^[A-Za-z0-9_-]{1,32}$/;
+		const SLOT_RE$1 = /^[A-Za-z0-9_-]{1,32}$/;
 		function clamp$1(n, lo, hi, def) {
 			return typeof n === "number" && isFinite(n) ? Math.min(hi, Math.max(lo, n)) : def;
 		}
@@ -908,18 +530,12 @@ window.__ModuleLoader__.load({
 			}
 		}
 		/**
-		* Coerce one persisted transition block; a config written before this setting
-		* existed has no `transition` key at all and gets the shipped default, which is
-		* the behaviour it already had.
+		* Coerce one persisted transition block; a config without one gets the shipped
+		* default, which is what it was already showing.
 		*
-		* `legacyMs` is the per-rule `fadeMs` this shape replaced (see `legacyFadeMs`),
-		* adopted only when the incoming config has no `durationMs` of its own — so a
-		* deliberate hand-tuned blend survives the upgrade instead of being dropped with
-		* the field it used to live on.
-		*
-		* `durationMs` is clamped with `0` kept as a real value (a hard cut) rather than
-		* read as "absent": 0 is exactly how a hard cut is asked for without changing
-		* the effect.
+		* `legacyMs` is the per-rule `fadeMs` this shape replaced (`legacyFadeMs`), adopted
+		* only when the incoming config carries no `durationMs` of its own. `0` is kept as
+		* a real value (a hard cut), not read as "absent".
 		*/
 		function normalizeTransition(raw, legacyMs) {
 			const t = raw ?? {};
@@ -934,29 +550,19 @@ window.__ModuleLoader__.load({
 		/**
 		* Coerce one persisted image entry, or null when it lacks a usable slot.
 		*
-		* `inherit` is the RULE's own color, and it is applied only to an entry that has
-		* no `color` key at all — the shape every release before 0.7.1 wrote, where a
-		* rule's color was the only color there was. Lifting it here, once, is what makes
-		* an upgrade a no-op on screen: a themed wallpaper keeps its theme instead of
-		* silently dropping to the system palette, and it happens in the shared sanitizer
-		* so both halves lift identically.
-		*
-		* The KEY's presence is the whole distinction, which is why `null` is not the
-		* same as absent: an entry with `color: null` is an image the user explicitly set
-		* to "follow the system theme", and re-inheriting the rule's color over that
-		* would undo a deliberate choice on every load.
+		* `inherit` (the RULE's colour) is applied only to an entry with no `color` KEY at
+		* all — the shape written before per-image colours, where the rule's colour was the
+		* only one there was. The key's PRESENCE is the whole distinction: `color: null` is
+		* a deliberate "follow the system theme" and must not be re-inherited on every load.
 		*
-		* `inheritMode` is the same one-shot lift for the layout mode, and it is the
-		* caller's to resolve because the two callers answer differently: a user rule
-		* passes the mode its config carried at the RULE level (a schema-5 config, where
-		* 适应/填充 was one choice for the whole rotation), a holiday passes `fill` (its
-		* own default, which is not up for the lift to change). An entry that HAS a
-		* `bgMode` key keeps it — including one that has just been set to a value equal
-		* to the default, which is a decision and not an absence.
+		* `inheritMode` is the same one-shot lift for the layout mode. It is the caller's to
+		* resolve because the callers answer differently: a user rule passes the mode its
+		* config carried at the RULE level (schema 5), a holiday passes its own `fill`. An
+		* entry that HAS a `bgMode` key keeps it, even when it equals the default.
 		*/
 		function normalizeImage(raw, inherit = null, inheritMode = "fit") {
 			const i = raw ?? {};
-			if (typeof i.slot !== "string" || !SLOT_RE.test(i.slot)) return null;
+			if (typeof i.slot !== "string" || !SLOT_RE$1.test(i.slot)) return null;
 			return {
 				slot: i.slot,
 				bgMode: BG_MODES$1.includes(i.bgMode) ? i.bgMode : inheritMode,
@@ -965,36 +571,21 @@ window.__ModuleLoader__.load({
 			};
 		}
 		/**
-		* Coerce one persisted rule, or null when it names no image AT ALL.
+		* Coerce one persisted rule, or null when it names no image ANYWHERE.
 		*
-		* Accepts BOTH image shapes: the 0.7 list (`images`), and the single
-		* `slot`/`bgState` pair every earlier version wrote — the latter is lifted to a
-		* one-entry list here rather than at a dozen call sites, which is what keeps the
-		* rest of the codebase free of "old config" branches. Duplicate slots inside one
-		* rule are dropped: two entries pointing at the same bytes would only make the
-		* rotation look stuck.
+		* Both image shapes are accepted here and nowhere else: the 0.7 list (`images`),
+		* and the single `slot`/`bgState` pair every earlier version wrote, lifted into a
+		* one-entry list. That is what keeps the rest of the codebase free of "old config"
+		* branches. Duplicate slots inside one rule are dropped — two entries pointing at
+		* the same bytes only make a rotation look stuck.
 		*
-		* The rule's color is resolved FIRST and handed to every image entry, because it
-		* is what an entry written before 0.7.1 inherits (`normalizeImage`). The rule keeps
-		* it as well: it is not a default for its images at paint time any more, but it
-		* is still what the rule paints once its last picture is gone.
+		* The rule's colour is resolved FIRST and handed to every image entry (what a
+		* pre-0.7.1 entry inherits), and the rule keeps it: it is what the rule paints once
+		* its last picture is gone. The layout mode makes the same trip from the RULE level
+		* a pre-0.7.5 config carries, so the user's choice survives the move.
 		*
-		* The layout mode makes the same trip in the other direction, and this is the
-		* last release that has to: a config written before 0.7.5 keeps `bgMode` at the RULE
-		* level, where one value covered every picture of a rotation, so it is read here
-		* once and handed to each image as its inherited mode. What the user chose
-		* therefore survives the move the same way it survived the color's — the mode is
-		* not reset to the default on upgrade, and the field it used to live on is simply
-		* not written back.
-		*
-		* An EMPTY list is a legitimate rule, not a broken one: removing a rule's last
-		* picture has to be expressible, and forcing an entry back in is what produced a
-		* phantom blank image that took slot 1 and could never be deleted again (the next
-		* upload landed at position 2 and the rule kept painting nothing). What such a
-		* rule then does is `ruleCanPaint`'s business: with a color of its own it paints
-		* the interface, with neither it is skipped by matching — which the card's own
-		* hint says in so many words. Only a rule that names no image anywhere — no list,
-		* no legacy slot, or a slot that could never be a filename — is dropped.
+		* An EMPTY list is a legitimate rule: removing a rule's last picture has to be
+		* expressible. `ruleCanPaint` decides what such a rule then does.
 		*/
 		function normalizeRule(raw) {
 			const r = raw ?? {};
@@ -1011,7 +602,7 @@ window.__ModuleLoader__.load({
 				seen.add(image.slot);
 				images.push(image);
 			}
-			const legacySlot = typeof r.slot === "string" && SLOT_RE.test(r.slot) ? r.slot : null;
+			const legacySlot = typeof r.slot === "string" && SLOT_RE$1.test(r.slot) ? r.slot : null;
 			if (images.length === 0 && legacySlot !== null) images.push({
 				slot: legacySlot,
 				bgMode: mode,
@@ -1038,17 +629,11 @@ window.__ModuleLoader__.load({
 		/**
 		* Coerce one persisted holiday entry.
 		*
-		* `id`, `images` and every theme color (the rule's and each image's) come from
-		* the DEFINITION, never from disk: a holiday's slot is the only thing tying it to
-		* its bytes, and its theme color is a fixed part of what that holiday looks like —
-		* so a stale or hand-edited value would either orphan the wallpaper, point the
-		* holiday at a rule's image, or paint a festival in a color it does not have.
-		* Everything else is sanitized exactly like a rule's field — except three things
-		* that stay the definition's own: the image list and the rotation (so a festival
-		* can never be swapped or cycled), and the layout mode, which is the definition's
-		* `fill` for the same reason the color is its own — full-bleed art letterboxed by
-		* a stale `fit` is the one thing this feature must not do, and the mode is not
-		* editable for a holiday anywhere in the panel.
+		* `id`, the image list and every theme colour come from the DEFINITION, never from
+		* disk: a stale or hand-edited value would orphan the wallpaper, point the holiday
+		* at a rule's image, or paint a festival in a colour it does not have. The layout
+		* mode and the rotation stay the definition's own for the same reason (a festival
+		* is never swapped or cycled). Everything else is sanitized like a rule's field.
 		*/
 		function normalizeHolidayRule(def, raw) {
 			const r = raw ?? {};
@@ -1081,21 +666,12 @@ window.__ModuleLoader__.load({
 			};
 		}
 		/**
-		* The file-preview panel's own opacity.
-		*
-		* Three states, and the middle one is why this is a function rather than the
-		* one-line fallback every other field gets: a real number is the card's own
-		* value, `null` is "never owned, so follow `opacities.bg`", and a KEY that is not
-		* there at all — a hand-written config, or one written before the option existed
-		* — is the shipped profile's 45% (see DEFAULT_RIGHTBAR_OPACITY).
+		* The file-preview panel's own opacity: a number is the card's own value, `null` is
+		* "never owned, follow `opacities.bg`", and a MISSING key is the shipped 45%.
 		*
-		* `null` has to survive as ITSELF instead of falling through to the default:
-		* every release so far has written it — a panel the user never dragged is
-		* persisted as an explicit `null` — so treating it as "missing" would hand the
-		* shipped 45% to every configuration whose preview panel was following the main
-		* background, a silent change to a setup nobody asked to change. It is also
-		* unreachable from the UI (no control returns to it); it exists for configs that
-		* were written while the shipped default was `null`.
+		* `null` has to survive as itself: every release so far persisted it for a panel the
+		* user never dragged, so treating it as missing would silently hand the shipped 45%
+		* to every configuration that was following the main background.
 		*/
 		function normalizeRightbarOpacity(v) {
 			if (v === null) return null;
@@ -1179,7 +755,6 @@ window.__ModuleLoader__.load({
 		}
 		let activeRuleId = null;
 		let activeMatched = false;
-		let modelLabel = "";
 		/**
 		* Which image of the ACTIVE rule is painted right now.
 		*
@@ -1194,9 +769,6 @@ window.__ModuleLoader__.load({
 			activeRuleId = ruleId;
 			activeMatched = matched;
 		}
-		function setModelLabel(label) {
-			modelLabel = label;
-		}
 		/** The image index the render layer is on, clamped into `rule`'s own range. */
 		function imageIndexOf(rule) {
 			if (rule.images.length === 0) return 0;
@@ -1218,23 +790,16 @@ window.__ModuleLoader__.load({
 			return activeImage()?.slot ?? "";
 		}
 		/**
-		* The theme color in force right now, or null for "follow the system theme".
-		*
-		* Two rungs, in this order and no others:
-		*   1. the color of the IMAGE that is on screen, when the rule has one;
-		*   2. the rule's own color, which is all an image-less rule has to paint with.
+		* The theme colour in force right now, or null for "follow the system theme".
 		*
-		* There is deliberately no third rung where an image INHERITS its rule's color:
-		* a rule's color is not a default for its pictures (see `BgRule.color`). If it
-		* were, a rotation through a green picture, a red one and a system-themed one
-		* could not be expressed at all — clearing a picture's color would only hand it
-		* back to the rule's, and the clear button would look broken. Images that predate
-		* per-image colors get the rule's color LIFTED onto them at read time instead
-		* (`normalizeImage`), so nothing loses its theme on upgrade.
+		* Two rungs and no others: the colour of the IMAGE being painted, else the rule's
+		* own colour (all an image-less rule has). There is deliberately no third rung
+		* where an image inherits its rule's colour — that would make a rotation through a
+		* green, a red and a system-themed picture inexpressible, and clearing a picture's
+		* colour would only hand it back to the rule's.
 		*
-		* The image is the one being PAINTED (`imageIndexOf`), not the one the panel has
-		* selected — the panel's selection is an editing cursor and must not repaint the
-		* interface while the user is fixing another picture's framing.
+		* The image is the one being PAINTED, not the one the panel has selected: the
+		* selection is an editing cursor and must not repaint the interface.
 		*/
 		function activeColor() {
 			const rule = activeRule();
@@ -1414,187 +979,31 @@ window.__ModuleLoader__.load({
 			clearImages();
 			activeRuleId = null;
 			activeMatched = false;
-			modelLabel = "";
 			rotIndex = 0;
 		}
 		//#endregion
-		//#region src/preset.ts
-		/**
-		* JSON with object keys in a fixed (sorted) order — the same string for the same
-		* value, whatever order the object that carried it happened to build its keys in.
-		*
-		* `JSON.stringify` alone is not an identity for a value that came off the wire and
-		* through a sanitizer: key order is an accident of how the object was assembled,
-		* and a resume that missed on it would silently re-download everything (the safe
-		* direction) while a resume that MATCHED on a value it should not have would be
-		* the unsafe one — so this is deliberately total as well: anything JSON cannot
-		* carry (a function, a `Symbol`, `undefined`) serializes as `null` and an
-		* `undefined` property is skipped, exactly as `JSON.stringify` treats it.
-		*/
-		function canonical(value) {
-			if (Array.isArray(value)) return `[${value.map(canonical).join(",")}]`;
-			if (value !== null && typeof value === "object") return `{${Object.entries(value).filter(([, v]) => v !== void 0).sort(([a], [b]) => a < b ? -1 : a > b ? 1 : 0).map(([k, v]) => `${JSON.stringify(k)}:${canonical(v)}`).join(",")}}`;
-			return JSON.stringify(value) ?? "null";
+		//#region src/client/rpc.ts
+		const RPC_CHANNEL = "/dsh-background-by-model";
+		const RPC_NS = "dshBackgroundByModel";
+		const rpcEndpoint = (method) => `${RPC_NS}/${method}`;
+		let hostShape = "unknown";
+		let warnedLegacy = false;
+		/** Whether this bundle may write its config to the host it is talking to. */
+		function canWriteConfig() {
+			return hostShape !== "legacy";
 		}
-		/**
-		* The identity of one revision of the profile: the manifest's shape version plus
-		* the config, in canonical form.
-		*
-		* The profile is served at ONE version of the assets repository, but a version
-		* reference is only as fixed as the tag behind it: re-point the tag and every
-		* edge that has not been purged keeps answering with the previous bytes of the
-		* same URL. So "the profile" is still not guaranteed to be one fixed thing, and
-		* the bytes a previous attempt is holding are only known to belong to what is
-		* being installed when that config comes back the same. Order-insensitivity is
-		* what lets this be a comparison of VALUES rather than of spellings —
-		* `normalizeConfig` (./schema) rebuilds the config it reads, so pinning the key
-		* to the exact key order the wire happened to use would make the hold useless
-		* the moment anything upstream normalized differently.
-		*/
-		function presetKey(version, config) {
-			return `${version}\n${canonical(config)}`;
+		/** Whether the running host process cannot read this bundle's config shape. */
+		function hostIsLegacy() {
+			return hostShape === "legacy";
 		}
-		/**
-		* The bytes of a failed attempt that may be reused for the revision `key` names.
-		*
-		* A fresh object every time, never the held record itself: the caller fills it in
-		* as the rest of the profile arrives, and handing out the same mutable record
-		* would let a re-fetch of one file edit the state the NEXT attempt resumes from.
-		* An empty answer — nothing held, or held for a different revision — is the honest
-		* one either way: the pool then asks for every slot the config names.
-		*/
-		function presetResume(held, key) {
-			if (held === null || held.key !== key) return {};
-			return { ...held.images };
+		function holdWrite() {
+			if (warnedLegacy) return;
+			warnedLegacy = true;
+			console.warn("dsh-background-by-model: the running host is an older build that cannot read this bundle's config shape — holding config writes so its sanitizer cannot drop this profile's rules. Restart DSH to load the new node half.");
 		}
-		/**
-		* The slots of `slots` that `images` does not hold yet, in the config's own order.
-		*
-		* Order matters in the only way it can here: it decides which file a worker takes
-		* first, and the files are not the same size. Only names the CONFIG asked for are
-		* ever returned, so a held picture nothing points at — a slot the author removed
-		* from the profile — can never be fetched again or shipped.
-		*/
-		function presetMissing(slots, images) {
-			return slots.filter((slot) => images[slot] === void 0);
-		}
-		//#endregion
-		//#region src/client/rotation.ts
-		/** Dwell-time presets the settings UI offers, in ms. */
-		const ROTATE_PRESETS = [
-			{
-				ms: 1e4,
-				key: "rotEvery10s"
-			},
-			{
-				ms: 3e4,
-				key: "rotEvery30s"
-			},
-			{
-				ms: 6e4,
-				key: "rotEvery1m"
-			},
-			{
-				ms: 3e5,
-				key: "rotEvery5m"
-			},
-			{
-				ms: 18e5,
-				key: "rotEvery30m"
-			}
-		];
-		/**
-		* The index to paint after the current one, or null when there is nowhere to go
-		* (fewer than two images — the caller must not start a timer at all then).
-		*
-		* `order` walks the list and wraps; `shuffle` picks uniformly among every index
-		* EXCEPT the current one, because landing on the same image reads as a missed
-		* tick. `current` outside the list is treated as 0 rather than trusted: it comes
-		* from the UI as often as from the timer, and a stale index must not be able to
-		* index past the end.
-		*
-		* `rand` is injectable so the shuffle branch is testable without stubbing a
-		* global.
-		*/
-		function nextIndex(len, order, current, rand = Math.random) {
-			if (!Number.isFinite(len) || len < 2) return null;
-			const count = Math.floor(len);
-			const cur = Number.isFinite(current) && current >= 0 && current < count ? Math.floor(current) : 0;
-			if (order === "shuffle") {
-				const roll = Math.min(Math.floor(Math.max(rand(), 0) * (count - 1)), count - 2);
-				return roll >= cur ? roll + 1 : roll;
-			}
-			return (cur + 1) % count;
-		}
-		/**
-		* Whether a rotation is worth running: two images, the switch on, and a positive
-		* dwell time. Kept here (rather than at the call site) so the UI's "rotating"
-		* badge and the timer agree by construction — a badge that says "rotating" while
-		* no timer exists is the one failure this feature can produce silently.
-		*/
-		function isRotating(len, enabled, intervalMs) {
-			return enabled && len >= 2 && Number.isFinite(intervalMs) && intervalMs > 0;
-		}
-		//#endregion
-		//#region src/client/repaint.ts
-		/**
-		* The repaint decision, as a pure function.
-		*
-		* Every edit to a rule ends with the same question: does the interface have to be
-		* repainted, or is refreshing the panel's readout enough? Repainting is the
-		* expensive half (the theme skin is re-registered, the wallpaper layer is
-		* rewritten, the host's theme is switched), so it must not be done for a rule
-		* that is not the one on screen — but it MUST be done the moment the edit
-		* changes what should be on screen.
-		*
-		* The naive test — "is the edited rule the active one?" — is wrong in exactly the
-		* case that kept being reported as "更新的不太及时，只有我动调色盘或者切模型的时候
-		* 才出现": an edit that CREATES the winner. Uploading a rule's first picture, or
-		* an auto-extracted color landing on a rule that had none, makes that rule
-		* paintable *through that very edit* (see `ruleCanPaint`), so the rule is not the
-		* active one at the moment of the check; the wallpaper and the skin then only
-		* showed up later, when an unrelated drag or model switch happened to re-run the
-		* resolution.
-		*
-		* Sampling the winner on BOTH sides of the edit is what makes such a change land
-		* at once, and `editedId === winnerAfter` additionally covers the edit that does
-		* not move the resolution but changes the look of the rule that IS painting (a
-		* color, a slider, a framing).
-		*
-		* `null` is "nothing of ours is painting" (the interface falls back to the host's
-		* own look), which is a winner like any other id.
-		*
-		* Kept free of imports on purpose: `scripts/repaint-check.ts` exercises it on
-		* plain node, the same way `rotation.ts` is exercised. A rule's `color`/`match`
-		* are the inputs that make the resolution move, which is why they are the fields
-		* whose write paths all end here.
-		*/
-		function shouldRepaint(editedId, winnerBefore, winnerAfter) {
-			return winnerAfter === editedId || winnerAfter !== winnerBefore;
-		}
-		//#endregion
-		//#region src/client/rpc.ts
-		const RPC_CHANNEL = "/dsh-background-by-model";
-		const RPC_NS = "dshBackgroundByModel";
-		const rpcEndpoint = (method) => `${RPC_NS}/${method}`;
-		let hostShape = "unknown";
-		let warnedLegacy = false;
-		/** Whether this bundle may write its config to the host it is talking to. */
-		function canWriteConfig() {
-			return hostShape !== "legacy";
-		}
-		/** Whether the running host process is older than this client bundle. */
-		function hostIsLegacy() {
-			return hostShape === "legacy";
-		}
-		function holdWrite() {
-			if (warnedLegacy) return;
-			warnedLegacy = true;
-			console.warn("dsh-background-by-model: the running host is an older build that cannot read the multi-image config shape — holding config writes so its sanitizer cannot drop this profile's rules. Restart DSH to load the new node half.");
-		}
-		let rpcCallFn = null;
-		function initRpc(call) {
-			rpcCallFn = call;
+		let rpcCallFn = null;
+		function initRpc(call) {
+			rpcCallFn = call;
 		}
 		async function rpcCall(method, payload) {
 			if (!rpcCallFn) return void 0;
@@ -1655,7 +1064,7 @@ window.__ModuleLoader__.load({
 			const d = data;
 			const slots = Array.isArray(d.slots) ? d.slots.filter((s) => typeof s === "string") : [];
 			const schema = typeof d.schema === "number" && isFinite(d.schema) ? d.schema : null;
-			hostShape = schema === null ? "legacy" : schema >= 9 ? "current" : "legacy";
+			hostShape = typeof schema === "number" && schema >= 9 ? "current" : "legacy";
 			if (hostShape === "legacy") holdWrite();
 			return {
 				config: d.config,
@@ -1759,61 +1168,6 @@ window.__ModuleLoader__.load({
 			return parts.length > 0 ? parts.join(" ") : null;
 		}
 		//#endregion
-		//#region src/client/palette-fade.ts
-		/**
-		* Whether a palette change may interpolate at all.
-		*
-		* Only while the SCHEME stays put. A light↔dark flip is not a tint of the same
-		* palette, it is a different palette: interpolating between them walks the whole
-		* interface through mid-tones whose ink is wrong in both directions (dark text
-		* half-way into a dark palette), which looks worse than the switch it replaces.
-		* The wallpaper has no such problem — one image fades into another either way —
-		* so its own animation is deliberately untouched by this.
-		*
-		* `previous === null` means nothing has been painted yet (the first apply after a
-		* load): there is no colour to come from, so there is nothing to fade.
-		*/
-		function paletteFadeAllowed(previous, next) {
-			return previous === next;
-		}
-		/** One `@property` block per registered token. */
-		function registrations(names, initial) {
-			return names.map((n) => `@property ${n}{syntax:'<color>';inherits:true;initial-value:${initial[n]}}`).join("");
-		}
-		/**
-		* The stylesheet for one state: the registrations always, the transition only
-		* while a palette change is actually being painted.
-		*
-		* `durationMs = 0` deliberately emits NO transition rule. That is not only
-		* "instant": it is what keeps a slider drag instant, because the same call sites
-		* rewrite the `body{…}` rule on every frame of a drag and a live transition on
-		* those tokens would make the alphas lag behind the pointer.
-		*/
-		function paletteFadeCss(input) {
-			const names = Object.keys(input.initial).filter((n) => n.startsWith("--"));
-			if (names.length === 0) return "";
-			const css = registrations(names, input.initial);
-			if (!(input.durationMs > 0)) return css;
-			const written = new Set(input.written);
-			const timing = (n) => `${n} ${input.durationMs}ms ${input.easing}`;
-			return `${css}${input.scopes.map((s) => ({
-				selector: s.selector,
-				transitions: [...s.tokens.filter((n) => names.includes(n) && written.has(n)), ...s.properties ?? []]
-			})).filter((s) => s.transitions.length > 0).map((s) => `${s.selector}{transition:${s.transitions.map(timing).join(",")}}`).join("")}`;
-		}
-		/**
-		* The same fade for an element the plugin paints INLINE (its columns and cards).
-		*
-		* No custom property is involved there — the element's own `background-color` is
-		* what changes — so the standard property is what has to be told. `0` means
-		* `none` rather than an empty value: an empty value would leave whatever the host
-		* had declared on that element, and the point of the 0 case is that a drag must
-		* not fade at all.
-		*/
-		function paletteFadeInline(durationMs, easing) {
-			return durationMs > 0 ? `background-color ${durationMs}ms ${easing}` : "none";
-		}
-		//#endregion
 		//#region src/client/utils/color.ts
 		function hsvToHsl(h, s, v) {
 			const l = v * (1 - s / 2);
@@ -2183,106 +1537,277 @@ window.__ModuleLoader__.load({
 				Math.round((b + m) * 255)
 			];
 		}
-		const UI_CSS = `
-/* The section is rendered INLINE inside the host settings dialog's content
- * column: the host provides the modal chrome (backdrop, centering, closing).
- * These classes style only the embedded shell; transient fixed layers (toast,
- * color picker, background editor) escape through Portals on <html>. */
-.dab-root{position:relative;color:var(--dsw-alias-label-primary);animation:dab-fade-in .35s ease both;container-type:inline-size;display:flex;flex-direction:column;align-items:center;width:100%;min-width:0;--dab-mono:ui-monospace,"Cascadia Mono","SF Mono",Consolas,"Courier New",monospace}
-.dab-root *,.dab-root *::before,.dab-root *::after{box-sizing:border-box}
-.dab-root button{font-family:inherit}
-/* ── scrollbars: the same bar as the settings panel we sit inside ────────────
- * The host styles scrollbars globally off its --dsh-scrollbar-* tokens, but those
- * declarations describe the app shell and its own scroll containers; a strip
- * nested this deep got the platform default instead — a thick light bar with
- * arrows, which is what the tab strip used to show beside the panel's own slim
- * vertical one.
- *
- * So the plugin declares the block for its OWN scroll containers. The values are
- * the host theme package's, for the layer-2 surface this panel is painted in:
- * 5px, rounded, layer-2 tint, transparent track. Two notes for whoever edits it:
- *
- *   - the tokens go ON THE SCROLLER (the selector that carries the overflow), not
- *     on .dab-root. A container that declares scrollbar-width:thin (as the nav
- *     rail does on narrow panels) paints its own standard bar regardless of the
- *     webkit block, and the host's standard-property fallback reads the thumb
- *     token from that same element.
- *   - every selector here is scoped to a dab- class: the stylesheet is injected
- *     into the host page once, so a bare webkit-scrollbar selector would restyle
- *     the whole harness. */
-.dab-tabs,.dab-pick-menu{--dsh-scrollbar-thumb:var(--dsw-alias-scrollbar-bg-l2);--dsh-scrollbar-thumb-hover:var(--dsw-alias-scrollbar-hover-l2);--dsh-scrollbar-width:5px}
-.dab-tabs::-webkit-scrollbar,.dab-pick-menu::-webkit-scrollbar{width:var(--dsh-scrollbar-width,5px);height:var(--dsh-scrollbar-width,5px)}
-.dab-tabs::-webkit-scrollbar-track,.dab-pick-menu::-webkit-scrollbar-track{background:transparent}
-.dab-tabs::-webkit-scrollbar-thumb,.dab-pick-menu::-webkit-scrollbar-thumb{background:var(--dsh-scrollbar-thumb);background-clip:content-box;border-radius:999px}
-.dab-tabs::-webkit-scrollbar-thumb:hover,.dab-pick-menu::-webkit-scrollbar-thumb:hover{background:var(--dsh-scrollbar-thumb-hover)}
-.dab-tabs::-webkit-scrollbar-corner,.dab-pick-menu::-webkit-scrollbar-corner{background:transparent}
-/* The host hides the platform's stepper arrows; without this the strip keeps the
-   little os arrows at both ends of the track while the panel's bar has none. */
-.dab-tabs::-webkit-scrollbar-button,.dab-pick-menu::-webkit-scrollbar-button{display:none}
-
-/* ── shell: nav rail + page body ─────────────────────────────────────────── */
-.dab-shell{display:grid;grid-template-columns:158px minmax(0,1fr);gap:26px;align-items:start;padding-bottom:8px;width:100%;max-width:980px;margin:0 auto}
-.dab-nav{position:sticky;top:0;display:flex;flex-direction:column;gap:18px}
-/* The brand is an <a> (it opens the repository): an anchor brings its own colour
-   and underline, so both are reset here rather than left to the host's link
-   styles, which would repaint the tile's label. */
-.dab-brand{display:flex;align-items:center;gap:10px;padding:2px 6px;color:inherit;text-decoration:none}
-.dab-brand:hover .dab-brand-name{color:var(--dsw-alias-brand-primary)}
-.dab-brand-tile{width:30px;height:30px;flex:none;border-radius:9px;display:grid;place-items:center;color:var(--dsw-alias-label-primary-inverted);background:var(--dsw-alias-brand-primary);box-shadow:0 4px 14px -4px var(--dsw-alias-brand-primary)}
-.dab-brand-name{font-size:13px;font-weight:650;letter-spacing:.01em;line-height:1.25}
-/* The weak token was written as quaternary-WITH-a-fallback, so this tag has
-   always painted tertiary: the dead name is dropped rather than being kept as
-   decoration nothing resolves to (check:ui rejects the name outright now). */
-.dab-brand-tag{font-size:9px;letter-spacing:.16em;font-weight:600;color:var(--dsw-alias-label-tertiary);text-transform:uppercase}
-.dab-nav-list{position:relative;display:flex;flex-direction:column;gap:4px}
-.dab-nav-ind{position:absolute;left:0;right:0;top:0;height:38px;border-radius:11px;background:var(--dsw-alias-bg-layer-2);border:1px solid var(--dsw-alias-border-l2);background:color-mix(in srgb,var(--dsw-alias-brand-primary) 13%,transparent);border-color:color-mix(in srgb,var(--dsw-alias-brand-primary) 25%,transparent);transition:transform .38s cubic-bezier(.22,1,.36,1)}
-.dab-nav-item{position:relative;z-index:1;display:flex;align-items:center;gap:10px;height:38px;padding:0 12px;border:0;background:none;border-radius:11px;color:var(--dsw-alias-label-tertiary);font-size:13px;cursor:pointer;text-align:left;transition:color .22s ease}
-.dab-nav-item:hover{color:var(--dsw-alias-label-primary)}
-.dab-nav-item.is-active{color:var(--dsw-alias-brand-primary);font-weight:600}
-.dab-nav-item svg{flex:none;transition:transform .3s cubic-bezier(.34,1.56,.64,1)}
-.dab-nav-item:hover svg{transform:scale(1.14) rotate(-5deg)}
-
-/* ── page chrome ─────────────────────────────────────────────────────────── */
-.dab-page{animation:dab-page-in .4s cubic-bezier(.22,1,.36,1) both;min-width:0;display:flex;flex-direction:column;gap:13px}
-.dab-head{margin:2px 0 5px}
-.dab-overline{font-size:10.5px;font-weight:700;letter-spacing:.18em;text-transform:uppercase;color:var(--dsw-alias-brand-primary);opacity:.9}
-.dab-h1{margin:4px 0 0;font-size:21px;font-weight:700;letter-spacing:-.01em}
-/* No max-width on the page description: it is a single line of context under the
-   title, and capping it at a prose measure left it wrapping early with dead space
-   to its right while the cards below ran the full width of the panel. */
-.dab-desc{margin:6px 0 0;font-size:12.5px;line-height:1.55;color:var(--dsw-alias-label-tertiary)}
-.dab-card{background:var(--dsw-alias-bg-layer-1);border:1px solid var(--dsw-alias-border-l2);border-radius:16px;padding:18px}
-.dab-card-hover{transition:transform .28s ease,box-shadow .28s ease,border-color .28s ease}
-.dab-card-hover:hover{transform:translateY(-2px);box-shadow:0 10px 28px -12px rgba(0,0,0,.28)}
-.dab-rise{animation:dab-rise-in .55s cubic-bezier(.22,1,.36,1) both;animation-delay:calc(var(--d,0) * 62ms)}
-
-/* ── accent hero (color orb) ─────────────────────────────────────────────── */
-.dab-hero-accent{display:flex;align-items:center;gap:24px;flex-wrap:wrap}
-.dab-orb-wrap{position:relative;width:118px;height:118px;flex:none}
-.dab-orb{position:absolute;inset:11px;border-radius:50%;background:radial-gradient(circle at 32% 28%,rgba(255,255,255,.5),rgba(255,255,255,0) 44%),var(--c,#888);box-shadow:0 16px 36px -10px var(--c-soft,transparent),inset 0 -10px 20px rgba(0,0,0,.16);animation:dab-orb-in .7s cubic-bezier(.22,1,.36,1) both}
-.dab-orb-ring{position:absolute;inset:0;border-radius:50%;background:conic-gradient(from 0deg,transparent 0 30%,var(--c,#888) 46%,transparent 62%,transparent 76%,var(--c,#888) 90%,transparent 100%);-webkit-mask:radial-gradient(farthest-side,transparent calc(100% - 3.5px),#000 calc(100% - 2.5px));mask:radial-gradient(farthest-side,transparent calc(100% - 3.5px),#000 calc(100% - 2.5px));animation:dab-spin 7s linear infinite;opacity:.9}
-.dab-hex{font-family:var(--dab-mono);font-size:24px;font-weight:600;letter-spacing:.02em;line-height:1.2;margin-top:2px}
-.dab-hsl-row{display:flex;gap:16px;margin-top:7px;font-family:var(--dab-mono);font-size:11px;color:var(--dsw-alias-label-tertiary)}
-.dab-hsl-row b{font-weight:600;color:var(--dsw-alias-label-secondary,var(--dsw-alias-label-tertiary))}
-
-/* ── swatches ────────────────────────────────────────────────────────────── */
-.dab-swatch-title{font-size:12px;font-weight:600;margin-bottom:10px;color:var(--dsw-alias-label-secondary,var(--dsw-alias-label-tertiary))}
-
-/* ── wheel card ──────────────────────────────────────────────────────────── */
-.dab-wheel-card{position:relative;display:flex;align-items:center;justify-content:center;gap:28px;flex-wrap:wrap;padding:24px 18px}
-.dab-wheel-glow{position:absolute;width:230px;height:230px;border-radius:50%;filter:blur(48px);opacity:.2;background:var(--c,#888);pointer-events:none;transition:background .4s ease}
-.dab-wheel{position:relative;cursor:crosshair;border-radius:50%;box-shadow:0 12px 32px -14px rgba(0,0,0,.4)}
-.dab-hint{font-size:11.5px;line-height:1.55;color:var(--dsw-alias-label-tertiary);padding:0 4px}
-/* The "your edits are being held" notice: it reports a state the user has to act
-   on, so it is tinted like a warning rather than left as grey hint text. */
-.dab-stale{color:var(--dsw-alias-state-error-primary);background:color-mix(in srgb,var(--dsw-alias-state-error-primary) 10%,transparent);border:1px solid color-mix(in srgb,var(--dsw-alias-state-error-primary) 35%,transparent);border-radius:9px;padding:8px 10px}
-
-/* ── precise color inputs ────────────────────────────────────────────────── */
-.dab-inputs{display:flex;flex-direction:column;gap:10px;min-width:172px}
-.dab-field{display:flex;align-items:center;gap:8px}
-.dab-field-label{width:14px;text-align:center;font-family:var(--dab-mono);font-size:11px;font-weight:600;color:var(--dsw-alias-label-tertiary)}
-.dab-num{flex:1;min-width:0;height:30px;padding:0 10px;border-radius:9px;border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-2);color:var(--dsw-alias-label-primary);font-family:var(--dab-mono);font-size:12px;outline:none;transition:border-color .2s,box-shadow .2s}
-.dab-num:focus{border-color:var(--dsw-alias-brand-primary);box-shadow:0 0 0 3px color-mix(in srgb,var(--dsw-alias-brand-primary) 18%,transparent)}
+		//#endregion
+		//#region src/client/auto-extract.ts
+		function createAutoExtract(host) {
+			/** The entry this extraction is about, re-resolved on every read. */
+			const target = (ruleId, slot) => {
+				const rule = ruleById(ruleId);
+				if (rule === null) return void 0;
+				return (slot === void 0 ? void 0 : rule.images.find((i) => i.slot === slot)) ?? rule.images[0];
+			};
+			const one = async (ruleId, slot) => {
+				if (!cfg.autoExtract) return;
+				const image = target(ruleId, slot);
+				if (image === void 0 || image.color !== null) return;
+				const url = host.paintable(image.slot);
+				if (url === null) return;
+				let hsl = null;
+				try {
+					hsl = await extractWallpaperColor(url, image.bgState);
+				} catch {
+					hsl = null;
+				}
+				if (hsl === null) return;
+				const current = target(ruleId, slot);
+				if (current === void 0 || current.color !== null) return;
+				const winner = host.winnerId();
+				current.color = hsl;
+				host.bumpRulesRev();
+				saveConfig();
+				host.repaint(ruleId, winner);
+			};
+			return {
+				one,
+				async each(ruleId, slots) {
+					for (const slot of slots) await one(ruleId, slot);
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/theme-skin.ts
+		/** Id of the plugin's own registered theme. */
+		const CUSTOM_ID = "custom-color";
+		/** How long a colour drag waits before the (host-visible) skin switch is made. */
+		const SKIN_DEBOUNCE_MS = 60;
+		function createSkin(ctx) {
+			let customDispose = null;
+			let skinTimer = null;
+			/** Colour scheme of the skin this plugin registered, or null when none is. */
+			let skinScheme = null;
+			/** Scheme the host currently holds for our theme id; null when it is not there. */
+			const registeredScheme = () => {
+				const theme = ctx.theme.getTheme().themes.find((t) => t.id === CUSTOM_ID);
+				return theme === void 0 ? null : theme.colorScheme;
+			};
+			const hasSkin = () => ctx.theme.getTheme().themes.some((t) => t.id === CUSTOM_ID);
+			const register = (h, s, l) => {
+				const { colorScheme, tokens } = genTokens(h, s, l);
+				if (skinScheme === colorScheme && registeredScheme() !== null) {
+					if (ctx.theme.getTheme().preference !== "custom-color") ctx.theme.setTheme(CUSTOM_ID);
+					return;
+				}
+				customDispose?.();
+				try {
+					customDispose = ctx.theme.register({
+						id: CUSTOM_ID,
+						colorScheme,
+						tokens
+					});
+				} catch {
+					customDispose = null;
+				}
+				skinScheme = registeredScheme() ?? colorScheme;
+				if (hasSkin()) ctx.theme.setTheme(CUSTOM_ID);
+			};
+			const drop = () => {
+				customDispose?.();
+				customDispose = null;
+				skinScheme = null;
+				try {
+					if (ctx.theme.getTheme().preference === "custom-color") ctx.theme.setTheme("system");
+				} catch {}
+			};
+			return {
+				commit(color) {
+					if (skinTimer !== null) window.clearTimeout(skinTimer);
+					if (color === null) {
+						skinTimer = null;
+						drop();
+						return;
+					}
+					skinTimer = window.setTimeout(() => {
+						skinTimer = null;
+						register(color[0], color[1], color[2]);
+					}, SKIN_DEBOUNCE_MS);
+				},
+				reassert(color) {
+					if (!hasSkin()) {
+						register(color[0], color[1], color[2]);
+						return true;
+					}
+					if (ctx.theme.getTheme().preference !== "custom-color") {
+						ctx.theme.setTheme(CUSTOM_ID);
+						return true;
+					}
+					return false;
+				},
+				drop,
+				dispose() {
+					if (skinTimer !== null) {
+						window.clearTimeout(skinTimer);
+						skinTimer = null;
+					}
+					customDispose?.();
+					customDispose = null;
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/palette-fade.ts
+		/**
+		* Whether a palette change may interpolate at all.
+		*
+		* Only while the SCHEME stays put. A light↔dark flip is not a tint of the same
+		* palette, it is a different palette: interpolating between them walks the whole
+		* interface through mid-tones whose ink is wrong in both directions (dark text
+		* half-way into a dark palette), which looks worse than the switch it replaces.
+		* The wallpaper has no such problem — one image fades into another either way —
+		* so its own animation is deliberately untouched by this.
+		*
+		* `previous === null` means nothing has been painted yet (the first apply after a
+		* load): there is no colour to come from, so there is nothing to fade.
+		*/
+		function paletteFadeAllowed(previous, next) {
+			return previous === next;
+		}
+		/** One `@property` block per registered token. */
+		function registrations(names, initial) {
+			return names.map((n) => `@property ${n}{syntax:'<color>';inherits:true;initial-value:${initial[n]}}`).join("");
+		}
+		/**
+		* The stylesheet for one state: the registrations always, the transition only
+		* while a palette change is actually being painted.
+		*
+		* `durationMs = 0` deliberately emits NO transition rule. That is not only
+		* "instant": it is what keeps a slider drag instant, because the same call sites
+		* rewrite the `body{…}` rule on every frame of a drag and a live transition on
+		* those tokens would make the alphas lag behind the pointer.
+		*/
+		function paletteFadeCss(input) {
+			const names = Object.keys(input.initial).filter((n) => n.startsWith("--"));
+			if (names.length === 0) return "";
+			const css = registrations(names, input.initial);
+			if (!(input.durationMs > 0)) return css;
+			const written = new Set(input.written);
+			const timing = (n) => `${n} ${input.durationMs}ms ${input.easing}`;
+			return `${css}${input.scopes.map((s) => ({
+				selector: s.selector,
+				transitions: [...s.tokens.filter((n) => names.includes(n) && written.has(n)), ...s.properties ?? []]
+			})).filter((s) => s.transitions.length > 0).map((s) => `${s.selector}{transition:${s.transitions.map(timing).join(",")}}`).join("")}`;
+		}
+		/**
+		* The same fade for an element the plugin paints INLINE (its columns and cards).
+		*
+		* No custom property is involved there — the element's own `background-color` is
+		* what changes — so the standard property is what has to be told. `0` means
+		* `none` rather than an empty value: an empty value would leave whatever the host
+		* had declared on that element, and the point of the 0 case is that a drag must
+		* not fade at all.
+		*/
+		function paletteFadeInline(durationMs, easing) {
+			return durationMs > 0 ? `background-color ${durationMs}ms ${easing}` : "none";
+		}
+		const UI_CSS = `
+/* The section is rendered INLINE inside the host settings dialog's content
+ * column: the host provides the modal chrome (backdrop, centering, closing).
+ * These classes style only the embedded shell; transient fixed layers (toast,
+ * color picker, background editor) escape through Portals on <html>. */
+.dab-root{position:relative;color:var(--dsw-alias-label-primary);animation:dab-fade-in .35s ease both;container-type:inline-size;display:flex;flex-direction:column;align-items:center;width:100%;min-width:0;--dab-mono:ui-monospace,"Cascadia Mono","SF Mono",Consolas,"Courier New",monospace}
+.dab-root *,.dab-root *::before,.dab-root *::after{box-sizing:border-box}
+.dab-root button{font-family:inherit}
+/* ── scrollbars: the same bar as the settings panel we sit inside ────────────
+ * The host styles scrollbars globally off its --dsh-scrollbar-* tokens, but those
+ * declarations describe the app shell and its own scroll containers; a strip
+ * nested this deep got the platform default instead — a thick light bar with
+ * arrows, which is what the tab strip used to show beside the panel's own slim
+ * vertical one.
+ *
+ * So the plugin declares the block for its OWN scroll containers. The values are
+ * the host theme package's, for the layer-2 surface this panel is painted in:
+ * 5px, rounded, layer-2 tint, transparent track. Two notes for whoever edits it:
+ *
+ *   - the tokens go ON THE SCROLLER (the selector that carries the overflow), not
+ *     on .dab-root. A container that declares scrollbar-width:thin (as the nav
+ *     rail does on narrow panels) paints its own standard bar regardless of the
+ *     webkit block, and the host's standard-property fallback reads the thumb
+ *     token from that same element.
+ *   - every selector here is scoped to a dab- class: the stylesheet is injected
+ *     into the host page once, so a bare webkit-scrollbar selector would restyle
+ *     the whole harness. */
+.dab-tabs,.dab-pick-menu{--dsh-scrollbar-thumb:var(--dsw-alias-scrollbar-bg-l2);--dsh-scrollbar-thumb-hover:var(--dsw-alias-scrollbar-hover-l2);--dsh-scrollbar-width:5px}
+.dab-tabs::-webkit-scrollbar,.dab-pick-menu::-webkit-scrollbar{width:var(--dsh-scrollbar-width,5px);height:var(--dsh-scrollbar-width,5px)}
+.dab-tabs::-webkit-scrollbar-track,.dab-pick-menu::-webkit-scrollbar-track{background:transparent}
+.dab-tabs::-webkit-scrollbar-thumb,.dab-pick-menu::-webkit-scrollbar-thumb{background:var(--dsh-scrollbar-thumb);background-clip:content-box;border-radius:999px}
+.dab-tabs::-webkit-scrollbar-thumb:hover,.dab-pick-menu::-webkit-scrollbar-thumb:hover{background:var(--dsh-scrollbar-thumb-hover)}
+.dab-tabs::-webkit-scrollbar-corner,.dab-pick-menu::-webkit-scrollbar-corner{background:transparent}
+/* The host hides the platform's stepper arrows; without this the strip keeps the
+   little os arrows at both ends of the track while the panel's bar has none. */
+.dab-tabs::-webkit-scrollbar-button,.dab-pick-menu::-webkit-scrollbar-button{display:none}
+
+/* ── shell: nav rail + page body ─────────────────────────────────────────── */
+.dab-shell{display:grid;grid-template-columns:158px minmax(0,1fr);gap:26px;align-items:start;padding-bottom:8px;width:100%;max-width:980px;margin:0 auto}
+.dab-nav{position:sticky;top:0;display:flex;flex-direction:column;gap:18px}
+/* The brand is an <a> (it opens the repository): an anchor brings its own colour
+   and underline, so both are reset here rather than left to the host's link
+   styles, which would repaint the tile's label. */
+.dab-brand{display:flex;align-items:center;gap:10px;padding:2px 6px;color:inherit;text-decoration:none}
+.dab-brand:hover .dab-brand-name{color:var(--dsw-alias-brand-primary)}
+.dab-brand-tile{width:30px;height:30px;flex:none;border-radius:9px;display:grid;place-items:center;color:var(--dsw-alias-label-primary-inverted);background:var(--dsw-alias-brand-primary);box-shadow:0 4px 14px -4px var(--dsw-alias-brand-primary)}
+.dab-brand-name{font-size:13px;font-weight:650;letter-spacing:.01em;line-height:1.25}
+/* The weak token was written as quaternary-WITH-a-fallback, so this tag has
+   always painted tertiary: the dead name is dropped rather than being kept as
+   decoration nothing resolves to (check:ui rejects the name outright now). */
+.dab-brand-tag{font-size:9px;letter-spacing:.16em;font-weight:600;color:var(--dsw-alias-label-tertiary);text-transform:uppercase}
+.dab-nav-list{position:relative;display:flex;flex-direction:column;gap:4px}
+.dab-nav-ind{position:absolute;left:0;right:0;top:0;height:38px;border-radius:11px;background:var(--dsw-alias-bg-layer-2);border:1px solid var(--dsw-alias-border-l2);background:color-mix(in srgb,var(--dsw-alias-brand-primary) 13%,transparent);border-color:color-mix(in srgb,var(--dsw-alias-brand-primary) 25%,transparent);transition:transform .38s cubic-bezier(.22,1,.36,1)}
+.dab-nav-item{position:relative;z-index:1;display:flex;align-items:center;gap:10px;height:38px;padding:0 12px;border:0;background:none;border-radius:11px;color:var(--dsw-alias-label-tertiary);font-size:13px;cursor:pointer;text-align:left;transition:color .22s ease}
+.dab-nav-item:hover{color:var(--dsw-alias-label-primary)}
+.dab-nav-item.is-active{color:var(--dsw-alias-brand-primary);font-weight:600}
+.dab-nav-item svg{flex:none;transition:transform .3s cubic-bezier(.34,1.56,.64,1)}
+.dab-nav-item:hover svg{transform:scale(1.14) rotate(-5deg)}
+
+/* ── page chrome ─────────────────────────────────────────────────────────── */
+.dab-page{animation:dab-page-in .4s cubic-bezier(.22,1,.36,1) both;min-width:0;display:flex;flex-direction:column;gap:13px}
+.dab-head{margin:2px 0 5px}
+.dab-overline{font-size:10.5px;font-weight:700;letter-spacing:.18em;text-transform:uppercase;color:var(--dsw-alias-brand-primary);opacity:.9}
+.dab-h1{margin:4px 0 0;font-size:21px;font-weight:700;letter-spacing:-.01em}
+/* No max-width on the page description: it is a single line of context under the
+   title, and capping it at a prose measure left it wrapping early with dead space
+   to its right while the cards below ran the full width of the panel. */
+.dab-desc{margin:6px 0 0;font-size:12.5px;line-height:1.55;color:var(--dsw-alias-label-tertiary)}
+.dab-card{background:var(--dsw-alias-bg-layer-1);border:1px solid var(--dsw-alias-border-l2);border-radius:16px;padding:18px}
+.dab-card-hover{transition:transform .28s ease,box-shadow .28s ease,border-color .28s ease}
+.dab-card-hover:hover{transform:translateY(-2px);box-shadow:0 10px 28px -12px rgba(0,0,0,.28)}
+.dab-rise{animation:dab-rise-in .55s cubic-bezier(.22,1,.36,1) both;animation-delay:calc(var(--d,0) * 62ms)}
+
+/* ── accent hero (color orb) ─────────────────────────────────────────────── */
+.dab-hero-accent{display:flex;align-items:center;gap:24px;flex-wrap:wrap}
+.dab-orb-wrap{position:relative;width:118px;height:118px;flex:none}
+.dab-orb{position:absolute;inset:11px;border-radius:50%;background:radial-gradient(circle at 32% 28%,rgba(255,255,255,.5),rgba(255,255,255,0) 44%),var(--c,#888);box-shadow:0 16px 36px -10px var(--c-soft,transparent),inset 0 -10px 20px rgba(0,0,0,.16);animation:dab-orb-in .7s cubic-bezier(.22,1,.36,1) both}
+.dab-orb-ring{position:absolute;inset:0;border-radius:50%;background:conic-gradient(from 0deg,transparent 0 30%,var(--c,#888) 46%,transparent 62%,transparent 76%,var(--c,#888) 90%,transparent 100%);-webkit-mask:radial-gradient(farthest-side,transparent calc(100% - 3.5px),#000 calc(100% - 2.5px));mask:radial-gradient(farthest-side,transparent calc(100% - 3.5px),#000 calc(100% - 2.5px));animation:dab-spin 7s linear infinite;opacity:.9}
+.dab-hex{font-family:var(--dab-mono);font-size:24px;font-weight:600;letter-spacing:.02em;line-height:1.2;margin-top:2px}
+.dab-hsl-row{display:flex;gap:16px;margin-top:7px;font-family:var(--dab-mono);font-size:11px;color:var(--dsw-alias-label-tertiary)}
+.dab-hsl-row b{font-weight:600;color:var(--dsw-alias-label-secondary,var(--dsw-alias-label-tertiary))}
+
+/* ── swatches ────────────────────────────────────────────────────────────── */
+.dab-swatch-title{font-size:12px;font-weight:600;margin-bottom:10px;color:var(--dsw-alias-label-secondary,var(--dsw-alias-label-tertiary))}
+
+/* ── wheel card ──────────────────────────────────────────────────────────── */
+.dab-wheel-card{position:relative;display:flex;align-items:center;justify-content:center;gap:28px;flex-wrap:wrap;padding:24px 18px}
+.dab-wheel-glow{position:absolute;width:230px;height:230px;border-radius:50%;filter:blur(48px);opacity:.2;background:var(--c,#888);pointer-events:none;transition:background .4s ease}
+.dab-wheel{position:relative;cursor:crosshair;border-radius:50%;box-shadow:0 12px 32px -14px rgba(0,0,0,.4)}
+.dab-hint{font-size:11.5px;line-height:1.55;color:var(--dsw-alias-label-tertiary);padding:0 4px}
+/* The "your edits are being held" notice: it reports a state the user has to act
+   on, so it is tinted like a warning rather than left as grey hint text. */
+.dab-stale{color:var(--dsw-alias-state-error-primary);background:color-mix(in srgb,var(--dsw-alias-state-error-primary) 10%,transparent);border:1px solid color-mix(in srgb,var(--dsw-alias-state-error-primary) 35%,transparent);border-radius:9px;padding:8px 10px}
+
+/* ── precise color inputs ────────────────────────────────────────────────── */
+.dab-inputs{display:flex;flex-direction:column;gap:10px;min-width:172px}
+.dab-field{display:flex;align-items:center;gap:8px}
+.dab-field-label{width:14px;text-align:center;font-family:var(--dab-mono);font-size:11px;font-weight:600;color:var(--dsw-alias-label-tertiary)}
+.dab-num{flex:1;min-width:0;height:30px;padding:0 10px;border-radius:9px;border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-2);color:var(--dsw-alias-label-primary);font-family:var(--dab-mono);font-size:12px;outline:none;transition:border-color .2s,box-shadow .2s}
+.dab-num:focus{border-color:var(--dsw-alias-brand-primary);box-shadow:0 0 0 3px color-mix(in srgb,var(--dsw-alias-brand-primary) 18%,transparent)}
 .dab-num::-webkit-outer-spin-button,.dab-num::-webkit-inner-spin-button{-webkit-appearance:none;margin:0}
 .dab-num{-moz-appearance:textfield;appearance:textfield}
 .dab-urlinput{flex:1;min-width:180px;height:34px;padding:0 12px;border-radius:10px;border:1px solid var(--dsw-alias-border-l2);background:var(--dsw-alias-bg-layer-2);color:var(--dsw-alias-label-primary);font-size:12.5px;outline:none;transition:border-color .2s}
@@ -2708,6 +2233,7 @@ window.__ModuleLoader__.load({
 			appliedTokenNames = [];
 			baseTokenKey = "";
 			lastBgKey = "";
+			document.documentElement.removeAttribute(THEMED_ATTR);
 		}
 		/** Drop every surface the plugin owns: the variables the scoped
 		*  dialog/trajectory rules read, and the inline backgrounds written onto the
@@ -2873,6 +2399,18 @@ window.__ModuleLoader__.load({
 			}
 		}
 		/**
+		* A scheme verdict for the third caller: "whoever is in force". Reads the host
+		* preference the browser half published, falling back to the host's own boot
+		* flag and then the OS query — the same two rungs `resolveHostDark` uses.
+		*/
+		function hostSchemeIsDark() {
+			return resolveHostDark();
+		}
+		/** Whether this plugin is the one holding the scheme flag right now. */
+		function ownsSchemeFlag() {
+			return document.body.getAttribute(DARK_ATTR) === OWN_SCHEME;
+		}
+		/**
 		* Keep `data-ds-dark-theme` in the HOST's own form (a boolean attribute) while
 		* the plugin does not own a palette.
 		*
@@ -2882,15 +2420,23 @@ window.__ModuleLoader__.load({
 		* its light palette on a dark system, the readback then hands those light
 		* surfaces back to the plugin, and the interface stays light until some
 		* unrelated event happens to re-run an apply. Restoring the flag from the
-		* resolved scheme closes that hole, and the write is skipped when it already
-		* matches so this never churns the theme observer.
+		* resolved scheme closes that hole.
+		*
+		* It must not PUSH a host scheme either, though, and that is the other half of
+		* the same hole: the verdict it works from is the plugin's own last reading,
+		* which is already stale by the time the host has dropped the flag without
+		* telling anyone. Writing the stale verdict turns a host that just went dark
+		* back to light and sticks it there — the flag now "matches", so every later
+		* pass skips it. So only the OWNER of the flag is corrected: the plugin's own
+		* value is replaced, and a flag nobody has claimed is left to the host.
+		*
+		* The write is skipped when it already matches, so this never churns the theme
+		* observer.
 		*/
 		function adoptHostScheme() {
-			const dark = resolveHostDark();
-			const current = document.body.getAttribute(DARK_ATTR);
-			if (dark) {
-				if (current !== "") document.body.setAttribute(DARK_ATTR, "");
-			} else if (current !== null) document.body.removeAttribute(DARK_ATTR);
+			if (!ownsSchemeFlag()) return;
+			if (resolveHostDark()) document.body.setAttribute(DARK_ATTR, "");
+			else document.body.removeAttribute(DARK_ATTR);
 		}
 		/** Re-read the host palette and repaint from it when it moved. Called while a
 		*  color-less rule is active (the host can re-project its palette at any time,
@@ -3235,11 +2781,10 @@ window.__ModuleLoader__.load({
 		/**
 		* Whether one of the element's class names ENDS with `suffix`.
 		*
-		* A SUFFIX test, deliberately not `classList.contains`: the harness emits these
-		* classes from a CSS module, so a column carries `pI_x6G_centerCol` and matching
-		* the whole string `centerCol` is false for every column of every build. The
-		* failure mode is the quiet one — the class never matches, the part falls through
-		* to a weaker guess and a setting disappears without an error.
+		* A SUFFIX test, not `classList.contains`: the host emits these classes from a CSS
+		* module, so a column carries `pI_x6G_centerCol` and an exact match is false for
+		* every column of every build — quietly, with the part falling through to a weaker
+		* guess.
 		*/
 		function hasClassSuffix(el, suffix) {
 			for (const name of Array.from(el.classList)) if (name === suffix || name.endsWith(suffix)) return true;
@@ -3291,13 +2836,11 @@ window.__ModuleLoader__.load({
 			}
 		}
 		/**
-		* Re-derive every plugin-owned interface surface that is not a palette token:
-		* the conversation view card and the function pages in the main slot.
+		* Re-derive every plugin-owned interface surface that is not a palette token: the
+		* conversation view card and the function pages in the main slot.
 		*
-		* ONE pass, run by the full apply and by the frame observer: a page mounts and
-		* unmounts with a NAVIGATION, not with a slider, so its discovery has to happen
-		* on the same beat as everything else. `fade` carries the palette-moved case
-		* through to the inline-painted view card (see `applyCustomTokens`).
+		* ONE pass, run by the full apply and the frame observer — a page mounts and
+		* unmounts with a NAVIGATION, so its discovery happens on the same beat.
 		*/
 		function applyInterfaceParts(fade = false) {
 			applyViewCards(fade);
@@ -3306,10 +2849,9 @@ window.__ModuleLoader__.load({
 		const PAGE_ANCHOR_SEL = "[data-slot=\"main\"]";
 		const PAGE_MARK = "data-dab-page";
 		/**
-		* `!important`, because the page's own background is a class rule of the host's
-		* and equal-specificity cascade order is not something to rely on. The fallback
-		* is the host's own surface token, so a mark that ever outlives its discovery
-		* paints what that page would have painted anyway.
+		* `!important`, because the page's own background is a host class rule and cascade
+		* order at equal specificity is not something to rely on. The fallback is the
+		* host's own token, so a stale mark paints what the page would have painted.
 		*/
 		const PAGE_STYLE_RULE = `[${PAGE_MARK}]{background:var(--dsh-any-bg-page,var(--dsw-alias-bg-base))!important}`;
 		/** The elements currently marked — unmarked again at zero or on teardown. */
@@ -3346,14 +2888,7 @@ window.__ModuleLoader__.load({
 		function pageIsShowing() {
 			return discoverPageEls().length > 0;
 		}
-		/**
-		* Point the 插件页面 item at whatever the main slot is showing.
-		*
-		* Called from `applyInterfaceParts`, the one pass the full apply and the frame
-		* observer both run, and from the item's own drag: a page mounts and unmounts
-		* with a NAVIGATION, not with a slider, so the discovery has to happen on the
-		* same beat as everything else.
-		*/
+		/** Point the 插件页面 item at whatever the main slot is showing. */
 		function applyPageSurfaces() {
 			discoverParts();
 			const base = palette()?.tokens["--dsw-alias-bg-base"];
@@ -3917,32 +3452,182 @@ window.__ModuleLoader__.load({
 			stopWatchingParts();
 		}
 		//#endregion
-		//#region src/client/modelbg.ts
-		/** Rules that can actually paint: see `ruleCanPaint` (./schema). */
-		function usable(rules) {
-			return rules.filter(ruleCanPaint);
-		}
+		//#region src/client/cadence.ts
 		/**
-		* Resolve the rule for one model text.
-		*
-		* Top→bottom, first case-insensitive substring hit wins; an empty `match` never
-		* hits on its own. When nothing hits, the FIRST usable rule is the fallback
-		* (rule 1 deliberately doubles as both a matcher and the fallback).
+		* The scheduler entry points the plugin registers, and the cadences they run at.
 		*
-		* "Usable" is `ruleCanPaint` — an image, or a theme color of its own — so a rule
-		* whose pictures were all removed still holds the models it matches (and paints
-		* its color alone) instead of quietly handing them to the next rule.
+		* Every interval the plugin owns is declared HERE rather than at its call site, so
+		* "what does this plugin poll, and how often" has one answer. The scheduler itself
+		* lives in ./watchdogs; the questions live in their own modules (boot restore and
+		* the theme watchdog in ./appearance, the holiday rollover in ./holiday-status).
 		*/
-		function matchRule(rules, modelText) {
-			const list = usable(rules);
-			if (list.length === 0) return {
-				rule: null,
-				matched: false
-			};
-			const hay = modelText.toLowerCase();
-			if (hay.trim() !== "") for (const rule of list) {
-				const needle = rule.match.trim().toLowerCase();
-				if (needle === "") continue;
+		/** The theme skin / host palette re-assert, once a second while a colour is live. */
+		const THEME_WATCH_MS = 1e3;
+		/**
+		* The delayed boot restores. Two of them because the theme service and the host
+		* settings scope settle asynchronously after `apply` — a single late pass misses a
+		* host adoption that happens after it, and an early one misses the one before it.
+		*/
+		const RESTORE_DELAYS_MS = [300, 1500];
+		/** The holiday rollover: the answer only moves at Beijing midnight, a whole day wide. */
+		const HOLIDAY_WATCH_MS = 3e4;
+		//#endregion
+		//#region src/client/appearance.ts
+		function createAppearance(host) {
+			const skin = createSkin(host.ctx);
+			/** The host scheme last published, so a move can be told from a repeat. */
+			let lastScheme = null;
+			/**
+			* Publish the scheme the host's own preference resolves to. The theme service is
+			* the only place that knows it (a custom active theme included); the wallpaper
+			* layer needs it to hand `data-ds-dark-theme` back in the host's own form while a
+			* colour-less rule follows that theme, instead of leaving the flag off — which
+			* pins the host to its LIGHT palette on a dark system.
+			*/
+			const syncHostScheme = () => {
+				try {
+					setHostScheme(host.ctx.theme.getTheme().active.colorScheme === "dark");
+				} catch {
+					setHostScheme(null);
+				}
+			};
+			const reassert = () => {
+				const color = activeColor();
+				return color === null ? false : skin.reassert(color);
+			};
+			/**
+			* Re-read the scheme the HOST preference resolves to, repainting when it moved.
+			*
+			* The host can flip it without telling anyone: the OS while the preference is
+			* `system`, a host-side settings adoption, and — the one that hides — a
+			* re-projection the host performs on its own, which our flag write can swallow.
+			* So the value is compared, not assumed: a moved scheme re-publishes it and
+			* repaints; an unchanged one only does the cheap readback while a
+			* colour-less rule paints from the host palette.
+			*
+			* @returns whether the host scheme moved (the caller repaints).
+			*/
+			const syncScheme = () => {
+				let dark;
+				try {
+					dark = host.ctx.theme.getTheme().active.colorScheme === "dark";
+				} catch {
+					dark = hostSchemeIsDark();
+				}
+				const moved = dark !== null && dark !== lastScheme;
+				if (dark !== null) {
+					lastScheme = dark;
+					setHostScheme(dark);
+				}
+				if (!moved && activeColor() === null) refreshSystemTheme();
+				return moved;
+			};
+			const restore = () => {
+				syncHostScheme();
+				if (reassert()) host.refresh();
+				applyWp();
+			};
+			return {
+				syncHostScheme,
+				reassert,
+				restore,
+				applyPalette() {
+					skin.commit(activeColor());
+					syncHostScheme();
+				},
+				watch() {
+					if (syncScheme()) {
+						host.refresh();
+						return;
+					}
+					if (reassert()) host.refresh();
+				},
+				/**
+				* Two delayed restores, because the theme service and the host settings scope
+				* settle asynchronously after `apply`: a single late pass misses an adoption
+				* that happens after it, and an early one misses the one before it.
+				*/
+				armRestores() {
+					const timers = RESTORE_DELAYS_MS.map((ms) => window.setTimeout(restore, ms));
+					return () => {
+						for (const id of timers) window.clearTimeout(id);
+					};
+				},
+				dispose() {
+					skin.dispose();
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/appearance-checks.ts
+		/**
+		* The theme watchdog. The theme service keeps only built-in preferences in
+		* memory, so any host-scope adoption can silently drop the custom theme —
+		* reverting the label colours and the inner surfaces to the system palette.
+		*
+		* A colour-less rule needs the same slow check for the opposite reason: it paints
+		* from the HOST palette, which the host can re-project (or which the scheme flag
+		* can fall behind) with no event of ours to hang a repaint on.
+		*/
+		function themeWatchdog(host) {
+			return {
+				name: "theme",
+				everyMs: THEME_WATCH_MS,
+				run() {
+					if (host.activeColor() === null) {
+						host.refreshHostPalette();
+						return;
+					}
+					host.restore();
+				}
+			};
+		}
+		/**
+		* The holiday rollover: a slow tick that does nothing at all until the day key
+		* actually moves. 30 s is plenty for a boundary that is a whole day wide.
+		*/
+		function holidayRollover(host) {
+			let day = host.activeHolidayId() ?? "";
+			return {
+				name: "holiday",
+				everyMs: HOLIDAY_WATCH_MS,
+				run() {
+					const next = host.activeHolidayId() ?? "";
+					if (next === day) return;
+					day = next;
+					const slot = host.todayHolidaySlot();
+					if (slot === null) host.applyActive();
+					else host.loadAndRepaint(slot);
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/modelbg.ts
+		/** Rules that can actually paint: see `ruleCanPaint` (./schema). */
+		function usable(rules) {
+			return rules.filter(ruleCanPaint);
+		}
+		/**
+		* Resolve the rule for one model text.
+		*
+		* Top→bottom, first case-insensitive substring hit wins; an empty `match` never
+		* hits on its own. When nothing hits, the FIRST usable rule is the fallback
+		* (rule 1 deliberately doubles as both a matcher and the fallback).
+		*
+		* "Usable" is `ruleCanPaint` — an image, or a theme color of its own — so a rule
+		* whose pictures were all removed still holds the models it matches (and paints
+		* its color alone) instead of quietly handing them to the next rule.
+		*/
+		function matchRule(rules, modelText) {
+			const list = usable(rules);
+			if (list.length === 0) return {
+				rule: null,
+				matched: false
+			};
+			const hay = modelText.toLowerCase();
+			if (hay.trim() !== "") for (const rule of list) {
+				const needle = rule.match.trim().toLowerCase();
+				if (needle === "") continue;
 				if (hay.includes(needle)) return {
 					rule,
 					matched: true
@@ -4183,6 +3868,265 @@ window.__ModuleLoader__.load({
 			};
 		}
 		//#endregion
+		//#region src/client/boot.ts
+		/**
+		* Boot: which image slots are read before the first frame, and in what order.
+		*
+		* Deliberately its own module, because the ORDER is the whole feature. A setup
+		* with five rules and four pictures each holds twenty full-size data URLs, and
+		* pulling all of them before painting would mean the interface opens blank for
+		* as long as they take. So exactly three things are read eagerly:
+		*
+		*   1. the slot that paints FIRST — today's holiday art, else the current model's
+		*      first image (see `prioritySlot`);
+		*   2. the first image of every other rule, because a rule card draws its first
+		*      image as its thumbnail;
+		*   3. today's holiday art, when it is not already (1).
+		*
+		* Everything past that is read ON DEMAND: by the rotation, which warms the image
+		* it is about to need as soon as its schedule is armed, and by the settings page
+		* when a card is expanded. The slot list the node half reports is not hydrated at
+		* all — an orphaned slot nothing points at has no card to appear on.
+		*/
+		/** One slot, read once: the cache is authoritative for "already here". */
+		async function loadSlot(slot) {
+			if (imageOf(slot) !== null) return;
+			const url = await readImage(slot);
+			if (url !== null) setImage(slot, url);
+		}
+		/**
+		* The slot that paints before anything else: the holiday in force when there is
+		* one, otherwise the FIRST image of the current model's rule. A holiday outranks
+		* the rule here for the same reason it outranks it when painting.
+		*
+		* Always the first image (never the one `advanceOnSwitch` would step to): boot
+		* paints without an advance, and hydrating an image the first frame is not going
+		* to use would leave the frame blank until the real one arrived.
+		*/
+		function prioritySlot(spec) {
+			if (spec.holidaySlot !== null) return spec.holidaySlot;
+			return matchRule(cfg.rules, spec.modelText).rule?.images[0]?.slot ?? null;
+		}
+		/** Every slot boot hydrates, the painted one first. */
+		function bootSlots(spec) {
+			const firsts = cfg.rules.map((r) => r.images[0]?.slot).filter((slot) => slot !== void 0);
+			const first = prioritySlot(spec);
+			return Array.from(/* @__PURE__ */ new Set([
+				...first === null ? [] : [first],
+				...firsts,
+				...spec.holidaySlot === null ? [] : [spec.holidaySlot]
+			]));
+		}
+		/**
+		* Read the boot set, calling `painted` once the first slot is in.
+		*
+		* Sequential on purpose: the painted one is requested first and the rest stream
+		* in after it, so a large multi-rule setup never delays the first frame. The
+		* callback fires on EVERY slot's turn, not once — the caller's repaint is cheap
+		* when the URL has not moved.
+		*/
+		async function hydrateBoot(spec, painted) {
+			const first = prioritySlot(spec);
+			for (const slot of bootSlots(spec)) {
+				await loadSlot(slot);
+				if (slot === first) painted();
+			}
+		}
+		//#endregion
+		//#region src/client/model-state.ts
+		/** A key that no real model text can equal, so the first report always lands. */
+		const EMPTY = "\0";
+		function createModelTracker() {
+			let state = {
+				text: "",
+				label: "",
+				source: "default",
+				note: "waiting"
+			};
+			let key = EMPTY;
+			const take = (next) => {
+				const nextKey = `${next.text}\u0001${next.source}\u0001${next.note}`;
+				const changed = nextKey !== key;
+				const textChanged = next.text !== state.text;
+				key = nextKey;
+				state = next;
+				return {
+					textChanged,
+					changed
+				};
+			};
+			return {
+				get state() {
+					return state;
+				},
+				update(text, label, source, note) {
+					return take({
+						text,
+						label: label !== "" ? label : text,
+						source,
+						note
+					});
+				},
+				adopt(text, source, note) {
+					return take({
+						text,
+						label: text,
+						source,
+						note
+					}).changed;
+				},
+				facts(rule, matched) {
+					return {
+						text: state.text,
+						source: state.source,
+						note: state.note,
+						rule,
+						matched
+					};
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/rotation.ts
+		/** Dwell-time presets the settings UI offers, in ms. */
+		const ROTATE_PRESETS = [
+			{
+				ms: 1e4,
+				key: "rotEvery10s"
+			},
+			{
+				ms: 3e4,
+				key: "rotEvery30s"
+			},
+			{
+				ms: 6e4,
+				key: "rotEvery1m"
+			},
+			{
+				ms: 3e5,
+				key: "rotEvery5m"
+			},
+			{
+				ms: 18e5,
+				key: "rotEvery30m"
+			}
+		];
+		/**
+		* The index to paint after the current one, or null when there is nowhere to go
+		* (fewer than two images — the caller must not start a timer at all then).
+		*
+		* `order` walks the list and wraps; `shuffle` picks uniformly among every index
+		* EXCEPT the current one, because landing on the same image reads as a missed
+		* tick. `current` outside the list is treated as 0 rather than trusted: it comes
+		* from the UI as often as from the timer, and a stale index must not be able to
+		* index past the end.
+		*
+		* `rand` is injectable so the shuffle branch is testable without stubbing a
+		* global.
+		*/
+		function nextIndex(len, order, current, rand = Math.random) {
+			if (!Number.isFinite(len) || len < 2) return null;
+			const count = Math.floor(len);
+			const cur = Number.isFinite(current) && current >= 0 && current < count ? Math.floor(current) : 0;
+			if (order === "shuffle") {
+				const roll = Math.min(Math.floor(Math.max(rand(), 0) * (count - 1)), count - 2);
+				return roll >= cur ? roll + 1 : roll;
+			}
+			return (cur + 1) % count;
+		}
+		/**
+		* Whether a rotation is worth running: two images, the switch on, and a positive
+		* dwell time. Kept here (rather than at the call site) so the UI's "rotating"
+		* badge and the timer agree by construction — a badge that says "rotating" while
+		* no timer exists is the one failure this feature can produce silently.
+		*/
+		function isRotating(len, enabled, intervalMs) {
+			return enabled && len >= 2 && Number.isFinite(intervalMs) && intervalMs > 0;
+		}
+		//#endregion
+		//#region src/client/rotation-timer.ts
+		/**
+		* The image rotation timer: ONE interval, always aimed at the ACTIVE rule.
+		*
+		* A timer per rule would burn wakeups on rules that are not painting anything,
+		* and since only one rule's images can be on screen at a time, one timer is all
+		* that is needed. It is kept out of `apply()` because a rotation is the one piece
+		* of this plugin that must keep working while nothing else changes — and the
+		* questions it has to answer (did the schedule's inputs move? is the tab
+		* hidden? which image is next?) read better gathered in one place.
+		*
+		* The schedule is armed by SIGNATURE rather than by "already armed": a slider drag
+		* on the active rule re-runs the whole apply dozens of times per second, and
+		* restarting the interval on each of those would mean the dwell timer never
+		* elapses while the user is dragging (a 10 s rotation would never advance). The
+		* signature carries exactly the inputs the schedule depends on, so a real change —
+		* another rule, another interval, the tab becoming visible again — re-arms while a
+		* repaint does not.
+		*/
+		function createRotation(host) {
+			let timer = null;
+			/** Identity of the schedule currently armed; a change means "re-arm". */
+			let signature = "";
+			const tick = () => {
+				const rule = activeRule();
+				if (rule === null) return;
+				const next = nextIndex(rule.images.length, rule.rotate.order, imageIndexOf(rule));
+				if (next === null) {
+					schedule(true);
+					return;
+				}
+				setRotIndex(next);
+				host.paintImage(rule, next);
+				const after = nextIndex(rule.images.length, rule.rotate.order, next);
+				if (after !== null) host.warmImage(rule, after);
+			};
+			const schedule = (force = false) => {
+				const rule = activeRule();
+				const sig = rule === null ? "" : [
+					rule.id,
+					rule.rotate.enabled,
+					rule.rotate.intervalMs,
+					rule.rotate.order,
+					rule.images.length,
+					document.hidden
+				].join("|");
+				if (!force && sig === signature) return;
+				signature = sig;
+				if (timer !== null) {
+					window.clearInterval(timer);
+					timer = null;
+				}
+				if (rule === null || document.hidden) return;
+				if (!isRotating(rule.images.length, rule.rotate.enabled, rule.rotate.intervalMs)) return;
+				const next = nextIndex(rule.images.length, rule.rotate.order, imageIndexOf(rule));
+				if (next !== null) host.warmImage(rule, next);
+				timer = window.setInterval(tick, rule.rotate.intervalMs);
+			};
+			return {
+				schedule,
+				step() {
+					const rule = activeRule();
+					if (rule === null) return false;
+					const next = nextIndex(rule.images.length, rule.rotate.order, imageIndexOf(rule));
+					if (next === null) return false;
+					setRotIndex(next);
+					host.paintImage(rule, next);
+					schedule(true);
+					return true;
+				},
+				onVisibility() {
+					schedule();
+					host.sync();
+				},
+				dispose() {
+					if (timer !== null) {
+						window.clearInterval(timer);
+						timer = null;
+					}
+				}
+			};
+		}
+		//#endregion
 		//#region src/client/components/icons.tsx
 		/** Sun glyph, migrated from @deepseek-ai/dsh-client-ui-primitives IconLightOutline16. */
 		const SUN_PATHS = "<path d=\"M11.3496 8C11.3496 6.14985 9.85015 4.65039 8 4.65039C6.14985 4.65039 4.65039 6.14985 4.65039 8C4.65039 9.85015 6.14985 11.3496 8 11.3496C9.85015 11.3496 11.3496 9.85015 11.3496 8ZM12.6504 8C12.6504 10.5681 10.5681 12.6504 8 12.6504C5.43188 12.6504 3.34961 10.5681 3.34961 8C3.34961 5.43188 5.43188 3.34961 8 3.34961C10.5681 3.34961 12.6504 5.43188 12.6504 8Z\" fill=\"currentColor\"/><path d=\"M8.65039 0.5V2.5H7.34961V0.5H8.65039Z\" fill=\"currentColor\"/><path d=\"M8.65039 13.5V15.5H7.34961V13.5H8.65039Z\" fill=\"currentColor\"/><path d=\"M3.15808 2.24035L4.57229 3.65456L3.6525 4.57435L2.23829 3.16014L3.15808 2.24035Z\" fill=\"currentColor\"/><path d=\"M12.3505 11.4327L13.7647 12.8469L12.8449 13.7667L11.4307 12.3525L12.3505 11.4327Z\" fill=\"currentColor\"/><path d=\"M2.24537 12.8469L3.65958 11.4327L4.57937 12.3525L3.16516 13.7667L2.24537 12.8469Z\" fill=\"currentColor\"/><path d=\"M11.4377 3.65455L12.852 2.24033L13.7718 3.16012L12.3575 4.57434L11.4377 3.65455Z\" fill=\"currentColor\"/><path d=\"M0.5 7.35461H2.5V8.6554H0.5L0.5 7.35461Z\" fill=\"currentColor\"/><path d=\"M13.5 7.35461H15.5V8.6554H13.5V8.6554Z\" fill=\"currentColor\"/>";
@@ -4442,6 +4386,667 @@ window.__ModuleLoader__.load({
 			children: /* @__PURE__ */ (0, react_jsx_runtime.jsx)("path", { d: "M4.3 6.4 8 10.1l3.7-3.7" })
 		});
 		//#endregion
+		//#region src/client/nav-icon.ts
+		/**
+		* The settings-nav glyph.
+		*
+		* The harness derives every section's nav icon from its id and exposes no hook for
+		* a plugin to supply one, so the mounted nav cell has to be found in the DOM and
+		* its `<svg>` swapped for this plugin's sun. That is a patch on the host's markup,
+		* and the two failure modes are both silent: patching too early finds no cell, and
+		* patching on every mutation burns a scan of the whole document per keystroke in
+		* the composer. Hence the narrow trigger below — only a settings DIALOG arriving
+		* in the tree starts a scan.
+		*/
+		/** The host's settings dialog, the only place this section's nav exists. */
+		const DIALOG_SEL = "[role=\"dialog\"][aria-modal=\"true\"][aria-labelledby]";
+		const MARK = "dabNavIcon";
+		/**
+		* Replace the nav glyph of the section whose label is `navLabel()`.
+		*
+		* Reads the label on every scan rather than capturing it: the section is rebuilt
+		* when the language changes, and a stale label would simply stop matching.
+		*/
+		function applyNavIcon(navLabel) {
+			const nav = document.querySelector(DIALOG_SEL)?.querySelector("nav");
+			if (!nav) return;
+			for (const cell of Array.from(nav.querySelectorAll("button"))) {
+				const label = cell.querySelector("span");
+				if (label === null || label.textContent?.trim() !== navLabel) continue;
+				const svg = cell.querySelector("svg");
+				if (svg !== null && svg.dataset[MARK] === "1") return;
+				const sun = document.createElementNS("http://www.w3.org/2000/svg", "svg");
+				sun.setAttribute("width", "16");
+				sun.setAttribute("height", "16");
+				sun.setAttribute("viewBox", "0 0 16 16");
+				sun.setAttribute("fill", "none");
+				sun.setAttribute("xmlns", "http://www.w3.org/2000/svg");
+				sun.dataset[MARK] = "1";
+				sun.innerHTML = SUN_PATHS;
+				svg?.replaceWith(sun);
+				if (svg === null) cell.prepend(sun);
+				return;
+			}
+		}
+		/** Watch for the settings dialog (re)appearing; returns the disposer. */
+		function watchNavIcon(navLabel) {
+			if (typeof MutationObserver === "undefined") return () => void 0;
+			const observer = new MutationObserver((records) => {
+				if (records.some((r) => {
+					for (const n of r.addedNodes) {
+						if (n.nodeType !== 1) continue;
+						const el = n;
+						if (el.matches?.(DIALOG_SEL) || el.querySelector?.(DIALOG_SEL)) return true;
+					}
+					return false;
+				})) applyNavIcon(navLabel());
+			});
+			observer.observe(document.body, {
+				childList: true,
+				subtree: true
+			});
+			applyNavIcon(navLabel());
+			return () => observer.disconnect();
+		}
+		//#endregion
+		//#region src/client/theme-file.ts
+		/** Slot names reach the filesystem, so an incoming file's are whitelisted. */
+		const SLOT_RE = /^[A-Za-z0-9_-]{1,32}$/;
+		/** The JSON document `exportTheme` writes; `images` carries every rule slot. */
+		function buildThemeFile() {
+			const images = {};
+			for (const slot of cfg.rules.flatMap(ruleSlots)) {
+				const url = imageOf(slot);
+				if (url !== null) images[slot] = url;
+			}
+			return {
+				version: 9,
+				exportedAt: (/* @__PURE__ */ new Date()).toISOString(),
+				config: cfg,
+				images
+			};
+		}
+		/**
+		* Write the current rules and wallpapers out as one JSON file.
+		*
+		* The object URL is attached to a hidden anchor and released on the NEXT task:
+		* a click is not a synchronous download, and releasing in the same tick cancels
+		* it in some browsers — while Firefox only honours the click on an anchor that is
+		* in the document.
+		*/
+		function saveThemeFile(file) {
+			const blob = new Blob([JSON.stringify(file, null, 2)], { type: "application/json" });
+			const url = URL.createObjectURL(blob);
+			const a = document.createElement("a");
+			a.href = url;
+			a.download = "dsh-background-by-model-theme.json";
+			a.style.display = "none";
+			document.body.append(a);
+			a.click();
+			window.setTimeout(() => {
+				a.remove();
+				URL.revokeObjectURL(url);
+			}, 0);
+		}
+		/**
+		* Write a whole theme file into the store: its rules, its wallpapers, nothing
+		* else.
+		*
+		* `wipeFirst` is the entire difference between the two imports, and it belongs to
+		* the recommended profile alone: `nextSlot` hands slots out as `m1`, `m2`, … — a
+		* counter, not a random token — so a downloaded profile and the store it lands in
+		* collide on those names as a matter of course. Emptying first is what makes
+		* "replace everything with this" literally true.
+		*/
+		async function applyThemeFile(host, data, wipeFirst) {
+			if (typeof data.version === "number" && data.version > 9) return false;
+			if (typeof data.config !== "object" || data.config === null) return false;
+			if (wipeFirst) {
+				await resetStore();
+				resetConfig();
+			}
+			adoptConfig(data.config);
+			const incoming = data.images ?? {};
+			const keep = /* @__PURE__ */ new Set();
+			for (const slot of cfg.rules.flatMap(ruleSlots)) {
+				keep.add(slot);
+				const raw = incoming[slot];
+				if (typeof raw === "string" && /^data:image\//.test(raw)) {
+					setImage(slot, raw);
+					writeImage(slot, raw);
+				} else {
+					setImage(slot, null);
+					deleteImage(slot);
+				}
+			}
+			for (const slot of Object.keys(incoming)) if (!keep.has(slot) && SLOT_RE.test(slot)) deleteImage(slot);
+			persistConfig();
+			host.applyActive();
+			return true;
+		}
+		//#endregion
+		//#region src/client/watchdogs.ts
+		/** The shortest cadence allowed — also the scheduler's own tick. */
+		const MIN_TICK_MS = 1e3;
+		/**
+		* Start one scheduler. It does NOT run anything on registration: the caller
+		* decides when the first pass happens (the plugin's boot sequence needs the
+		* order — wallpaper, model, palette), and registers with the intent that the
+		* first tick is the first run.
+		*
+		* The clock is `performance.now()` rather than `Date.now()`: a wall-clock jump
+		* (NTP, a laptop waking from sleep) would otherwise fire every entry at once or
+		* park them all for hours, and "how long ago did we last ask" is a duration, not
+		* a date.
+		*/
+		function createSchedule() {
+			const entries = /* @__PURE__ */ new Map();
+			let timer = null;
+			let disposed = false;
+			const now = () => typeof performance !== "undefined" ? performance.now() : Date.now();
+			const fire = (w, stamp) => {
+				stamp.last = now();
+				try {
+					w.run();
+				} catch (e) {
+					console.warn(`dsh-background-by-model: the "${w.name}" check threw`, e);
+				}
+			};
+			const tick = () => {
+				if (disposed || document.hidden) return;
+				const at = now();
+				for (const [w, stamp] of entries) if (at - stamp.last >= w.everyMs) fire(w, stamp);
+			};
+			/**
+			* One beat for the whole page, and it is the SHORTEST cadence any entry asks
+			* for, so each one fires within one beat of its own due time. With nothing
+			* registered there is no timer at all.
+			*/
+			const resync = () => {
+				if (timer !== null) {
+					window.clearInterval(timer);
+					timer = null;
+				}
+				if (disposed || entries.size === 0) return;
+				let beat = Infinity;
+				for (const w of entries.keys()) beat = Math.min(beat, w.everyMs);
+				timer = window.setInterval(tick, Math.max(MIN_TICK_MS, beat));
+			};
+			const onVisibility = () => {
+				if (!document.hidden) tick();
+			};
+			document.addEventListener("visibilitychange", onVisibility);
+			resync();
+			return {
+				add(watchdog) {
+					if (disposed) return () => void 0;
+					entries.set(watchdog, { last: now() });
+					resync();
+					return () => {
+						entries.delete(watchdog);
+						resync();
+					};
+				},
+				runAll() {
+					if (disposed) return;
+					for (const [w, stamp] of entries) fire(w, stamp);
+				},
+				dispose() {
+					if (disposed) return;
+					disposed = true;
+					entries.clear();
+					if (timer !== null) {
+						window.clearInterval(timer);
+						timer = null;
+					}
+					document.removeEventListener("visibilitychange", onVisibility);
+				}
+			};
+		}
+		//#endregion
+		//#region src/client/i18n.ts
+		const NS = "settings.anyBg";
+		const zh = {
+			nav: "模型背景",
+			brandTag: "按模型换背景",
+			pageInterface: "界面",
+			pageModelBg: "模型背景",
+			pageProfile: "配置",
+			descInterface: "为主界面的各个区域单独调节透明度，营造空间层次感。这里的设置对所有模型生效",
+			descModelBg: "每条规则 = 一个匹配串 + 一组背景图与外观。切换模型时，从上往下找第一条匹配串出现在模型名里的规则；都没中就使用第 1 条。一条规则可以放多张图，按你设的节奏轮换",
+			descProfile: "调整壁纸切换效果，并把当前全部规则连同图片导出备份，或从文件一键恢复",
+			uiTitle: "主界面",
+			uiOpacity: "透明度",
+			uiOpacityBg: "主背景",
+			uiOpacitySide: "左侧栏",
+			uiOpacityCard: "卡片与菜单面板",
+			uiOpacityCode: "代码块",
+			uiOpacityInput: "输入框与控件",
+			uiSop: "设置界面透明度",
+			uiChatRegion: "对话文本框",
+			uiTrajectory: "轨迹页",
+			uiPage: "插件页面",
+			uiPreview: "右侧栏",
+			statusUnknownHint: "检测不到时一律使用第 1 条可用规则；切换一次模型或稍等片刻会自动重试",
+			statusSourceDefaultHint: "只读到宿主默认模型，它不是本会话当前选择的模型；本会话的模型选择可用后会自动纠正",
+			statusNoteNoService: "仍未拿到会话服务（会话控制器晚于本插件加载），正在自动重试",
+			statusNoteNoSession: "会话服务已就绪，但还没有当前会话 id",
+			statusNoteNoProjection: "拿不到本会话的模型选择投影（binding / projections 不可用）",
+			statusNoteEmptySelection: "本会话的模型选择投影还没有值（切一次模型即可写入）",
+			hostStaleHint: "检测到 DSH 主进程仍在运行旧版插件：新版配置格式它还读不懂，为避免丢规则，本次只改界面不写入配置。重启 DSH 后多图与轮换即可正常保存",
+			tryoutTitle: "匹配试跑",
+			tryoutPlaceholder: "输入模型名，如 deepseek-flash",
+			tryoutUseCurrent: "填入当前模型",
+			tryoutHit: "命中规则",
+			tryoutFallback: "无匹配 · 走兜底规则",
+			tryoutNone: "没有可用规则（规则需要启用，并且有图片或主题色）",
+			tryoutEmpty: "输入模型名即可试跑",
+			autoExtract: "选图后自动取主题色",
+			ruleAdd: "新增规则",
+			ruleNoneHint: "还没有规则，点上面的「新增规则」新建一条",
+			ruleFallbackBadge: "兜底",
+			ruleMatchPlaceholder: "如 flash / glm（忽略大小写，留空则不参与匹配）",
+			ruleEnabled: "启用",
+			ruleUp: "上移",
+			ruleDown: "下移",
+			ruleRemove: "删除规则",
+			tabListLabel: "规则",
+			tabPick: "选择规则",
+			tabMore: "更多规则",
+			tabUnnamed: "未命名规则",
+			tabLive: "正在使用",
+			tabRotating: "轮换中",
+			tabOff: "已停用",
+			ruleRemoveConfirm: "再点一次删除",
+			ruleNoImage: "尚未选择图片",
+			ruleFromUrl: "从网址",
+			ruleUrlPlaceholder: "粘贴图片网址 https://…",
+			ruleUrlApply: "应用",
+			ruleUrlCancel: "取消",
+			ruleUrlApplying: "加载中…",
+			ruleUrlBadHttp: "仅支持 http/https 图片网址",
+			ruleUrlFail: "获取图片失败",
+			ruleImageRemove: "移除",
+			ruleEmptyHint: "这条规则还没有图片，也没有自己的主题色：没有可显示的内容，匹配和兜底都会跳过它",
+			ruleColorOnlyHint: "这条规则还没有图片：不会铺壁纸，界面只用这个主题色",
+			ruleImagePendingHint: "这张图片还没有取到内容，稍后会自己出现（也可以直接替换它）",
+			ruleColor: "主题色",
+			ruleColorNone: "跟随系统主题",
+			ruleColorNoneHint: "未设颜色时跟随系统主题：界面用宿主的配色，壁纸与各部位的透明度照旧生效",
+			ruleColorPick: "自定义颜色",
+			ruleColorPickHint: "优先从本图取色，取不到就用默认色",
+			ruleColorNoImageHint: "这条规则还没有图片，取不到色：选一个颜色可以只铺主题色，或先添加图片",
+			ruleColorPendingImageHint: "这张图片还没有取到内容，暂时取不了色：可以直接选一个颜色，或等它加载完",
+			ruleColorExtract: "从本图提取",
+			ruleColorTargetImage: "作用于选中的图片：",
+			ruleColorTargetRule: "作用于本规则（它还没有图片）",
+			ruleLayout: "布局模式",
+			ruleLayoutNoImage: "添加图片后可分别设置每张图的布局模式",
+			ruleFramingEdit: "编辑位置",
+			ruleOpacity: "背景透明度",
+			ruleBrightness: "背景亮度",
+			ruleBlur: "背景模糊",
+			ruleBlurHint: "这三条滑块都作用于壁纸层；界面页里的透明度作用于界面各区域，两者互不影响",
+			rotTitle: "多图轮换",
+			rotEnable: "轮换这组图",
+			rotNeedTwo: "至少两张图才能轮换",
+			rotEvery: "每张停留",
+			rotCustom: "自定义秒数",
+			rotSeconds: "秒",
+			rotOrder: "换图顺序",
+			rotOrderSeq: "按顺序",
+			rotOrderShuffle: "随机",
+			rotOnSwitch: "切换模型时也换一张",
+			rotNext: "下一张",
+			rotNextInactive: "只有正在生效的规则能换画面上的图",
+			rotPos: "第",
+			rotShowing: "正在显示",
+			rotAddImage: "添加",
+			rotReplaceImage: "替换",
+			rotDragHint: "拖动排序",
+			rotDblHint: "双击切换",
+			rotEvery10s: "10 秒",
+			rotEvery30s: "30 秒",
+			rotEvery1m: "1 分钟",
+			rotEvery5m: "5 分钟",
+			rotEvery30m: "30 分钟",
+			bgModeFit: "适应",
+			bgModeFill: "填充",
+			bgModeStretch: "拉伸",
+			bgModeTile: "平铺",
+			bgModeCenter: "居中",
+			editorTitle: "背景编辑器",
+			editorHint: "拖动移动画面，滚轮缩放大小",
+			editorCommit: "确认",
+			editorCancel: "取消",
+			editorReset: "重置",
+			extracting: "取色中…",
+			extractDone: "已应用图片配色",
+			extractFail: "未在这张图里找到鲜明的颜色，请换一张",
+			eyedropper: "从图片取色",
+			pickerTitle: "从图片取色",
+			pickerHint: "移动鼠标预览颜色，点击图片选取为主题色",
+			pickerClose: "关闭",
+			crashTitle: "界面渲染出错",
+			crashDesc: "设置面板遇到问题，点击下方按钮重置后重试",
+			crashReset: "重置面板",
+			exportTheme: "导出配置",
+			importTheme: "导入配置",
+			exportCardTitle: "导出配置",
+			exportCardDesc: "把全部规则、每条规则的颜色/布局/透明度/模糊与图片打包为 dsh-background-by-model-theme.json",
+			importCardTitle: "导入配置",
+			importCardDesc: "从之前导出的 JSON 文件一键恢复全部规则（会覆盖当前规则与图片）",
+			toastExportDone: "配置文件已开始下载",
+			importDone: "已导入配置",
+			importFail: "导入失败，文件格式不正确",
+			recCardTitle: "推荐配置",
+			recCardDesc: "从项目素材库下载作者维护的一整套配置（规则、壁纸与接口设置），一键替换当前的全部内容",
+			recAdopt: "采用推荐配置",
+			recBusy: "正在下载",
+			recConfirmTitle: "替换当前的全部配置？",
+			recConfirmBody: "会先删除你现在的全部规则与壁纸，再写入这份推荐配置。删除的文件无法恢复。",
+			recStatRules: "条规则",
+			recStatImages: "张壁纸",
+			recConfirmOk: "删除并替换",
+			recConfirmCancel: "取消",
+			recDone: "已采用推荐配置",
+			recFailNetwork: "推荐配置下载失败，请检查网络后重试",
+			recFailNotProfile: "素材库返回的内容不是配置，请稍后重试",
+			recFailNewer: "这份推荐配置需要更新的插件版本，未做任何改动",
+			recFailTooMany: "这份推荐配置列出的图片数量超出限制，未做任何改动",
+			recFailTooLarge: "这份推荐配置体积过大，未做任何改动",
+			recFailImage: "这张壁纸没拿到（素材库里缺这个文件）：",
+			recFailApply: "未能写入推荐配置，你原来的配置没有被改动",
+			footerTag: "按模型换背景插件",
+			repoLink: "在 GitHub 上打开仓库",
+			holidayTitle: "节日特殊背景",
+			holidayEnable: "启用节日特殊背景（中秋当天、国庆 10 月 1–7 日）",
+			trTitle: "切换效果",
+			trEffect: "切换方式",
+			trEffectFade: "淡入淡出",
+			trEffectNone: "直接切换",
+			trEffectZoom: "缩放淡入",
+			trEffectSlide: "平移推入",
+			trEasing: "缓动",
+			trEasingEase: "标准",
+			trEasingLinear: "匀速",
+			trEasingOut: "先快后慢",
+			trEasingInOut: "两端慢",
+			trDuration: "切换时长",
+			trPreview: "试放",
+			trHint: "效果对所有换图生效：切模型、轮换、手动下一张、节日。「直接切换」和 0 秒一样是硬切",
+			trReducedHint: "系统开启了「减少动态效果」，实际切换不会播放动画"
+		};
+		const en = {
+			nav: "Model background",
+			brandTag: "Per-model wallpaper",
+			pageInterface: "Interface",
+			pageModelBg: "Model background",
+			pageProfile: "Profile",
+			descInterface: "Tune opacity per surface to build depth. These settings are global and apply to every model",
+			descModelBg: "Each rule is a match string plus a set of wallpapers and one look. On a model switch the list is scanned top-down for the first match string contained in the model name; if nothing hits, rule 1 is used. A rule can hold several images and rotate through them on a rhythm you set",
+			descProfile: "Tune how the wallpaper switches, and back up every rule together with its image — or restore one from a file",
+			uiTitle: "Interface",
+			uiOpacity: "Opacity",
+			uiOpacityBg: "Main background",
+			uiOpacitySide: "Left panel",
+			uiOpacityCard: "Cards & menus",
+			uiOpacityCode: "Code blocks",
+			uiOpacityInput: "Input & controls",
+			uiSop: "Settings interface opacity",
+			uiChatRegion: "Conversation text frame",
+			uiTrajectory: "Trajectory view",
+			uiPage: "Plugin pages",
+			uiPreview: "Right panel",
+			statusUnknownHint: "Without a detected model rule 1 is always used; switching the model once or waiting a moment retries automatically",
+			statusSourceDefaultHint: "Only the host-wide default model could be read — that is not necessarily this session's selection. It self-corrects once this session's model selection is available.",
+			statusNoteNoService: "The sessions service is not available yet (the session controller loads after this plugin); retrying automatically",
+			statusNoteNoSession: "The sessions service is up but reports no current session yet",
+			statusNoteNoProjection: "This session's model-selection projection is unreachable (no binding / projections)",
+			statusNoteEmptySelection: "The model-selection projection exists but carries no value yet (selecting a model once writes it)",
+			hostStaleHint: "The DSH host process is still running the older plugin, which cannot read the new config shape. To avoid dropping rules, this session changes the interface but holds every config write — restart DSH and multi-image plus rotation will save normally",
+			tryoutTitle: "Match test",
+			tryoutPlaceholder: "Type a model name, e.g. deepseek-flash",
+			tryoutUseCurrent: "Use current model",
+			tryoutHit: "matches rule",
+			tryoutFallback: "no match · fallback rule",
+			tryoutNone: "No usable rule (a rule needs to be enabled and carry an image or a theme color)",
+			tryoutEmpty: "Type a model name to test the list",
+			autoExtract: "Extract the theme color when an image is chosen",
+			ruleAdd: "Add rule",
+			ruleNoneHint: "No rules yet — use “Add rule” in the tab strip above",
+			ruleFallbackBadge: "fallback",
+			ruleMatchPlaceholder: "e.g. flash / glm (case-insensitive, empty never matches)",
+			ruleEnabled: "Enabled",
+			ruleUp: "Move up",
+			ruleDown: "Move down",
+			ruleRemove: "Remove rule",
+			tabListLabel: "Rules",
+			tabPick: "Pick a rule",
+			tabMore: "More rules",
+			tabUnnamed: "Unnamed rule",
+			tabLive: "In use",
+			tabRotating: "Rotating",
+			tabOff: "Disabled",
+			ruleRemoveConfirm: "Click again to delete",
+			ruleNoImage: "No image yet",
+			ruleFromUrl: "From URL",
+			ruleUrlPlaceholder: "Paste an image URL https://…",
+			ruleUrlApply: "Apply",
+			ruleUrlCancel: "Cancel",
+			ruleUrlApplying: "Loading…",
+			ruleUrlBadHttp: "Only http/https image URLs are supported",
+			ruleUrlFail: "Could not fetch the image",
+			ruleImageRemove: "Remove",
+			ruleEmptyHint: "This rule has no image and no theme color of its own: it has nothing to show, so matching and the fallback both skip it",
+			ruleColorOnlyHint: "No image in this rule yet: no wallpaper is shown, and the interface is painted from this theme color alone",
+			ruleImagePendingHint: "This image has no content yet — it appears once it loads; you can also replace it",
+			ruleColor: "Theme color",
+			ruleColorNone: "Follow system theme",
+			ruleColorNoneHint: "Without a color this rule follows the system theme: the host palette paints the interface while the wallpaper and every opacity slider keep working",
+			ruleColorPick: "Custom color",
+			ruleColorPickHint: "Extracts from this image when it can, otherwise uses a default color",
+			ruleColorNoImageHint: "This rule has no image to take a color from: pick a color to tint the interface alone, or add an image first",
+			ruleColorPendingImageHint: "This image has no content yet, so there is nothing to extract from: pick a color directly, or wait for it to load",
+			ruleColorTargetImage: "Applies to the selected image:",
+			ruleColorTargetRule: "Applies to this rule (it has no image yet)",
+			ruleColorExtract: "Extract from image",
+			ruleLayout: "Layout mode",
+			ruleLayoutNoImage: "Add an image to give each one its own layout mode",
+			ruleFramingEdit: "Edit position",
+			ruleOpacity: "Background opacity",
+			ruleBrightness: "Background brightness",
+			ruleBlur: "Background blur",
+			ruleBlurHint: "These three sliders all treat the wallpaper layer; the opacity on the Interface page affects interface surfaces — they are independent",
+			rotTitle: "Image rotation",
+			rotEnable: "Rotate these images",
+			rotNeedTwo: "At least two images are needed to rotate",
+			rotEvery: "Dwell time per image",
+			rotCustom: "Custom seconds",
+			rotSeconds: "s",
+			rotOrder: "Order",
+			rotOrderSeq: "In order",
+			rotOrderShuffle: "Shuffle",
+			rotOnSwitch: "Also step on a model switch",
+			rotNext: "Next image",
+			rotNextInactive: "Only the active rule can step the background",
+			rotPos: "Image",
+			rotShowing: "On screen",
+			rotAddImage: "Add",
+			rotReplaceImage: "Replace",
+			rotDragHint: "drag to reorder",
+			rotDblHint: "double-click to show",
+			rotEvery10s: "10 s",
+			rotEvery30s: "30 s",
+			rotEvery1m: "1 min",
+			rotEvery5m: "5 min",
+			rotEvery30m: "30 min",
+			bgModeFit: "Fit",
+			bgModeFill: "Fill",
+			bgModeStretch: "Stretch",
+			bgModeTile: "Tile",
+			bgModeCenter: "Center",
+			editorTitle: "Background editor",
+			editorHint: "Drag to move, scroll to zoom",
+			editorCommit: "Confirm",
+			editorCancel: "Cancel",
+			editorReset: "Reset",
+			extracting: "Extracting…",
+			extractDone: "Image colors applied",
+			extractFail: "No vivid color found in this image, try another",
+			eyedropper: "Eyedropper",
+			pickerTitle: "Pick from image",
+			pickerHint: "Hover to preview, click to pick as the theme color",
+			pickerClose: "Close",
+			crashTitle: "Section crashed",
+			crashDesc: "The panel hit an error. Reset below to recover.",
+			crashReset: "Reset panel",
+			exportTheme: "Export",
+			importTheme: "Import",
+			exportCardTitle: "Export profile",
+			exportCardDesc: "Bundle every rule — color, layout, opacity, blur — and its image into dsh-background-by-model-theme.json",
+			importCardTitle: "Import profile",
+			importCardDesc: "Restore every rule and image from a previously exported JSON file (replaces the current set)",
+			toastExportDone: "Export started",
+			importDone: "Profile imported",
+			importFail: "Import failed — invalid file",
+			recCardTitle: "Recommended profile",
+			recCardDesc: "Download the author's own full setup — rules, wallpapers and interface settings — and replace everything with it",
+			recAdopt: "Use recommended profile",
+			recBusy: "Downloading",
+			recConfirmTitle: "Replace your entire profile?",
+			recConfirmBody: "Every rule and wallpaper you have is deleted first, then this profile is written in its place. Deleted files cannot be recovered.",
+			recStatRules: "rules",
+			recStatImages: "wallpapers",
+			recConfirmOk: "Delete and replace",
+			recConfirmCancel: "Cancel",
+			recDone: "Recommended profile applied",
+			recFailNetwork: "Could not download the recommended profile — check your connection and retry",
+			recFailNotProfile: "The asset host answered with something that is not a profile — try again later",
+			recFailNewer: "This profile needs a newer plugin version. Nothing was changed.",
+			recFailTooMany: "The recommended profile names more images than the plugin will fetch. Nothing was changed.",
+			recFailTooLarge: "The recommended profile is too large. Nothing was changed.",
+			recFailImage: "Could not fetch this wallpaper — the asset host has no such file:",
+			recFailApply: "Could not write the recommended profile — your own is untouched",
+			footerTag: "Per-model wallpaper plugin",
+			repoLink: "Open the repository on GitHub",
+			holidayTitle: "Holiday backgrounds",
+			holidayEnable: "Enable holiday backgrounds (Mid-Autumn day, Oct 1–7)",
+			trTitle: "Switch effect",
+			trEffect: "Transition",
+			trEffectFade: "Cross-fade",
+			trEffectNone: "Instant",
+			trEffectZoom: "Zoom in",
+			trEffectSlide: "Slide in",
+			trEasing: "Easing",
+			trEasingEase: "Standard",
+			trEasingLinear: "Linear",
+			trEasingOut: "Ease out",
+			trEasingInOut: "Ease in-out",
+			trDuration: "Duration",
+			trPreview: "Preview",
+			trHint: "The effect applies to every change: model switch, rotation, manual next, holidays. “Instant” and 0 s are the same hard cut",
+			trReducedHint: "Your system asks for reduced motion, so a real switch will not animate"
+		};
+		//#endregion
+		//#region src/preset.ts
+		/**
+		* JSON with object keys in a fixed (sorted) order — the same string for the same
+		* value, whatever order the object that carried it happened to build its keys in.
+		*
+		* `JSON.stringify` alone is not an identity for a value that came off the wire and
+		* through a sanitizer: key order is an accident of how the object was assembled,
+		* and a resume that missed on it would silently re-download everything (the safe
+		* direction) while a resume that MATCHED on a value it should not have would be
+		* the unsafe one — so this is deliberately total as well: anything JSON cannot
+		* carry (a function, a `Symbol`, `undefined`) serializes as `null` and an
+		* `undefined` property is skipped, exactly as `JSON.stringify` treats it.
+		*/
+		function canonical(value) {
+			if (Array.isArray(value)) return `[${value.map(canonical).join(",")}]`;
+			if (value !== null && typeof value === "object") return `{${Object.entries(value).filter(([, v]) => v !== void 0).sort(([a], [b]) => a < b ? -1 : a > b ? 1 : 0).map(([k, v]) => `${JSON.stringify(k)}:${canonical(v)}`).join(",")}}`;
+			return JSON.stringify(value) ?? "null";
+		}
+		/**
+		* The identity of one revision of the profile: the manifest's shape version plus
+		* the config, in canonical form.
+		*
+		* The profile is served at ONE version of the assets repository, but a version
+		* reference is only as fixed as the tag behind it: re-point the tag and every
+		* edge that has not been purged keeps answering with the previous bytes of the
+		* same URL. So "the profile" is still not guaranteed to be one fixed thing, and
+		* the bytes a previous attempt is holding are only known to belong to what is
+		* being installed when that config comes back the same. Order-insensitivity is
+		* what lets this be a comparison of VALUES rather than of spellings —
+		* `normalizeConfig` (./schema) rebuilds the config it reads, so pinning the key
+		* to the exact key order the wire happened to use would make the hold useless
+		* the moment anything upstream normalized differently.
+		*/
+		function presetKey(version, config) {
+			return `${version}\n${canonical(config)}`;
+		}
+		/**
+		* The bytes of a failed attempt that may be reused for the revision `key` names.
+		*
+		* A fresh object every time, never the held record itself: the caller fills it in
+		* as the rest of the profile arrives, and handing out the same mutable record
+		* would let a re-fetch of one file edit the state the NEXT attempt resumes from.
+		* An empty answer — nothing held, or held for a different revision — is the honest
+		* one either way: the pool then asks for every slot the config names.
+		*/
+		function presetResume(held, key) {
+			if (held === null || held.key !== key) return {};
+			return { ...held.images };
+		}
+		/**
+		* The slots of `slots` that `images` does not hold yet, in the config's own order.
+		*
+		* Order matters in the only way it can here: it decides which file a worker takes
+		* first, and the files are not the same size. Only names the CONFIG asked for are
+		* ever returned, so a held picture nothing points at — a slot the author removed
+		* from the profile — can never be fetched again or shipped.
+		*/
+		function presetMissing(slots, images) {
+			return slots.filter((slot) => images[slot] === void 0);
+		}
+		//#endregion
+		//#region src/client/repaint.ts
+		/**
+		* The repaint decision, as a pure function.
+		*
+		* Every edit to a rule ends with the same question: does the interface have to be
+		* repainted, or is refreshing the panel's readout enough? Repainting is the
+		* expensive half (the theme skin is re-registered, the wallpaper layer is
+		* rewritten, the host's theme is switched), so it must not be done for a rule
+		* that is not the one on screen — but it MUST be done the moment the edit
+		* changes what should be on screen.
+		*
+		* The naive test — "is the edited rule the active one?" — is wrong in exactly the
+		* case that kept being reported as "更新的不太及时，只有我动调色盘或者切模型的时候
+		* 才出现": an edit that CREATES the winner. Uploading a rule's first picture, or
+		* an auto-extracted color landing on a rule that had none, makes that rule
+		* paintable *through that very edit* (see `ruleCanPaint`), so the rule is not the
+		* active one at the moment of the check; the wallpaper and the skin then only
+		* showed up later, when an unrelated drag or model switch happened to re-run the
+		* resolution.
+		*
+		* Sampling the winner on BOTH sides of the edit is what makes such a change land
+		* at once, and `editedId === winnerAfter` additionally covers the edit that does
+		* not move the resolution but changes the look of the rule that IS painting (a
+		* color, a slider, a framing).
+		*
+		* `null` is "nothing of ours is painting" (the interface falls back to the host's
+		* own look), which is a winner like any other id.
+		*
+		* Kept free of imports on purpose: `scripts/repaint-check.ts` exercises it on
+		* plain node, the same way `rotation.ts` is exercised. A rule's `color`/`match`
+		* are the inputs that make the resolution move, which is why they are the fields
+		* whose write paths all end here.
+		*/
+		function shouldRepaint(editedId, winnerBefore, winnerAfter) {
+			return winnerAfter === editedId || winnerAfter !== winnerBefore;
+		}
+		//#endregion
 		//#region src/client/components/ErrorBoundary.tsx
 		/**
 		* Catches render errors from the theme section subtree (wheel, sliders, editor)
@@ -7255,10 +7860,11 @@ window.__ModuleLoader__.load({
 		/**
 		* dsh-background-by-model — browser half entry.
 		*
-		* Wires the plugin lifecycle: rule resolution against the current model,
-		* wallpaper layer, theme skin, viewport watch, i18n, settings-section injection,
-		* boot restore and watchdogs. The heavy lifting lives in the sibling modules
-		* (state / modelbg / rpc / wallpaper / components).
+		* Wires the plugin lifecycle and nothing else: rule resolution, the repaint gate,
+		* the settings section's actions and the teardown effects. The machinery lives in
+		* the sibling modules — appearance (skin, palette, restores), appearance-checks and
+		* watchdogs (recurring checks on one schedule), rotation-timer, boot, model-state,
+		* auto-extract, theme-file, nav-icon, wallpaper, state, modelbg, rpc.
 		*/
 		const name = "dsh-background-by-model";
 		const inject = [
@@ -7267,7 +7873,6 @@ window.__ModuleLoader__.load({
 			"theme",
 			"connection"
 		];
-		const CUSTOM_ID = "custom-color";
 		/**
 		* Ceiling on what one recommended profile may add up to, across every wallpaper.
 		*
@@ -7297,76 +7902,13 @@ window.__ModuleLoader__.load({
 		const PRESET_CONCURRENCY = 4;
 		function apply(ctx) {
 			initRpc((endpoint, payload) => ctx.connection.rpc.call(RPC_CHANNEL, endpoint, payload).then((res) => res));
-			let customDispose = null;
-			let skinTimer = null;
-			/** Colour scheme of the skin this plugin has registered, or null when none is. */
-			let skinScheme = null;
-			/** Scheme the host currently holds for our theme id; null when it is not there. */
-			const registeredScheme = () => {
-				const theme = ctx.theme.getTheme().themes.find((t) => t.id === CUSTOM_ID);
-				return theme === void 0 ? null : theme.colorScheme;
-			};
-			const registerCustom = (h, s, l) => {
-				const { colorScheme, tokens } = genTokens(h, s, l);
-				if (skinScheme === colorScheme && registeredScheme() !== null) {
-					if (ctx.theme.getTheme().preference !== CUSTOM_ID) ctx.theme.setTheme(CUSTOM_ID);
-					return;
-				}
-				customDispose?.();
-				try {
-					customDispose = ctx.theme.register({
-						id: CUSTOM_ID,
-						colorScheme,
-						tokens
-					});
-				} catch {
-					customDispose = null;
-				}
-				skinScheme = registeredScheme() ?? colorScheme;
-				if (ctx.theme.getTheme().themes.some((t) => t.id === CUSTOM_ID)) ctx.theme.setTheme(CUSTOM_ID);
-			};
-			/** A rule without a saved color means "follow the system theme". */
-			const dropCustom = () => {
-				customDispose?.();
-				customDispose = null;
-				skinScheme = null;
-				try {
-					if (ctx.theme.getTheme().preference === CUSTOM_ID) ctx.theme.setTheme("system");
-				} catch {}
-			};
-			/**
-			* Re-emit the interface palette for whatever is painted RIGHT NOW.
-			*
-			* Called from two places, and the second one is why this is a function: a
-			* model switch (`applyActive`) and a ROTATION STEP (`paintImage`). A theme color
-			* belongs to an image since 0.7.1, so stepping to the next picture changes the
-			* palette as much as switching models does — and a step that only repainted the
-			* wallpaper would leave the previous picture's color on the interface until
-			* something else happened to re-run an apply (dragging the wheel, switching
-			* models), which is precisely the "it only updates when I touch the color wheel"
-			* report this plugin already had once.
-			*
-			* The debounce is for the OTHER caller: a color drag runs a full apply dozens of
-			* times per second, and the host-visible skin switch (dispose + register +
-			* activate) must not happen on every pointer move. A rotation step pays the same
-			* 60 ms, which is invisible next to a dwell time of 5 s or more.
-			*/
-			const applyPalette = () => {
-				const color = activeColor();
-				if (skinTimer !== null) window.clearTimeout(skinTimer);
-				if (color === null) {
-					skinTimer = null;
-					dropCustom();
-				} else skinTimer = window.setTimeout(() => {
-					skinTimer = null;
-					registerCustom(color[0], color[1], color[2]);
-				}, 60);
-				syncHostScheme();
-			};
-			ctx.effect(() => () => {
-				if (skinTimer !== null) window.clearTimeout(skinTimer);
-				customDispose?.();
-			}, "dsh-background-by-model: skin dispose");
+			const appearance = createAppearance({
+				ctx,
+				refresh: () => applyWp()
+			});
+			ctx.effect(() => () => appearance.dispose(), "dsh-background-by-model: skin dispose");
+			const applyPalette = () => appearance.applyPalette();
+			const syncHostScheme = () => appearance.syncHostScheme();
 			const styleEl = document.createElement("style");
 			styleEl.dataset.plugin = "dsh-background-by-model";
 			markOwnSheet(styleEl);
@@ -7377,10 +7919,8 @@ window.__ModuleLoader__.load({
 			}, "dsh-background-by-model: gradient");
 			let rev = 0;
 			let rulesRev = 0;
-			let modelText = "";
-			let modelSource = "default";
-			let modelNote = "waiting";
-			let modelKey = "\0";
+			/** The model the rules are matched against, and whether it actually moved. */
+			const model = createModelTracker();
 			const store = defineStore({
 				init: () => ({
 					url: null,
@@ -7431,21 +7971,8 @@ window.__ModuleLoader__.load({
 			const sync = () => {
 				rev++;
 				const rot = rotationFacts();
-				bound?.sync(rWp(), rev, rulesRev, modelLabel !== "" ? modelLabel : modelText, modelSource, modelNote, activeRuleId, activeMatched, rot.index, rot.total, rot.rotating, hostIsLegacy());
-			};
-			/**
-			* Publish the scheme the host's own preference resolves to. The theme service
-			* is the only place that knows it (a custom active theme included); the
-			* wallpaper layer needs it to hand `data-ds-dark-theme` back in the host's own
-			* form while a color-less rule follows that theme, instead of leaving the flag
-			* off — which pins the host to its LIGHT palette on a dark system.
-			*/
-			const syncHostScheme = () => {
-				try {
-					setHostScheme(ctx.theme.getTheme().active.colorScheme === "dark");
-				} catch {
-					setHostScheme(null);
-				}
+				const m = model.state;
+				bound?.sync(rWp(), rev, rulesRev, m.label !== "" ? m.label : m.text, m.source, m.note, activeRuleId, activeMatched, rot.index, rot.total, rot.rotating, hostIsLegacy());
 			};
 			/**
 			* Which rule wins for the current model RIGHT NOW, and whether it was a
@@ -7464,7 +7991,7 @@ window.__ModuleLoader__.load({
 				return holiday !== null ? {
 					rule: holiday,
 					matched: false
-				} : matchRule(cfg.rules, modelText);
+				} : matchRule(cfg.rules, model.state.text);
 			};
 			/** Id of the rule that would paint right now; `null` = the host's own look. */
 			const winnerId = () => resolveRule().rule?.id ?? null;
@@ -7501,9 +8028,6 @@ window.__ModuleLoader__.load({
 				applyWp();
 				sync();
 			};
-			let rotTimer = null;
-			/** Identity of the schedule currently armed; a change means "re-arm". */
-			let rotSig = "";
 			/** Warm one image so a later switch fades toward bytes that are already here. */
 			const warmImage = (rule, idx) => {
 				const slot = rule.images[idx]?.slot;
@@ -7524,64 +8048,18 @@ window.__ModuleLoader__.load({
 					sync();
 				});
 			};
-			const rotateTick = () => {
-				const rule = activeRule();
-				if (rule === null) return;
-				const next = nextIndex(rule.images.length, rule.rotate.order, imageIndexOf(rule));
-				if (next === null) {
-					scheduleRotation(true);
-					return;
-				}
-				setRotIndex(next);
-				paintImage(rule, next);
-				const after = nextIndex(rule.images.length, rule.rotate.order, next);
-				if (after !== null) warmImage(rule, after);
-			};
-			/**
-			* Arm (or re-arm) the rotation for the active rule.
-			*
-			* Idempotent by SIGNATURE rather than by "already armed": a slider drag on the
-			* active rule re-runs the whole apply dozens of times per second, and restarting
-			* the interval on each of those would mean the dwell timer never elapses while
-			* the user is dragging (and a 10 s rotation would never advance). The signature
-			* carries exactly the inputs the schedule depends on, so a real change — another
-			* rule, another interval, the tab becoming visible again — re-arms while a
-			* repaint does not.
-			*/
-			const scheduleRotation = (force = false) => {
-				const rule = activeRule();
-				const sig = rule === null ? "" : [
-					rule.id,
-					rule.rotate.enabled,
-					rule.rotate.intervalMs,
-					rule.rotate.order,
-					rule.images.length,
-					document.hidden
-				].join("|");
-				if (!force && sig === rotSig) return;
-				rotSig = sig;
-				if (rotTimer !== null) {
-					window.clearInterval(rotTimer);
-					rotTimer = null;
-				}
-				if (rule === null || document.hidden) return;
-				if (!isRotating(rule.images.length, rule.rotate.enabled, rule.rotate.intervalMs)) return;
-				const next = nextIndex(rule.images.length, rule.rotate.order, imageIndexOf(rule));
-				if (next !== null) warmImage(rule, next);
-				rotTimer = window.setInterval(rotateTick, rule.rotate.intervalMs);
-			};
-			ctx.effect(() => () => {
-				if (rotTimer !== null) {
-					window.clearInterval(rotTimer);
-					rotTimer = null;
-				}
-			}, "dsh-background-by-model: rotation timer");
-			const onVisibility = () => {
-				scheduleRotation();
-				sync();
-			};
+			const rotation = createRotation({
+				paintImage,
+				warmImage,
+				sync
+			});
+			const scheduleRotation = (force = false) => rotation.schedule(force);
+			const onVisibility = () => rotation.onVisibility();
 			document.addEventListener("visibilitychange", onVisibility);
-			ctx.effect(() => () => document.removeEventListener("visibilitychange", onVisibility), "dsh-background-by-model: rotation visibility");
+			ctx.effect(() => () => {
+				document.removeEventListener("visibilitychange", onVisibility);
+				rotation.dispose();
+			}, "dsh-background-by-model: rotation");
 			/**
 			* The holiday the background must follow right now, or null.
 			*
@@ -7595,57 +8073,27 @@ window.__ModuleLoader__.load({
 			sync();
 			watchParts();
 			const offModel = watchModel(ctx, (text, label, source, note) => {
-				const key = `${text}\u0001${source}\u0001${note}`;
-				if (key === modelKey) return;
-				const textChanged = text !== modelText;
-				modelKey = key;
-				modelText = text;
-				modelSource = source;
-				modelNote = note;
-				setModelLabel(label !== "" ? label : text);
-				if (textChanged) applyActive(true);
+				const change = model.update(text, label, source, note);
+				if (!change.changed) return;
+				if (change.textChanged) applyActive(true);
 				else sync();
 			});
 			ctx.effect(() => () => offModel(), "dsh-background-by-model: model watch");
 			(async () => {
-				if (modelText !== "") return;
+				if (model.state.text !== "") return;
 				const fallback = await readDefaultModel();
-				if (fallback !== null && modelText === "") {
-					modelKey = `${fallback}\u0001default\u0001fallback`;
-					modelText = fallback;
-					modelSource = "default";
-					modelNote = "fallback";
-					setModelLabel(fallback);
+				if (fallback !== null && model.state.text === "") {
+					model.adopt(fallback, "default", "fallback");
 					applyActive();
 				}
 			})();
-			let holidayKey = activeHoliday() ?? "";
-			const holidayTimer = window.setInterval(() => {
-				const next = activeHoliday() ?? "";
-				if (next === holidayKey) return;
-				holidayKey = next;
-				const slot = todayHolidaySlot();
-				if (slot === null) applyActive();
-				else loadSlot(slot).then(() => applyActive());
-			}, 3e4);
-			ctx.effect(() => () => {
-				window.clearInterval(holidayTimer);
-			}, "dsh-background-by-model: holiday rollover");
-			/** Read one slot's bytes into the cache unless they are already there. */
-			const loadSlot = async (slot) => {
-				if (imageOf(slot) !== null) return;
-				const url = await readImage(slot);
-				if (url !== null) setImage(slot, url);
-			};
 			/**
 			* The slot of the holiday that could paint TODAY, or null.
 			*
-			* Gated on the CALENDAR, not merely on the switch — and this gate is worth more
-			* than it used to be. The art does not ship in the package any more: the first
-			* read on the day sends the node half to the network, so a profile that is
-			* simply not on a holiday must not merely avoid ~730 KB of base64 over this
-			* channel, it must avoid starting a download at all. On every other day this
-			* returns null and nothing is fetched, cached or paid for.
+			* Gated on the CALENDAR, not merely on the switch: the art does not ship in the
+			* package any more, so the first read on the day sends the node half to the
+			* network. On every other day this returns null and nothing is fetched, cached
+			* or paid for.
 			*/
 			const todayHolidaySlot = () => {
 				if (!cfg.holidays.enabled) return null;
@@ -7655,57 +8103,38 @@ window.__ModuleLoader__.load({
 				if (item === null || !item.enabled) return null;
 				return ruleSlots(item)[0] ?? null;
 			};
-			/**
-			* The slots boot hydrates, in no particular order: the FIRST image of every
-			* rule, today's holiday, and the image the current model paints.
-			*
-			* That first-image set is exactly what this plugin loaded per rule before
-			* multi-image existed — a rule card draws its first image as its thumbnail, so
-			* the settings page looks the same as it always did. Everything past the first
-			* image of a rule is read ON DEMAND: by the rotation (which warms the image it
-			* is about to need as soon as its schedule is armed) and by the settings page
-			* when a card is expanded. Hydrating every image of every rule here would mean
-			* twenty full-size data URLs over this channel before the first frame on a
-			* five-rule setup with four pictures each, which is the one cost this feature
-			* must not pay.
-			*
-			* The slot list the store knows about (`readPersisted().slots`) is deliberately
-			* NOT hydrated any more: an orphaned slot that no rule references has no card to
-			* appear on, so pulling its bytes over the channel at boot is pure waste. It
-			* stays on disk — and is still reported by the node half — until a rule
-			* references it again or it is deleted with its rule.
-			*/
-			const bootSlots = () => {
-				const holiday = todayHolidaySlot();
-				const firsts = cfg.rules.map((r) => r.images[0]?.slot).filter((slot) => slot !== void 0);
-				const current = prioritySlot();
-				return Array.from(/* @__PURE__ */ new Set([
-					...firsts,
-					...holiday === null ? [] : [holiday],
-					...current === null ? [] : [current]
-				]));
+			const activeHolidayId = () => activeHoliday();
+			/** Load one slot and repaint once its bytes are here (the art download). */
+			const loadAndRepaint = async (slot) => {
+				await loadSlot(slot);
+				applyActive();
 			};
-			/**
-			* The slot that paints before anything else: the holiday in force when there
-			* is one, otherwise the FIRST image of the current model's rule. A holiday
-			* outranks the rule here for the same reason it outranks it when painting.
-			*
-			* Always the first image (never the one `advanceOnSwitch` would step to): boot
-			* paints without an advance, and hydrating an image the first frame is not going
-			* to use would leave the frame blank until the real one arrived.
-			*/
-			const prioritySlot = () => todayHolidaySlot() ?? matchRule(cfg.rules, modelText).rule?.images[0]?.slot ?? null;
+			const schedule = createSchedule();
+			ctx.effect(() => () => schedule.dispose(), "dsh-background-by-model: schedule");
+			ctx.effect(appearance.armRestores(), "dsh-background-by-model: boot restore");
+			const checkHost = {
+				restore: appearance.watch,
+				activeColor,
+				refreshHostPalette: () => {
+					syncHostScheme();
+					applyWp();
+				},
+				refresh: () => applyWp(),
+				applyActive,
+				activeHolidayId,
+				todayHolidaySlot,
+				loadAndRepaint
+			};
+			schedule.add(themeWatchdog(checkHost));
+			schedule.add(holidayRollover(checkHost));
 			(async () => {
 				const persisted = await loadPersisted();
 				if (persisted !== null) {
 					adoptConfig(persisted.config);
-					const first = prioritySlot();
-					const slots = bootSlots();
-					const order = first === null ? slots : [first, ...slots.filter((s) => s !== first)];
-					for (const slot of order) {
-						await loadSlot(slot);
-						if (slot === first) applyActive();
-					}
+					await hydrateBoot({
+						modelText: model.state.text,
+						holidaySlot: todayHolidaySlot()
+					}, applyActive);
 				}
 				applyActive();
 			})();
@@ -7714,10 +8143,7 @@ window.__ModuleLoader__.load({
 			}, "dsh-background-by-model: wp cleanup");
 			ctx.effect(() => ctx.on("theme/change", () => {
 				syncHostScheme();
-				if (activeColor() !== null) {
-					const snapshot = ctx.theme.getTheme();
-					if (snapshot.preference !== CUSTOM_ID && snapshot.themes.some((t) => t.id === CUSTOM_ID)) ctx.theme.setTheme(CUSTOM_ID);
-				}
+				appearance.reassert();
 				applyWp();
 			}), "dsh-background-by-model: theme change");
 			let frame = 0;
@@ -7754,56 +8180,22 @@ window.__ModuleLoader__.load({
 			* their own palette since 0.7.1 and the one the user just added is the one they
 			* are looking at. Omitted (or unknown) falls back to the rule's first image.
 			*
-			* The question is asked of the IMAGE, not of the rule: a rule whose pictures
-			* were all cleared and then re-filled must theme each new picture, and a rule
-			* with a color of its own still has no say over the colors of its pictures.
-			*
 			* The decode is asynchronous, so the "still empty?" question is asked AGAIN on
 			* arrival: a color chosen while it ran must win over the one being computed.
+			* Sequential over a batch on purpose: a batch is a handful of full-size photos,
+			* and ten parallel decodes buy nothing while landing the colors in list order
+			* does (the card fills in from its first picture).
 			*/
-			const maybeAutoExtract = async (id, slot) => {
-				if (!cfg.autoExtract) return;
-				/** The entry this extraction is about, re-resolved on every read. */
-				const target = (rule) => {
-					if (rule === null) return void 0;
-					return (slot === void 0 ? void 0 : rule.images.find((i) => i.slot === slot)) ?? rule.images[0];
-				};
-				const image = target(ruleById(id));
-				if (image === void 0 || image.color !== null) return;
-				const url = displayImageOf(image.slot);
-				if (url === null) return;
-				let hsl = null;
-				try {
-					hsl = await extractWallpaperColor(url, image.bgState);
-				} catch {
-					hsl = null;
+			const extract = createAutoExtract({
+				paintable: (slot) => displayImageOf(slot),
+				repaint: (id, winner) => repaintIfMoved(id, winner),
+				winnerId,
+				bumpRulesRev: () => {
+					rulesRev++;
 				}
-				if (hsl === null) return;
-				const current = target(ruleById(id));
-				if (current === void 0 || current.color !== null) return;
-				const winner = winnerId();
-				current.color = hsl;
-				rulesRev++;
-				saveConfig();
-				repaintIfMoved(id, winner);
-			};
-			/**
-			* The batch form, for one upload that carried several pictures.
-			*
-			* EVERY picture that arrived is themed from its own bytes, the first ones
-			* included. The single-slot reading of an upload ("the last image added is the
-			* one being looked at") is true of the CARD's selection and false of the
-			* palette: since a theme color belongs to an image, a batch that themed only
-			* its last file left the rest of a fresh rotation on the system theme, with
-			* nothing in the interface to say why.
-			*
-			* Sequential on purpose: a batch is a handful of full-size photos, and ten
-			* parallel decodes buy nothing the user can see, while landing the colors in
-			* list order does (the card fills in from its first picture).
-			*/
-			const maybeAutoExtractEach = async (id, slots) => {
-				for (const slot of slots) await maybeAutoExtract(id, slot);
-			};
+			});
+			const maybeAutoExtract = (id, slot) => extract.one(id, slot);
+			const maybeAutoExtractEach = (id, slots) => extract.each(id, slots);
 			const activeLang = () => {
 				try {
 					const snapshot = ctx.locale.getSnapshot();
@@ -7815,74 +8207,8 @@ window.__ModuleLoader__.load({
 			/** The model-resolution facts the host self-check reports, read on demand. */
 			const readModelFacts = () => {
 				const rule = activeRuleId === null ? null : ruleById(activeRuleId);
-				return {
-					text: modelText,
-					source: modelSource,
-					note: modelNote,
-					rule: rule === null ? "" : rule.match !== "" ? rule.match : rule.id,
-					matched: activeMatched
-				};
-			};
-			/**
-			* Write a whole theme file into the store: its rules, its wallpapers, nothing
-			* else. The ONE door both imports come through — the file the user picked and
-			* the profile downloaded from the project's asset host — so a downloaded
-			* profile cannot arrive by a laxer route than a hand-picked file does.
-			*
-			* `wipeFirst` is the entire difference between them, and it belongs to the
-			* recommended profile alone. `nextSlot` hands slots out as `m1`, `m2`, … — a
-			* counter, not a random token — so a downloaded profile and the store it lands
-			* in collide on those names as a matter of course rather than by coincidence.
-			* Emptying the store first is what makes "replace everything with this"
-			* literally true, instead of overwriting whichever of the user's own pictures
-			* happened to share a name. The file path keeps the older behaviour: it
-			* replaces the rules but pre-emptively deletes nothing.
-			*
-			* The wipe happens HERE rather than before the download, and that ordering is
-			* the one thing worth being pedantic about: an unreachable CDN must not cost
-			* the user their configuration on the way to a profile that never arrived. By
-			* the time this runs the bytes are already in hand, so the caller has nothing
-			* left to fail at.
-			*/
-			const applyThemeFile = async (data, wipeFirst) => {
-				if (typeof data.version === "number" && data.version > 9) return false;
-				if (typeof data.config !== "object" || data.config === null) return false;
-				if (wipeFirst) {
-					await resetStore();
-					resetConfig();
-				}
-				adoptConfig(data.config);
-				const incoming = data.images ?? {};
-				const keep = /* @__PURE__ */ new Set();
-				for (const slot of cfg.rules.flatMap(ruleSlots)) {
-					keep.add(slot);
-					const raw = incoming[slot];
-					if (typeof raw === "string" && /^data:image\//.test(raw)) {
-						setImage(slot, raw);
-						writeImage(slot, raw);
-					} else {
-						setImage(slot, null);
-						deleteImage(slot);
-					}
-				}
-				for (const slot of Object.keys(incoming)) if (!keep.has(slot) && /^[A-Za-z0-9_-]{1,32}$/.test(slot)) deleteImage(slot);
-				persistConfig();
-				applyActive();
-				return true;
+				return model.facts(rule === null ? "" : rule.match !== "" ? rule.match : rule.id, activeMatched);
 			};
-			/**
-			* What the last FAILED profile attempt already had in hand.
-			*
-			* Only a failure leaves anything here — a download that completes is applied or
-			* thrown away whole, and holding megabytes of base64 for a re-click that a
-			* second re-download would settle is not a trade this makes. What it buys is the
-			* one case that had no answer at all before: a profile whose sixth of seven files
-			* failed now costs ONE file on the next press instead of seven.
-			*
-			* Held across section re-injections on purpose (it is declared here, in `apply`,
-			* not inside `sectionInject`): the retry is usually the next click of the same
-			* button, but the panel can be closed and reopened between them.
-			*/
 			let presetHeld = null;
 			const sectionInject = (actions) => {
 				bound = actions;
@@ -8010,16 +8336,11 @@ window.__ModuleLoader__.load({
 						repaintIfMoved(id, winner);
 					},
 					/**
-					* Store ONE image's layout mode. Addressed by slot like `setImageFraming`,
-					* for the same reason: how a picture meets the viewport is a property of the
-					* picture, and 适应 on a tall screenshot says nothing about the landscape
-					* photo beside it in the rotation.
+					* Store ONE image's layout mode. Addressed by slot like `setImageFraming`:
+					* how a picture meets the viewport is a property of the picture.
 					*
-					* A mode is a placement, not a paint: it changes nothing about WHICH image is
-					* on screen, only how it is laid out. So the patch is written, sanitized, and
-					* the layer repainted through the same `repaintIfMoved` the framing commit
-					* uses — that call repaints the current image whether or not the winner
-					* moved, which is what makes the chips feel live.
+					* A mode is a placement, not a paint — nothing changes about WHICH image is
+					* on screen — so it ends in the same gate the framing commit uses.
 					*/
 					setImageMode: (id, slot, mode) => {
 						const rule = ruleById(id);
@@ -8098,12 +8419,9 @@ window.__ModuleLoader__.load({
 						return res;
 					},
 					/**
-					* Store ONE image's theme color (null = that image follows the system
-					* theme). Addressed by slot exactly like `setImageFraming`, because the
-					* color belongs to the image: editing image 3's color must not rewrite
-					* image 1's, and it must not touch the RULE's color either — that one is
-					* what the rule paints once its last picture is gone, and it is edited only
-					* while there is no image to edit (the panel's own branch).
+					* Store ONE image's theme colour (null = that image follows the system theme).
+					* Addressed by slot like `setImageFraming`: editing one picture's colour must
+					* touch neither another picture's nor the RULE's own.
 					*/
 					setImageColor: (id, slot, color) => {
 						const rule = ruleById(id);
@@ -8156,14 +8474,10 @@ window.__ModuleLoader__.load({
 						sync();
 					},
 					/**
-					* Patch the GLOBAL wallpaper-switch transition (effect, easing, where the
-					* duration comes from).
+					* Patch the GLOBAL wallpaper-switch transition.
 					*
-					* Deliberately no `applyWp()`: this setting decides what the NEXT switch
-					* looks like and nothing on screen changes right now, so re-running the
-					* whole apply (token rewrite, every interface part) for something that
-					* paints nothing would be the expensive way to say "saved". The Config
-					* page's own preview plays the effect instead.
+					* Deliberately no `applyWp()`: this decides what the NEXT switch looks like
+					* and paints nothing now. The page's own preview plays the effect.
 					*/
 					setTransition: (patch) => {
 						cfg.transition = normalizeTransition({
@@ -8181,61 +8495,33 @@ window.__ModuleLoader__.load({
 						applyActive();
 					},
 					exportTheme: () => {
-						const images = {};
-						const slots = cfg.rules.flatMap(ruleSlots);
-						for (const slot of slots) {
-							const url = imageOf(slot);
-							if (url !== null) images[slot] = url;
-						}
-						const payload = {
-							version: 9,
-							exportedAt: (/* @__PURE__ */ new Date()).toISOString(),
-							config: cfg,
-							images
-						};
-						const blob = new Blob([JSON.stringify(payload, null, 2)], { type: "application/json" });
-						const url = URL.createObjectURL(blob);
-						const a = document.createElement("a");
-						a.href = url;
-						a.download = "dsh-background-by-model-theme.json";
-						a.click();
-						URL.revokeObjectURL(url);
+						saveThemeFile(buildThemeFile());
 					},
 					importTheme: async (file) => {
 						try {
 							const data = JSON.parse(await file.text());
 							if (!data || typeof data !== "object") return false;
-							return await applyThemeFile(data, false);
+							return await applyThemeFile({ applyActive }, data, false);
 						} catch {
 							return false;
 						}
 					},
 					/**
-					* Fetch the project's recommended profile. Downloads only.
-					*
-					* Split from applying it on purpose: the page has to ask before anything is
-					* destroyed, and a confirmation can only describe what is actually in hand
-					* — "7 rules, 7 wallpapers, 2.9 MB" — which means the download comes first
-					* and the question second.
+					* Fetch the project's recommended profile. Downloads only — applying it is
+					* separate, because the page has to ask before anything is destroyed and the
+					* question should describe what is actually in hand.
 					*
-					* The profile is a DIRECTORY now, so this is a pool rather than one call:
-					* the manifest and config say which slots exist, and each wallpaper is one
-					* request, up to `PRESET_CONCURRENCY` of them at a time. What the fan-out
-					* buys is wall-clock time — the real profile measured 8.3 s fetched one at
-					* a time against 4.8 s with four in flight — while each file keeps its own
-					* mirror fallback, its own retry rounds (the node half's business, see
-					* ./preset), its own validation, and its own slot name in a failure.
+					* The profile is a DIRECTORY, so this is a pool rather than one call: the
+					* config names the slots and each wallpaper is one request, up to
+					* `PRESET_CONCURRENCY` at a time. Each file keeps its own mirror fallback,
+					* retry rounds (the node half's business, ./preset), validation and slot name
+					* in a failure.
 					*
-					* STRICT, and the pool is what makes that a decision rather than a
-					* formality: the first wallpaper that cannot be had stops the queue, so the
-					* files nobody has asked for yet are never asked for. Whatever was already
-					* in flight finishes and is thrown away — but what it FETCHED is kept for the
-					* next press (`presetHeld` below), which is the difference between retrying
-					* one file and retrying the lot. Nothing has been touched at this point, so
-					* "the author renamed a file" arrives as an error naming the file rather
-					* than as a profile that is quietly missing a picture — and that loudness
-					* is what makes a reference the plugin does not fully control acceptable
-					* here.
+					* STRICT: the first wallpaper that cannot be had stops the queue. What had
+					* already arrived is kept for the next press (`presetHeld` below) — the
+					* difference between retrying one file and retrying the lot. Nothing is
+					* touched here, so "the author renamed a file" arrives as an error naming the
+					* file rather than as a profile quietly missing a picture.
 					*/
 					fetchRecommended: async (onProgress) => {
 						const head = await fetchPresetConfig();
@@ -8300,14 +8586,10 @@ window.__ModuleLoader__.load({
 							}
 						};
 					},
-					/**
-					* Replace EVERYTHING with a downloaded profile: empty the store, then write
-					* the profile into it. Irreversible by design, which is why the page asks
-					* first and why nothing here is offered as an undo.
-					*/
+					/** Replace EVERYTHING with a downloaded profile: empty the store, then write it. */
 					applyRecommended: async (preset) => {
 						if (!canWriteConfig()) return false;
-						return await applyThemeFile(preset, true);
+						return await applyThemeFile({ applyActive }, preset, true);
 					}
 				};
 			};
@@ -8320,89 +8602,7 @@ window.__ModuleLoader__.load({
 				store,
 				inject: sectionInject
 			}, ThemeSection));
-			const navLabel = () => ctx.locale.bind(NS)("nav");
-			const applyNavIcon = () => {
-				const nav = document.querySelector("[role=\"dialog\"][aria-modal=\"true\"][aria-labelledby]")?.querySelector("nav");
-				if (!nav) return;
-				const target = navLabel();
-				for (const cell of Array.from(nav.querySelectorAll("button"))) {
-					const label = cell.querySelector("span");
-					if (label && label.textContent?.trim() === target) {
-						const svg = cell.querySelector("svg");
-						if (svg && svg.dataset.dshAnyIcon !== "1") {
-							const sun = document.createElementNS("http://www.w3.org/2000/svg", "svg");
-							sun.setAttribute("width", "16");
-							sun.setAttribute("height", "16");
-							sun.setAttribute("viewBox", "0 0 16 16");
-							sun.setAttribute("fill", "none");
-							sun.setAttribute("xmlns", "http://www.w3.org/2000/svg");
-							sun.dataset.dshAnyIcon = "1";
-							sun.innerHTML = SUN_PATHS;
-							svg.replaceWith(sun);
-						}
-						return;
-					}
-				}
-			};
-			let navIconObserver = null;
-			const watchNavIcon = () => {
-				if (navIconObserver !== null || typeof MutationObserver === "undefined") return;
-				navIconObserver = new MutationObserver((records) => {
-					if (records.some((r) => {
-						for (const n of r.addedNodes) {
-							if (n.nodeType !== 1) continue;
-							const el = n;
-							if (el.matches?.("[role=\"dialog\"][aria-modal=\"true\"][aria-labelledby]") || el.querySelector?.("[role=\"dialog\"][aria-modal=\"true\"][aria-labelledby]")) return true;
-						}
-						return false;
-					})) applyNavIcon();
-				});
-				navIconObserver.observe(document.body, {
-					childList: true,
-					subtree: true
-				});
-				applyNavIcon();
-			};
-			watchNavIcon();
-			ctx.effect(() => () => {
-				navIconObserver?.disconnect();
-				navIconObserver = null;
-			}, "dsh-background-by-model: nav icon watch");
-			const restoreSaved = () => {
-				syncHostScheme();
-				const color = activeColor();
-				if (color !== null) {
-					const snapshot = ctx.theme.getTheme();
-					if (!snapshot.themes.some((t) => t.id === CUSTOM_ID)) registerCustom(color[0], color[1], color[2]);
-					else if (snapshot.preference !== CUSTOM_ID) ctx.theme.setTheme(CUSTOM_ID);
-				}
-				applyWp();
-			};
-			const restoreTimers = [300, 1500].map((delay) => window.setTimeout(restoreSaved, delay));
-			ctx.effect(() => () => {
-				restoreTimers.forEach((id) => window.clearTimeout(id));
-			}, "dsh-background-by-model: boot restore");
-			const watchdogId = window.setInterval(() => {
-				syncHostScheme();
-				const color = activeColor();
-				if (color === null) {
-					refreshSystemTheme();
-					return;
-				}
-				const snapshot = ctx.theme.getTheme();
-				let changed = false;
-				if (!snapshot.themes.some((t) => t.id === CUSTOM_ID)) {
-					registerCustom(color[0], color[1], color[2]);
-					changed = true;
-				} else if (snapshot.preference !== CUSTOM_ID) {
-					ctx.theme.setTheme(CUSTOM_ID);
-					changed = true;
-				}
-				if (changed) applyWp();
-			}, 1e3);
-			ctx.effect(() => () => {
-				window.clearInterval(watchdogId);
-			}, "dsh-background-by-model: theme watchdog");
+			ctx.effect(() => watchNavIcon(() => ctx.locale.bind(NS)("nav")), "dsh-background-by-model: nav icon watch");
 			const disposeThemeResets = watchThemeResets();
 			ctx.effect(() => () => {
 				disposeThemeResets();