fimo 2.2.0-staging.13 → 2.2.0-staging.14

package/assets/skills/fimo-code/references/frameworks/next/locales.md

@@ -35,7 +35,7 @@ When labels are not needed at that boundary, use `<FimoProvider locale={locale}>
 
 ## New-project boundary
 
-Choose the primary locale from the user's request before building pages. Put the first explicitly requested locale in `.fimo/config.json#i18n.defaultLocale` and keep all requested locales in `i18n.locales`. That is content and provider configuration: `src/locales.ts` reads the file, so the default locale passed to `FimoProvider` and the `<html lang>` follow it. It does not create locale URLs. If the user gives no locale signal, keep `en` and state that choice. Never add `NEXT_PUBLIC_FIMO_DEFAULT_LOCALE` or `FIMO_DEFAULT_LOCALE`; the runtime ignores them by design.
+Choose the primary locale from the user's request before building pages. Configure the supported locales and default through the `fimo-cli` locale workflow. `src/locales.ts` reads the synchronized config, so the default locale passed to `FimoProvider` and the `<html lang>` follow it. It does not create locale URLs. If the user gives no locale signal, keep `en` and state that choice. Never add `NEXT_PUBLIC_FIMO_DEFAULT_LOCALE` or `FIMO_DEFAULT_LOCALE`; the runtime ignores them by design.
 
 The starter is default-only: one ordinary root layout renders `<html lang={defaultLocale}>` and `FimoProvider`, `/` is the homepage, and unknown paths get Next's native 404. Implement a locale routing strategy only when the product asks for one — prefixed `[locale]` segments, middleware, cookies, domains, or an i18n library are all Next decisions — then resolve the locale in that strategy and pass it into Fimo server reads and `FimoProvider`. Do not install a top-level `[locale]` route or an optional catch-all speculatively: it captures `/favicon.ico` and every unknown top-level path, and Fimo never requires it.
 
@@ -45,7 +45,7 @@ When the app implements a localized URL shape, describe it in `.fimo/config.json
 
 With `next-i18next`, keep its routing and translation provider for the strings it owns. Pass the same resolved locale to Fimo; do not replace the library or duplicate its route structure.
 
-Before creating non-default Fimo labels or content variants, confirm that those locales are enabled for the linked Fimo project. Load `fimo-cli` with its `locales` reference and run `fimo locales add <locale> --yes --json`; `.fimo/config.json` documents the application's locale policy, but `fimo validate` does not add project locales.
+Before creating non-default Fimo labels or content variants, confirm that those locales are enabled for the linked Fimo project. Load `fimo-cli` with its `locales` reference and run `fimo locales add <locale> --yes --json`; `fimo validate` does not add project locales.
 
 ## Ownership boundary
 

package/assets/skills/fimo-code/references/locales.md

@@ -13,11 +13,13 @@ The application owns locale resolution and routing. Fimo consumes the resolved l
 }
 ```
 
-For new projects, derive the primary locale from the request; when several are explicit, the first one named is the default. Update `i18n.defaultLocale`, `i18n.locales`, the document language default, and any framework-native locale route boundary or matcher the application implements. If the user gives no locale signal, retain the starter default and state that choice.
+For a linked project, load `fimo-cli` with its `locales` reference and use the typed locale commands to change the supported locales or default. That reference owns the synchronization and recovery contract.
+
+For new projects, derive the primary locale from the request; when several are explicit, the first one named is the default. Configure that locale set through the lifecycle commands, then update the document language default and any framework-native locale route boundary or matcher the application implements. If the user gives no locale signal, retain the starter default and state that choice.
 
 Keep one locale unless the product asks for multilingual output. Keep it locale-ready without forcing `/en`, a language switcher, global path-prefix routing, or localized schemas. Locale tags should be structurally valid, such as `en`, `pt-BR`, or `zh-Hans`.
 
-For an already linked project, enable each locale in Fimo before writing non-default label or content variants. Load `fimo-cli` with its `locales` reference and run `fimo locales add <locale> --yes --json`; local config and `fimo validate` do not provision project locales. Do not change the application's route strategy to work around a missing locale.
+Enable each locale before writing non-default label or content variants. Run `fimo locales add <locale> --yes --json`; `fimo validate` does not provision project locales. Do not change the application's route strategy to work around a missing locale.
 
 ## Application responsibilities
 

package/assets/skills/fimo-studio/references/ai-chat.md

@@ -13,7 +13,7 @@ On desktop, the AI chat opens docked on the left by default. You can make it flo
 
 The AI can place choices, cards, tables, images, and contextual actions directly in its reply. Optional suggestions do not interrupt the conversation.
 
-When the AI needs an answer before it can continue, it shows a form in the chat and waits for your response. Complete the form for a structured answer, or reply normally in the chat to answer in your own words.
+When the AI needs an answer before it can continue, it pins a form directly above the message box and waits for your response. The form stays there while you scroll the conversation; the message that asked shows **Waiting for your answer...** in its place in the history. Select **Minimize** to fold the form to one line without losing your answers, then select that line to reopen it. **Submit** sends only the completed form and leaves anything typed in the message box unsent. Sending from the message box includes any selections already made in the form with your message; with no selections, it is an ordinary reply. A form with many steps scrolls inside its own area, and its **Next** / **Submit** buttons stay in view.
 
 ## Attaching Context
 
@@ -60,7 +60,6 @@ The AI runs on credits. You can see your balance by clicking the **coin icon** n
 
 Clicking it opens a breakdown showing:
 
-- **Daily free credits** that reset each day.
 - **Monthly credits** included with your plan.
 - **Purchased credits** you bought separately.
 - **Earned credits** from referrals or promotions.

package/assets/skills/fimo-studio/references/billing-and-credits.md

@@ -1,13 +1,12 @@
 ## Credit Types
 
-Fimo uses credits for AI-powered features. There are four kinds:
+Fimo uses credits for AI-powered features. There are three kinds:
 
-- **Daily free credits** -- a small pool that resets every day. Available on all plans, including free.
-- **Monthly credits** -- a larger pool that comes with your plan. Resets at the start of each billing cycle.
+- **Monthly credits** -- the pool that comes with your plan. Resets at the start of each billing cycle.
 - **Purchased credits** -- bought with real money. These do not expire and stay in your account until you use them.
 - **Awarded credits** -- gained through referrals or promotions. These also do not expire.
 
-Credits are consumed in order: daily free first, then monthly, then awarded, then purchased.
+Credits are consumed in order: monthly first, then awarded, then purchased.
 
 ## Checking Your Balance
 
@@ -16,11 +15,11 @@ Look for the **coin icon with a number** near the chat send button. That number
 - Click it to open a detailed breakdown showing how many credits you have in each category.
 - When your balance is low, opening that breakdown shows an alert-triangle warning ("No credits left" or "_N_ credits left") at the bottom.
 
-From a linked project directory, `fimo credits` shows the same organization balance in the CLI. Its "Available now" total already includes the visible buckets; the daily allowance section is not additional balance.
+From a linked project directory, `fimo credits` shows the same organization balance in the CLI. Its "Available now" total already includes the visible buckets.
 
 ## Buying More Credits
 
-Buying credits is available on the **Premium** plan, since it charges the payment method already on file.
+Buying credits is available on paid plans, since it charges the payment method already on file.
 
 1. Click the credit display near the chat input.
 2. Click **Buy credits**.
@@ -30,7 +29,7 @@ Buying credits is available on the **Premium** plan, since it charges the paymen
 
 ## Refilling Credits Automatically
 
-Organization billing admins on Premium can configure auto-refill from **Settings > Billing**:
+Organization billing admins on a paid plan can configure auto-refill from **Settings > Billing**:
 
 1. Choose the balance threshold that should trigger a refill.
 2. Choose the dollar amount to purchase when the balance crosses that threshold.
@@ -52,6 +51,14 @@ From there:
 3. Pick a plan and complete checkout.
 4. Your new monthly credit pool is available right away.
 
+## Changing or leaving a paid plan
+
+- Free to Pay as you go or Pro, and Pay as you go to Pro, use checkout and take effect after payment succeeds.
+- Pro to Pay as you go or Free takes effect at the end of the current billing period. Billing shows the destination and effective date until then.
+- Choosing the current plan again before that date cancels the scheduled change.
+- Pay as you go requires an active payment method. Removing its only valid card returns the organization to Free immediately.
+- A failed Pro renewal follows the payment-recovery flow. It never silently changes the organization to Pay as you go.
+
 ## Legacy plan transitions
 
 Some organizations that already have Premium may see a **Plan transition**

package/assets/skills/fimo-studio/references/webhooks.md

@@ -17,7 +17,7 @@ Only project members with Full Access can see Webhooks in Settings or manage its
 
 The event groups are Entries, Forms, Publish, Agents, Analytics, Media, Domains, Labels, Locales, and Environments. Webhooks belong to the project, with up to 20 configurations. Choose the Main Branch, All Branches, Production, Preview, or one custom Environment. Main Branch is the default.
 
-Entry webhooks show **Combine rapid changes**. The default waits 5 seconds after direct editing stops and sends one delivery with the combined changes. Immediate, 30-second, and 1-minute windows are also available. Bulk edits and environment merges already produce batches and send immediately.
+Entry webhooks send one delivery per committed write. A bulk edit or environment merge may contain a bounded batch, and wider changes split into separately delivered batches.
 
 ## Configure the request
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-28T21:37:20.437Z",
+  "bundledAt": "2026-09-01T08:14:56.822Z",
   "cliVersion": "2.1.0",
   "external": [
     "oxc-parser",