fimo 2.8.0-staging.6 → 2.8.0-staging.7

package/assets/skills/fimo-studio/references/custom-domains.md

@@ -5,7 +5,7 @@ If you're driving Fimo from the terminal, the equivalent commands are `fimo doma
 ## Before You Start
 
 - You need a **premium plan**. Without it, the Domains option shows an "Upgrade" label.
-- Your project must be **published at least once**. An alert appears if it has not been published yet.
+- Your site must be **published at least once**. An alert appears if it has not been published yet.
 - You need access to your **domain registrar** (GoDaddy, Namecheap, Cloudflare, etc.).
 - Both **subdomains** (e.g., `blog.example.com`) and **apex/root domains** (e.g., `example.com`) are supported. A subdomain uses a single CNAME record; an apex domain uses two A records, with an optional automatic redirect to its `www` subdomain. The redirect direction can be reversed later without changing DNS.
 

package/assets/skills/fimo-studio/references/drawing-and-wireframing.md

@@ -1,8 +1,6 @@
 ## Opening the Drawing Tool
 
-Inside an existing project, open the wireframe canvas from the chat attachment dropdown: click the add-attachments (**+**) button next to the chat input, then choose **Draw**. (This option is hidden on mobile.)
-
-<!-- TODO(audit 2026-06-03): The previously documented "pen icon in the project creation form" entry point could not be confirmed in apps/ui. The drawing dialog there is only opened from the chat attachment dropdown. If a creation-form pen icon exists on the landing/home surface, document it here. -->
+Inside an existing site, open the wireframe canvas from the chat attachment dropdown: click the add-attachments (**+**) button next to the chat input, then choose **Draw**. (This option is hidden on mobile.)
 
 Selecting **Draw** opens a large drawing canvas powered by Excalidraw, displayed in a centered dialog.
 
@@ -54,7 +52,7 @@ When you are happy with your sketch:
 
 Click the **clear canvas** button to start fresh. A confirmation dialog appears before clearing to prevent accidental loss.
 
-Your work is retained while you close and reopen the canvas within the same session, so you can step away and come back to it. It is cleared once you attach the drawing, and it is not persisted across page reloads or navigating away from the project.
+Your work is retained while you close and reopen the canvas within the same session, so you can step away and come back to it. It is cleared once you attach the drawing, and it is not persisted across page reloads or navigating away from the site.
 
 ## Getting the Best Results
 

package/assets/skills/fimo-studio/references/preview-and-responsive.md

@@ -38,8 +38,8 @@ You may see different overlays depending on what is happening:
 - **"Recovering preview…"** -- The visible preview is reloading after a refresh or a recoverable development-server failure.
 - **"Editing unavailable"** -- The site remains visible, but its Fimo integration did not connect in time. Visual editing and the route selector stay unavailable; preview and refresh still work.
 - **Error overlay** -- Something went wrong. The overlay shows details about the issue, and the AI can often auto-fix it for you.
-- **"Some installed packages need approval"** -- Choose **Fix with Fimo** to send the complete repair context to the coding agent, or **Copy details** to handle it elsewhere. Review every named package, commit only trusted package-specific approvals, and retry Preview. Never replace the project policy with a blanket allow-all setting.
-- **First generation progress** -- When your project is being built for the first time, a progress overlay shows the current status.
+- **"Some installed packages need approval"** -- Choose **Fix with Fimo** to send the complete repair context to the coding agent, or **Copy details** to handle it elsewhere. Review every named package, commit only trusted package-specific approvals, and retry Preview. Never replace the site policy with a blanket allow-all setting.
+- **First generation progress** -- When your site is being built for the first time, a progress overlay shows the current status.
 
 ## Switching Workspaces
 

package/assets/skills/fimo-studio/references/project-creation.md

@@ -1,16 +1,16 @@
-## Create a Project
+## Create a Site
 
-1. Open **Projects** in Fimo Studio.
-2. Select **Create project**. If the button is unavailable, ask an organization admin for project creation permission.
-3. Enter a project name and select **Create**.
-4. Studio opens the new project's **Getting started** view.
+1. Open **Sites** in Fimo Studio.
+2. Select **Create site**. If the button is unavailable, ask an organization admin for site creation permission.
+3. Enter a site name and select **Create**.
+4. Studio opens the new site's **Getting started** view.
 
-## Set Up the Project
+## Set Up the Site
 
-The **For agents** tab is the default. Copy its prompt into your coding agent, or use one of the available agent shortcuts. The prompt identifies this as a newly created Fimo project, gives the agent the exact `fimo init` command, pins the selected CLI channel for every `fimo` command in the setup, and links to the coding-agent guide. Following that guide, the agent initializes the project and creates its first hosted preview with one plain preview deploy — unless you tell it not to deploy.
+The **For agents** tab is the default. Copy its prompt into your coding agent, or use one of the available agent shortcuts. The prompt identifies this as a newly created Fimo site, gives the agent the exact `fimo init` command, pins the selected CLI channel for every `fimo` command in the setup, and links to the coding-agent guide. Following that guide, the agent initializes the site and creates its first hosted preview with one plain preview deploy — unless you tell it not to deploy.
 
 Use **Manual setup** when you want to run the steps yourself. It provides the exact `fimo init` command, coding-agent shortcuts, and the final `fimo deploy` command.
 
-The first deploy completes onboarding and removes **Getting started** from the project. You can also select **Dismiss getting started** to hide it without deploying.
+The first deploy completes onboarding and removes **Getting started** from the site. You can also select **Dismiss getting started** to hide it without deploying.
 
 Deploying creates a preview. It does not publish the site. Publishing is a separate action in Fimo Studio; see **Publish & Deploy** when the site is ready to go live.

package/assets/skills/fimo-studio/references/publish-and-deploy.md

@@ -2,15 +2,15 @@
 
 1. Look for the **Publish** button in the top-right of the header bar.
 2. Click it to open the publish panel. This shows your current status, your live URL (once you have one), any custom domains, and a **SEO Settings** shortcut.
-3. Click **Publish** inside the panel to start the deploy. A toast notification says "Publishing project..." and the panel's status badge switches to **Publishing** with a spinner.
+3. Click **Publish** inside the panel to start the deploy. A toast notification says "Publishing site..." and the panel's status badge switches to **Publishing** with a spinner.
 4. Once done, the panel shows a **Published** status, your live URL under a **Published site** heading, and a **Last published** date and time.
 5. Click the URL to open your live site in a new tab.
 
-> **Next step:** After publishing, consider inviting teammates to collaborate using the **Invite** button in the project header. You can grant them Full, Edit, Comment, or View access.
+> **Next step:** After publishing, consider inviting teammates to collaborate using the **Invite** button in the site header. You can grant them Full, Edit, Comment, or View access.
 
 ## Re-publishing After Changes
 
-Every change you make is automatically saved to your project, but saved changes are not live yet. Think of it like writing a draft: it is saved, but nobody sees it until you publish.
+Every change you make is automatically saved to your site, but saved changes are not live yet. Think of it like writing a draft: it is saved, but nobody sees it until you publish.
 
 To push your latest changes live, open the publish panel from the header **Publish** button and click **Publish** inside it again. It redeploys with your latest code and content.
 
@@ -27,11 +27,11 @@ When the AI requested publication, the review dialog offers **Merge and publish*
 The header **Publish** button itself only shows the label "Publish" (or a spinner while a deploy is running). Open the panel to see the current state:
 
 - **"Not published yet"** — Your site has never been published. Use **Publish** inside the panel when it is enabled.
-- **"This project uses an older version of Fimo"** — Upgrade the project's Production source before publishing new changes. **Upgrade project** opens its Preview, where you can request the migration in the existing chat. Your previously published site stays online.
+- **"This site uses an older version of Fimo"** — Upgrade the site's Production source before publishing new changes. **Upgrade site** opens its Preview, where you can request the migration in the existing chat. Your previously published site stays online.
 - **"Publishing"** — Publishing is in progress. A spinner and a **Publishing** status badge show while it builds, and the button is disabled.
 - **"Published"** — Your site is live. A **Published** status badge appears, your live URL is listed under a **Published site** heading as a clickable link, and a **Last published** date and time is shown.
-- **"Couldn't publish · N issues"** — Project validation found issues that must be fixed first. Choose **Fix with Fimo** to send the safe issue list to the project chat and ask Fimo to repair it.
-- **"Latest update failed"** — The newest publication did not finish. The panel says what went wrong and, for a site that was published before, that the previous version remains the active release — so it can appear beside **Published**. It stays until a newer publication finishes. Studio never shows the build output; read it with `fimo publish logs <id>`, taking the id from `fimo publish list`. The person who published and the project's managers get an email that opens this panel, unless they turned off **Publication failures** in Account settings → Notifications.
+- **"Couldn't publish · N issues"** — Site validation found issues that must be fixed first. Choose **Fix with Fimo** to send the safe issue list to the site chat and ask Fimo to repair it.
+- **"Latest update failed"** — The newest publication did not finish. The panel says what went wrong and, for a site that was published before, that the previous version remains the active release — so it can appear beside **Published**. It stays until a newer publication finishes. Studio never shows the build output; read it with `fimo publish logs <id>`, taking the id from `fimo publish list`. The person who published and the site's managers get an email that opens this panel, unless they turned off **Publication failures** in Account settings → Notifications.
 
 ## Key Concepts
 
@@ -43,5 +43,5 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
 ## Troubleshooting
 
 - **Changes not showing on the live site**: Try clearing your browser cache or opening the site in an incognito/private window.
-- **Publish button is disabled or missing**: Check the upgrade explanation and your publish permissions. If the button shows a tooltip about permissions, ask the project owner to check your role.
+- **Publish button is disabled or missing**: Check the upgrade explanation and your publish permissions. If the button shows a tooltip about permissions, ask the site owner to check your role.
 - **On mobile**: The header **Publish** button opens a drawer with the same status and confirmation action as the desktop panel.

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

@@ -1,10 +1,10 @@
 # Schedules
 
-Schedules run recurring project commands in one environment. Use the Studio surface to review configuration, pause or resume automatic runs, start work now, and inspect what happened afterward.
+Schedules run recurring site commands in one environment. Use the Studio surface to review configuration, pause or resume automatic runs, start work now, and inspect what happened afterward.
 
 ## Open schedules
 
-1. Open the project and choose **Settings**.
+1. Open the site and choose **Settings**.
 2. Select **Schedules**.
 3. Choose the environment whose schedules you want to manage.
 
@@ -16,10 +16,10 @@ Choose **New schedule** to set:
 
 - A human-readable name
 - A standard five-field cron expression
-- The command to run from the project root
-- The project secret keys the command is allowed to use
+- The command to run from the site root
+- The site secret keys the command is allowed to use
 
-A schedule with no selected secret keys receives no project secrets. Studio displays key names only and never reveals secret values.
+A schedule with no selected secret keys receives no site secrets. Studio displays key names only and never reveals secret values.
 
 Open a schedule to change its configuration. Use **Pause** to prevent future cron runs without deleting its history, and **Resume** to make the cron active again.
 

package/assets/skills/fimo-studio/references/sharing-and-collaboration.md

@@ -1,19 +1,19 @@
-## Inviting People to Your Project
+## Inviting People to Your Site
 
-1. Click the **Invite** button in the project header.
+1. Click the **Invite** button in the site header.
 2. A sharing panel opens showing your current team. On desktop this appears as a popover; on mobile it opens as a drawer.
 3. Type the email address of the person you want to invite.
 4. Choose an access level for them:
-   - **Full access** -- complete control over the project, including settings and member management.
-   - **Can edit** -- can edit content and assets, and use the AI chat to change code. Cannot change project settings.
-   - **Can comment** -- can view the project and leave comments but cannot make edits.
-   - **Can view** -- can see the project but cannot make any changes or comments.
+   - **Full access** -- complete control over the site, including settings and member management.
+   - **Can edit** -- can edit content and assets, and use the AI chat to change code. Cannot change site settings.
+   - **Can comment** -- can view the site and leave comments but cannot make edits.
+   - **Can view** -- can see the site but cannot make any changes or comments.
 5. Click **Invite**.
 6. The invite appears in the member list marked **Pending invitation** until the person accepts it.
 
 ## Managing Members
 
-Open the sharing panel to see everyone who has access to your project. Each member appears with their avatar, name, and current access level.
+Open the sharing panel to see everyone who has access to your site. Each member appears with their avatar, name, and current access level.
 
 - **Change access**: Click the role dropdown next to a member's name and pick a new level.
 - **Remove someone**: Open the role dropdown next to their name and choose **Delete** to revoke access.
@@ -21,15 +21,15 @@ Open the sharing panel to see everyone who has access to your project. Each memb
 
 ## Real-Time Collaboration
 
-When multiple people are working on the same project at the same time, you can see each other's activity:
+When multiple people are working on the same site at the same time, you can see each other's activity:
 
 - Each person's cursor is labeled with their name in the preview, so you can tell who is who.
 - CMS content changes appear in real time.
 
 ## Organization Access
 
-If your project belongs to an organization, some members may already have access based on their organization role.
+If your site belongs to an organization, some members may already have access based on their organization role.
 
 - At the bottom of the sharing panel, below the invite field and the member list, an **Everyone in <your organization>** row lets you set the default access level for all org members. This control also offers **No access** to turn org-wide access off.
-- When org-wide access is set, all organization members can see the project at that level.
+- When org-wide access is set, all organization members can see the site at that level.
 - You can still invite people individually for more specific access.

package/assets/skills/fimo-studio/references/version-history.md

@@ -1,10 +1,10 @@
 ## Where to Find Version History
 
-Click your **project name** in the top bar to open the project dropdown menu, then select **History**. This opens the version history panel showing all your saved versions.
+Click your **site name** in the top bar to open the site dropdown menu, then select **History**. This opens the version history panel showing all your saved versions.
 
 ## How Versions Are Created
 
-Versions are created automatically as you work — you don't create them by hand. Whenever the AI makes meaningful changes to your project, it captures a restore point for the current environment that you can browse, rename, and restore. A restore point includes the project code and CMS data, including schemas, entries, translations, and forms. There is no "create version" button in the panel; the history list only shows the restore points that already exist.
+Versions are created automatically as you work — you don't create them by hand. Whenever the AI makes meaningful changes to your site, it captures a restore point for the current environment that you can browse, rename, and restore. A restore point includes the site code and CMS data, including schemas, entries, translations, and forms. There is no "create version" button in the panel; the history list only shows the restore points that already exist.
 
 ## Browsing Versions
 
@@ -25,7 +25,7 @@ Find the version you want to update, click the **three-dot menu**, select **Edit
 
 ## Key Concepts
 
-- **Automatic versions** -- The AI creates these whenever it makes significant changes to your project. You do not need to do anything for these to appear.
+- **Automatic versions** -- The AI creates these whenever it makes significant changes to your site. You do not need to do anything for these to appear.
 - **Studio is browse and restore** -- Studio does not create restore points manually. Developers can use `fimo history create "Name"` from the CLI.
 - **Environment-scoped history** -- Each environment has its own restore points. Restoring one environment does not change another.
 - **Safe restore** -- Fimo records the current code and CMS data as a safety point before replacing them.
@@ -33,7 +33,7 @@ Find the version you want to update, click the **three-dot menu**, select **Edit
 
 ## Quick Restore from Chat
 
-Each AI message in the chat that made changes to your project shows an **undo button** (↩ icon) on the right side. Click it and a **"Restore version?"** prompt appears; confirm it to restore the current environment to the state it was in at that message. Fimo saves a safety point first, so CMS work completed after that message remains recoverable. This is the fastest way to undo a recent change without opening the full version history panel.
+Each AI message in the chat that made changes to your site shows an **undo button** (↩ icon) on the right side. Click it and a **"Restore version?"** prompt appears; confirm it to restore the current environment to the state it was in at that message. Fimo saves a safety point first, so CMS work completed after that message remains recoverable. This is the fastest way to undo a recent change without opening the full version history panel.
 
 The undo button is disabled on the most recent change (you can't restore the version you're already on) and is only available to members with permission to manage history.
 

package/assets/skills/fimo-studio/references/visual-editing.md

@@ -1,6 +1,6 @@
 ## Entering Edit Mode
 
-Click the **Edit mode** icon in the preview header, next to Share, or press **Alt+E** (⌥+E on Mac). You can also hold **Alt** (**Option** on Mac); the icon stays active without opening a panel. Select an element, release the key, and continue editing. Releasing without a selection leaves temporary edit mode. Shortcuts are inactive while typing in a field. The preview must be visible and your project fully loaded before edit mode is available. Note: edit mode is not available on mobile.
+Click the **Edit mode** icon in the preview header, next to Share, or press **Alt+E** (⌥+E on Mac). You can also hold **Alt** (**Option** on Mac); the icon stays active without opening a panel. Select an element, release the key, and continue editing. Releasing without a selection leaves temporary edit mode. Shortcuts are inactive while typing in a field. The preview must be visible and your site fully loaded before edit mode is available. Note: edit mode is not available on mobile.
 
 ## Selecting and Editing Elements
 

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

@@ -2,26 +2,26 @@
 
 > Test each destination and review its delivery history before depending on it in production.
 
-Webhooks send project activity to an external HTTPS endpoint. Use them for focused reactions such as adding a waitlist submission to an email tool, notifying Slack after a publish, or starting a GitHub workflow after an agent review.
+Webhooks send site activity to an external HTTPS endpoint. Use them for focused reactions such as adding a waitlist submission to an email tool, notifying Slack after a publish, or starting a GitHub workflow after an agent review.
 
-Only project members with Full Access can see Webhooks in Settings or manage its destinations and delivery history.
+Only site members with Full Access can see Webhooks in Settings or manage its destinations and delivery history.
 
 ## Create one
 
-1. Open the project and choose **Settings**.
+1. Open the site and choose **Settings**.
 2. Select **Webhooks**.
 3. Choose **New webhook**.
 4. Name it, select one event, and enter the destination URL.
 5. Optionally narrow form, agent, media, or entry events with the filter shown for that event.
 6. Review the request and select **Save**.
 
-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.
+The event groups are Entries, Forms, Publish, Agents, Analytics, Media, Domains, Labels, Locales, and Environments. Webhooks belong to the site, with up to 20 configurations. Choose the Main Branch, All Branches, Production, Preview, or one custom Environment. Main Branch is the default.
 
 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
 
-The default payload is the complete Fimo event, including its type, project, scalar Environment and Branch context, timestamp, and event-specific data. The legacy `env.name` Branch field remains available. Keep the complete payload when the destination can accept it.
+The default payload is the complete Fimo event, including its type, site, scalar Environment and Branch context, timestamp, and event-specific data. The legacy `env.name` Branch field remains available. Keep the complete payload when the destination can accept it.
 
 Choose **Custom template** when a service expects a specific JSON shape. Use **Insert variable** to pick fields for the selected event. Variables use paths such as `{{ event.data.submission.data.email }}`. The preview catches invalid JSON and missing variables before save.
 
@@ -29,7 +29,7 @@ When Studio recognizes a Resend, Slack, or GitHub URL, it offers a request setup
 
 ## Add authentication
 
-Under **Headers**, add a header name and type any non-secret prefix, such as `Bearer `. Choose **Insert secret** to select an existing project secret or create one without leaving the webhook editor. Creating a secret never replaces an existing secret with the same name; select the existing secret instead. Fixed values are suitable only for non-sensitive headers.
+Under **Headers**, add a header name and type any non-secret prefix, such as `Bearer `. Choose **Insert secret** to select an existing site secret or create one without leaving the webhook editor. Creating a secret never replaces an existing secret with the same name; select the existing secret instead. Fixed values are suitable only for non-sensitive headers.
 
 Fimo signs requests by default. Save the signing secret shown after creation so a custom receiver can verify `X-Fimo-Signature`. Rotate it from the webhook configuration if it is exposed.
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-10-06T12:40:39.311Z",
+  "bundledAt": "2026-10-08T06:10:28.838Z",
   "cliVersion": "2.7.1",
   "external": [
     "oxc-parser",