uniweb 0.80.8 → 0.81.1

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "0.80.8",
+  "version": "0.81.1",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -41,17 +41,17 @@
     "js-yaml": "^4.1.0",
     "prompts": "^2.4.2",
     "tar": "^7.0.0",
-    "@uniweb/core": "^0.35.4",
-    "@uniweb/runtime": "^0.28.9",
+    "@uniweb/runtime": "^0.28.10",
     "@uniweb/content-writer": "^0.3.4",
-    "@uniweb/schemas": "^0.10.1",
-    "@uniweb/kit": "^0.19.14",
+    "@uniweb/schemas": "^0.10.2",
+    "@uniweb/core": "^0.36.0",
+    "@uniweb/kit": "^0.19.15",
     "@uniweb/semantic-parser": "^1.5.1"
   },
   "peerDependencies": {
     "@uniweb/content-reader": "^1.2.8",
     "@uniweb/semantic-parser": "^1.5.1",
-    "@uniweb/build": "^0.74.4"
+    "@uniweb/build": "^0.75.0"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -1031,7 +1031,7 @@ import LessonHeader from '../../components/LessonHeader' // ❌ breaks if you re
 
 Within the same directory, use normal relative imports (`./AIFeedbackCard`).
 
-**Foundation entry (`main.js`).** A single `export default { … }` whose top-level keys are the foundation's identity — `name` (what it registers as, `@org/<name>`) and `description` — and the capabilities it provides — `defaultLayout`, `defaultSection`, `viewTransitions`, `props`, `defaultInsets`, `xref`, `outputs`, `handlers` — plus an optional named `vars` export. The capabilities are read at render; the one thing a foundation declares that *isn't* — which host services it supports — lives in `package.json` instead (see [Declaring what your foundation supports](#declaring-what-your-foundation-supports)). Section types and layouts are auto-discovered and merged in by `@uniweb/build`. The build wraps your default export under `default.capabilities` in `dist/entry.js`; you never write that wrapper. The one place it matters: when you import your **own** `main.js` from a component (e.g. a download button calling `compileDocument(website, { foundation })`), you get the bare default object — pass it through directly, Press handles both shapes.
+**Foundation entry (`main.js`).** A single `export default { … }` whose top-level keys are the foundation's identity — `name` (what it registers as, `@org/<name>`) and `description` — and the capabilities it provides — `defaultLayout`, `defaultSection`, `viewTransitions`, `defaultInsets`, `xref`, `outputs`, `handlers` — plus an optional named `vars` export. The capabilities are read at render; the one thing a foundation declares that *isn't* — which host services it supports — lives in `package.json` instead (see [Declaring what your foundation supports](#declaring-what-your-foundation-supports)). Section types and layouts are auto-discovered and merged in by `@uniweb/build`. The build carries into `default.capabilities` in `dist/entry.js` only what a published page reads of your default export — the code it calls (`handlers`, `defaultInsets`, `xref`, `transports`, `outputs`) and its data, lean (`defaultLayout`, `defaultSection`, `viewTransitions`, `scroll`, each var's `default`, `type` and `applyTo`, each `data:` key's schema ref). `name`, `description`, a var's label or description and any key the framework does not read stay out of the published bundle: they are for the editor, which reads them from the foundation's schema. You never write that wrapper. The file is `main.js` — never `main.jsx`, which the build refuses; `main.js` may hold JSX. The one place it matters: when you import your **own** `main.js` from a component (e.g. a download button calling `compileDocument(website, { foundation })`), you get the bare default object — pass it through directly, Press handles both shapes.
 
 ### Props interface
 
@@ -2726,8 +2726,8 @@ That freezes sites using your foundation on the recorded version. Only reach for
 ```yaml
 # site.yml
 defaultLanguage: en
-languages: [en, es, fr]        # or [{ code: es, label: Español }, …], or '*' to
-                               # auto-discover from the locales/ folder
+languages: [en, es, fr]        # codes only — a language's name comes from its code;
+                               # or '*' to auto-discover from the locales/ folder
 publishLanguages: [en, es]     # optional — fr stays a dev-previewable draft,
                                # excluded from production output entirely
 ```
@@ -2742,6 +2742,8 @@ 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"`).
+
 **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:
 
 ```json
@@ -2858,4 +2860,8 @@ Source repo (public, cloneable): **https://github.com/uniweb/docs** · any page
 | `development/` | Foundations, component patterns, project structures, data, layouts, i18n, migration, schemas |
 | `reference/` | site.yml, page.yml, content structure, meta.js, kit API, navigation, records, queries, data fetching, parametric pages, CLI, deployment |
 
-The by-task table is in Part 0. For CLI flags, prefer `uniweb <command> --help` over this file — it's always current.
+The by-task table is in Part 0. For CLI flags, prefer `uniweb <command> --help` over this file — it's always current.
+
+## Notes about this project
+
+Conventions, decisions, where things are — keep them in a file of your own (`NOTES.md`, say). `uniweb update` rewrites this file for each new version, and the one part it keeps is a block between `<!-- project-notes:start -->` and `<!-- project-notes:end -->`, each on a line of its own, which it moves to the end of the file. That block is the place for a line pointing to your notes, or for short notes themselves.

package/src/commands/update.js

@@ -47,7 +47,9 @@ import prompts from 'prompts'
 import { findWorkspaceRoot } from '../utils/workspace.js'
 import {
   readAgentsVersion,
-  generateAgentsContent
+  refreshAgentsContent,
+  PROJECT_NOTES_START,
+  PROJECT_NOTES_END
 } from '../utils/agents-stamp.js'
 import { getCliVersion } from '../versions.js'
 import { isNonInteractive } from '../utils/interactive.js'
@@ -775,9 +777,27 @@ async function refreshAgents(ctx) {
     return 'current'
   }
 
+  // The project's notes travel to the new file (`refreshAgentsContent`). Markers that do not pair
+  // up leave AGENTS.md as it is: where a block ends would be a guess, and a wrong one loses notes.
+  const refreshed = refreshAgentsContent(
+    existsSync(agentsPath) ? readFileSync(agentsPath, 'utf8') : null
+  )
+  if (refreshed.error) {
+    warn(`AGENTS.md left as it is: ${refreshed.error}.`)
+    log(
+      `${colors.dim}Your project notes are kept between ${PROJECT_NOTES_START} and ${PROJECT_NOTES_END}, each on a line of its own. Fix the markers, then re-run${colors.reset} ${colors.cyan}uniweb update${colors.reset}${colors.dim}.${colors.reset}`
+    )
+    log('')
+    if (agentsOnly) process.exit(1)
+    return 'skipped'
+  }
+  const keeping = refreshed.kept
+    ? `, keeping ${refreshed.kept === 1 ? 'its project notes' : `its ${refreshed.kept} project-notes blocks`}`
+    : ''
+
   if (dryRun) {
     info(
-      `Dry-run: would ${currentAgentsVersion ? `update AGENTS.md (v${currentAgentsVersion} → v${cliVersion})` : `create AGENTS.md (v${cliVersion})`}.`
+      `Dry-run: would ${currentAgentsVersion ? `update AGENTS.md (v${currentAgentsVersion} → v${cliVersion})` : `create AGENTS.md (v${cliVersion})`}${keeping}.`
     )
     return 'skipped'
   }
@@ -798,9 +818,9 @@ async function refreshAgents(ctx) {
     }
   }
 
-  writeFileSync(agentsPath, generateAgentsContent())
+  writeFileSync(agentsPath, refreshed.content)
   if (currentAgentsVersion) {
-    success(`Updated AGENTS.md (v${currentAgentsVersion} → v${cliVersion}).`)
+    success(`Updated AGENTS.md (v${currentAgentsVersion} → v${cliVersion})${keeping}.`)
     return 'updated'
   }
   success(`Created AGENTS.md (v${cliVersion}).`)

package/src/framework-index.json

@@ -1,16 +1,16 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-01T14:16:42.270Z",
+  "generatedAt": "2026-10-02T03:03:06.390Z",
   "packages": {
     "@uniweb/api": {
-      "version": "0.6.8",
+      "version": "0.6.9",
       "path": "framework/api",
       "deps": [
         "@uniweb/core"
       ]
     },
     "@uniweb/build": {
-      "version": "0.74.4",
+      "version": "0.75.0",
       "path": "framework/build",
       "deps": [
         "@uniweb/content-reader",
@@ -35,7 +35,7 @@
       "deps": []
     },
     "@uniweb/core": {
-      "version": "0.35.4",
+      "version": "0.36.0",
       "path": "framework/core",
       "deps": [
         "@uniweb/semantic-parser",
@@ -48,14 +48,14 @@
       "deps": []
     },
     "@uniweb/icons": {
-      "version": "0.4.26",
+      "version": "0.4.27",
       "path": "framework/icons",
       "deps": [
         "@uniweb/core"
       ]
     },
     "@uniweb/kit": {
-      "version": "0.19.14",
+      "version": "0.19.15",
       "path": "framework/kit",
       "deps": [
         "@uniweb/core",
@@ -76,7 +76,7 @@
       "deps": []
     },
     "@uniweb/projections": {
-      "version": "0.7.12",
+      "version": "0.7.13",
       "path": "framework/projections",
       "deps": [
         "@uniweb/content-writer",
@@ -84,7 +84,7 @@
       ]
     },
     "@uniweb/runtime": {
-      "version": "0.28.9",
+      "version": "0.28.10",
       "path": "framework/runtime",
       "deps": [
         "@uniweb/core",
@@ -97,7 +97,7 @@
       "deps": []
     },
     "@uniweb/schemas": {
-      "version": "0.10.1",
+      "version": "0.10.2",
       "path": "framework/schemas",
       "deps": []
     },
@@ -117,7 +117,7 @@
       "deps": []
     },
     "@uniweb/templates": {
-      "version": "0.17.10",
+      "version": "0.17.11",
       "path": "framework/templates",
       "deps": []
     },
@@ -127,7 +127,7 @@
       "deps": []
     },
     "@uniweb/unipress": {
-      "version": "0.10.17",
+      "version": "0.10.19",
       "path": "framework/unipress",
       "deps": [
         "@uniweb/build",

package/src/utils/agents-stamp.js

@@ -39,3 +39,72 @@ export function generateAgentsContent() {
   const agentsContent = readFileSync(join(partialsDir, 'agents.md'), 'utf8')
   return `<!-- uniweb-agents v${getCliVersion()} -->\n${agentsContent}\n`
 }
+
+/**
+ * ⭐ THE ONE PART OF AGENTS.md A PROJECT KEEPS: its project-notes blocks. `update` rewrites the
+ * file from this CLI's partial, so a note written anywhere else in it is lost on the next version.
+ * A block runs from a `<!-- project-notes:start -->` line to a `<!-- project-notes:end -->` line,
+ * and is carried over verbatim, at the end of the new file. ⛔ Until 2026-10-01 nothing was kept.
+ *
+ * A marker is a line of its own, outside a code fence — so the partial can name the markers in a
+ * sentence without its own text being taken for a block.
+ */
+export const PROJECT_NOTES_START = '<!-- project-notes:start -->'
+export const PROJECT_NOTES_END = '<!-- project-notes:end -->'
+
+const MARKER_LINE = /^<!--\s*project-notes:(start|end)\s*-->$/
+const FENCE_LINE = /^(`{3,}|~{3,})/
+
+/**
+ * The project-notes blocks of an AGENTS.md, in order, each from its start line to its end line.
+ *
+ * @param {string} text
+ * @returns {{ blocks: string[] } | { error: string }} an error when the markers do not pair up —
+ *   where a block ends would be a guess, and a wrong one loses notes
+ */
+export function readProjectNotes(text) {
+  const blocks = []
+  let block = null
+  let fence = null
+  let lineNumber = 0
+  for (const line of String(text ?? '').split(/(?<=\n)/)) {
+    lineNumber++
+    const trimmed = line.trim()
+    const fenceMark = trimmed.match(FENCE_LINE)?.[1]
+    if (fenceMark && (!fence || fenceMark.startsWith(fence))) fence = fence ? null : fenceMark
+    const marker = !fence && !fenceMark ? trimmed.match(MARKER_LINE)?.[1] : null
+
+    if (marker === 'start') {
+      if (block) return { error: `a second ${PROJECT_NOTES_START} on line ${lineNumber}, before the first one's ${PROJECT_NOTES_END}` }
+      block = [line]
+    } else if (marker === 'end') {
+      if (!block) return { error: `${PROJECT_NOTES_END} on line ${lineNumber} has no ${PROJECT_NOTES_START} before it` }
+      block.push(line)
+      blocks.push(block.join('').replace(/\s+$/, ''))
+      block = null
+    } else if (block) {
+      block.push(line)
+    }
+  }
+  if (block) return { error: `${PROJECT_NOTES_START} has no ${PROJECT_NOTES_END} after it` }
+  return { blocks }
+}
+
+/**
+ * AGENTS.md as `update` writes it: this CLI's partial, stamped, and the project-notes blocks of the
+ * file it replaces after it.
+ *
+ * @param {string|null} existing - the current AGENTS.md, or null when there is none
+ * @returns {{ content: string, kept: number } | { error: string }}
+ */
+export function refreshAgentsContent(existing) {
+  const fresh = generateAgentsContent()
+  if (existing == null) return { content: fresh, kept: 0 }
+  const notes = readProjectNotes(existing)
+  if (notes.error) return notes
+  if (!notes.blocks.length) return { content: fresh, kept: 0 }
+  return {
+    content: `${fresh.replace(/\s+$/, '')}\n\n${notes.blocks.join('\n\n')}\n`,
+    kept: notes.blocks.length,
+  }
+}

package/templates/foundation/main.js.hbs

@@ -1,5 +1,4 @@
 // Foundation Configuration
-// Schema: schemas/foundation.schema.json
 //
 // ─── CSS Custom Properties ──────────────────────────────────────────────────────
 // Export `vars` to declare CSS custom properties that sites can override in theme.yml:
@@ -30,9 +29,5 @@ export default {
   // ─── Layout ─────────────────────────────────────────────────────────────────
   // Create layouts in layouts/MyLayout/index.jsx (auto-discovered).
   // defaultLayout: 'MyLayout',
-
-  // ─── Props ──────────────────────────────────────────────────────────────────
-  // Foundation-wide data accessible via website.foundationProps in components.
-  // props: {},
 }
 {{/if}}

package/templates/workspace/README.md.hbs

@@ -11,7 +11,7 @@ A website built with [Uniweb](https://github.com/uniweb/cli) — a component web
 ├── src/                 # Foundation package (the site's source code; pkg name: src)
 │   ├── sections/        # Section types (selectable by content authors)
 │   ├── styles.css       # Tailwind CSS v4 theme
-│   ├── main.js          # Foundation declarations (vars, defaultLayout, props)
+│   ├── main.js          # Foundation declarations (name, vars, defaultLayout)
 │   └── vite.config.js   # defineFoundationConfig()
 │
 ├── site/                # Content (markdown)