fimo 2.2.0-staging.12 → 2.2.0-staging.14

package/assets/skills/fimo-cli/references/projects.md

@@ -9,16 +9,16 @@ fimo projects list [--org <id>]                 # list projects in an org (defau
 fimo projects create [dir] [--org <id>] [--framework react-router|astro|nextjs|sveltekit] [--install|--no-install]
 fimo projects clone [projectId] [dir] [--branch <name>] # clone an existing project locally
 fimo projects delete [projectId] [-C <dir>] [-y] # delete (defaults to current project)
-fimo projects publish [projectId] [-C <dir>]     # make the project live (publish from main)
+fimo projects publish [projectId] [-C <dir>]     # make the project live from its Production source Branch
 fimo projects unpublish [projectId] [-C <dir>]   # take the project offline
 fimo projects rename <name> [projectId] [-C <dir>]   # set seo.siteName in the linked project config
 ```
 
 - **`list`** — projects you can see in the org. Live projects are marked.
 - **`create`** — identical to `fimo init` (create-new path); see `references/init.md`.
-- **`clone`** — clone a remote Fimo project's git repo to your machine and write the local `.fimo/project.json` and agent files. Use `fimo clone <projectId>` when scripting or when the ID is known. In an interactive terminal, bare `fimo clone` opens a project picker for the active org; JSON mode and non-TTY shells require an explicit project ID and fail fast instead of prompting. By default it clones `main`; pass `--branch <name>` to clone a specific Branch. The legacy `--env <name>` spelling remains a compatibility alias. The target directory defaults to the project display name/name, or pass `[dir]` explicitly.
+- **`clone`** — clone a remote Fimo project's git repo to your machine and write the local `.fimo/project.json` and agent files. Use `fimo clone <projectId>` when scripting or when the ID is known. In an interactive terminal, bare `fimo clone` opens a project picker for the active org; JSON mode and non-TTY shells require an explicit project ID and fail fast instead of prompting. By default it clones `main`; pass `--branch <name>` to clone a specific Branch. The removed `--env <name>` spelling is rejected as a Branch selector. The target directory defaults to the project display name/name, or pass `[dir]` explicitly.
 - **`delete`** — destructive; prompts unless `-y`. Removes the remote project.
-- **`publish` / `unpublish`** — toggle the project's public visibility. `publish` flips the current `main` state live (the same "go live" as `fimo deploy --publish`, minus the git push).
+- **`publish` / `unpublish`** — toggle the project's public visibility. `publish` flips the configured Production source state live (the same "go live" as `fimo deploy --publish`, minus the git push).
 - **`rename`** — edits only the linked local project's `seo.siteName`. It does not commit or deploy. It requires a project marker in the cwd, and if you pass a `[projectId]` that doesn't match the linked project it errors and exits 1 (so you can't rename a different project). Later remote config commands may require reconciliation while the local config is dirty. Finish your local edits, then explicitly run `fimo deploy --no-wait` when ready for a quick sync.
 
 ## Top-level clone shortcut
@@ -43,10 +43,10 @@ fimo rename "<Site Name>"        # local edit: set seo.siteName in the project c
 
 ## Publish commands
 
-| Command                 | Effect                                                                  |
-| ----------------------- | ----------------------------------------------------------------------- |
-| `fimo deploy --publish` | Push current `main` + flip the project live in one shot.                |
-| `fimo projects publish` | Flip the project live (no git push).                                    |
-| `fimo publish`          | Flip the already-synced `main` revision live; optional label and notes. |
+| Command                 | Effect                                                                     |
+| ----------------------- | -------------------------------------------------------------------------- |
+| `fimo deploy --publish` | Push the current Production source + flip the project live in one shot.    |
+| `fimo projects publish` | Flip the project live (no git push).                                       |
+| `fimo publish`          | Flip the synced Production source revision live; optional label and notes. |
 
 See `references/deploy.md` and `references/branches.md` for the full picture.

package/assets/skills/fimo-cli/references/schedules.md

@@ -2,7 +2,7 @@
 
 `fimo schedules` manages recurring commands for one project Branch. It uses the
 current checkout Branch by default, or the Branch passed with `--branch <name>`.
-The legacy `--env <name>` spelling remains a compatibility alias.
+The removed `--env <name>` spelling is rejected as a Branch selector.
 
 The command starts in that Branch's sandbox. Commands can still target another
 Branch explicitly, for example with `fimo schemas list --branch preview`.
@@ -72,6 +72,6 @@ All schedule commands support the CLI's global `--json` mode. List, detail, and
 
 ## Notes
 
-- Every operation is scoped to the active Branch unless `--branch` (or the legacy `--env` alias) is passed.
+- Every operation is scoped to the active Branch unless `--branch` is passed.
 - Pausing stops future cron runs. It does not delete history.
 - A failed or skipped manual run exits non-zero with its run ID and an exact `runs show` command for inspecting detail.

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

@@ -28,12 +28,13 @@ Run this before writing a custom payload. The list shows supported event types,
 - Publish: `publish.started`, `publish.succeeded`, `publish.failed`, `publish.unpublished`
 - Agents: run started/completed/failed/cancelled and review requested/resolved
 - Analytics: `analytics.report_ready`
-- Media: uploaded/updated/deleted/generated/processing_failed
+- Media: uploaded/updated/deleted
 - Entries: `entry.changed`
 - Domains: `domain.created`, `domain.deleted`
 - Labels: `label.changed`
 - Locales: `locale.created`, `locale.default_changed`, `locale.deleted`
-- Environment events (legacy wire names): `environment.created`, `environment.deleted`, `environment.merged`, `environment.restored`
+- Branch restore: `branch.restored`
+- Existing lifecycle wire names: `environment.created`, `environment.deleted`, `environment.merged`
 
 Do not guess variable paths. The common envelope is:
 
@@ -110,9 +111,8 @@ Available filters are event-specific:
 - `--agent <name>` for agent events
 - `--media-type <image|video|audio|document|other>` for media events
 - `--action <created|updated|deleted>`, `--content-type <name>`, and `--locale <locale>` for `entry.changed`
-- `--debounce-changes <immediate|5s|30s|1m>` for direct `entry.changed` delivery grouping
 
-`entry.changed` represents content accepted in the selected Environment. New entry webhooks wait 5 seconds after the last direct edit by default, then send one delivery with the combined `data.changes`. Exact repeated autosave changes appear once. Use `--debounce-changes immediate` to disable grouping. Accepted agent edits and environment merges already carry compact batches and send immediately. Operations above the delivery batch size share an `operationId` and include `{ index, total }` batch metadata. Every event includes scalar `environment` and `branch` context and keeps the legacy Branch value at `event.env.name`. Publish events always report Production on `main`.
+`entry.changed` represents content committed in the selected Environment. Each committed write sends one delivery whose `data.changes` lists every affected entry; environment merges arrive the same way with `reason: "environment_merge"`. Operations above the delivery batch size share an `operationId` and include `{ index, total }` batch metadata. Retries resend the same delivery (same event `id`), never a new one. Every event includes scalar `environment` and `branch` context and keeps the legacy Branch value at `event.env.name`. Publish events always report Production on `main`.
 
 ## Inspect before depending on it
 

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

@@ -1,12 +1,12 @@
-# Assets — package surface
+# Assets in code
 
 > For the CLI commands (`fimo assets upload`, `fimo image generate`, folder management) and the "when to generate AI images" workflow rules, see **`fimo-cli/references/assets.md`**.
 
-This file covers the package surface for working with assets in code: the `media` field value shape, rendering primitives, and URL format.
+This file covers media fields and the Fimo image components.
 
-## `media` field value (stored/wire shape)
+## Media field values
 
-Asset values returned from `fimo assets upload` or Fimo media tasks, and stored in `media` content-type fields:
+A media field stores a reference to an asset, not a copy of the asset metadata. Write the value returned by upload or generation:
 
 ```json
 {
@@ -16,11 +16,22 @@ Asset values returned from `fimo assets upload` or Fimo media tasks, and stored
 }
 ```
 
-- `source`: `"local"` for uploaded/generated assets in the Fimo media library. `"external"` for hard-coded third-party URLs (avoid when possible — editors can't manage these).
-- `url`: stable HTTPS URL, no auth required, safe to embed.
-- `alt`: optional alt text.
+- `source`: `"local"` for a Fimo media-library asset, or `"external"` for a third-party URL.
+- `url`: the public asset URL.
+- `alt`: optional text owned by the entry.
 
-Generated content reads wrap this stored value in `FimoMedia`, which exposes `url`, `alt`, `name`, `mime`, and optional `width`/`height`. It does not expose `source`; Fimo tracks that internally. Pass the whole entry value to `<Image>` / `<Video>`.
+For a local asset, Fimo stores its ID and keeps the URL as a fallback. Do not copy `name`, `mime`, `width`, or `height` into the value. Those facts belong to the asset and are removed from writes.
+
+By default, reads return the stored reference without an asset lookup. Name a media or blocks field in `populate` when the page needs the asset's current URL, name, MIME type, or intrinsic size:
+
+```ts
+const post = await Post.getBySlug('hello');
+const withAsset = await Post.getBySlug('hello', { populate: ['cover'] });
+```
+
+`populate` takes top-level field names. A blocks field populates every media value inside it. One lookup covers all selected media in the response. Media inside a populated reference target stays a reference. Use `fimo assets open <id> --download` to inspect the source file.
+
+Generated reads wrap media in `FimoMedia`. Its `id`, `alt`, `name`, `mime`, `width`, and `height` can be absent. A populated value has the current facts when the asset resolves; missing or external assets stay unchanged. `source` is internal. Pass the whole value to `<Image>` or `<Video>`.
 
 ## Rendering in application code
 
@@ -41,11 +52,11 @@ import { Image, StaticImage, Video } from 'fimo-next';
 <StaticImage src="https://assets.fimo.ai/<project>/<id>.jpg" alt="Hero" width={1200} height={630} />
 ```
 
-Fimo's `<Image>` is not Next's `next/image` component. Do not pass Next-only props such as `priority`, `fill`, `quality`, or `loader`; use only the props documented for the Fimo primitive. Preserve `next/image` for non-Fimo images when the application needs those Next-specific controls.
+Fimo's `<Image>` is not Next's `next/image`. Use the Fimo props documented here. Keep `next/image` for non-Fimo images that need its controls.
 
-**Provide `width` and `height` when known** so Fimo can optimize the asset and reserve layout space (prevents CLS).
+Choose dimensions, CSS, `sizes`, and `fit` from the page design. Do not copy the source file's intrinsic dimensions into layout props by default. When a read includes intrinsic size, Fimo uses it for aspect-ratio reservation and responsive candidates.
 
-**Never hand-construct a `FimoMedia` object** to pass into `<Image>` — that bypasses inline-editing metadata. If you have a raw URL, use `<StaticImage>` instead.
+**Never hand-construct a `FimoMedia` object** to pass into `<Image>`. That bypasses inline-editing metadata. If you have a raw URL, use `<StaticImage>` instead.
 
 See `references/ui.md` for the full component table and rules.
 

package/assets/skills/fimo-code/references/content/clients.md

@@ -125,7 +125,21 @@ const page = await Article.list({
 });
 ```
 
-Fimo always keeps `id`, `entryId`, `documentId`, and `locale`. Without `populate`, references are `{ id }`; with it, they become the target entry or `null`. Populate is depth-one and only accepts reference field names.
+Fimo always keeps `id`, `entryId`, `documentId`, and `locale`, plus every field named in `populate`.
+
+`populate` is depth-one and takes top-level field names of two kinds:
+
+| Field named          | Without `populate`       | With it                                                                                     |
+| -------------------- | ------------------------ | ------------------------------------------------------------------------------------------- |
+| reference            | `{ id }`                 | the target entry, or `null`                                                                 |
+| media                | the stored reference     | `FimoPopulatedMedia` with current asset facts when it resolves; asset facts remain optional |
+| blocks holding media | stored references inside | every media value inside it populated; item types unchanged                                 |
+
+Any other field name is a 400. A populated reference target carries its own media as stored references. Population does not recurse, and a missing or external asset keeps its stored media value.
+
+Even when media is populated, `id`, `name`, `mime`, `width`, and `height` can be absent for external, missing, or incomplete assets. The stored `url` remains the fallback, and `alt` is optional entry-owned text.
+
+Generated schema modules keep `FimoMediaRef` and `FimoPopulatedMedia` local. Their shapes depend on the schema, while the installed runtime package may be an older release.
 
 When a named type is needed, use the generated result type rather than typing populated data as the base entry:
 

package/assets/skills/fimo-code/references/frameworks/astro.md

@@ -115,7 +115,7 @@ export async function getStaticPaths() {
 
 Configure Astro i18n from `.fimo/config.json#i18n` and use `Astro.currentLocale` for content reads, `getLabels({ locale })`, and `<html lang>`. The standard starter keeps the configured default locale unprefixed and prefixes the others. Existing applications may instead resolve locale through middleware, domains, cookies, or another application-owned strategy. Astro needs no Fimo locale provider. Ownership rules: `references/locales.md`.
 
-The new-project shell pairs unprefixed default-locale pages with a parallel `[locale]` tree because Astro has no optional single-segment page filename. Add locales in `.fimo/config.json`; Astro's native i18n router validates the prefixed tree. Route metadata uses `/:locale` with `params.locale.optional: true`; Astro page files remain authoritative.
+The new-project shell pairs unprefixed default-locale pages with a parallel `[locale]` tree because Astro has no optional single-segment page filename. Add locales through the `fimo-cli` locale workflow; Astro's native i18n router reads the synchronized config and validates the prefixed tree. Route metadata uses `/:locale` with `params.locale.optional: true`; Astro page files remain authoritative.
 
 ## Studio route catalog
 

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-migration/SKILL.md

@@ -248,9 +248,13 @@ ID supplied by the owner — without one, stop with an unresolved owner action
 instead of inventing an ID:
 
 - Link an owner-supplied (empty) project:
-  `fimo migrate init <target-dir> --project-id <projectId> --framework <framework>`
+  `fimo migrate init <target-dir> --project-id <projectId> --framework <framework> --source-platform <platform>`
 - Create a new project in an owner-supplied organization:
-  `fimo migrate init <target-dir> --org <organizationId> --framework <framework>`
+  `fimo migrate init <target-dir> --org <organizationId> --framework <framework> --source-platform <platform>`
+
+`--source-platform` names what the site is migrated from (`wordpress`, `nextjs`,
+`astro`, `react-router`, `webflow`, `framer`, `squarespace`, `wix`, `carrd`,
+`other`); pass what the source checkout proves, `unknown` only when nothing does.
 
 After setup, check `.fimo/config.json#runtime.framework` and the scaffold's
 framework files before starting workers. A Next.js target must still have its
@@ -286,7 +290,10 @@ Commands that perform actual data writes, all requiring the linked target:
 - `fimo schemas push`, `fimo assets upload`, `fimo entries create|update`,
   `fimo singles update`, `fimo labels set|set-many`, `fimo forms push`.
 - `fimo migrate init` (source-backed form): the project link/creation and
-  initial commit push described above.
+  initial commit push described above. Pass `--source-platform <platform>`
+  (webflow, framer, squarespace, wix, carrd, wordpress, nextjs, astro,
+  react-router, other) when the source is known; URL crawls detect it.
+
 - `fimo link`: project creation or selection plus the in-place adoption of a
   copied source target.
 - `fimo deploy` / `fimo publish` — owner-approved only.

package/assets/skills/fimo-migration/references/media.md

@@ -86,6 +86,17 @@ the asset owns the uploaded bytes and their metadata, and the entry field holds
 the media value `{ source, url, alt }` that points at it. Keep both carrying the
 same alt text, and do not duplicate alt into a second schema field.
 
+Do not copy upload metadata into media values yourself. Writing `{ source, url,
+alt }` is enough: the write path resolves and persists the media-library ID, and
+a read that names the field in `populate` returns the asset's current URL, name,
+MIME type, and intrinsic dimensions from the library. A read that does not name
+it returns the stored reference. The ID lets you inspect the asset later with
+`fimo assets open <id> --download`.
+
+Treat intrinsic dimensions as source facts, not layout instructions. Choose the
+displayed size, crop, `sizes`, loading behavior, and fit from the migrated page's
+design and responsive behavior.
+
 ## Failure Handling
 
 If a media asset cannot be downloaded or uploaded:

package/assets/skills/fimo-migration/references/workflow.md

@@ -21,6 +21,9 @@ ask a generic optimization question.
    - URL migration: `fimo migrate init <source-url> <target-dir> --framework <framework>`
    - link an existing project: `fimo migrate init <target-dir> --project-id <projectId> --framework <framework>`
    - create a project: `fimo migrate init <target-dir> --org <organizationId> --framework <framework>`
+   - add `--source-platform <platform>` when the source platform is known
+     (webflow, framer, squarespace, wix, carrd, wordpress, nextjs, astro,
+     react-router, other); URL crawls detect it themselves.
      Use the detected source framework for source-backed migrations. A framework
      conversion requires an explicit user choice; URL-only and rebuild
      migrations ask the user which framework to use. Never choose a framework by

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-28T14:46:45.101Z",
+  "bundledAt": "2026-09-01T08:14:56.822Z",
   "cliVersion": "2.1.0",
   "external": [
     "oxc-parser",