uniweb 1.21.4 → 1.21.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.21.4",
+  "version": "1.21.5",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -42,14 +42,14 @@
     "prompts": "^2.4.2",
     "tar": "^7.5.21",
     "@uniweb/content-writer": "~1.3.1",
-    "@uniweb/core": "~1.4.7",
+    "@uniweb/schemas": "~1.6.5",
     "@uniweb/semantic-parser": "~1.13.0",
-    "@uniweb/schemas": "~1.6.5"
+    "@uniweb/core": "~1.4.7"
   },
   "peerDependencies": {
-    "@uniweb/content-reader": "~1.5.7",
+    "@uniweb/build": "~1.10.5",
     "@uniweb/semantic-parser": "~1.13.0",
-    "@uniweb/build": "~1.10.5"
+    "@uniweb/content-reader": "~1.5.7"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -67,7 +67,7 @@ https://uniweb.io/llms.txt
 
 It lists every documentation page with a one-line description and a fetchable link. Go there whenever your question isn't answered in this file — and *especially* when you don't know whether a feature exists at all. That's where guessing does the most damage: **a 404 on a path you invented tells you your guess was wrong, not that the feature is missing.** Concluding "the framework doesn't support X" from a failed fetch is a mistake worth actively guarding against; the index answers the existence question directly.
 
-Then **follow the link the index gives you** rather than constructing one yourself. The index is the source of truth for where pages live, so it stays correct when the site's URL conventions change. (Pages also serve markdown to any client that sends `Accept: text/markdown`.)
+Then **follow the link the index gives you** rather than constructing one yourself. The index is the source of truth for where pages live, so it stays correct when the site's URL conventions change. Each link it gives is the page as Markdown.
 
 **Clone the repo instead** when you expect several lookups, or may lose network access later:
 

package/src/commands/status.js

@@ -368,7 +368,7 @@ async function gitChecks(siteDir, { offline, origin }) {
       state: 'attention',
       summary: `${count(n, 'other file')} here ${n === 1 ? 'is' : 'are'} not committed — a push sends only the site's content, and your team builds what git holds.`,
       files: others,
-      lines: ofFoundation ? ["The foundation's source is among them: the next push or publish releases it from these files, so commit them first."] : []
+      lines: ofFoundation ? ["The foundation's files are among them: when a push or publish releases it, it is built from these files as they are, so commit them first."] : []
     })
     proposals.push({ step: 'commit', command: null, why: `commit the ${count(n, 'other file')} here: \`git add\` ${n === 1 ? 'it' : 'them'}, then \`git commit -m "<what changed>"\``, ask: true })
   } else if (others) {