dsh-deepseek-style-theme 1.43.4 → 1.43.7

package/README.md

@@ -2,6 +2,17 @@
 
 为 DeepSeek Harness Web GUI 复刻 DeepSeek 官网视觉的主题皮肤插件。
 
+## 鸣谢
+
+本插件的两块核心视觉——**流体背景**与**玻璃质感**——都不是从零写出来的，它们分别来自下面两个上游项目。没有它们，这个主题不会有现在这个样子：
+
+| 上游 | 作者 | 本插件用到了什么 |
+|---|---|---|
+| [dsh-theme-mineradio](https://github.com/dhicoc/dsh-theme-mineradio) | [@dhicoc](https://github.com/dhicoc) | 流体背景的**三段 GLSL 着色器**（顶点 / 流场 / 显示）是上游的逐字节副本；四分之一分辨率流场 + 双 framebuffer 乒乓的求解器结构、玻璃色散折射滤镜、光标视差、对话框悬停倾斜同样移植自上游 |
+| [deepseek-harness-background](https://github.com/HaoyueQin/deepseek-harness-background) | [@HaoyueQin](https://github.com/HaoyueQin) | 液态玻璃配方的**技法来源**（半透明填充 + 竖向光泽 + 背板滤镜链的设计思路），本插件按自己的选择器与 `--dshome-glass-*` 变量重新表达，未复制源码 |
+
+两个项目均为 MIT 许可；完整许可原文见 [`THIRD-PARTY-NOTICES.md`](./THIRD-PARTY-NOTICES.md)，随包发布，再分发时必须保留。详细的移植范围与改写点见下文「[第三方代码与署名](#第三方代码与署名)」。
+
 ## 特性
 
 - **流体流动背景（1.42.0+）**：全屏 WebGL2 双通道流体模拟——四分之一分辨率的流场（衰减 + 带速度的指针笔刷，两个 framebuffer 乒乓）被全分辨率的域扭曲噪声渲染器采样，带旋流迭代与三色柔性混合；按钮悬停会轻推流场、点击则荡开涟漪。配色跟随 DSTT 三色令牌（峰谷红 / 谷时蓝 / 常态绿）实时重新着色，无需重挂。**无 WebGL2 时自动回落到原来的粒子背景**（粒子实现完整保留）

package/lib/client.js

@@ -995,18 +995,20 @@ void main() {
 		const CORE_CSS = `
 :root{--ds-brand:#059669;--ds-brand-deep:#047857;--ds-brand-mid:#10B981;--ds-brand-light:#34D399;--ds-glass-blur:24px}
 html,body{background-color:transparent!important}
-/* The page background below is painted from OUR scheme marker
-   (body[data-dshome-dark]), while message text takes its colour from the
-   product's --dsw-alias-* tokens. Those are two different signals, and when
-   they disagree — the marker is derived from the theme service and can miss a
-   scheme change — the result is near-white text on a near-white page: every
-   paragraph vanishes while anything carrying its own background (tool cards)
-   stays readable. Reproduced by clearing the marker on a dark page.
-   Declaring the same two label tokens under the same marker puts both sides on
-   ONE signal. The values are exactly what theme.overrideTokens() already
-   installs for each scheme, so a page where the two agree repaints identically. */
-body{--dsw-alias-label-primary:#152443!important;--dsw-alias-label-secondary:#3c4a63!important}
-body[data-dshome-dark]{--dsw-alias-label-primary:#eef2ff!important;--dsw-alias-label-secondary:#a9b8d8!important}
+/* THE LABEL TOKENS ARE NOT PINNED HERE, AND MUST NOT BE AGAIN.
+   A previous attempt at the invisible-text bug declared
+   body{--dsw-alias-label-primary:...!important} under our own scheme marker,
+   so that background and text could never end up on opposite sides. It did fix
+   that, and it broke something worse: those !important declarations outrank the
+   PRODUCT's tokens, so when the user switched appearance the product changed its
+   own tokens and this stylesheet kept painting the old ones. The UI looked like
+   the switch was dead.
+   Measured on the real page: with the theme's style tags removed the switch
+   works, with them present it does not, and reverting the header z-index changes
+   nothing -- i.e. it is this sheet, and it is these declarations.
+   The invisible-text hazard stays open on purpose. A stuck appearance switch is
+   a broken control; near-white text on a near-white page at least still reads
+   once the marker agrees. Do not re-add these two rules. */
 body{background:radial-gradient(1200px 700px at 12% -10%,color-mix(in srgb,var(--ds-brand) 14%,transparent),transparent 60%),radial-gradient(1000px 600px at 105% 12%,color-mix(in srgb,var(--ds-brand-light) 16%,transparent),transparent 55%),radial-gradient(900px 700px at 50% 115%,color-mix(in srgb,var(--ds-brand) 10%,transparent),transparent 60%),linear-gradient(180deg,#fbfbfd 0%,#f5f6fa 100%);background-attachment:fixed}
 body[data-dshome-color=red]{--ds-brand:#F5222D;--ds-brand-deep:#CF1322;--ds-brand-mid:#FF4D4F;--ds-brand-light:#FF7875}
 body[data-dshome-color=blue]{--ds-brand:#4D6BFE;--ds-brand-deep:#3A65C2;--ds-brand-mid:#4176E6;--ds-brand-light:#73A3D2}
@@ -1726,6 +1728,20 @@ html[data-dshome-blur="off"] body{
 		* subscription is unavailable.
 		*/
 		function createDarkSync(ctx, theme) {
+			/** Last value we wrote to the body; null until the first apply(). */
+			let lastDark = null;
+			/**
+			* Scheme-change listeners. The dark marker is a marker only if someone
+			* reads it: the stylesheet matches on it, and the ambient background reads
+			* it for its palette (see startAmbient). A listener that throws must not
+			* cost the others their update, so each call is boxed.
+			*/
+			const darkListeners = new Set();
+			const notifyDark = (dark) => {
+				for (const fn of darkListeners) {
+					try { fn(dark); } catch (error) {}
+				}
+			};
 			const apply = () => {
 				let dark = false;
 				// Two signals, and BOTH of them lie in some state -- measured, not
@@ -1749,10 +1765,19 @@ html[data-dshome-blur="off"] body{
 					}
 				}
 				if (!dark) dark = document.body.hasAttribute('data-ds-dark-theme');
+				// Remember what we actually put on the body, so a later apply() that
+				// lands on the same answer does not wake the background up for
+				// nothing. `lastDark` is null until the first write.
+				const changed = lastDark !== dark;
+				lastDark = dark;
 				if (dark) document.body.setAttribute('data-dshome-dark', '');
 				else document.body.removeAttribute('data-dshome-dark');
+				// Publish the write. The marker is what EVERY dark rule and the fluid
+				// palette read, so a light/dark switch that only set the attribute left
+				// the background on the scheme it was mounted with -- reported as
+				// "切到深色背景还是蓝白".
+				if (changed) notifyDark(dark);
 			};
-			apply();
 			let unsubscribe = null;
 			try {
 				unsubscribe = ctx.on('theme/change', apply);
@@ -1769,9 +1794,21 @@ html[data-dshome-blur="off"] body{
 			} catch (error) {
 				mirror = null;
 			}
-			return () => {
-				if (unsubscribe !== null) unsubscribe();
-				if (mirror !== null) mirror.disconnect();
+			return {
+				/**
+				* Subscribe to light/dark *writes*. Nothing is replayed on subscribe:
+				* a reader that needs the current value reads the attribute (or calls
+				* dshomeDark()), which keeps one source of truth.
+				*/
+				subscribe: (fn) => {
+					darkListeners.add(fn);
+					return () => darkListeners.delete(fn);
+				},
+				dispose: () => {
+					darkListeners.clear();
+					if (unsubscribe !== null) unsubscribe();
+					if (mirror !== null) mirror.disconnect();
+				}
 			};
 		}
 
@@ -1815,6 +1852,24 @@ html[data-dshome-blur="off"] body{
 		/** Edge-tint hue for the glass dispersion, following the DSTT colour. */
 		const FLUID_HUES = { green: 152, blue: 221, red: 356 };
 
+		/**
+		* A cheap key over everything the palette derives from: the colour token and
+		* the scheme marker, both on <body>.
+		*
+		* The ambient fluid compares this every rendered frame. Why polling instead
+		* of trusting the notification chain: measured on the live page with the
+		* instrumented build, the canvas was mounted once, the page WAS running the
+		* patched bundle, and the fluid was demonstrably alive (both programs
+		* compiled and linked, ping-pong FBOs complete, a draw pair per frame,
+		* glError 0) -- yet u_color1..3 kept arriving as the light-blue triple for
+		* the entire session while <body> said green. So the mount had resolved the
+		* palette before the colour driver's first write, and nothing later re-read
+		* the token. Two getAttribute calls per frame when nothing changed, and it
+		* cannot miss a writer the way a listener can.
+		*/
+		const dsttMarkerKey = () => (document.body.getAttribute('data-dshome-color') || 'green')
+			+ '|' + (document.body.hasAttribute('data-dshome-dark') ? 'dark' : 'light');
+
 		/** The active DSTT colour token. */
 		function dshomeColor() {
 			const value = document.body.getAttribute('data-dshome-color');
@@ -2008,6 +2063,13 @@ html[data-dshome-blur="off"] body{
 		*/
 		function startAmbient() {
 			if (!supportsWebgl2()) return startParticles();
+			// Which build is running, readable from the page. The fluid palette is
+			// resolved at mount and re-derived from the DOM afterwards (syncFluid +
+			// markerPoll below); when a report says the background did not follow the
+			// colour token, this marker is the first thing to check in the console:
+			//   window.__dshomeBuild        -> '1.43.7 palette-poll'
+			// It is also what tools/dstt-dark-report.js prints as buildMarker.
+			try { window.__dshomeBuild = '1.43.7 palette-poll'; } catch (error) {}
 			const canvas = document.createElement('canvas');
 			canvas.setAttribute('data-dsh-deepseek-canvas', '');
 			const style = canvas.style;
@@ -2037,25 +2099,56 @@ html[data-dshome-blur="off"] body{
 			};
 			applyGlass();
 			const unsubscribeGlass = dsttSubscribe(applyGlass);
-			const unsubscribe = subscribeColor((color) => {
-				fluid.setParams(dshomeFluidParams());
-				dispersion.setTint(FLUID_HUES[color] ?? FLUID_HUES.green);
+			// ── palette reconciliation ────────────────────────────────────────────
+			// One reader for BOTH inputs the palette depends on: the colour token on
+			// <body> and the dark marker. Reported symptom: "切主题模式背景不变 /
+			// 深色模式背景还是蓝白". The colour half of that was a real dead end --
+			// `subscribeColor` only fires when the notified colour string CHANGES, so
+			// the boot race (this canvas mounts, then the durable mode arrives over
+			// the async bridge and re-resolves the colour) left the flow painted from
+			// whatever the driver had guessed first, and a mode switch that resolved
+			// to the same colour never notified at all. The scheme half had no
+			// listener: a MutationObserver was watching the marker, but `darkSync`
+			// pointedly does not set a *changed* value twice, and the marker itself
+			// was the only thing written.
+			// So: derive from the DOM on every signal instead of trusting the event to
+			// carry it, and box every listener so one throw cannot cost the rest.
+			let fluidParams = JSON.stringify(dshomeFluidParams());
+			const syncFluid = () => {
+				const next = dshomeFluidParams();
+				const key = JSON.stringify(next);
+				if (key === fluidParams) return;
+				fluidParams = key;
+				try { fluid.setParams(next); } catch (error) {}
+			};
+			const unsubscribeColor = subscribeColor((color) => {
+				syncFluid();
+				try { dispersion.setTint(FLUID_HUES[color] ?? FLUID_HUES.green); } catch (error) {}
 			});
-			// The palette is chosen per colour SCHEME, not only per colour token:
-			// without this the canvas keeps whatever palette it was mounted with,
-			// so a page that loads light and is then switched to dark keeps a
-			// bright flow under a dark shell.
-			let darkMirror = null;
+			const unsubscribeDark = darkSync === null ? null : darkSync.subscribe(syncFluid);
+			// The colour driver writes the token as an attribute; watching it as well
+			// keeps this correct no matter who wrote it (the peak-hour chain, a manual
+			// mode pick, or a future caller that forgets to notify).
+			let tokenMirror = null;
 			try {
-				darkMirror = new MutationObserver(() => { fluid.setParams(dshomeFluidParams()); });
-				darkMirror.observe(document.body, { attributes: true, attributeFilter: ['data-dshome-dark'] });
+				tokenMirror = new MutationObserver(syncFluid);
+				tokenMirror.observe(document.body, { attributes: true, attributeFilter: ['data-dshome-color'] });
 			} catch (error) {
-				darkMirror = null;
+				tokenMirror = null;
 			}
+			// The backstop that actually fixed it. Events above are the fast path;
+			// this poll is the guarantee. It is the same decision as
+			// dsttMarkerKey()'s comment describes -- the palette is derived from the
+			// DOM, so it is re-derived from the DOM, once every half second, for as
+			// long as the canvas lives. syncFluid() itself is a no-op when the key is
+			// unchanged, so the steady-state cost is two getAttribute calls.
+			const markerPoll = setInterval(syncFluid, 500);
 			return () => {
-				unsubscribe();
+				clearInterval(markerPoll);
+				unsubscribeColor();
+				if (unsubscribeDark !== null) unsubscribeDark();
 				unsubscribeGlass();
-				if (darkMirror !== null) darkMirror.disconnect();
+				if (tokenMirror !== null) tokenMirror.disconnect();
 				dispersion.dispose();
 				stopParallax();
 				stopSpotter();
@@ -2177,7 +2270,20 @@ html[data-dshome-blur="off"] body{
 				const colors = palette();
 				for (const p of parts) p.c = colors[(Math.random() * colors.length) | 0];
 			};
+			// Two inputs again: the colour token (notified) and the dark marker
+			// (written by darkSync). The particle palette is per scheme, so a
+			// light/dark switch has to re-roll the colours too -- otherwise the
+			// fallback background keeps the scheme it was mounted with, exactly the
+			// bug the fluid path had.
 			const unsubscribeColor = subscribeColor(refreshColors);
+			const unsubscribeDark = darkSync === null ? null : darkSync.subscribe(refreshColors);
+			let tokenMirror = null;
+			try {
+				tokenMirror = new MutationObserver(refreshColors);
+				tokenMirror.observe(document.body, { attributes: true, attributeFilter: ['data-dshome-color'] });
+			} catch (error) {
+				tokenMirror = null;
+			}
 
 			window.addEventListener('resize', resize);
 			resize();
@@ -2189,6 +2295,8 @@ html[data-dshome-blur="off"] body{
 				cancelAnimationFrame(rafId);
 				window.removeEventListener('resize', resize);
 				unsubscribeColor();
+				if (unsubscribeDark !== null) unsubscribeDark();
+				if (tokenMirror !== null) tokenMirror.disconnect();
 				canvas.remove();
 			};
 		}
@@ -3747,10 +3855,18 @@ body[data-dshome-dark] .${CLS}{background:rgba(14,30,60,.94);box-shadow:0 18px 4
 
 			anchor();
 
+			// The durable mode crosses an async bridge (dsttSync), so the anchor above
+			// may have resolved the colour from the DEFAULT mode -- its 常态绿/常态蓝
+			// token then never appears, and the background keeps the first guess. One
+			// extra read after the sync has had its turn fixes the boot race, and it
+			// is idempotent, so it cannot fight a later answer.
+			const bootTimer = setTimeout(anchor, 0);
+
 			try { unsubscribe = dsttSubscribe(anchor); } catch (error) { unsubscribe = null; }
 
 			return () => {
 				stopped = true;
+				clearTimeout(bootTimer);
 				if (chainTimer !== 0) clearTimeout(chainTimer);
 				if (unsubscribe !== null) unsubscribe();
 				document.removeEventListener('visibilitychange', onVisibility);
@@ -3954,8 +4070,18 @@ body[data-dshome-dark] .${CLS}{background:rgba(14,30,60,.94);box-shadow:0 18px 4
 
 			// Dark marker: owned attribute driven by the theme service, never by
 			// the product's attribute name. Must precede the patch blocks so the
-			// dark selectors match from the first paint.
-			ctx.effect(() => createDarkSync(ctx, theme), 'deepseek-style-theme: dark sync');
+			// dark selectors match from the first paint. The handle is kept in scope
+			// because the ambient background subscribes to its writes: the marker
+			// alone was not enough, since nothing re-read it when the scheme changed.
+			let darkSync = null;
+			ctx.effect(() => {
+				const handle = createDarkSync(ctx, theme);
+				darkSync = handle;
+				return () => {
+					if (darkSync === handle) darkSync = null;
+					handle.dispose();
+				};
+			}, 'deepseek-style-theme: dark sync');
 
 			// Glass-recipe marker: same idea, and it has to be on <html> before the
 			// first paint of the glass surfaces or the pane flashes the other recipe.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "dsh-deepseek-style-theme",
   "description": "DeepSeek official-home style theme: WebGL fluid-flow background, liquid glass with SVG edge refraction, glass sidebar and composer, frosted header, running-subagent progress panel, and DeepSeek brand link for the dsh web GUI",
-  "version": "1.43.4",
+  "version": "1.43.7",
   "type": "module",
   "keywords": [
     "deepseek",