your-ai-workflow-firebase-os 1.2.41 → 1.2.44

package/README.md

@@ -31,7 +31,7 @@ That's it. **One component. Zero configuration files.**
 | 📋 **Templates** | Board (Kanban), Calendar, Table, Drive, Inline Form, Popup Form, Confirmation |
 | 🎨 **Theme Engine** | Full dark/light mode, custom accent colours, fonts, corner radii, logo |
 | 📁 **File Storage** | An admin-only Assets screen for public images, plus a drive preset any page can be built on |
-| 📬 **Forms** | Ask the AI for a form — it shows up in `/forms`, where the title, fields and button text are editable |
+| 📬 **Forms** | Created with their pages on `/pages` — say what a form should ask and the AI builds it with the page; see and hand-edit every form afterwards on `/forms` |
 | 📥 **Inbox** | Every form entry in one list at `/inbox`, filtered "From anyone" or "From signed-in users" |
 | 📖 **Guide** | A walkthrough at `/guide` with the sentences to paste into your assistant |
 | 📊 **Dashboard** | Personalised user dashboard |
@@ -67,7 +67,7 @@ Installing runs a postinstall step that patches the consumer project: it clears
 
 The package ships a Vite plugin, `yourAiFirebase()`, that puts the project's structure out of the assistant's reach. `src/App.tsx` and `src/main.tsx` are owned files: the plugin serves its own canonical source for both and rewrites them on disk whenever they differ, so an edit there has no effect. Pages, forms and content files are discovered from `src/your-ai-workflow-firebase-os/configs/` and `microcomponents/` through a virtual module, so a deleted registry import can no longer make a page vanish. And every discovered file is validated before the build: a config file with the wrong name, a `route` that is not one string starting with `/`, an address used twice, a `*Tab.config.ts` without a valid `pageType`, a missing `*Config` export, a `systemName` that does not match the file, or a content file with no default export fails the build with one sentence that names the fix. A hand-written `<form>` in a content file only warns — its entries would never reach the Inbox.
 
-Manual-first recipe: the owner adds the page on `/pages` (or the form on `/forms`) and then asks the assistant for the content, which is a single `microcomponents/<PascalCaseName>Content.tsx` file — no config file, no second address.
+Manual-first recipe: the owner adds the page — and its form, if it needs one — on `/pages` and then asks the assistant for the content, which is a single `microcomponents/<PascalCaseName>Content.tsx` file — no config file, no second address.
 
 ---
 
@@ -209,7 +209,7 @@ Your AI Firebase is built to be driven from an AI chat (Google AI Studio, Cursor
 
 **That file is the contract, and it is the only copy.** It is generated by [`scripts/postinstall.js`](scripts/postinstall.js) — read it there, and change it there. This README deliberately does not restate it, so the two can never disagree.
 
-The short version for a person evaluating the library: you ask for a page or a form in plain language, the assistant writes it, and it appears on the `/pages` or `/forms` screen where the basics — name, web address, icon, linked form, order, visibility — are yours to edit. Everything else is the assistant's job; ask it in chat.
+The short version for a person evaluating the library: you ask for a page or a form in plain language, the assistant writes it, and it appears on the `/pages` screen where the basics — name, web address, icon, order, visibility — are yours to edit. A form is created with its page there, and once built it also shows up on `/forms`, where you edit its title, questions and button text yourself. Everything else is the assistant's job; ask it in chat.
 
 ## 📐 CSS Isolation