fimo 2.10.0-staging.2 → 2.10.0-staging.3

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

@@ -72,7 +72,7 @@ Choosing the slug does not publish the site. The first successful `fimo deploy -
 
 The CLI never charges directly. Two distinct money paths:
 
-1. **Starter or higher** — gates custom-domain operations. Starter or Pro is chosen in the Fimo web app (Hyperline-hosted checkout). Organizations that still have Pay as you go keep custom domains. When a Free user runs a gated command they get a 403 with the billing URL; surface it as-is to the user.
+1. **Starter or higher** — gates custom-domain operations. Starter or Pro is chosen in the Fimo web app (Hyperline-hosted checkout). When a Free user runs a gated command they get a 403 with the billing URL; surface it as-is to the user.
 2. **Domain registration** — `fimo domains buy` creates a Hyperline invoice with `payment_method_strategy: 'external'` and returns a `checkoutUrl`. The user opens that URL in a browser to pay. **No money moves until they pay the invoice.** That's why `--yes` on `buy` is safe: it queues an invoice; the human still has to consent at checkout.
 
 Domain prices come from name.com via the registrar reseller. They vary by TLD and can change. Pricing is in USD (cents in the API, formatted as dollars in CLI output).

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

@@ -32,7 +32,7 @@ fimo history list --all-pages
 ```
 
 The list also reports compressed snapshot usage and the current retention period. Restore points expire after 1 day on
-Free, 30 days on Starter and Pay as you go, or 90 days on Premium and Pro. The expiry is fixed when each point is created.
+Free, 30 days on Starter, or 90 days on Premium and Pro. The expiry is fixed when each point is created.
 
 ## Restore safety
 

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

@@ -8,9 +8,9 @@ Chat has its own **Chats** tab in the site header; the tab shows how many chats
 
 ## Agents
 
-The plan decides the agents (FIMO-2856): Free has the SEO and GEO default agents, each running only its weekly checkup (**Weekly SEO checkup**, **Weekly AI check**), and its agent settings list the routines Starter adds with **See plans**; Starter (and legacy Pay as you go) has every default agent with its detailed routines, and a change wakes each routine at most once a day (the changes made meanwhile wait and the next run, a day after the last one started, checks them together; the routine's next run shows when, and **Run now** and schedules never wait); Pro runs them right after each change and adds agents of one's own (**New agent**). In the **+** menu, what the plan does not include shows **Upgrade** and opens the plans. Default agents are Fimo's: their routines follow Fimo's instructions, only switch off and on or get deleted (a deleted one stays deleted), and nothing is added to them (`routine_is_default`); routines of one's own live in a custom agent, on Pro (`routine_needs_pro` below Pro). A default agent's name, description and portrait cannot be changed on any plan, and a custom agent's change only on Pro: below Pro its settings are read-only, say its routines are paused and offer **See plans**, and it can still be deleted. A plan change changes which agents open and which routines run; agents, routines and past runs stay. Fimo support can give an organization Pro's agents on any plan. A routine Fimo retires from a default agent stops running and leaves the list.
+The plan decides the agents (FIMO-2856): Free has the SEO and GEO default agents, each running only its weekly checkup (**Weekly SEO checkup**, **Weekly AI check**), and its agent settings list the routines Starter adds with **See plans**; Starter has every default agent with its detailed routines, and a change wakes each routine at most once a day (the changes made meanwhile wait and the next run, a day after the last one started, checks them together; the routine's next run shows when, and **Run now** and schedules never wait); Pro runs them right after each change and adds live agents of one's own (**New agent**: any plan can set one up, only Pro makes it live). In the **+** menu, what the plan does not include shows **Upgrade** and opens the plans. Default agents are Fimo's: their routines follow Fimo's instructions, only switch off and on or get deleted (a deleted one stays deleted), and nothing is added to them (`routine_is_default`); routines of one's own live in a custom agent, on Pro (`routine_needs_pro` below Pro). A default agent's name, summary, instructions and portrait cannot be changed on any plan, and a live custom agent's change only on Pro: below Pro its settings are read-only, say its routines are paused and offer **See plans**, and it can still be deleted. A plan change changes which agents open and which routines run; agents, routines and past runs stay. Fimo support can give an organization Pro's agents on any plan. A routine Fimo retires from a default agent stops running and leaves the list.
 
-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**, **GEO**, **Content**, **Quality**, **Compliance**); a new site starts with SEO and GEO listed, their routines active from the start; Content, Quality and Compliance, and every default on an older site, are created the first time someone selects them, routines active, the same chat every time after. In an agent, the header shows the name alone and the message box reads **Message <name>**. A default agent's empty state greets in its own words and offers its own starter requests; its description stays in its settings. A custom agent's empty state shows its description (the first three lines; a cut description shows whole on hover, or on tap on a phone) and three starter requests every agent can answer. A starter is sent as shown, by anyone who can send messages. 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.
+An agent is a chat with a job: a name, a one-line summary for people, and instructions that Fimo reads at the start of every reply in that chat and every run of its routines (FIMO-3079). Live agents are shared like any chat, with an **Agent** tag after the name. The **+** above the chat list is a menu: **New chat** (blank), **New agent** (opens the new agent's chat at once: the agent asks what it should do with three one-click answers, then drafts its name, summary, instructions and routines on one card; **Create agent** sends the person's agreement and the agent goes live, the team sees it and its routines start; until then only its creator sees it, as **New agent** with **Setting up…**, its routines do not run, and its chat changes nothing on the site (it reads the site, its data and the web; no CLI, files, work sessions or publish), and it goes live only after the person saw its latest draft; a routine time the person did not name keeps its hour and Fimo picks the minute; below Pro, **Create agent** opens the plans), and under **Agents** Fimo's default agents (**SEO**, **GEO**, **Content**, **Quality**, **Compliance**); a new site starts with SEO and GEO listed, their routines active from the start; Content, Quality and Compliance, and every default on an older site, are created the first time someone selects them, routines active, the same chat every time after. In an agent, the header shows the name alone and the message box reads **Message <name>**. A default agent's empty state greets in its own words and offers its own starter requests; its description stays in its settings. A starter is sent as shown, by anyone who can send messages. Asked to, an agent changes its own instructions with its `agent` tool; the chat shows **Updated instructions** with **View change** (before and after). The agent's settings page has **Summary** and **Instructions** fields, shared with everyone (empty means none), and an **Instruction history** where **Restore previous** puts back the text a change replaced. In text, an agent links another as `[Name](agent://id)`, shown as a chip that opens it. The filter icon's **Kind** option shows only chats or only agents; search finds an agent by its name.
 
 The **SEO** default runs six 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, and changes since its last run: pages moved without a redirect), **Broken links**, **Meta tags** (titles, descriptions, Open Graph, the site's title ending, length in characters and pixels), **Image SEO** (alt text, file names, images over 200 KB: one in the media library or the site's own files is rendered through Fimo's resizing on its own, a file of the site uploaded first), **Hreflang** (only on a site in more than one language) and **Internal linking** (orphan and deep pages, articles with no link up to a hub or product page or more than eight links). Each default routine wakes on the changes on main that can matter to it, before a publish (CMS edits, code changes, images, languages, forms; the first publish and a new domain for Technical SEO and Cookie consent): a small model reads each change first, so a quiet site runs nothing, and the run checks what changed (the whole site on its first run). A schedule covers what no single change shows: every Monday, Technical SEO, Meta tags and Internal linking read every page of main's hosted preview (pages out of the sitemap, shared titles and title shape, orphan and deep pages); what changes without anyone touching the site also keeps one: Broken links checks outbound links on the 1st of every month, Content refresh runs on the 2nd, Content lifecycle every three months, Privacy and legal pages once a year. A page it changed is left alone for 8 weeks, the time Google takes to show the effect. 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 link on words the text already uses to name another page; a 301 from a page's old address once the same page is live at a new one); a change to what visitors read, which page wins a search, whether a page exists, a redirect with more than one possible target, a price or a legal page is asked as a decision; page removals and the robots policy are never changed on its own. A change a person asks for in a chat is made. 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.
 

package/assets/skills/fimo-studio/references/billing-and-credits.md

@@ -63,15 +63,14 @@ From there:
 
 ## Extra usage budget
 
-Open **Billing & usage**, then **Details** beside public bandwidth. Billing admins on Starter, Pro or legacy Pay as you go can edit one **Monthly budget** for extra public bandwidth. The page shows its cost and **Spent this period**. This budget does not cover AI credit purchases or auto-refill.
+Open **Billing & usage**, then **Details** beside public bandwidth. Billing admins on Starter or Pro can edit one **Monthly budget** for extra public bandwidth. The page shows its cost and **Spent this period**. This budget does not cover AI credit purchases or auto-refill.
 
 - At the budget, additional paid usage stops; remaining included allowances stay usable.
 - Disabling extra usage preserves charges already incurred. The budget cannot be lowered below existing extra-usage charges.
 
 ## Changing or leaving a paid plan
 
-- Free to Starter or Pro, and Starter or Pay as you go to Pro, use checkout and take effect after payment succeeds. Starter to Pro credits back the unused part of the Starter month.
-- Pay as you go is no longer offered. An organization that has it keeps it; once it leaves, it cannot choose it again.
+- Free to Starter or Pro, and Starter to Pro, use checkout and take effect after payment succeeds. Starter to Pro credits back the unused part of the Starter month.
 - Moving down from a paid monthly plan stops auto-refill and paid extra usage immediately, whether the destination is Free or Starter. The current plan, remaining allowances, credits, and reset date stay unchanged until the destination takes over at renewal. Manual credit purchases remain available while the paid plan is active.
 - Automatic spending cannot be enabled while a plan change is scheduled. Keep your plan first; then you can immediately enable auto-refill and paid extra usage independently. Keeping the plan itself leaves both off.
 - Usage before the change remains payable. Enabling extra usage again does not make usage from the off-period billable.
@@ -79,7 +78,7 @@ Open **Billing & usage**, then **Details** beside public bandwidth. Billing admi
 - Review the confirmation before scheduling Pro to Starter. It explains the immediate spending stop, retained benefits and charges already incurred; opening it does not change the plan.
 - Switching the scheduled destination between Free and Starter keeps the same effective date and the same moment automatic spending stopped. Nothing is re-granted. Team organizations reach Free through **Cancel subscription**, not the plan dialog.
 - Choosing the current plan again before that date cancels the scheduled change and its Starter successor.
-- A scheduled Starter starts with its first monthly payment. With no card on file that payment fails and the organization moves to Free through payment recovery. Legacy Pay as you go requires an active payment method: removing its only valid card returns the organization to Free immediately.
+- A scheduled Starter starts with its first monthly payment. With no card on file that payment fails and the organization moves to Free through payment recovery.
 - A failed Pro renewal follows the payment-recovery flow. It never silently changes the organization to Starter.
 
 ## Legacy plan transitions

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-10-23T10:48:42.104Z",
+  "bundledAt": "2026-10-23T14:06:49.897Z",
   "cliVersion": "2.9.0",
   "external": [
     "oxc-parser",