fimo 2.8.0-staging.5 → 2.8.0-staging.6

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

@@ -107,7 +107,6 @@ Load the matching reference when the user's request fires its trigger. Recipes t
 - "Modify the URL of the website / change my project's address / connect a custom domain (e.g. blog.example.com) / rename the Fimo-provided `*.fimo.site` subdomain / buy a new domain through Fimo / set up a domain" → `references/domains.md`
 - "Invite a collaborator / add Marc / share with client" → `references/invite.md`
 - "Login / log out / who am I / switch organization" → `references/account.md` — note: switching **org** is `fimo orgs switch`; bare `fimo switch` changes the active **Fimo Branch** (see `references/branches.md`)
-- "Check the Inbox / what are my agents waiting on / answer a blocked agent / an agent asked me a question / approve or deny what an agent asked for (`fimo inbox *`)" → `references/inbox.md`. Never answer on the person's behalf.
 - "Create / scaffold / run / validate an agent / agent bundle / wire or enable its triggers / list agent templates / view agent runs, reports, or logs (`fimo agents *`)" → `references/agents.md`
 - "Install Fimo for my agent / fimo skills install / set up Claude Code, Codex, or Cursor for Fimo" → `references/agent-setup.md`
 - "Add, inspect, search, or run a remote MCP server / use `fimo mcp`" → `references/mcp.md`
@@ -132,7 +131,7 @@ These fire at specific moments in the project lifecycle. **Surface them proactiv
 - **You need the current preview URL but haven't changed code** (opening it, screenshotting it, handing it to another tool, the previous URL expired) → `fimo preview url`, never a no-op `fimo deploy`. See `references/preview.md`.
 - **When the user wants to try something risky / explore a redesign without touching the live site** → suggest a feature Branch: `fimo checkout -b <name>` gives an isolated Branch + DB + preview. Deploy previews there, then `fimo merge` it back and `fimo publish`. See `references/branches.md`.
 - **After completing or safely preserving the user's main work, when a confirmed Fimo platform failure still materially blocks the task after one safe recovery attempt, or a confirmed missing capability blocks completion or forces a fragile or heavily manual workaround** → use the built-in `supportReport` tool. Do not wait for the user to ask and do not stop after only describing the gap. See `references/support.md`.
-- **When a project agent has stopped and is waiting on a person** → `fimo inbox list --topic agent_question --unread` surfaces it. Show the stored form to the person, collect their explicit answer, and submit it with `fimo inbox answer`. See `references/inbox.md`.
+- **When a project agent has stopped and is waiting on a person** → a project member answers its question in Studio, on the run's page; the question email links there. The CLI cannot answer it. Never answer on the person's behalf.
 - **After the first successful `fimo deploy`** → suggest `fimo invite` if the project involves multiple people. Typical roles: `edit` for developers/content editors, `view` or `comment` for clients/stakeholders, `full` for project leads. See `references/invite.md`.
 - **After the automatic first-preview deploy on the create-new path, before the project has been published** → if there is no custom domain and the free default `*.fimo.site` slug still looks generated or was never explicitly chosen, offer to find a cleaner free subdomain. It needs no DNS. Never claim one without explicit user confirmation: suggest candidates, let the user choose, then rename it. Choosing the slug does not publish the site; the URL starts resolving only after the first successful `fimo deploy --publish`. Skip this nudge if the user already chose the default slug, attached a custom domain, or declined. See `references/domains.md` § Offer a cleaner default URL before first publish.
 - **When the user wants to modify the URL of their website** → walk through `references/domains.md`. The CLI surface covers renaming the Fimo-provided subdomain (`fimo domains rename-default`, free), attaching a domain they already own (`fimo domains add`, Premium), and buying a new domain through Fimo (`fimo domains buy`, Premium).

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

@@ -141,9 +141,10 @@ A review-first content agent could use this complete policy:
 - Discard only when no useful draft was produced or the attempted approach was fully abandoned.
 ```
 
-When a run cannot continue correctly without a decision from a project member, it may call `ask_user` instead. The
-question goes to the Fimo Inbox and the current invocation ends. It can reference zero or more sessions. An authorized
-answer starts a continuation in the same thread; the referenced work stays open and the original model process does not wait.
+When a run cannot continue correctly without a decision from a project member, it may call `ask_user` instead. Fimo
+emails project members a link to answer it in Studio, and the current invocation ends. It can reference zero or more
+sessions. An authorized answer starts a continuation in the same thread; the referenced work stays open and the original
+model process does not wait.
 
 Use `ask_user` sparingly, especially from scheduled agents:
 
@@ -170,8 +171,8 @@ changes and records a brief report of what is waiting.
 
 ## Define reporting preferences when they matter
 
-Fimo's default report needs no setup: a short, scannable brief appears in email and the Inbox, while the full report in
-Fimo carries the organized evidence and depth. Do not add a reporting section merely to restate that default.
+Fimo's default report needs no setup: a short, scannable brief appears in email, while the full report in Fimo carries
+the organized evidence and depth. Do not add a reporting section merely to restate that default.
 
 When the user names an audience, depth, recurring comparison, required section, or useful visual, preserve the request
 in a short **Reporting** section of `GOAL.md`. Describe the communication outcome in ordinary language. Do not prescribe

package/assets/skills/fimo-studio/references/command-palette.md

@@ -25,7 +25,6 @@ Studio adds commands that are relevant to the page you are viewing. Depending on
 - Uploading an asset, creating a folder, or generating an image
 - Running an agent, opening its Preview result, or resolving proposed changes
 - Editing or opening the current CMS page in Preview
-- Marking the current Inbox item read or unread, and archiving or restoring it
 - Running, pausing, resuming, or opening runs for the current schedule
 - Sending a test or opening deliveries for the current webhook
 - Inviting a member or buying a domain from the corresponding organization page

package/assets/skills/fimo-studio/references/media-library.md

@@ -28,6 +28,10 @@ Click any file to open a preview dialog:
 
 The preview shows file metadata (size, dimensions, upload date) and editable fields for **name**, **alt text**, and **caption**. Alt text and captions are generated automatically by AI after upload -- you'll see a **Generating with AI** indicator, then an **AI generated** badge once they're ready, and you can edit the suggested text inline. From here you can also **copy the link** or **send the file to chat**. To **move**, **rename**, or **delete** a file, use its right-click menu in the grid instead.
 
+## Replacing a File in Content
+
+In a file's details, choose **Replace file**, pick a replacement, then select **Continue** to review the Current Branch reference count. **Back** or **Escape** returns to the picker with the choice preserved; closing the picker returns to the file's details. Only confirming the replacement changes references. Main, the live site, other Branches, and the original file stay unchanged.
+
 ## AI Image Generation
 
 1. Click the **Plus (+) dropdown** in the media library and select **Generate Image**.

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

@@ -31,7 +31,7 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
 - **"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. **View details** opens the reader's Inbox item about the failure, which offers **Open publishing** and **Contact support**. 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 that Inbox item, plus an email unless they turned off **Publication failures** in Account settings → Notifications.
+- **"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.
 
 ## Key Concepts
 

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

@@ -4,13 +4,15 @@ Click the **Edit mode** icon in the preview header, next to Share, or press **Al
 
 ## Selecting and Editing Elements
 
-Once in edit mode, click an element in the preview. An orange outline highlights it. Plain CMS-managed text edits in place; images, rich text, and structured fields open the side editor.
+Once in edit mode, click an element in the preview. An orange outline highlights it. CMS-managed text, images, rich text, and structured fields open the side editor.
 
 ### Editing Content
 
-Type directly into selected CMS-managed text, then press **Enter** or choose **Done** above it to save. **Escape** discards the text edit; **Shift+Enter** inserts a newline. **Ask Fimo** opens chat with the selected element as context. Selecting an image opens its image editor. Image and structured-field changes save automatically; inline text is saved only with Enter or Done. Failed text saves keep the toolbar open for correction or retry. Text and images written directly in the site code remain selectable for chat context; ask the AI chat to change them.
+Update the selected field in the sidebar. Changes save automatically and appear in the preview. Failed saves keep the draft available for correction or retry. Use AI chat to change text and images written directly in the site code.
 
-The link icon in the selected element's toolbar opens its label or CMS entry. Choose **All fields** in the side editor 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.
+The link icon beside the field in the sidebar opens its label or CMS entry. Choose **All fields** in the side editor 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.
+
+Incomplete JSON drafts stay local. Leaving an empty JSON field saves `null` and updates the preview without reloading the page.
 
 ### References and Components
 
@@ -26,7 +28,7 @@ Selecting an element with nothing editable (a container, a spacer, a decorative
 
 ## Exiting Edit Mode
 
-Choose **Done** above selected text or click the **Edit mode** icon again to return to preview mode. Closing the side panel dismisses its selected field.
+Click the **Edit mode** icon again to return to preview mode. Closing the side panel dismisses its selected field.
 
 ## When to Use Edit Mode vs. Chat
 

package/dist/cli/bundle.json

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