@colixsystems/widget-sdk 0.145.0 → 0.146.0

package/README.md

@@ -71,7 +71,17 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 ## Status
 
-`v0.145.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+`v0.146.0` — pre-publish. The package surface (types, function names, export paths) is the v1 contract; runtime behaviour for some hooks is stubbed (each hook documents what's wired and what isn't). It is **not yet published to npm**.
+
+### What's new in 0.146.0 (contract 1.114.0)
+
+**The chrome divider's width is bounded in the resolver, so both hosts agree (sc-7965).** `resolveFooterTokens` and `resolveSidebarTokens` returned `borderWidth` as any finite number. Only the export bounded it — on its way into the StyleSheet — so a stored `1e9` ruled a **billion-pixel border across the published web app** and a normal one in the exported app. The clamp moved into the shared resolver, where both hosts inherit it.
+
+- **Clamped, not dropped.** A value past the end lands **on** the end (1–8), the idiom `tabRadiusOr` / `tabIndicatorOr` already use. This moves the EXPORT too for such a value: it used to *drop* out-of-range and fall back to the 1px hairline, and now renders 8px like the Player.
+- **Zero clamps up**, matching what the export already rendered there — the divider's COLOUR is its switch, so a coloured 0px edge is a contradiction rather than "off".
+- **Every legal 1–8 value is untouched**, and the write path has always refused anything else, so only a hand-edited or pre-coercer `theme_config` can hold a value this moves.
+
+The site header was already bounded by its own resolver and is unchanged. The compiler keeps its own `coerceBorderWidth` as defence in depth over a blob `PUT /tenant/config` still stores verbatim; a test pins the two bounds to each other behaviourally, since the SDK cannot import the backend coercer.
 
 ### What's new in 0.145.0 (contract 1.113.0)
 

package/dist/contract.cjs

@@ -4054,7 +4054,17 @@ const CONTRACT = deepFreeze({
   //    and the inherited colours are hex-guarded on the way out as well as in.
   //    Every colour still falls back to the sidebar's: an untouched workspace is
   //    unchanged.
-  version: "1.113.0",
+  // 1.114.0: behaviour (sc-7965) — `resolveFooterTokens` / `resolveSidebarTokens`
+  //    now return a `borderWidth` CLAMPED to 1-8 instead of any finite number.
+  //    The bound lived only in the export (`coerceBorderWidth(...) ?? 1`), so a
+  //    stored `1e9` ruled a billion-pixel divider across the web Player and a
+  //    1px one in the exported app. Clamped rather than dropped, like the tab
+  //    measurements beside it: a value past the end lands ON the end, which also
+  //    moves the EXPORT for such a value (it used to drop to the 1px hairline).
+  //    Zero clamps up for the same reason the export already rendered 1 there —
+  //    the divider's COLOUR is its switch. Every legal 1-8 value is unchanged,
+  //    and only a hand-edited or pre-coercer blob can hold anything else.
+  version: "1.114.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/contract.js

@@ -4050,7 +4050,17 @@ const CONTRACT = deepFreeze({
   //    and the inherited colours are hex-guarded on the way out as well as in.
   //    Every colour still falls back to the sidebar's: an untouched workspace is
   //    unchanged.
-  version: "1.113.0",
+  // 1.114.0: behaviour (sc-7965) — `resolveFooterTokens` / `resolveSidebarTokens`
+  //    now return a `borderWidth` CLAMPED to 1-8 instead of any finite number.
+  //    The bound lived only in the export (`coerceBorderWidth(...) ?? 1`), so a
+  //    stored `1e9` ruled a billion-pixel divider across the web Player and a
+  //    1px one in the exported app. Clamped rather than dropped, like the tab
+  //    measurements beside it: a value past the end lands ON the end, which also
+  //    moves the EXPORT for such a value (it used to drop to the 1px hairline).
+  //    Zero clamps up for the same reason the export already rendered 1 there —
+  //    the divider's COLOUR is its switch. Every legal 1-8 value is unchanged,
+  //    and only a hand-edited or pre-coercer blob can hold anything else.
+  version: "1.114.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,

package/dist/navigation.cjs

@@ -365,11 +365,28 @@ function resolveTopBarTokens(theme) {
   };
 }
 
+// REQ-THEME-LOOK: the divider's width in px, bounded HERE so both hosts inherit
+// one range. The export clamped it on its way into the StyleSheet
+// (`coerceBorderWidth(...) ?? 1`) where the Player passed any finite number
+// straight to a style object, so a stored `1e9` ruled a billion-pixel border
+// across the published web app and a 1px one in the exported one (sc-7965).
+//
+// Clamped rather than dropped, like the tab measurements above: a value past
+// the end lands on the end instead of reverting to the hairline. Zero clamps up
+// for the same reason the export already turned it into one — the divider's
+// COLOUR is its switch, so a coloured 0px edge is a contradiction, not "off".
+const BORDER_WIDTH_MIN = 1;
+const BORDER_WIDTH_MAX = 8;
 function borderWidthOr(...values) {
   for (const value of values) {
-    if (typeof value === "number" && Number.isFinite(value)) return value;
+    if (typeof value === "number" && Number.isFinite(value)) {
+      return Math.min(
+        Math.max(Math.round(value), BORDER_WIDTH_MIN),
+        BORDER_WIDTH_MAX,
+      );
+    }
   }
-  return 1;
+  return BORDER_WIDTH_MIN;
 }
 
 module.exports = { normaliseNavigation, menuItemCap, resolveFooterTokens, resolveSidebarTokens, resolveTopBarTokens };

package/dist/navigation.js

@@ -356,9 +356,26 @@ export function resolveTopBarTokens(theme) {
   };
 }
 
+// REQ-THEME-LOOK: the divider's width in px, bounded HERE so both hosts inherit
+// one range. The export clamped it on its way into the StyleSheet
+// (`coerceBorderWidth(...) ?? 1`) where the Player passed any finite number
+// straight to a style object, so a stored `1e9` ruled a billion-pixel border
+// across the published web app and a 1px one in the exported one (sc-7965).
+//
+// Clamped rather than dropped, like the tab measurements above: a value past
+// the end lands on the end instead of reverting to the hairline. Zero clamps up
+// for the same reason the export already turned it into one — the divider's
+// COLOUR is its switch, so a coloured 0px edge is a contradiction, not "off".
+const BORDER_WIDTH_MIN = 1;
+const BORDER_WIDTH_MAX = 8;
 function borderWidthOr(...values) {
   for (const value of values) {
-    if (typeof value === "number" && Number.isFinite(value)) return value;
+    if (typeof value === "number" && Number.isFinite(value)) {
+      return Math.min(
+        Math.max(Math.round(value), BORDER_WIDTH_MIN),
+        BORDER_WIDTH_MAX,
+      );
+    }
   }
-  return 1;
+  return BORDER_WIDTH_MIN;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@colixsystems/widget-sdk",
-  "version": "0.145.0",
+  "version": "0.146.0",
   "description": "Common widget interface for AppStudio. Implements WidgetManifest, WidgetContext, property schema, and helper hooks.",
   "homepage": "https://github.com/Colix-AB/AppStudio",
   "type": "module",