@poodle64/ui 2026.8.14 → 2026.8.15

package/README.md

@@ -751,7 +751,11 @@ node harness/additivity.mjs ui-v2026.8.3
 Tailwind chain, exactly as a consuming app wires it — a class that generates no
 rule, a colour that resolves to nothing, a registered theme key nothing reads, a
 variant whose selector cannot match the DOM, and a sizing utility that has
-silently changed meaning all fail there rather than shipping.
+silently changed meaning all fail there rather than shipping. It also sweeps the
+source for the one craft defect none of those can see — a content container that
+draws a border and declares no surface, so it computes transparent and the page
+shows through it (`src/test/bordered-surface.test.ts`, which carries its own
+limits at the foot of the file).
 
 `pnpm run test:browser` is the leg nothing else can stand in for: jsdom applies
 no stylesheet and returns unresolved `var(…)` literals, so it passes just as

package/dist/components/ui/library-browse/document-table.svelte

@@ -38,7 +38,19 @@
 	const hasBadges = $derived(documents.some((d) => d.badges?.length));
 </script>
 
-<div class="rounded-md border">
+<!-- The card surface, not a bare border. This wrapper holds CONTENT, so it has
+     to paint one: with `border` alone the table and every ancestor computed
+     rgba(0,0,0,0) at 1440x900 in both themes, so the page background showed
+     straight through a container sitting beside opaque cards. `bg-card
+     border-border ds-edge` is the same trio Panel, StatCard, StatList,
+     DetailPanel, EmptyState and DataTableTanstack use — and `border-border`
+     matters on its own: a bare `border` resolves to currentColor, which was
+     drawing this hairline in full-strength foreground rather than the border
+     token. `overflow-hidden` comes with the surface, as it does on every
+     sibling: a row's `hover:bg-muted/50` otherwise paints square corners over
+     the wrapper's radius now that there is a surface to paint over.
+     Gated by src/test/bordered-surface.test.ts. -->
+<div class="bg-card border-border ds-edge overflow-hidden rounded-md border">
 	<TableRoot>
 		<TableHeader>
 			<TableRow>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@poodle64/ui",
-  "version": "2026.8.14",
+  "version": "2026.8.15",
   "description": "Household shared component layer: shadcn-svelte primitives (bits-ui) plus the composed page chrome every app builds its routes from, restyled by each app's @poodle64/design-tokens alias layer. One fix reaches every app.",
   "type": "module",
   "license": "MIT",

package/registry/component-map.json

@@ -1,7 +1,7 @@
 {
 	"meta": {
 		"package": "@poodle64/ui",
-		"version": "2026.8.14",
+		"version": "2026.8.15",
 		"generatedBy": "scripts/generate-registry.mjs",
 		"source": "scripts/situations.json + package source (DO NOT EDIT the outputs by hand)",
 		"componentCount": 54,

package/registry/component-map.md

@@ -1,7 +1,7 @@
 # @poodle64/ui — situation → component map
 
 <!-- GENERATED by scripts/generate-registry.mjs from scripts/situations.json + package source. DO NOT EDIT. -->
-Generated from `@poodle64/ui@2026.8.14`. 54 components, 14 situations.
+Generated from `@poodle64/ui@2026.8.15`. 54 components, 14 situations.
 
 **Read this before writing a `<div>`.** Find the SITUATION you are in below, then compose the component named for it — do not hand-build it from raw `Card` or utility classes. Import is `import { Name } from '<import path>'`. Props marked `?` are optional. This map is the retrieval step the [`frontend-design` skill] makes mandatory; the [CHI 2026 study] measured composing-from-a-registry at 95% design-system compliance against 71% for writing the CSS from a prose style guide.