@uniweb/core 0.29.2 → 0.29.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/core",
-  "version": "0.29.2",
+  "version": "0.29.4",
   "description": "Core classes for the Uniweb platform - Uniweb, Website, Page, Block",
   "type": "module",
   "exports": {

package/src/index.js

@@ -67,6 +67,7 @@ export {
   splitPathCapture,
   joinPathCapture,
   recordHandle,
+  recordTitle,
   routeParamValue,
   routeParamValues,
   matchesRouteParam,

package/src/route-match.js

@@ -261,6 +261,36 @@ export function recordHandle(record) {
   return record.slug
 }
 
+/**
+ * A record's DISPLAY TITLE — what the page about it, and a search result for it, are called.
+ *
+ * ⭐ ONE RULE, read by every producer of that title (ruled 2026-09-14 [Diego]): the
+ * parametric page (`Website._createDynamicPage`, so the SPA and a host's render), the
+ * static build's page expansion, and the record search index (`@uniweb/projections`).
+ *
+ *     title  →  name  →  the record's handle (`recordHandle`: `$name`, else `slug`)
+ *
+ * ⛔ Until then a page read `title` alone while the search index read `title || name`,
+ * so a record with a `name` and no `title` — a person — titled its search result and
+ * left its page carrying the template's own title, which on the site where this was
+ * measured was the route token itself: `:slug` (2026-09-14).
+ *
+ * Only a non-empty string (or a finite number — `title: 2024` in YAML) names a record.
+ * A localized map or a rich document is structure this rule cannot render, and
+ * `String()` of one is `[object Object]`.
+ *
+ * @param {Object} record
+ * @returns {string|undefined}
+ */
+export function recordTitle(record) {
+  if (!record || typeof record !== 'object') return undefined
+  for (const value of [record.title, record.name, recordHandle(record)]) {
+    if (typeof value === 'string' && value.trim() !== '') return value
+    if (typeof value === 'number' && Number.isFinite(value)) return String(value)
+  }
+  return undefined
+}
+
 /**
  * The record field a route param is matched on — ONE MAP, read by the local match
  * (`routeParamValue`, below) and by the records service's record question (`match`,

package/src/services.js

@@ -21,6 +21,18 @@ import { applyBasePath } from './base-path.js'
  *      does not provide, and on a static site, where no host speaks, the whole
  *      answer.
  *
+ * ## ⛔ THE TWO TIERS ARE NOT TWO SOURCES OF ONE KIND OF THING
+ *
+ * ⭐ **A site's block is an EXPRESSION OF INTENT — a request for something. The
+ * host's is THE ANSWER.** That is the real reason step 1 wins below, and it is
+ * not a detail of precedence: an operator's declaration can be answered
+ * differently by the deployment that serves it, and is routinely settled later
+ * than the moment it was written.
+ *
+ * ⇒ **So never read a site's declaration as what the site HAS**, and never
+ * report a resolved address back as what the operator asked for. The two are
+ * different kinds of statement that happen to share a spelling.
+ *
  * Absent from both means the site has no such service, and the caller acts on
  * that rather than guessing an address. That is the same rule for every service,
  * and it is why this module exists: it was previously implemented three times —
@@ -80,6 +92,14 @@ import { applyBasePath } from './base-path.js'
  * and a framework that encodes which capabilities cost money ships the business
  * model into open source.
  *
+ * ⛔ **AND IT COVERS A FIELD'S JUSTIFICATION, NOT ONLY ITS NAME.** A field naming
+ * no tier still breaks this if the reason it exists is to help someone manage
+ * what a host charges for: the commercial surface has then been designed around,
+ * which is the same coupling wearing a neutral spelling. ⇒ **Ask what a field is
+ * FOR, not only what it says** — a neutral spelling with a commercial purpose
+ * passes every check that reads only the name. (One such field was proposed and
+ * rejected on this ground, 2026-09-15.)
+ *
  * ⛔ **There is deliberately no explanatory string, and there was one — it was
  * a mistake.** Until 2026-08-13 a declining host could supply a `reason` that
  * this module relayed "to the UI verbatim", with an English default when nothing

package/src/website.js

@@ -11,7 +11,7 @@ import FetcherDispatcher from './fetcher-dispatcher.js'
 import ObservableState from './observable-state.js'
 import { normalizeSeo } from './seo.js'
 import { resolveDefaultLocale, localeLabel } from './locale-config.js'
-import { matchDynamicRoute, decodeRouteValue, matchesRouteParam, routeBinding, routeParamName, parentRouteOf } from './route-match.js'
+import { matchDynamicRoute, decodeRouteValue, matchesRouteParam, recordTitle, routeBinding, routeParamName, parentRouteOf } from './route-match.js'
 import { resolveFetchConfigs, pageRouteQuery, recordPages, routeSelection, siteReaches } from './fetch-config.js'
 import { declaredKeys } from './data-keys.js'
 import { buildDetailConfig } from './detail-url.js'
@@ -679,7 +679,11 @@ export default class Website {
       }
 
       if (currentItem) {
-        if (currentItem.title) pageData.title = currentItem.title
+        // ⭐ The record names the page by the one rule its search result is named by
+        // too (`recordTitle`: `title`, `name`, then its handle). ⛔ Until 2026-09-14 this
+        // read `title` alone, so a person record kept the template's title — `:slug`.
+        const title = recordTitle(currentItem)
+        if (title) pageData.title = title
         if (currentItem.description || currentItem.excerpt) {
           pageData.description = currentItem.description || currentItem.excerpt
         }