dsh-deepseek-style-theme 1.43.6 → 1.43.7

package/lib/client.js

@@ -1852,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');
@@ -2045,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;
@@ -2111,7 +2136,15 @@ html[data-dshome-blur="off"] body{
 			} catch (error) {
 				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 () => {
+				clearInterval(markerPoll);
 				unsubscribeColor();
 				if (unsubscribeDark !== null) unsubscribeDark();
 				unsubscribeGlass();

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.6",
+  "version": "1.43.7",
   "type": "module",
   "keywords": [
     "deepseek",