basalt-ui 1.8.0 → 1.10.0

package/src/guard/check-source.test.ts

@@ -409,6 +409,16 @@ describe('raw-html-layout', () => {
     const f = find(`<div style={{ display: 'flex' }} /> // theme-allow`)
     expect(kinds(f)).not.toContain('raw-html-layout')
   })
+
+  it('does NOT flag a raw <div> with inline display:flex in a chart file — the Flex/Grid/Group remedy is @mantine/*, banned in the Mantine-free chart layer', () => {
+    const f = find(`<div style={{ display: 'flex', gap: 8 }} />`, CHART_PATH)
+    expect(kinds(f)).not.toContain('raw-html-layout')
+  })
+
+  it('still flags the same literal in a non-chart path (the check is not globally weakened)', () => {
+    const f = find(`<div style={{ display: 'flex', gap: 8 }} />`, PATH)
+    expect(kinds(f)).toContain('raw-html-layout')
+  })
 })
 
 // ── 10. inline-spacing ───────────────────────────────────────────────────────
@@ -527,6 +537,16 @@ describe('inline-display', () => {
     const f = find(`<Box style={{ display: 'flex' }} /> // theme-allow`)
     expect(kinds(f)).not.toContain('inline-display')
   })
+
+  it('does NOT flag display: "flex" in a chart file — the Flex/Grid/Group remedy is @mantine/*, banned in the Mantine-free chart layer', () => {
+    const f = find(`<Box style={{ display: 'flex' }} />`, CHART_PATH)
+    expect(kinds(f)).not.toContain('inline-display')
+  })
+
+  it('still flags the same literal in a non-chart path (the check is not globally weakened)', () => {
+    const f = find(`<Box style={{ display: 'flex' }} />`, PATH)
+    expect(kinds(f)).toContain('inline-display')
+  })
 })
 
 // ── 12. raw-visx-axis ────────────────────────────────────────────────────────

package/src/guard/index.ts

@@ -282,10 +282,13 @@ export const DEFAULT_GUARD_CONFIG: GuardConfig = {
  * promotion, and belongs in its own commit so the changelog says enforcement got stricter.
  *
  * `mantine-shade-index` landed in 1.7.0 and is the sole entry — it rejects `c="yellow.7"`, which
- * previously passed, and the one real consumer has several. Its promotion is **deferred to 1.9.0**:
- * 1.8.0 shipped the same day as 1.7.0, so promoting on the next minor number would have given the
- * consumer roughly no runway at all — which is the exact failure the grace minor exists to prevent,
- * and the runway is measured in consumer upgrades, not in version numbers. Promote it by deleting
+ * previously passed, and the one real consumer has several. Its promotion is **deferred to 1.10.0**,
+ * for the second time and for the same reason both times: the runway is measured in consumer
+ * upgrades, not in version numbers. 1.8.0 shipped the same day as 1.7.0, so promoting there would
+ * have given no runway at all. 1.9.0 then carried the chart-layer batch the same consumer asked
+ * for — bundling a build-breaking promotion into the minor they upgrade for the fixes turns a
+ * routine bump into an unplanned refactor, which is precisely what the grace minor exists to
+ * prevent. 1.10.0 is the first minor they can take the promotion on its own. Promote it by deleting
  * the entry (its own commit).
  *
  * @example
@@ -294,7 +297,7 @@ export const DEFAULT_GUARD_CONFIG: GuardConfig = {
  * }
  */
 const GRACE_PERIOD_KINDS: Partial<Record<GuardKind, string>> = {
-  'mantine-shade-index': 'introduced 1.7.0 — promote to error in 1.9.0',
+  'mantine-shade-index': 'introduced 1.7.0 — promote to error in 1.10.0',
 }
 
 /** A kind's effective severity: consumer override first, then the grace table, then `error`. */
@@ -688,8 +691,12 @@ export const GUARD_RULES = {
     kind: 'raw-html-layout',
     pattern: RAW_HTML_TAG, // handled inline (3-condition conjunction); entry keeps registry complete
     enabled: (cfg: GuardConfig) => cfg.rawHtmlLayout,
-    // JSX-tag-shaped (`<div style={{...}}>`) — never appears in CSS text.
-    appliesTo: (relPath) => !relPath.endsWith('.css'),
+    // JSX-tag-shaped (`<div style={{...}}>`) — never appears in CSS text. Also excluded from
+    // chart files: the remedy (Box/Flex/Grid/Stack/Group) is `@mantine/*`, and src/charts/** is a
+    // lint-enforced Mantine-free layer (basalt/token-layer-boundary) — so inside a chart file the
+    // finding is unactionable, not merely inconvenient, and the only "fix" would be a theme-allow
+    // comment written inside the very directory this rule protects.
+    appliesTo: (relPath) => !isChartFile(relPath) && !relPath.endsWith('.css'),
     message:
       'Raw HTML element with inline layout/surface styling — use a Mantine layout primitive (Box/Flex/Grid/Stack/Group).',
   },
@@ -704,8 +711,12 @@ export const GUARD_RULES = {
     pattern: INLINE_DISPLAY,
     enabled: (cfg: GuardConfig) => cfg.inlineDisplay,
     // JSX-object-shaped (`display: 'flex'`, quoted value) — CSS never quotes a keyword value
-    // (`display: flex;` is bare), so the pattern's quote anchor can never match real CSS.
-    appliesTo: (relPath) => !relPath.endsWith('.css'),
+    // (`display: flex;` is bare), so the pattern's quote anchor can never match real CSS. Also
+    // excluded from chart files: the remedy (Flex/Grid/Group) is `@mantine/*`, and src/charts/**
+    // is a lint-enforced Mantine-free layer (basalt/token-layer-boundary) — so inside a chart file
+    // the finding is unactionable, not merely inconvenient, and the only "fix" would be a
+    // theme-allow comment written inside the very directory this rule protects.
+    appliesTo: (relPath) => !isChartFile(relPath) && !relPath.endsWith('.css'),
     message: 'Use <Flex>/<Grid>/<Group> instead of an inline display:flex/grid.',
   },
   'raw-visx-axis': {

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'