your-ai-workflow-firebase-os 1.2.42 → 1.2.46

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** | A page gets its form right on `/pages` — say what it should ask and the AI builds it with the page |
+| 📬 **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 |
@@ -132,11 +132,12 @@ interface FirebaseOSProps {
   };
 
   /**
-   * Email addresses that are automatically assigned the 'admin' role once
-   * they have verified their email. Replaces the VITE_ADMIN_EMAILS env var.
-   * The same addresses have to be in the Firestore rules you pasted during
-   * setup — /setup writes them in for you — since the rules, not the client,
-   * are what actually grant the role.
+   * Optional. Who owns the app is decided by the Firestore rules alone: the
+   * /setup page has a bar where the owner types their address and generates
+   * rules that already name them, and the app simply asks Firebase for the
+   * role — the rules say yes to the listed addresses and no to everyone else.
+   * This prop only prefills that bar (handy for pre-configured installs);
+   * nothing requires it any more.
    */
   adminEmails?: string[];
 
@@ -209,7 +210,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` screen where the basics — name, web address, icon, 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