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

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "your-ai-workflow-firebase-os",
-  "version": "1.2.46",
+  "version": "1.2.49",
   "description": "Your AI Firebase — a complete Firebase-powered admin app in one React component.",
   "type": "module",
   "main": "dist/your-ai-workflow-firebase-os.cjs.js",

package/scripts/postinstall.js

@@ -863,12 +863,20 @@ Field \`type\` must be one of: \`text\`, \`email\`, \`tel\` (phone / WhatsApp,
 renders a country-code picker), \`textarea\`, \`number\`, \`date\` (renders a
 calendar picker; the answer is stored as \`YYYY-MM-DD\`), \`select\` (needs
 \`options\`: a list of plain strings), \`checkbox\`, \`currency\` (optional
-\`currencySymbol\`, default \`$\`), \`age\`. Any other value renders nothing.
+\`currencySymbol\`, default \`$\`), \`age\`, \`file\` (the person attaches a file —
+it uploads as they pick it, and the Inbox entry links to it; optional
+\`accept\`, e.g. \`'image/*'\` or \`'.pdf,.doc,.docx'\`). Any other value renders
+nothing.
 
 A day is always a \`date\` field — booking day, preferred date, start date,
 deadline, date of birth, appointment. NEVER a \`text\` field asking people to
 type a date, and never three questions for day, month and year.
 
+An attachment is always a \`file\` field — CV, photo, receipt, screenshot,
+"send us your logo". It works on public and private forms alike; NEVER ask
+people to paste a link to their file instead, and never write your own upload
+code for a form.
+
 Money is always a \`currency\` field (budget, price, cost, fee), never
 \`number\`. When the owner names a currency — "in euros", "GBP", "₹" — set
 \`currencySymbol\` to it (\`'€'\`, \`'£'\`, \`'₹'\`); otherwise leave the default \`$\`.

package/src/index.css

@@ -197,6 +197,17 @@ h3,
   }
 }
 
+/* Before PageTitle existed, a page title was
+   `text-3xl md:text-4xl lg:text-5xl`, and of the weight rules above it was
+   .text-3xl/.text-4xl — same !important, written later — that won at every
+   width. So the title has always rendered at the h2 weight; a bare h1 now
+   reaches the heavier --weight-h1 instead, which is the whole of the "the
+   titles look different" change. Unlayered and more specific than the `h1`
+   rule, so it wins without depending on layer order. */
+.page-title {
+  font-weight: var(--weight-h2, 700) !important;
+}
+
 @layer utilities {
   .glass-panel {
     background: var(--panel-bg);
@@ -235,6 +246,30 @@ h3,
       0 2px 6px rgba(24, 16, 64, 0.07);
   }
 
+  /* A form card. It holds questions people must read and boxes they must
+     fill, so it cannot be the 5% .glass-panel wash — over a photo or a busy
+     page the labels dissolved into whatever sat behind them. Not as solid as
+     .glass-popover either: a form sits IN the page, not over it, so a little
+     of the ground still comes through. Defined below FBOS:THEME-END so it
+     ships compiled and existing installs pick it up without a theme.css
+     change. */
+  .glass-form {
+    background: color-mix(in srgb, var(--bg-color) 82%, transparent);
+    backdrop-filter: blur(24px) saturate(160%);
+    -webkit-backdrop-filter: blur(24px) saturate(160%);
+    border: 1px solid var(--panel-border);
+    transition: all 0.4s cubic-bezier(0.4, 0, 0.2, 1);
+  }
+
+  [data-theme='light'] .glass-form {
+    background: color-mix(in srgb, var(--bg-color) 88%, transparent);
+  }
+
+  .glass-form:hover {
+    border-color: var(--accent-color);
+    box-shadow: 0 8px 30px var(--glow-color, var(--primary-glow));
+  }
+
   /* An open drop-down. Deliberately NOT .glow-focus: the 25px halo read as a
      spotlight on what is just a list being open, and it was sliced off by any
      panel animating its height nearby. An inset ring cannot be clipped. */
@@ -435,6 +470,36 @@ h3,
     background-image: var(--text-gradient);
   }
 
+  /* The page-title h1 (components/PageTitle.tsx). Fluid on a phone — the
+     component shrinks a long title to fit the line and only sets data-fold
+     when even the floor size cannot hold it — but from md up the sizes are
+     the pre-PageTitle breakpoint steps (36px/48px), so desktop looks exactly
+     as it always did. No .text-2xl/.text-3xl here on purpose: those classes
+     carry weight rules that would fight these sizes — the weight comes from
+     the unlayered .page-title rule further up, which pins the h2 weight the
+     title has always rendered at. */
+  .page-title {
+    font-size: clamp(1.5rem, 1.05rem + 1.9vw, 2.25rem);
+    line-height: 1.2;
+    white-space: nowrap;
+  }
+
+  /* The line heights are the old text-4xl / text-5xl ones, not a single
+     ratio: at 48px a 1.2 line box stands ~10px taller than the title always
+     did and pushes the route row down with it. */
+  @media (min-width: 768px) {
+    .page-title { font-size: 2.25rem; line-height: 2.5rem; }
+  }
+
+  @media (min-width: 1024px) {
+    .page-title { font-size: 3rem; line-height: 1; }
+  }
+
+  .page-title[data-fold] {
+    white-space: normal;
+    text-wrap: balance;
+  }
+
   .accent-gradient {
     background: linear-gradient(135deg, #6d28d9 0%, #a78bfa 100%);
   }

package/src/pages/Home.tsx

@@ -32,7 +32,7 @@ export function Home() {
         </motion.div>
 
         <motion.h1
-          className="text-5xl sm:text-6xl md:text-7xl lg:text-[5.5rem] font-extrabold tracking-tight mb-6 md:mb-8 text-gradient animate-float leading-[1.1] md:leading-[1.15] px-2"
+          className="text-4xl sm:text-5xl md:text-6xl lg:text-[4.5rem] font-extrabold tracking-tight mb-6 md:mb-8 text-gradient animate-float leading-[1.1] md:leading-[1.15] px-2"
         >
           Your AI Firebase
         </motion.h1>