uniweb 1.21.13 → 1.21.14

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "uniweb",
-  "version": "1.21.13",
+  "version": "1.21.14",
   "description": "Create structured Vite + React sites with content/code separation",
   "type": "module",
   "bin": {
@@ -47,9 +47,9 @@
     "@uniweb/schemas": "~1.6.5"
   },
   "peerDependencies": {
-    "@uniweb/build": "~1.10.9",
-    "@uniweb/semantic-parser": "~1.13.0",
-    "@uniweb/content-reader": "~1.5.7"
+    "@uniweb/build": "~1.10.10",
+    "@uniweb/content-reader": "~1.5.7",
+    "@uniweb/semantic-parser": "~1.13.0"
   },
   "peerDependenciesMeta": {
     "@uniweb/build": {

package/partials/agents.md

@@ -592,14 +592,14 @@ Fenced code serves three purposes depending on its info string: `yaml:`/`json:`
 
 ````markdown
 ```yaml:form
-fields:
-  - name: email
-    type: email
-submitLabel: Send
+- name: email
+  type: string
+  format: email
+  label: Email
 ```
 ````
 
-→ `content.data?.form` = `{ fields: [...], submitLabel: "Send" }`, when the component declares `data: { form: … }`. A block under a key the component does not declare stays out of `content.data` (the dev console says so) and is still in `content.sequence`. A block inside an item is that item's (`content.items[n].data`) and needs no declaration.
+→ `content.data?.form` = `[{ name: "email", type: "string", format: "email", label: "Email" }]`, when the component declares `data: { form: … }`. A block under a key the component does not declare stays out of `content.data` (the dev console says so) and is still in `content.sequence`. A block inside an item is that item's (`content.items[n].data`) and needs no declaration.
 
 **Code snippets** — display content with a language for syntax highlighting, collected in `content.snippets` as `[{ language, code }]`. Filter with `content.snippets.filter(s => s.language === 'css')`.
 
@@ -2074,6 +2074,10 @@ A form gets its destination from the first of these that applies:
 3. **Neither** — there is no destination: render no form, or fall back to contact
    details the site already carries.
 
+In `uniweb dev` the dev server is the host: `submit: true` is answered there, so a form shows and
+can be sent while you work. Each submission is printed in the terminal and kept in the site's
+`.uniweb/dev-submissions/` — read it there to see exactly what an endpoint would receive.
+
 That is the general arrangement, not a forms-only one. A host states everything
 it offers in the served payload's `config.services`, keyed by name, and every service
 resolves by the same rule — the host's offer, then the site's own address, then

package/src/framework-index.json

@@ -1,12 +1,12 @@
 {
   "schemaVersion": 1,
-  "generatedAt": "2026-10-27T19:36:44.502Z",
+  "generatedAt": "2026-10-27T20:03:17.272Z",
   "packages": {
     "@uniweb/api": {
       "version": "1.6.4"
     },
     "@uniweb/build": {
-      "version": "1.10.9"
+      "version": "1.10.10"
     },
     "@uniweb/content-reader": {
       "version": "1.5.7"