fimo 2.2.0-staging.8 → 2.2.0

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

@@ -4,6 +4,15 @@ Use this as the phase contract for a complete migration. The coordinator and
 workers communicate in plain text. JSON is used only for Fimo schemas and the
 content payloads that the data-plane commands import.
 
+## Preflight: inspect and ask
+
+Before target initialization or any other write, inspect the source read-only
+and follow `references/questions-and-improvements.md`. Use the coding agent's
+native structured-question UI to ask one stacked batch for integration,
+environment, framework, and ownership decisions that the source cannot settle.
+Never move environment values or credentials without explicit consent. Do not
+ask a generic optimization question.
+
 ## Phase 0: Initialize the target
 
 1. Confirm the target path. The target is a separate directory; the source
@@ -12,6 +21,9 @@ content payloads that the data-plane commands import.
    - 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
@@ -20,9 +32,15 @@ content payloads that the data-plane commands import.
 3. Inspect the target's real `package.json`, `.fimo/config.json`, framework config, and route
    directories. They are the authority for paths. Do not infer an app root
    from a skill example and do not create a second `app/` or `src/app/` tree.
-4. If the target is non-empty and not a Fimo project, stop and ask for a target
+4. Verify dependency provenance before workers start. A project created by a
+   published CLI pins that exact CLI release and matching companion packages.
+   A local source-checkout project uses the checkout-local CLI. Stop when the
+   target records an absolute package-manager cache path, an unapproved
+   `latest`, or a CLI and API from different runtime channels; do not let the
+   producer repair release setup inside the migration.
+5. If the target is non-empty and not a Fimo project, stop and ask for a target
    path; do not overlay a template on top of it.
-5. Keep source material in `.fimo/migration/source` or another explicit source
+6. Keep source material in `.fimo/migration/source` or another explicit source
    location. Do not copy source files over the initialized target root.
 
 Write a short `.fimo/migration/migration-plan.md` containing the source
@@ -46,8 +64,10 @@ Classify the available evidence:
 For private APIs or CMSs, ask for a user-provided export or a narrowly scoped
 server-side credential. Never recover credentials from browser bundles or copy
 them into migration artifacts. If the source API URL or access is missing or
-unreachable, stop and ask the user for it; do not guess or continue with
-replacement content.
+unreachable, stop and ask whether to use scoped access, reconstruct only the
+selected published routes from the public site, or migrate code without the CMS
+records. Continue with public reconstruction only after that explicit choice,
+and record everything the rendered site cannot reveal.
 
 For API-backed content, trace active clients, endpoints, frontend types, and
 consumers first. Prefer backend source schemas; otherwise use public OpenAPI,
@@ -143,12 +163,22 @@ one generic static shell. Apply the matching framework reference before
 disposing of provider-specific rules; redirects, headers, feeds, metadata,
 forms, and freshness behavior are observable contracts.
 
+When local or bundled content becomes Fimo-backed, follow the content-delivery
+contract in `references/questions-and-improvements.md`. Preserve build-time or
+server rendering, direct lookups, bounded reads, request parallelism, and edit
+freshness. A new browser waterfall, repeated full-list read, avoidable
+sequential request chain, or stale edit is a migration regression.
+
 ## Phase 6: Fan in, validate, and report
 
 Workers return the plain-text receipt defined in `references/workers.md`.
 The coordinator checks those claims against the diff, source, CLI read-back,
-build, and rendered routes. Then an independent worker follows
-`references/workers/validator.md`; a worker saying "done" is not evidence.
+build, and rendered routes. Then it runs the read-only validation wave from
+`references/workers/validator.md`, passing the accepted scope and deliberate
+user-approved differences as task context; a worker saying "done" is not
+evidence.
+Collect the complete finding set before assigning repairs. Run disjoint repair
+owners together, wait for all repairs, and rerun one central validation wave.
 
 Write `.fimo/migration/migration-report.md` with route/content/media/form/SEO
 coverage, import counts, worker timings, unresolved items, and next actions.

package/assets/skills/fimo-studio/SKILL.md

@@ -6,7 +6,7 @@ description: >-
   Triggers: "in Fimo Studio", "in the dashboard", "in the web app",
   "how do I X in the UI", or screenshots of the dashboard. Topics
   covered: dashboard content and CMS, publishing from the dashboard,
-  dashboard SEO/domain settings, project connections, schedules and run history, outbound webhooks,
+  dashboard SEO/domain settings, project connections, agents, schedules and run history, outbound webhooks,
   visual editing, version history UI, dashboard sharing/billing, dashboard chat,
   and the command palette. Never describe
   UI locations, buttons, or panels from memory — always read the relevant
@@ -39,6 +39,7 @@ Read the relevant reference file when the user's question matches a topic.
 | AI Chat                  | references/ai-chat.md                   | "What can the AI do?", "How do I give context?"       |
 | Code Editor              | references/code-editor.md               | "How do I edit code?", "Where are my files?"          |
 | SEO Settings             | references/seo-settings.md              | "How do I set up SEO?", "Favicon, title, share image" |
+| Agents                   | references/agents.md                    | "Run an agent", "Pause an agent", "Next agent run"    |
 | Schedules                | references/schedules.md                 | "Recurring commands", "Run history", "Run now"        |
 | Webhooks                 | references/webhooks.md                  | "React to forms", "Send events to another service"    |
 | Connections              | references/connections.md               | "Connect a service", "Add an MCP server"              |
@@ -60,6 +61,7 @@ Read the relevant reference file when the user's question matches a topic.
 | Content/CMS             | AI Chat, Media Library                                                         |
 | Webhooks                | Project secrets, Forms, Publishing, Agents                                     |
 | Connections             | AI Chat, Agents, Project secrets                                               |
+| Agents                  | Connections, Project secrets, Branches                                         |
 | Schedules               | Project secrets, Environments, Agents                                          |
 | Visual changes          | Edit Mode (quick tweaks), AI Chat (bigger changes), Code Editor (full control) |
 | Something went wrong    | Version History, AI Chat                                                       |

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

@@ -0,0 +1,25 @@
+# Agents
+
+Project agents are versioned bundles from the project's repository. Studio lets project members inspect their configuration and run history, while project managers can start, stop, and resume them.
+
+## Open an agent
+
+1. Open the project and choose **Agents**.
+2. Select **Agents** again to see the available bundles.
+3. Choose an agent to open its **Runs** and **Settings** tabs.
+
+When the agent has a live schedule, its next run appears first in **Runs**, marked **Scheduled**. The row uses **Next** for its projected ID, a relative date such as **Tomorrow at 11:00 AM**, and **—** for changes and duration until it starts. **Settings** shows the bundle's declared capabilities and trigger wiring; it is read-only because the repository remains the source of truth.
+
+## Run, stop, or resume
+
+Choose **Run** to start an agent whose manual trigger is live.
+
+Choose **Stop** to pause every future trigger and stop planned or running work. Studio asks for confirmation and explains that the bundle, trigger configuration, model, capabilities, and other settings are preserved.
+
+A stopped agent shows **Paused** in the header. **Resume** makes the same triggers live again with their previous settings.
+
+Only project managers see Run, Stop, and Resume. Other project members can still see schedule timing, status, settings, and run history.
+
+## Inspect runs
+
+Open **Runs** on an agent to see only that bundle's history. Select a run to read its status, report, captured changes, and any question or review state that needs attention.

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/visual-editing.md

@@ -8,7 +8,15 @@ Once in edit mode, click on any element in the preview -- text, buttons, images,
 
 ### Editing Content
 
-For text elements, the side panel shows editable fields where you can change the text directly. This covers CMS-managed content, hardcoded text, and hardcoded images. Changes save automatically, and the preview updates as you type.
+For text elements, the side panel opens the selected field immediately with its current value. This covers CMS-managed content, hardcoded text, and hardcoded images. Changes save automatically, and the preview updates as you type.
+
+For CMS content, choose **All fields** to open the complete entry form. Studio keeps the content type's field order, scrolls to the field you selected, and focuses it in place. Loading appears only while Studio fetches this additional entry data or moves to another entry.
+
+### References and Components
+
+Selecting a field rendered from a referenced entry edits that entry. For example, selecting an author's name opens the Author entry, not the Post relation that links to it. The header shows the relation path. Select the owning entry in that path to return to its complete form with the relation field focused; use that relation field to open, replace, or clear the linked entry.
+
+Selecting a field inside a component focuses that nested field. Choose **All fields** to see it in the complete entry form without moving it out of schema order. The shared CMS form provides the existing add, duplicate, remove, and reorder controls for repeatable components and blocks.
 
 ### Editing Styles
 

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,8 +1,8 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-27T11:27:23.831Z",
-  "cliVersion": "2.1.0",
+  "bundledAt": "2026-09-01T17:10:31.208Z",
+  "cliVersion": "2.2.0",
   "external": [
     "oxc-parser",
     "fsevents",