@uniweb/build 0.44.3 → 0.44.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uniweb/build",
-  "version": "0.44.3",
+  "version": "0.44.4",
   "description": "Build tooling for the Uniweb Component Web Platform",
   "type": "module",
   "exports": {
@@ -57,15 +57,15 @@
     "js-yaml": "^4.1.0",
     "sharp": "^0.35.3",
     "yaml": "^2.5.0",
-    "@uniweb/schemas": "^0.2.13",
-    "@uniweb/content-reader": "^1.2.4",
+    "@uniweb/content-writer": "^0.3.4",
     "@uniweb/projections": "^0.6.0",
+    "@uniweb/schemas": "^0.2.13",
+    "@uniweb/semantic-parser": "^1.4.0",
     "@uniweb/theming": "^0.1.15",
-    "@uniweb/content-writer": "^0.3.4",
-    "@uniweb/semantic-parser": "^1.4.0"
+    "@uniweb/content-reader": "^1.2.4"
   },
   "optionalDependencies": {
-    "@uniweb/runtime": "^0.19.4"
+    "@uniweb/runtime": "^0.19.5"
   },
   "peerDependencies": {
     "vite": "^5.0.0 || ^6.0.0 || ^7.0.0",
@@ -74,7 +74,7 @@
     "@tailwindcss/vite": "^4.0.0",
     "@vitejs/plugin-react": "^4.0.0 || ^5.0.0",
     "vite-plugin-svgr": "^4.0.0",
-    "@uniweb/core": "^0.24.3"
+    "@uniweb/core": "^0.24.4"
   },
   "peerDependenciesMeta": {
     "vite": {

package/src/site/content-collector.js

@@ -84,7 +84,7 @@ function warnRetiredFetcherKeys(fetcher) {
       `[uniweb] site.yml fetcher: ${retired.map((k) => `\`${k}\``).join(', ')} ` +
         `${retired.length === 1 ? 'is' : 'are'} retired and ignored. The default fetcher reads a ` +
         `site's own files and a host's records lane; a backend of your own is reached through a ` +
-        `foundation transport (docs: development/connecting-a-backend.md). Kept: ` +
+        `foundation transport (docs: development/data-sources.md). Kept: ` +
         `\`fetcher.transports\` and a transport's own binding config.`
     )
   }

package/src/uwx/site.js

@@ -1212,16 +1212,18 @@ export async function siteProjectToDocument(siteRoot, opts = {}) {
   // a bug fix.
   //
   // ⭐ `api` is the one service a site does not AUTHOR. It is a real backend that is
-  // provisioned and paid for, so its address is the host's to supply — it arrives as
+  // provisioned, so its address is the host's to supply — it arrives as
   // `config.services.api` and `@uniweb/api` reads it there (`resolveBase`). An
-  // authored `api:` is the SITE tier, which outranks the host permanently.
+  // authored `api:` is the SITE tier: it yields to a host that offers the service,
+  // and is the answer wherever one does not.
   //
-  // ⇒ Carrying it would turn a local-dev override into a production one the moment
-  // someone pushed: the host would store `info.api` and serve it back as `config.api`,
-  // which wins over the address of the backend the site actually has. The vanish on
-  // this lane is the correct behaviour, not the bug the comments above describe —
-  // there, a dropped block leaves a site with NO endpoint; here it leaves the site
-  // with the RIGHT one.
+  // ⇒ Carrying it would turn a local-dev address into a production one the moment
+  // someone pushed: the host would store `settings.api` and serve it back as
+  // `config.api`, and a site with no `api` service of its own would draw sign-in
+  // against an address nobody answers — where the absence would have drawn
+  // nothing. The vanish on this lane is the correct behaviour, not the bug the
+  // comments above describe — there, a dropped block leaves a site with NO
+  // endpoint; here it leaves the site with the RIGHT answer.
   //
   // The provisioned record rides the `$services` section instead (see servicesNested).
   // ⭐ DESUGARED, like every other tier. `data:` is the shorthand for `fetch:`