fimo 2.8.0-staging.10 → 2.8.0-staging.12

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

@@ -9,7 +9,7 @@ fimo preview url --branch main --json
 curl -L "$(fimo preview url)"
 ```
 
-The command returns the hosted deployment URL in every output mode, whatever the project's Preview setting says: every live Branch except production owns a hosted build.
+The command returns the hosted deployment URL in every output mode: every live Branch except production owns a hosted build.
 
 If the current generation is queued or building, the command waits up to five minutes, polling with a backoff. It stops at once — without waiting — on a state waiting cannot change: a build that failed, and a Branch with no hosted preview (production, or a Branch nothing has changed yet). Every failure returns `PREVIEW_URL_FAILED`; read `error.message` for which one it was and `error.hint` for the next step. Only the timeout is worth retrying.
 

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

@@ -10,6 +10,8 @@ Chat has its own **Chats** tab in the site header; the tab shows how many chats
 
 An agent is a chat with a job: a name and a description that Fimo reads at the start of every reply in that chat. Agents are shared like any chat and are listed as soon as they are created, with an **Agent** tag after the name. The **+** above the chat list is a menu: **New chat** (blank), **New agent** (a name and a description, then the empty agent opens), and under **Agents** Fimo's default agents (**SEO**, **Site health**, **Writer**, **Translator**); a new site starts with all four listed, their routines off until someone turns them on, and on an older site selecting a default creates the site's chat for it the first time, the same chat every time after. In an agent, the description shows next to its name in the header, the empty state introduces the agent by name and job, and the message box reads **Message <name>**. The agent's settings page has a **Description** field, shared with everyone; empty means none. The filter icon's **Kind** option shows only chats or only agents; search finds an agent by its name.
 
+The **SEO** default runs seven routines backed by Studio's built-in `fimo-seo` skill, which checks the site as a browser renders it and fixes at the source: **Technical SEO** (status, redirects, canonicals, sitemap, robots.txt, language, main heading), **Broken links**, **Meta tags** (titles, descriptions, Open Graph), **Image SEO** (alt text, file names), **Hreflang** (only on a site in more than one language) and **SEO monitoring** (changes since its last run) every day, and **Internal linking** (orphan and deep pages) every Monday. A fix with one right answer from the page's own words is made without a message (a link only once the new target is checked to be the same content in the same language); a change to what visitors read, which page wins a search, whether a page exists, or a redirect is asked as a decision; prices, legal pages, the robots policy, redirects that carry traffic and page removals are never changed on its own. What a check could not tell (a timeout, a 5xx, a page past the crawl limit) is never acted on: the run retries once, then says the check was incomplete.
+
 ### Routines
 
 A routine is saved instructions an agent runs in a thread of its own, by hand or on a schedule, so each run sees its earlier runs and the agent's chat never fills with its work. The agent's settings list its **Routines** as cards (name, cadence such as **Every Monday at 08:00** or **By hand**, next run, an **Active** switch) with a **New routine** button; the default agents come with theirs. A routine's page holds **Name**, **Instructions** (the task, run on every trigger), **Triggers** (**By hand** with **Run now**, which starts a run right away, or sends the routine a message as its next run; **Schedule**: none, every day, every week on a weekday, or every month on a day, at a time, in the timezone shown (a default agent's routines take the opener's browser timezone), at most every 15 minutes), the **Runs** list (newest first, two lines each: how it ended (**Quiet**, **Sent to agent**, **Asked for a decision**, or **Failed** and **Stopped** in red), when and what started it (**On schedule**, or **By hand** with the person's name or **agent** when their message started it), then the first sentence of what it told the agent; select one to open the routine's thread, read-only, at that run), the **Active** switch in the header (pauses the schedule only) and **Delete routine** (removes its thread too). Routines report to the agent, never to a person: a run that has something the agent should know writes it to the agent's chat as a message only the agent reads, and the agent takes a turn on it (reports waiting together are read in one turn); a run with nothing to say reports nothing. The agent decides what the team sees: nothing (the chat stays as it was, the row stays read), one short message (several reports folded into one), or a form when a person must decide, and the chat's row reads **Needs you** while that form is open. A person answers the form in the chat; the agent sends the decision to the routine with its `send_message` tool and the routine runs again with it. Only the agent answers a routine: its page has no answer box. Quiet runs leave no message: they fold into one line placed where the last run happened among the messages (**N runs since <date>**), counted from the last report the agent answered visibly, and the chat's row reads **Ran <date>** with that count while the newest thing in the chat is a run, the ordinary status and the last words when a message is newer, and **First check <day> <time>** or **No checks scheduled** before the first run. A routine whose runs keep failing or are refused for credits is reported to the agent once per streak, as a message from Fimo.

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

@@ -11,9 +11,11 @@ To build with your own AI instead, select **Build with ChatGPT, Claude or a codi
 ## Start From a Website
 
 1. Enter the website address. Fimo checks that it can read the site; if it cannot, it says why and nothing is created.
-2. Fimo creates the site, reads its homepage, then asks three questions in a short chat: what the business does, who its competitors are, and what sets it apart. The answers are saved as the site's knowledge.
-3. The report shows how ready the site is for search engines (SEO) and AI answers (GEO), with every check and how to fix it. Leaving and coming back resumes where you left off.
-4. Select **Clone & fix your homepage**. The site opens on its **Getting started** chat, where Fimo rebuilds the homepage with the report's problems fixed. Fimo covers the cost of the analysis, the questions and the rebuild; credits are not used.
+2. Fimo creates the site, reads its homepage, works out what kind of site it is (business, non-profit, portfolio, hobby or personal site), and asks three questions that fit it in a short chat. It always starts by confirming what it understood. A business then keeps or adds its competitors and says how it stands out and how it is priced; other sites say what visitors should do and what to put forward, picking suggestions or typing their own. The answers are saved as the site's knowledge. If Fimo cannot read the site for the questions, select **Try again**.
+3. The report opens as soon as the last question is answered. It shows how ready the site is for search engines (SEO) and AI answers (GEO), with every check and how to fix it. Leaving and coming back resumes where you left off.
+4. Select **Copy & optimize my homepage**, at the top of the report. The site opens on its **Getting started** chat, where Fimo rebuilds the homepage with the report's problems fixed, then shows the scores before the rebuild and the checks it fixed. Only the homepage is rebuilt; links to other pages still go to the current site. Fimo covers the cost of the analysis, the questions and the first two rebuilds; credits are not used for them.
+
+Fimo does not rebuild a site that breaks its terms of use: the onboarding stops with a message to contact support.
 
 The report and the homepage copy Fimo read are deleted after 7 days.
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-10-12T08:45:36.990Z",
+  "bundledAt": "2026-10-12T19:39:46.372Z",
   "cliVersion": "2.7.1",
   "external": [
     "oxc-parser",