basalt-ui 1.9.0 → 1.10.0

package/src/provider/index.test.tsx

@@ -10,11 +10,12 @@
  * The `BasaltBridge density wiring` block below covers the layer `composeInjectedCss` alone can't:
  * that `BasaltBridge` (not just the pure `composeInjectedCss` helper) actually reads
  * `theme.other.basaltDensity` off the RUNNING theme and feeds it through `buildDensityCss` into the
- * injected `<style>`, end to end from `createBasaltTheme(undefined, { density })`. No
- * `@testing-library/react`/jsdom is configured in this repo (see `tokens/build-fonts-css.test.ts`'s
- * doc for that same limitation elsewhere) — `react-dom/server`'s `renderToStaticMarkup` renders the
- * real `BasaltProvider` tree without a DOM, which is enough since the injected `<style>` is plain
- * text content, not something that needs a live DOM to assert on.
+ * injected `<style>`, end to end from `createBasaltTheme(undefined, { density })`. A DOM harness now
+ * exists (`tests/setup/dom.ts`, preloaded via the root `bunfig.toml`) — this suite still uses
+ * `react-dom/server`'s `renderToStaticMarkup` deliberately, since the injected `<style>` is plain
+ * text content on server-rendered markup, not something that needs a live DOM to assert on.
+ * Converting this to mount through the DOM harness would only be worth it if a future assertion here
+ * needed live DOM behavior (event handling, layout, effects) rather than the static markup string.
  */
 import { describe, expect, test } from 'bun:test'
 import { renderToStaticMarkup } from 'react-dom/server'

package/src/surfaces.ts

@@ -371,6 +371,28 @@ export const SURFACES = {
     // @visx/* ban dropped — `basalt/visx-boundary` now bans it universally outside charts.
     forbiddenImports: [...MANTINE_BANS],
   },
+  './agent-chat': {
+    kind: 'doctrine',
+    layer: 'mantine-coupled',
+    rule: 'agent',
+    skill: ['basalt-app'],
+    guardKinds: [],
+    description:
+      'Mantine-styled thread-chat components over basalt-ui/agent: ThreadWorkspace, ThreadFeed, ThreadOutcomeCard, ThreadDetailPanel, Composer, ThreadTranscript, threadPartRenderers (Mantine-coupled). remend and motion are required, not optional — ThreadTranscript imports content/markdown.tsx (remend eagerly), and ThreadFeed/ThreadDetailPanel import motion/react eagerly, so this subpath fails to resolve without both installed even though peerDependenciesMeta marks them optional (npm has no per-subpath optionality).',
+    optionalPeers: [
+      'ai',
+      'motion',
+      'remend',
+      'use-stick-to-bottom',
+      'react-markdown',
+      'remark-gfm',
+      'shiki',
+      '@shikijs/langs',
+      '@shikijs/themes',
+      'beautiful-mermaid',
+    ],
+    forbiddenImports: [],
+  },
   './content': {
     kind: 'doctrine',
     layer: 'mantine-coupled',

package/src/theme/use-basalt-spacing.test.tsx

@@ -6,10 +6,13 @@
  * with every other density test still green, since those all exercise `deriveSpacing`/
  * `createBasaltTheme` directly, never this hook.
  *
- * No `@testing-library/react`/jsdom is configured in this repo (see `tokens/build-fonts-css.test.ts`'s
- * doc for that same limitation elsewhere) — `react-dom/server`'s `renderToStaticMarkup` is enough to
- * invoke a hook inside a REAL `MantineProvider` tree without a DOM, so these assertions exercise the
- * actual `useMantineTheme()` read, not a re-implementation of it.
+ * A DOM harness now exists (`tests/setup/dom.ts`, preloaded via the root `bunfig.toml`; see
+ * `tokens/build-fonts-css.test.ts`'s doc for that same note elsewhere) — this suite still uses
+ * `react-dom/server`'s `renderToStaticMarkup` deliberately: it's enough to invoke a hook inside a
+ * REAL `MantineProvider` tree without a DOM, so these assertions exercise the actual
+ * `useMantineTheme()` read, not a re-implementation of it. Converting to the DOM harness would only
+ * be worth it if a future assertion here needed the hook to react to a live DOM event (e.g. a
+ * `ResizeObserver`-driven remeasure) rather than a single render-time read.
  */
 import { MantineProvider } from '@mantine/core'
 import type { MantineProviderProps } from '@mantine/core'

package/src/tokens/build-fonts-css.test.ts

@@ -2,8 +2,9 @@
  * `buildFontsCss` — the pure CSS-building half of the `{ fonts }` option (see
  * `../theme/fonts-option.test.ts` for the `theme.other.basaltFonts` round-trip this consumes).
  * `BasaltBridge` calls this directly to append `--basalt-font-*` declarations to the same injected
- * `<style>` as the palette CSS; no DOM/render harness is configured in this package, so the pure
- * function is the testable seam.
+ * `<style>` as the palette CSS. A DOM harness now exists (`tests/setup/dom.ts`, preloaded via the
+ * root `bunfig.toml`), but this pure function needs no render at all — it's the testable seam on
+ * its own, so this suite calls it directly rather than mounting anything.
  */
 import { describe, expect, test } from 'bun:test'
 import { buildFontsCss } from './index'