uniweb 1.7.0 → 1.7.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.7.0",
+  "version": "1.7.2",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -43,11 +43,11 @@
     "tar": "^7.0.0",
     "@uniweb/content-writer": "~1.1.2",
     "@uniweb/core": "~1.2.2",
-    "@uniweb/schemas": "~1.3.0",
-    "@uniweb/semantic-parser": "~1.8.1"
+    "@uniweb/semantic-parser": "~1.8.1",
+    "@uniweb/schemas": "~1.3.1"
   },
   "peerDependencies": {
-    "@uniweb/build": "~1.3.5",
+    "@uniweb/build": "~1.3.7",
     "@uniweb/content-reader": "~1.4.0",
     "@uniweb/semantic-parser": "~1.8.1"
   },

package/partials/agents.md

@@ -2517,15 +2517,17 @@ component that never needed one.
 ### Reading
 
 ```jsx
-const { status, records } = useRecords({ schema: '@acme/track' })   // summaries: record.brief, no items
-const { entity } = useEntity({ schema: '@acme/track', uuid: record.uuid })
+const { status, records } = useRecords({ schema: '@/track' })   // summaries: record.brief, no items
+const { entity } = useEntity({ schema: '@/track', uuid: record.uuid })
 const sessions = entity?.hydrated?.items.filter((item) => item.section === 'sessions')
 ```
 
-⛔ **Name a type by its full name, `@scope/name`** — the scope your foundation registered
-under (`@acme/track`). `@/track` is right in `meta.js` and `queries.yml`, where the build and
-`push` qualify it for you, but a `schema` you hand `@uniweb/api` goes to the backend as written,
-and the backend matches the exact name: `@/track` is a `404`.
+⭐ **Name your foundation's own types `@/track`**, as `meta.js` and `queries.yml` do. A built
+foundation sends one in the scope in its name — `@acme/track` for `@acme/marketing`, the name
+`register` stored it under — and `uniweb dev` sends it as written, which is how your mock's
+seed names it. Name any other type in full (`@std/person`). Real-backend testing is a job for a
+built foundation. Outside a Uniweb build nothing knows your scope, so `@/track` is refused
+before anything is sent (`kind: 'invalid'`).
 
 ⛔ **What a member wrote is text.** Render a field as `{record.brief.name}` or `<PlainText text={…} />` — never `<P text>`, `<H1>`–`<H6>` or `SafeHtml`, which render HTML: a member who typed `<img src=x onerror=…>` would run it as whoever views the page. A rich-text field (a ProseMirror document) renders through kit's `Render`, which escapes its text.
 
@@ -2545,7 +2547,7 @@ for the first tells a visitor their content is gone when it was never requested.
 ### Writing
 
 ```jsx
-const writer = useEntityWriter({ schema: '@acme/track', uuid: track.uuid })
+const writer = useEntityWriter({ schema: '@/track', uuid: track.uuid })
 
 await writer.create({ title: 'Keynote' }, { section: 'sessions', position: 'last' })
 await writer.update(itemId, { ...item.data, room: 'Hall A' })   // whole-data replace
@@ -2747,7 +2749,8 @@ server's terminal, its link on your site's root — follow it to try your page.
 `offers: [{ email, invitations: 1 }]` to try an invitation: mailed to an address no
 account holds, or waiting at once for the seeded account whose address it is. A seeded
 entity takes `grants: { member: 'read' }`, and `units: [{ handle, parent?, members, floor? }]`
-gives a create somewhere to land. State is in memory; restart to reset.
+gives a create somewhere to land. A seed names your own types `@/track`, as `uniweb dev` sends
+them, and any other in full; it matches a name exactly. State is in memory; restart to reset.
 
 `uniweb create my-event --template conference` is a worked example of all of this.
 
@@ -2973,7 +2976,7 @@ uniweb build                   # merges translations, emits dist/es/, dist/fr/
 
 Running `extract` before a build is the usual first mistake — it reads the compiled content, so a stale build yields a stale manifest. After content changes, `uniweb i18n sync` updates the manifest and `init` refreshes the language files; `status` and `audit` report coverage and stale entries.
 
-**A value is inline Markdown.** A sentence's links and bold go into its translation — `"Voir [Rôles](page:docs/roles)."` — or it renders without them, and coverage still counts it; `uniweb i18n status` lists these under *Loses markup*. A **button** — a line that is only a link — is the exception: translate its label alone and it keeps its link and options (`{role=primary}`). Buttons on consecutive lines are one string; give one label per line (`"Créer un groupe\nEn savoir plus"`).
+**A value is inline Markdown.** A sentence's links and bold go into its translation — `"Voir [Rôles](page:docs/roles)."` — or it renders without them, and coverage still counts it; `uniweb i18n status` lists these under *Loses markup*. A **button** — a line that is only a link — is the exception: translate its label alone and it keeps its link and options (`{role=primary}`). Buttons on consecutive lines are one string; give one label per line (`"Créer un groupe\nEn savoir plus"`). The same words are one string wherever they appear: where their places differ — a heading here, a link there — the manifest marks it `markupVaries`, `init` seeds the plain words, and the words alone are what to write: a link or button keeps its own target, and a link written into the value goes to every place the string appears.
 
 **Two mechanisms.** *Hash-based strings* (the default) — `locales/{locale}.json` maps content hash → translation, so structure stays identical across languages. When one source string needs different translations depending on where it appears, the value takes an override form:
 

package/src/commands/i18n.js

@@ -384,12 +384,23 @@ async function runExtract(siteRoot, config, args) {
  * translation value as inline markdown, so the value channel was lossless the whole
  * time — only the prompt was lossy. Measured 2026-09-18, @uniweb/build 0.44.4.
  *
+ * ⭐ Except where the unit's places disagree on markup (`markupVaries`, written by
+ * `@uniweb/build`'s extraction): one value serves every place, so such a unit starts
+ * with its plain words — which a plain place takes as they are, and a link or a button
+ * takes as its label, keeping its own target. ⛔ Until 2026-10-16 it started with the
+ * markup of whichever place had some, so an untouched file turned a header's heading
+ * into a link. A manifest from an extraction before that has no `markupVaries`, and
+ * seeds as it did.
+ *
  * ⚠️ This fills MISSING keys only. A locale file already seeded from the flat source
  * is not repaired by re-running; use `uniweb i18n generate <locale> --force` against
  * a freshly extracted manifest to get the markup-bearing source back.
+ *
+ * @param {{ source: string, markup?: string, markupVaries?: boolean }} unit - a manifest unit
+ * @returns {string}
  */
-function starterValue(unit) {
-  return unit.markup || unit.source
+export function starterValue(unit) {
+  return unit.markupVaries ? unit.source : unit.markup || unit.source
 }
 
 /**

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-16T22:49:32.412Z",
+  "generatedAt": "2026-10-17T13:42:01.369Z",
   "packages": {
     "@uniweb/api": {
-      "version": "1.2.5"
+      "version": "1.4.0"
     },
     "@uniweb/build": {
-      "version": "1.3.5"
+      "version": "1.3.7"
     },
     "@uniweb/content-reader": {
       "version": "1.4.0"
@@ -42,7 +42,7 @@
       "version": "1.0.1"
     },
     "@uniweb/schemas": {
-      "version": "1.3.0"
+      "version": "1.3.1"
     },
     "@uniweb/scholar": {
       "version": "1.1.0"