@colixsystems/widget-sdk 0.138.0 → 0.139.0

package/README.md

@@ -72,6 +72,17 @@ See the design reference for the full architecture: [`docs/architecture/widget-m
 
 `v0.137.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.139.0 (contract 1.108.0)
+
+**An author can BIND a colour field to the workspace brand instead of freezing a hex (sc-7800).** A `type: "color"` field tracked the theme only while it was *unset*, through its `themeDefault` placeholder. The moment the author picked a colour it became a literal that outranked the theme forever, so "make this our brand colour" was inexpressible — the author had to type today's hex, and it went stale silently at the next rebrand.
+
+A colour field's value may now be a **binding** — `"theme:colors.primary"` or `"theme:colors.secondary"` — which both hosts resolve to the workspace's current colour at render.
+
+- **Nothing changes for a widget author.** You keep declaring `{ type: "color", … }` and reading the value off `props.style` / `props`. The host hands your code an ordinary colour string either way, so never branch on a binding, never parse the `theme:` prefix, and never add a "use theme colour" toggle beside a colour field — the Studio's picker already offers the choice, and a second control for it is a dead knob.
+- **Only the two brand tokens are bindable**, listed on `CONTRACT.themeColorTokens`. The derived and contrast-paired tokens (`onPrimary`, `primarySoft`, `primaryStrong`, `loader`) are deliberately withheld: they are the host's to compute, and binding one half of a contrast pair produces unreadable text.
+- **An unresolvable binding falls back to the field's `themeDefault`**, exactly as an unset field does — it never paints blank.
+- **Fully additive.** Every colour already stored is a literal, is untouched, and renders byte-identically.
+
 ### What's new in 0.138.0 (contract 1.107.0)
 
 **Every file upload from the Expo export works again.** Expo's `fetch` implements the WEB FormData spec, so a part must be a string or a Blob — but `useCamera`, `useImageEditor` and `<FilePicker>` all handed back React Native's legacy `{ uri, name, type }` triple, which it rejects with `Unsupported FormDataPart implementation` before a byte leaves the device. Web was unaffected because a browser `File` **is** a Blob, so it only ever reproduced on device. All three now hand back expo-file-system's `File`, carrying the same `uri` / `name` / `type` / `size` — so no widget needs a change.

package/dist/contract.cjs

@@ -121,6 +121,26 @@ const DEFAULT_THEME_TOKENS = Object.freeze({
   widgetStyles: Object.freeze({}),
 });
 
+// sc-7800 -- the colour tokens an AUTHOR may BIND a `type: "color"` field to.
+//
+// A colour field already tracked the theme while unset (its `themeDefault`
+// placeholder); the moment it was set it froze to a hex and stopped following a
+// rebrand. A bound field stores `theme:<path>` instead, and the hosts resolve it
+// per render, so the author's INTENT ("our brand colour") survives the rebrand.
+//
+// Deliberately only the two BRAND tokens. The derived and contrast-paired
+// tokens -- `onPrimary`, `primarySoft`, `primaryStrong`, `loader` -- are the
+// host's to compute: offering them would let an author pick one half of a
+// contrast pair and produce unreadable text with no way to see it was their
+// choice. `label` is the author-facing name; the Studio picker, the host
+// resolver and the AI widget agent all read this ONE list, so what may be
+// written and what will resolve cannot drift.
+const THEME_COLOR_TOKENS = Object.freeze([
+  Object.freeze({ path: "colors.primary", label: "Primary" }),
+  Object.freeze({ path: "colors.secondary", label: "Secondary" }),
+]);
+
+
 // REQ-THEME-15 (sc-1497) — per-component style tokens. The global palette is a
 // single lever: remapping `primaryColor` to recolour "the buttons" recolours
 // every element that shares it. A theme may therefore also carry
@@ -3947,7 +3967,16 @@ const CONTRACT = deepFreeze({
   //    ON the part otherwise, since expo-file-system's File is NOT
   //    `instanceof Blob` at runtime and Expo reads the name off the part.
   //    One upload path on both hosts, as before.
-  version: "1.107.0",
+  // 1.108.0: additive (sc-7800) -- `themeColorTokens`: the brand colour tokens
+  //    an author may BIND a `type: "color"` field to, plus the `theme:<path>`
+  //    value grammar and the `resolveThemeTokenRefs` host resolver behind it.
+  //    A set colour field used to freeze to a hex literal and stop following
+  //    the workspace theme, so "make this our brand colour" was inexpressible
+  //    and every picked colour went stale on the next rebrand. Purely additive:
+  //    a stored hex is untouched and still renders byte-identically, and an
+  //    unresolvable binding falls back to the field's `themeDefault` rather
+  //    than painting blank.
+  version: "1.108.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,
@@ -3958,6 +3987,7 @@ const CONTRACT = deepFreeze({
   actionScriptGlobals: ACTION_SCRIPT_GLOBALS,
   actionScriptMaxBytes: ACTION_SCRIPT_MAX_BYTES,
   themeTokens: DEFAULT_THEME_TOKENS,
+  themeColorTokens: THEME_COLOR_TOKENS,
   themeComponents: THEME_COMPONENTS,
   themeComponentShadows: THEME_COMPONENT_SHADOWS,
   themeComponentTextTransforms: THEME_COMPONENT_TEXT_TRANSFORMS,

package/dist/contract.js

@@ -121,6 +121,26 @@ const DEFAULT_THEME_TOKENS = Object.freeze({
   widgetStyles: Object.freeze({}),
 });
 
+// sc-7800 -- the colour tokens an AUTHOR may BIND a `type: "color"` field to.
+//
+// A colour field already tracked the theme while unset (its `themeDefault`
+// placeholder); the moment it was set it froze to a hex and stopped following a
+// rebrand. A bound field stores `theme:<path>` instead, and the hosts resolve it
+// per render, so the author's INTENT ("our brand colour") survives the rebrand.
+//
+// Deliberately only the two BRAND tokens. The derived and contrast-paired
+// tokens -- `onPrimary`, `primarySoft`, `primaryStrong`, `loader` -- are the
+// host's to compute: offering them would let an author pick one half of a
+// contrast pair and produce unreadable text with no way to see it was their
+// choice. `label` is the author-facing name; the Studio picker, the host
+// resolver and the AI widget agent all read this ONE list, so what may be
+// written and what will resolve cannot drift.
+const THEME_COLOR_TOKENS = Object.freeze([
+  Object.freeze({ path: "colors.primary", label: "Primary" }),
+  Object.freeze({ path: "colors.secondary", label: "Secondary" }),
+]);
+
+
 // REQ-THEME-15 (sc-1497) — per-component style tokens. The global palette is a
 // single lever: remapping `primaryColor` to recolour "the buttons" recolours
 // every element that shares it. A theme may therefore also carry
@@ -3947,7 +3967,16 @@ const CONTRACT = deepFreeze({
   //    ON the part otherwise, since expo-file-system's File is NOT
   //    `instanceof Blob` at runtime and Expo reads the name off the part.
   //    One upload path on both hosts, as before.
-  version: "1.107.0",
+  // 1.108.0: additive (sc-7800) -- `themeColorTokens`: the brand colour tokens
+  //    an author may BIND a `type: "color"` field to, plus the `theme:<path>`
+  //    value grammar and the `resolveThemeTokenRefs` host resolver behind it.
+  //    A set colour field used to freeze to a hex literal and stop following
+  //    the workspace theme, so "make this our brand colour" was inexpressible
+  //    and every picked colour went stale on the next rebrand. Purely additive:
+  //    a stored hex is untouched and still renders byte-identically, and an
+  //    unresolvable binding falls back to the field's `themeDefault` rather
+  //    than painting blank.
+  version: "1.108.0",
   sharedTranslationKeys: SHARED_TRANSLATION_KEYS,
   hooks: HOOKS,
   primitives: PRIMITIVES,
@@ -3958,6 +3987,7 @@ const CONTRACT = deepFreeze({
   actionScriptGlobals: ACTION_SCRIPT_GLOBALS,
   actionScriptMaxBytes: ACTION_SCRIPT_MAX_BYTES,
   themeTokens: DEFAULT_THEME_TOKENS,
+  themeColorTokens: THEME_COLOR_TOKENS,
   themeComponents: THEME_COMPONENTS,
   themeComponentShadows: THEME_COMPONENT_SHADOWS,
   themeComponentTextTransforms: THEME_COMPONENT_TEXT_TRANSFORMS,

package/dist/host.d.ts

@@ -334,3 +334,28 @@ export interface LoginDesign {
 
 /** The sign-in screen's authored design, or null when nothing is configured. */
 export function normaliseLoginDesign(raw: unknown): LoginDesign | null;
+
+/** sc-7800 — true when a stored value is a `theme:<path>` colour binding. */
+export function isThemeTokenRef(value: unknown): boolean;
+
+/**
+ * Resolve one `theme:<path>` binding against a resolved widget theme. Returns
+ * `undefined` for a non-binding, a token outside `CONTRACT.themeColorTokens`,
+ * or a path that does not resolve to a colour.
+ */
+export function resolveThemeTokenRef(
+  value: unknown,
+  theme: unknown,
+): string | undefined;
+
+/**
+ * Replace every bound `type: "color"` field on a widget's props — both the
+ * top-level `propertySchema` fields and the `styleSchema` fields under
+ * `props.style` — with the colour its token currently resolves to. Returns the
+ * same reference when nothing is bound.
+ */
+export function resolveThemeTokenRefs<T>(
+  props: T,
+  theme: unknown,
+  schemas?: { propertySchema?: unknown; styleSchema?: unknown },
+): T;

package/dist/host.js

@@ -23,6 +23,17 @@ export {
   applyThemeComponentStyle,
 } from "./theme-components.js";
 
+// sc-7800: the theme-token colour bindings. `resolveThemeTokenRefs` replaces a
+// bound `type: "color"` field with the colour its token currently resolves to,
+// at the SAME render boundary on both hosts — so a rebrand repaints the Player,
+// the Canvas and the exported app alike, and the widget still receives a plain
+// colour string.
+export {
+  isThemeTokenRef,
+  resolveThemeTokenRef,
+  resolveThemeTokenRefs,
+} from "./theme-token-refs.js";
+
 // REQ-THEME-SURFACE: the surface-token derivation both hosts apply per painted
 // surface — the page background and every container that carries its own fill.
 // Host plumbing, deliberately off the author entry point: a widget reads the

package/dist/index.d.ts

@@ -2700,6 +2700,8 @@ export interface AiWidgetContract {
   readonly manifestCategories: ReadonlyArray<string>;
   readonly manifestPlatforms: ReadonlyArray<string>;
   readonly themeTokens: ThemeTokens;
+  /** sc-7800 — the brand colour tokens a `type: "color"` field may bind to. */
+  readonly themeColorTokens: ReadonlyArray<{ path: string; label: string }>;
   readonly widgetContextShape: Readonly<
     Record<
       string,

package/dist/theme-token-refs.js

@@ -0,0 +1,198 @@
+// sc-7800 — the host side of THEME-TOKEN COLOUR BINDINGS.
+//
+// Host-integration surface, re-exported from `host.js`: consumed ONLY by the
+// platform hosts that render widgets (the web Player / Studio Canvas via
+// buildHostWidgetContext.js, and the exported Expo app's generated WidgetHost),
+// never by a widget author. A widget keeps reading a plain colour string off
+// `props` / `props.style` and never learns a token was involved.
+//
+// Living here — one implementation both hosts import — is what makes a bound
+// colour resolve identically in the Player and the export (widget-parity
+// skill). The alternative, a copy per host, is the drift this file exists to
+// prevent.
+//
+// WHY THIS EXISTS: a `type: "color"` field already tracks the workspace theme
+// while it is UNSET, through its `themeDefault` placeholder. The moment an
+// author picks a colour it became a frozen hex that never followed a rebrand
+// again, and "make this our brand colour" was inexpressible — the author had to
+// type today's hex, which went stale silently. A bound field stores the TOKEN,
+// so the intent survives the rebrand.
+
+import { CONTRACT } from "./contract.js";
+
+// A value is a binding, not a colour, when it carries this prefix. No CSS
+// colour can begin with it, so a stored literal can never be misread as one.
+const PREFIX = "theme:";
+
+/** True when `value` is a theme-token binding rather than a literal colour. */
+export function isThemeTokenRef(value) {
+  return typeof value === "string" && value.startsWith(PREFIX);
+}
+
+/**
+ * Resolve one binding against a resolved widget theme.
+ *
+ * Returns `undefined` for anything that is not a binding, names a token outside
+ * the bindable allowlist, or resolves to a non-string — the caller then leaves
+ * the field unset so it falls back to its `themeDefault` exactly as an
+ * un-bound field does. A malformed binding must never paint blank.
+ */
+export function resolveThemeTokenRef(value, theme) {
+  if (!isThemeTokenRef(value)) return undefined;
+  const path = value.slice(PREFIX.length);
+  // The allowlist is the contract's, so what the Studio may WRITE and what a
+  // host will RESOLVE cannot drift apart.
+  if (!CONTRACT.themeColorTokens.some((token) => token.path === path)) {
+    return undefined;
+  }
+  const resolved = path
+    .split(".")
+    .reduce((o, k) => (o == null ? undefined : o[k]), theme);
+  return typeof resolved === "string" && resolved.trim() !== ""
+    ? resolved
+    : undefined;
+}
+
+function isPlainObject(value) {
+  return value !== null && typeof value === "object" && !Array.isArray(value);
+}
+
+// The same guard the neighbouring style validators apply: these props are
+// author-stored JSON, and assigning such a key while rebuilding an object would
+// silently reseat its prototype instead of carrying the value.
+const UNSAFE_KEYS = new Set(["__proto__", "constructor", "prototype"]);
+
+/**
+ * Walk a declared schema alongside a value and replace every bound `color`
+ * leaf with the colour its token currently resolves to.
+ *
+ * Schema-GUIDED rather than a blind string sweep, because top-level props hold
+ * arbitrary author content — body copy, rich text, a stored link — where a
+ * `theme:`-prefixed string is data and must be left verbatim. Only a field the
+ * widget declared as a colour is eligible here. (`props.style` is different and
+ * is handled by `resolveStyleBag` below.)
+ *
+ * Returns the SAME reference when nothing is bound, so an app that uses no
+ * bindings takes no extra render work and behaves exactly as it did before.
+ */
+function resolveAgainstSchema(schema, value, theme) {
+  if (!isPlainObject(schema) || !isPlainObject(value)) return value;
+  let changed = false;
+  const out = {};
+  for (const [key, raw] of Object.entries(value)) {
+    if (UNSAFE_KEYS.has(key)) continue;
+    const def = schema[key];
+    out[key] = raw;
+    if (!isPlainObject(def)) continue;
+
+    if (def.type === "color") {
+      if (isThemeTokenRef(raw)) {
+        // An unresolvable binding is dropped rather than painted: the field goes
+        // back to unset, which is what already renders its `themeDefault`.
+        out[key] = resolveThemeTokenRef(raw, theme);
+        changed = true;
+      }
+      continue;
+    }
+    if (def.type === "object" && isPlainObject(def.properties)) {
+      const next = resolveAgainstSchema(def.properties, raw, theme);
+      if (next !== raw) {
+        out[key] = next;
+        changed = true;
+      }
+      continue;
+    }
+    if (def.type === "array" && isPlainObject(def.items) && Array.isArray(raw)) {
+      let itemChanged = false;
+      const items = raw.map((item) => {
+        const next =
+          def.items.type === "object" && isPlainObject(def.items.properties)
+            ? resolveAgainstSchema(def.items.properties, item, theme)
+            : item;
+        if (next !== item) itemChanged = true;
+        return next;
+      });
+      if (itemChanged) {
+        out[key] = items;
+        changed = true;
+      }
+    }
+  }
+  return changed ? out : value;
+}
+
+// A style bag is resolved WITHOUT a schema, and deliberately so. Both hosts
+// thread `styleSchema` only for marketplace / AI-agent widgets; a BUILT-IN
+// passes `undefined` on web and `null` on native (it keeps its defaults in
+// code). Requiring the schema would therefore have left every built-in's colour
+// field bindable in the Studio but unresolved at render — the author picks
+// "Primary" and the widget is handed the literal string. Resolving the bag
+// directly is what makes a built-in and a generated widget behave the same, on
+// both hosts, with nothing new baked into the export.
+//
+// Safe without a schema because `props.style` is by construction a bag of style
+// VALUES — colours, sizes, enums — so an allowlisted `theme:` string in it can
+// only ever have been a binding. The depth cap keeps the walk bounded for the
+// structured style values (a gradient's stops, per-corner radii).
+const MAX_STYLE_DEPTH = 3;
+
+function resolveStyleBag(value, theme, depth) {
+  if (typeof value === "string") {
+    if (!isThemeTokenRef(value)) return value;
+    // Unresolvable drops to unset, which is what renders `themeDefault`.
+    return resolveThemeTokenRef(value, theme);
+  }
+  if (depth >= MAX_STYLE_DEPTH) return value;
+  if (Array.isArray(value)) {
+    let changed = false;
+    const items = value.map((item) => {
+      const next = resolveStyleBag(item, theme, depth + 1);
+      if (next !== item) changed = true;
+      return next;
+    });
+    return changed ? items : value;
+  }
+  if (isPlainObject(value)) {
+    let changed = false;
+    const out = {};
+    for (const [key, item] of Object.entries(value)) {
+      if (UNSAFE_KEYS.has(key)) continue;
+      const next = resolveStyleBag(item, theme, depth + 1);
+      out[key] = next;
+      if (next !== item) changed = true;
+    }
+    return changed ? out : value;
+  }
+  return value;
+}
+
+/**
+ * The host render-boundary call: resolve every theme-token colour binding on a
+ * widget's props, both the top-level `propertySchema` fields and the style
+ * values under `props.style`.
+ *
+ * Called by BOTH hosts in the same place, immediately after
+ * `applyThemeComponentStyle` — a binding is the author's own per-instance
+ * value, so it sits at the top of the style precedence and is resolved once the
+ * lower layers have been folded in.
+ *
+ * @param {object} props — the widget's props (post-`applyThemeComponentStyle`).
+ * @param {object} theme — the resolved widget theme (`workspace.theme`).
+ * @param {object} [schemas] — `{ propertySchema }` as declared by the widget's
+ *   manifest, used for the top-level props only. `props.style` needs no schema
+ *   (see above), so a built-in resolves exactly like a generated widget.
+ * @returns {object} props, with every bound colour resolved.
+ */
+export function resolveThemeTokenRefs(props, theme, schemas) {
+  if (!isPlainObject(props)) return props;
+  const { propertySchema } = schemas || {};
+  let out = resolveAgainstSchema(propertySchema, props, theme);
+  const style = out.style;
+  if (isPlainObject(style)) {
+    const nextStyle = resolveStyleBag(style, theme, 1);
+    if (nextStyle !== style) {
+      out = { ...out, style: nextStyle };
+    }
+  }
+  return out;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@colixsystems/widget-sdk",
-  "version": "0.138.0",
+  "version": "0.139.0",
   "description": "Common widget interface for AppStudio. Implements WidgetManifest, WidgetContext, property schema, and helper hooks.",
   "homepage": "https://github.com/Colix-AB/AppStudio",
   "type": "module",
@@ -49,7 +49,7 @@
   ],
   "scripts": {
     "build": "node scripts/build.js",
-    "test": "node --test src/__tests__/contract.test.js src/__tests__/vetted-imports-audit.test.js src/__tests__/hooks-users.test.js src/__tests__/hooks-groups.test.js src/__tests__/hooks-invites.test.js src/__tests__/hooks-schema.test.js src/__tests__/hooks-assets-by-tag.test.js src/__tests__/hooks-filestore-upload.test.js src/__tests__/hooks-filestore-file.test.js src/__tests__/hooks-mutation.test.js src/__tests__/hooks-payments.test.js src/__tests__/hooks-record-permissions.test.js src/__tests__/hooks-geolocation.test.js src/__tests__/hooks-section-empty.test.js src/__tests__/hooks-widget-event.test.js src/__tests__/hooks-widget-input.test.js src/__tests__/hooks-identification.test.js src/__tests__/hooks-subscription.test.js src/__tests__/hooks-volatile-query-key.test.js src/__tests__/linter-users-scope.test.js src/__tests__/linter-comments.test.js src/__tests__/linter-translation-api.test.js src/__tests__/linter-page-url.test.js src/__tests__/linter-image-height.test.js src/__tests__/linter-flex-basis-percent.test.js src/__tests__/linter-hardcoded-design.test.js src/__tests__/linter-measured-padding.test.js src/__tests__/linter-payment-error.test.js src/__tests__/linter-platform.test.js src/__tests__/linter-react-import.test.js src/__tests__/lucide-icon-names.test.js src/__tests__/lucideIconName.test.js src/__tests__/manifest-actions.test.js src/__tests__/widget-translations.test.js src/__tests__/hooks-translate.test.js src/__tests__/devserver.test.js src/__tests__/flatten-entry.test.js src/__tests__/host-externals.test.js src/__tests__/datetimepicker.test.js src/__tests__/property-schema-resolve.test.js src/__tests__/corner-radius.test.js src/__tests__/theme-components-parity.test.js src/__tests__/navigation-parity.test.js src/__tests__/theme-depth-tokens.test.js src/__tests__/interaction-lift.test.js src/__tests__/toast-host.test.js src/__tests__/overlay-tokens.test.js src/__tests__/hooks-domain-error-mapping.test.js src/__tests__/linter-datastore-error.test.js src/__tests__/linter-write-gating.test.js src/__tests__/hooks-speech-to-text.test.js src/__tests__/hooks-camera.test.js src/__tests__/hooks-barcode.test.js src/__tests__/hooks-image-editor.test.js src/__tests__/hooks-bound-columns.test.js src/__tests__/hooks-stable-query.test.js src/__tests__/hooks-can-write.test.js src/__tests__/widget-route.test.js src/__tests__/linter-html-in-content.test.js src/__tests__/markdown.test.js src/__tests__/markdown-edit.test.js src/__tests__/richtext-tokens.test.js src/__tests__/style-group.test.js"
+    "test": "node --test src/__tests__/contract.test.js src/__tests__/theme-token-refs.test.js src/__tests__/vetted-imports-audit.test.js src/__tests__/hooks-users.test.js src/__tests__/hooks-groups.test.js src/__tests__/hooks-invites.test.js src/__tests__/hooks-schema.test.js src/__tests__/hooks-assets-by-tag.test.js src/__tests__/hooks-filestore-upload.test.js src/__tests__/hooks-filestore-file.test.js src/__tests__/hooks-mutation.test.js src/__tests__/hooks-payments.test.js src/__tests__/hooks-record-permissions.test.js src/__tests__/hooks-geolocation.test.js src/__tests__/hooks-section-empty.test.js src/__tests__/hooks-widget-event.test.js src/__tests__/hooks-widget-input.test.js src/__tests__/hooks-identification.test.js src/__tests__/hooks-subscription.test.js src/__tests__/hooks-volatile-query-key.test.js src/__tests__/linter-users-scope.test.js src/__tests__/linter-comments.test.js src/__tests__/linter-translation-api.test.js src/__tests__/linter-page-url.test.js src/__tests__/linter-image-height.test.js src/__tests__/linter-flex-basis-percent.test.js src/__tests__/linter-hardcoded-design.test.js src/__tests__/linter-measured-padding.test.js src/__tests__/linter-payment-error.test.js src/__tests__/linter-platform.test.js src/__tests__/linter-react-import.test.js src/__tests__/lucide-icon-names.test.js src/__tests__/lucideIconName.test.js src/__tests__/manifest-actions.test.js src/__tests__/widget-translations.test.js src/__tests__/hooks-translate.test.js src/__tests__/devserver.test.js src/__tests__/flatten-entry.test.js src/__tests__/host-externals.test.js src/__tests__/datetimepicker.test.js src/__tests__/property-schema-resolve.test.js src/__tests__/corner-radius.test.js src/__tests__/theme-components-parity.test.js src/__tests__/navigation-parity.test.js src/__tests__/theme-depth-tokens.test.js src/__tests__/interaction-lift.test.js src/__tests__/toast-host.test.js src/__tests__/overlay-tokens.test.js src/__tests__/hooks-domain-error-mapping.test.js src/__tests__/linter-datastore-error.test.js src/__tests__/linter-write-gating.test.js src/__tests__/hooks-speech-to-text.test.js src/__tests__/hooks-camera.test.js src/__tests__/hooks-barcode.test.js src/__tests__/hooks-image-editor.test.js src/__tests__/hooks-bound-columns.test.js src/__tests__/hooks-stable-query.test.js src/__tests__/hooks-can-write.test.js src/__tests__/widget-route.test.js src/__tests__/linter-html-in-content.test.js src/__tests__/markdown.test.js src/__tests__/markdown-edit.test.js src/__tests__/richtext-tokens.test.js src/__tests__/style-group.test.js"
   },
   "engines": {
     "node": ">=18"