uniweb 0.14.0 → 0.14.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.14.0",
+  "version": "0.14.2",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -42,8 +42,8 @@
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
     "@uniweb/core": "0.8.0",
-    "@uniweb/kit": "0.10.0",
-    "@uniweb/runtime": "0.9.0"
+    "@uniweb/runtime": "0.9.0",
+    "@uniweb/kit": "0.10.2"
   },
   "peerDependencies": {
     "@uniweb/build": "0.16.0",

package/partials/agents.md

@@ -869,14 +869,13 @@ Names only — for signatures and props, read the package: it's on disk at `node
 **Header/layout:** `useScrolled(threshold)`, `useMobileMenu()`, `useAppearance()`
 **Overlays:** `Overlay` (modals, palettes, drawers, toasts — portals out of the layout, contains focus; read the note below before hand-rolling one)
 **Keyboard:** `useShortcut('mod+k', fn)`, `useShortcuts({…})`, `useShortcutLabel('mod+k')` — `mod` is Cmd on Apple platforms and Ctrl elsewhere, and the label renders per-platform so a hint never shows the wrong key
-**Long-form prose:** `<Prose>` and the container you put `<Render>` output in both use Tailwind Typography's `prose` classes, which come from a plugin your *foundation* installs — kit ships no stylesheet. Without it the markup is right and completely unstyled. Add `@tailwindcss/typography` to the foundation's deps, then:
+**Long-form prose:** `<Prose>` and the container you put `<Render>` output in both use Tailwind Typography's `prose` classes. One line in the foundation's `styles.css` supplies them and points them at the site's theme:
 
 ```css
-@plugin "@tailwindcss/typography";
-@import "@uniweb/kit/prose-tokens.css";   /* makes prose answer to theme.yml */
+@import "@uniweb/kit/prose-tokens.css";   /* the plugin, wired to theme.yml */
 ```
 
-Use **one** `prose` container per subtree — the `--tw-prose-*` variables are inherited, so a nested one silently resets them and the outer container goes on looking correct. The section that renders the document is usually the better owner; a layout should supply column width and padding.
+Nothing to install — the import brings the plugin with it. **Skip the import and prose is completely unstyled**, silently: the class is there and no rules are behind it. `uniweb doctor` flags that. Use **one** `prose` container per subtree — the `--tw-prose-*` variables are inherited, so a nested one silently resets them and the outer container goes on looking correct. The section that renders the document is usually the better owner; a layout should supply column width and padding.
 
 **Documentation shells:** `useHeadings()` (the page's headings + the one being read, derived from content so it prerenders), `website.getBranchHierarchy({ route, for })` (the page tree for one branch). Kit ships no ready-made layout — a layout is your foundation's design; write it in `src/layouts/` and use these for the behaviour.
 **Layout helpers:** `useGridLayout(columns, { gap })`, `useAccordion({ multiple, defaultOpen })`

package/src/commands/doctor.js

@@ -169,6 +169,41 @@ function loadSiteYml(dir) {
  *    committed, and then looks like something you may edit. That is how
  *    hand-authored files ended up there in the first place.
  */
+/**
+ * Whether any component source under `dir` matches `pattern`.
+ *
+ * Only the directories a foundation puts components in, and never
+ * `node_modules` — this answers "did the developer write this", so a match
+ * inside a dependency is the wrong answer.
+ */
+function sourceMatches(dir, pattern) {
+  const roots = ['sections', 'layouts', 'components']
+  const walk = (d, depth = 0) => {
+    if (depth > 6) return false
+    let entries
+    try {
+      entries = readdirSync(d, { withFileTypes: true })
+    } catch {
+      return false
+    }
+    for (const entry of entries) {
+      if (entry.name === 'node_modules' || entry.name.startsWith('.')) continue
+      const p = join(d, entry.name)
+      if (entry.isDirectory()) {
+        if (walk(p, depth + 1)) return true
+      } else if (/\.(jsx?|tsx?)$/.test(entry.name)) {
+        try {
+          if (pattern.test(readFileSync(p, 'utf8'))) return true
+        } catch {
+          // unreadable file — not this check's problem to report
+        }
+      }
+    }
+    return false
+  }
+  return roots.some((r) => walk(join(dir, r)))
+}
+
 function checkGeneratedDataDir({ sitePath, siteName, siteYml, issues, shouldFix, fixed }) {
   const dataDir = join(sitePath, 'public', DATA_DIR)
   const declared = new Set(Object.keys(siteYml.collections || {}))
@@ -380,6 +415,52 @@ export async function doctor(args = []) {
     }
   }
 
+  // Prose without the tokens — a silent, total loss of styling.
+  //
+  // `@uniweb/kit/prose-tokens.css` brings Tailwind Typography with it and then
+  // points it at the site's theme.yml. A foundation that writes `prose` (or
+  // renders <Prose>/<Article>, which emit it) and does NOT import that file
+  // gets the class and no rules behind it: correct markup, zero styling, and
+  // nothing reported anywhere. Measured 2026-07-30 on a foundation missing only
+  // the plugin — every paragraph `margin-top: 0px`, no warning from Vite,
+  // Tailwind or the browser.
+  //
+  // kit closes this for anyone who imports the file; this closes it for anyone
+  // who does not, which is the case kit cannot reach.
+  for (const f of foundations) {
+    // `f.path` is already absolute (built above with join(workspaceDir, …)).
+    const stylesPath = join(f.path, 'styles.css')
+    if (!existsSync(stylesPath)) continue
+
+    const styles = readFileSync(stylesPath, 'utf8')
+    if (styles.includes('@uniweb/kit/prose-tokens.css')) continue
+
+    // Does anything here actually ask for prose? Either the class in the
+    // stylesheet, or kit's components, which render it.
+    const usesProseClass = /(^|[\s"'`])prose(\s|["'`]|$)/m.test(styles)
+    const usesProseComponent = sourceMatches(f.path, /<(Prose|Article)\b/)
+
+    if (!usesProseClass && !usesProseComponent) continue
+
+    const id = 'prose-without-tokens'
+    const reason = usesProseComponent
+      ? 'renders <Prose> or <Article>'
+      : 'uses the `prose` class'
+    issues.push({
+      id,
+      type: 'warning',
+      foundation: f.name,
+      message: `${f.name} ${reason} but does not import prose-tokens.css`
+    })
+    warn(`[${id}] ${f.name} ${reason}, with no prose styling behind it`)
+    log(
+      `    Tailwind Typography supplies the rules and it is not loaded, so the ` +
+      `markup is correct and completely unstyled — silently.`
+    )
+    log(`    Add to ${f.folderName}/styles.css:`)
+    log(`      ${colors.dim}@import "@uniweb/kit/prose-tokens.css";${colors.reset}`)
+  }
+
   if (extensions.length > 0) {
     log('')
     success(`Found ${extensions.length} extension(s):`)

package/src/framework-index.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-07-30T18:57:10.510Z",
+  "generatedAt": "2026-07-30T22:09:40.317Z",
   "packages": {
     "@uniweb/build": {
       "version": "0.16.0",
@@ -45,7 +45,7 @@
       "deps": []
     },
     "@uniweb/kit": {
-      "version": "0.10.0",
+      "version": "0.10.2",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core",
@@ -110,7 +110,7 @@
       "deps": []
     },
     "@uniweb/unipress": {
-      "version": "0.5.14",
+      "version": "0.6.0",
       "path": "framework/unipress",
       "deps": [
         "@uniweb/build",