uniweb 1.7.0 → 1.7.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.7.0",
+  "version": "1.7.1",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,15 +41,15 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/content-writer": "~1.1.2",
     "@uniweb/core": "~1.2.2",
+    "@uniweb/semantic-parser": "~1.8.1",
     "@uniweb/schemas": "~1.3.0",
-    "@uniweb/semantic-parser": "~1.8.1"
+    "@uniweb/content-writer": "~1.1.2"
   },
   "peerDependencies": {
-    "@uniweb/build": "~1.3.5",
+    "@uniweb/semantic-parser": "~1.8.1",
     "@uniweb/content-reader": "~1.4.0",
-    "@uniweb/semantic-parser": "~1.8.1"
+    "@uniweb/build": "~1.3.6"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -2525,7 +2525,8 @@ const sessions = entity?.hydrated?.items.filter((item) => item.section === 'sess
 ⛔ **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`.
+and the backend matches the exact name — so the package refuses `@/track` before sending it
+(`kind: 'invalid'`), and its mock refuses a seed that names one.
 
 ⛔ **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.
 
@@ -2692,7 +2693,7 @@ it, and takes it back. An instructor enrolling students in a course is this; nam
 your solution does ("enrolled", "course staff"):
 
 ```jsx
-const { status, grants, grant, revoke, working } = useAccess({ schema: '@/course', uuid: course.uuid })
+const { status, grants, grant, revoke, working } = useAccess({ schema: '@acme/course', uuid: course.uuid })
 // status 'ready' for whoever administers it; 'forbidden' for everyone else — draw nothing
 // grants: [{ account_id, permission, account: { handle, uuid, … }, … }]
 await grant({ handle: 'sam' }, 'read')     // or an account id: a candidate, a grant's account, an owner_id
@@ -2716,7 +2717,7 @@ viewer is placed in:
 
 ```jsx
 const { units } = useUnits()               // [{ unit, id, handle?, name?, parent?, depth, primary }]
-await createEntity({ schema: '@/submission', unit: course.unit, items: [...] })
+await createEntity({ schema: '@acme/submission', unit: course.unit, items: [...] })
 ```
 
 Landing decides where an entry is, not who may open it.
@@ -2973,7 +2974,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"`). A link belongs to the place whose source has one: the same words are one string wherever they appear, so where they appear without a link — a heading, a page title, a data block's plain string — the translation's link is left off and its words kept.
 
 **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/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-16T22:49:32.412Z",
+  "generatedAt": "2026-10-17T02:22:18.325Z",
   "packages": {
     "@uniweb/api": {
-      "version": "1.2.5"
+      "version": "1.3.0"
     },
     "@uniweb/build": {
-      "version": "1.3.5"
+      "version": "1.3.6"
     },
     "@uniweb/content-reader": {
       "version": "1.4.0"