@uniweb/build 0.52.0 → 0.52.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.52.0",
+  "version": "0.52.2",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -57,15 +57,15 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/content-reader": "^1.2.5",
-    "@uniweb/schemas": "^0.2.13",
-    "@uniweb/theming": "^0.1.15",
-    "@uniweb/projections": "^0.7.2",
     "@uniweb/semantic-parser": "^1.4.0",
+    "@uniweb/schemas": "^0.2.14",
+    "@uniweb/theming": "^0.1.15",
+    "@uniweb/content-reader": "^1.2.5",
+    "@uniweb/projections": "^0.7.3",
     "@uniweb/content-writer": "^0.3.4"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "^0.26.1"
+    "@uniweb/runtime": "^0.26.4"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -74,7 +74,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.29.2"
+    "@uniweb/core": "^0.29.4"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/foundation/derive-supports.js

@@ -44,6 +44,23 @@
  * `submit`, because the framework has no list of permitted names
  * (`core/src/services.js`).
  *
+ * ## ⛔ THE `tracking` ENTRY IS SLATED FOR REMOVAL — DO NOT EXTEND IT (decided 2026-09-15)
+ *
+ * ⭐ **Tracking renders nothing.** This field exists because a service with no
+ * surface to draw is invisible from outside — a search endpoint with no search
+ * box. But the runtime emits `page_view` / `outbound_click` / `section_view` for
+ * every foundation alike (`wireTracker`), so a foundation neither supplies nor
+ * withholds tracking, and under the three-state rule (*these and only these*)
+ * emitting it conditionally **asserts something false about every foundation that
+ * does not call these** — not a missing niche capability.
+ *
+ * ⛔ **So the gap is not a gap, and the obvious fixes are wrong:** `block.track()`
+ * (a `Website`-adjacent method in externalized core, invisible here) and
+ * `kit/src/hooks/useReadingDepth.js` (a second hook the module rule below never
+ * named) both emit custom events and derive nothing. **A matcher for either was
+ * considered and rejected.** The rule below and the name `tracking` both go; until
+ * they do, this paragraph is why nobody should widen them.
+ *
  * Two gates need help, and only two:
  *
  *   - **`useTracker`** resolves nothing itself — it calls through to

package/src/prerender.js

@@ -24,7 +24,7 @@ import {
   deriveCacheKey,
   evaluateQuery,
 } from '@uniweb/core'
-import { routePatternToRegex } from '@uniweb/core/route-match'
+import { recordTitle, routePatternToRegex } from '@uniweb/core/route-match'
 import { executeFetch, mergeDataIntoContent, toFetchList } from './site/data-fetcher.js'
 import { shouldSplitContent } from './site/split-content.js'
 import { FONT_LINKS_MARKER } from './site/head-markers.js'
@@ -458,8 +458,11 @@ export function expandDynamicPages(pages, fetched, onProgress = () => {}, stats
           paramValue: binding.paramValue,
         }
 
-        // Use item data for page metadata if available
-        if (item.title) concretePage.title = item.title
+        // The record names the page by the rule the SPA and the search index read
+        // (`recordTitle`: `title`, `name`, then its handle). ⛔ Until 2026-09-14 this read
+        // `title` alone, so a person record's page kept the template's own title.
+        const title = recordTitle(item)
+        if (title) concretePage.title = title
         if (item.description || item.excerpt) concretePage.description = item.description || item.excerpt
 
         expandedPages.push(concretePage)

package/src/schema.js

@@ -464,11 +464,27 @@ function hasEntryFile(dirPath, dirName) {
  * Create an implicit empty meta for a section type discovered without meta.js
  */
 function createImplicitMeta(name) {
-  return { title: inferTitle(name) }
+  return { title: inferTitle(name), titleInferred: true }
 }
 
 /**
- * Build a component entry with title inference applied
+ * Build a component entry with title inference applied.
+ *
+ * ⭐ `titleInferred` SAYS THE TITLE IS OURS, NOT THE AUTHOR'S, and without it a
+ * consumer cannot tell. We fill `title` from the component name whenever
+ * `meta.js` declares none, so `title` is ALWAYS present — which means an editor
+ * showing section names has no way to know that `"Hero"` is a string the build
+ * invented rather than one a developer chose.
+ *
+ * ⛔ THAT DIFFERENCE DECIDES WHETHER THE NAME CAN BE TRANSLATED. An authored
+ * title is the foundation's own words and must be shown verbatim in every UI
+ * language. An inferred one is a placeholder, and a consumer that knows the
+ * section's `family` has a better string available — one it can localize. A
+ * foundation that never named its Hero would otherwise ship the English
+ * `"Hero"` to every author in the world.
+ *
+ * ⚖️ The build itself reads neither field. This is a statement ABOUT the title,
+ * for whoever renders it.
  */
 function buildComponentEntry(name, relativePath, meta) {
   const entry = {
@@ -479,6 +495,7 @@ function buildComponentEntry(name, relativePath, meta) {
   // Apply title inference if meta has no explicit title
   if (!entry.title) {
     entry.title = inferTitle(name)
+    entry.titleInferred = true
   }
   return entry
 }