dsh-deepseek-style-theme 1.43.6 → 1.43.8

package/lib/client.js

@@ -1837,21 +1837,84 @@ html[data-dshome-blur="off"] body{
 		}
 
 		/**
-		* Fluid palette per DSTT colour. The site ships `#8AA3D6` plus two pure
-		* whites, which reads as one faint blue meander — legible on deepseek.com
-		* but far too quiet to carry a colour token, so each entry here uses a
-		* stronger lead and a genuinely different third tone: the display shader
-		* blends all three across the noise field, so three near-identical colours
-		* flatten the flow into a single wash.
+		* Fluid palette per DSTT colour, built the way the upstream fluid builds its
+		* own: three tones off ONE hue with high saturation and a lightness ramp
+		* (dsh-theme-mineradio's `fluidToneColors`).
+		*
+		* This replaces hand-picked hex triples, and the measurement is why. On the
+		* live page, with the colour token green, the canvas read 235,240,252 while
+		* the CSS background behind it read 233,242,241: the light green set
+		* (#4FBE92 / #FFFFFF / #D6F2E4) is three near-white tones, and three
+		* near-white tones average into a wash in which the eye reads the blue
+		* channel. Hiding the canvas turned the page green instantly -- the canvas
+		* was painting the wash over it. Upstream's lead tone is hsl(hue, 1, .27..),
+		* i.e. genuinely saturated, which is what makes a hue swap visible.
+		*
+		* Hues stay the site's own (FLUID_HUES below).
 		*/
-		const FLUID_COLORS = {
-			green: { light: ['#4FBE92', '#FFFFFF', '#D6F2E4'], dark: ['#1F6B4E', '#061423', '#0E3A2A'] },
-			blue: { light: ['#5E82DE', '#FFFFFF', '#D8E2FA'], dark: ['#2C4A9E', '#050F26', '#122A5C'] },
-			red: { light: ['#D4797F', '#FFFFFF', '#FAD6D8'], dark: ['#8E2F36', '#1A0A0D', '#40141A'] }
-		};
+		const FLUID_DEPTH = { light: 22, dark: 26 };
+
+		/** hsl -> #rrggbb, same shape as the upstream helper. */
+		function fluidHsl(h, s, l) {
+			const hue = ((h % 360) + 360) % 360;
+			const c = (1 - Math.abs(2 * l - 1)) * s;
+			const x = c * (1 - Math.abs(((hue / 60) % 2) - 1));
+			const m = l - c / 2;
+			const seg = Math.floor(hue / 60) % 6;
+			const rgb = seg === 0 ? [c, x, 0]
+				: seg === 1 ? [x, c, 0]
+					: seg === 2 ? [0, c, x]
+						: seg === 3 ? [0, x, c]
+							: seg === 4 ? [x, 0, c]
+								: [c, 0, x];
+			return '#' + rgb.map((v) => Math.round((v + m) * 255).toString(16).padStart(2, '0')).join('');
+		}
+
+		/**
+		* The three fluid tones for one hue. `depth` is upstream's knob: 0 is the
+		* deepest and most saturated, 100 the palest. The dark scheme walks the same
+		* ramp so the flow still reads as a dark shell.
+		*/
+		function fluidToneColors(dark, hue, depth) {
+			const d = Math.min(1, Math.max(0, depth / 100));
+			const ramp = (deep, mid, pale) => (d < 0.5
+				? deep + (mid - deep) * d / 0.5
+				: mid + (pale - mid) * (d - 0.5) / 0.5);
+			if (dark) {
+				return [
+					fluidHsl(hue, 0.85, ramp(0, 0.46, 0.62)),
+					fluidHsl(hue, 0.9, ramp(0, 0.305, 0.45)),
+					fluidHsl(hue, 0.5, ramp(0, 0.075, 0.1))
+				];
+			}
+			return [
+				fluidHsl(hue, 1, ramp(0.27, 0.45, 0.9)),
+				fluidHsl(hue, 0.55, 0.86),
+				fluidHsl(hue, 0.25, 0.955)
+			];
+		}
+
 		/** 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');
@@ -1862,8 +1925,8 @@ html[data-dshome-blur="off"] body{
 		}
 		/** The whole fluid parameter set for the current DSTT colour and scheme. */
 		function dshomeFluidParams() {
-			const palette = FLUID_COLORS[dshomeColor()];
-			const pick = dshomeDark() ? palette.dark : palette.light;
+			const dark = dshomeDark();
+			const pick = fluidToneColors(dark, FLUID_HUES[dshomeColor()], dark ? FLUID_DEPTH.dark : FLUID_DEPTH.light);
 			// `mouseFeed` is ours, not upstream's: false keeps the cursor from
 			// writing a wake into the flow field (see the DSTT `fluidBrush` setting).
 			return { ...SITE_FLUID_PARAMS, color1: pick[0], color2: pick[1], color3: pick[2], mouseFeed: dsttBrush() };
@@ -2045,6 +2108,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 +2181,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.8",
   "type": "module",
   "keywords": [
     "deepseek",