fimo 2.10.0-staging.1 → 2.10.0-staging.3

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

@@ -51,7 +51,7 @@ Global flags: `--project <id>` / `-C, --cwd <dir>` for project resolution, `--or
 When a user says "I want to change my website's URL," ask which case fits:
 
 - **"It's fine as-is, just nicer"** → `rename-default` or `suggest-default`. Free, instant, no DNS.
-- **"I own example.com already"** → `add example.com`. Pay as you go or higher. They configure CNAME at their registrar.
+- **"I own example.com already"** → `add example.com`. Starter or higher. They configure CNAME at their registrar.
 - **"I want to buy a domain"** → `search` → `pricing` → `buy`. The registered-domains feature flag and an eligible plan must be on (the flag is not enabled in every environment).
 
 If they aren't sure, run `fimo domains suggest-default` first — it's free, takes one step, and a good fallback if they don't want to commit to a domain purchase.
@@ -60,7 +60,7 @@ If they aren't sure, run `fimo domains suggest-default` first — it's free, tak
 
 After the automatic first-preview deploy on a newly created project, offer a cleaner free `*.fimo.site` URL before the first public publish when there is no custom domain and the current default slug still looks generated or was never explicitly chosen. Choosing it now lets the first public launch use the clean URL. Skip the offer if the user already chose the default slug, attached a custom domain, or declined.
 
-The default URL is free and needs no DNS. A custom domain uses the Pay as you go (or higher) workflow above. A default slug can be reserved before publication, but it returns "Project Not Found" until the site is published. Renaming changes the address that will become public, so never silently claim a suggestion:
+The default URL is free and needs no DNS. A custom domain needs Starter or higher, as above. A default slug can be reserved before publication, but it returns "Project Not Found" until the site is published. Renaming changes the address that will become public, so never silently claim a suggestion:
 
 1. Run `fimo domains suggest-default --base "<brand>" --json` to get candidates.
 2. Show the candidates and ask the user to choose one explicitly.
@@ -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. **Pay as you go or higher** — gates custom-domain operations. A valid card activates Pay as you go through 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.
+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).
@@ -121,7 +121,7 @@ Propagation: typically 15–30 minutes, up to 48 hours rarely.
 ## Common errors
 
 - **"Project Not Found" on a new URL or custom domain.** The route exists but the site was never published — run `fimo deploy --publish`.
-- **"Custom domains require Pay as you go or higher."** — add a card at `/app/billing`, then retry. Free users can still run `list`, `rename-default`, `suggest-default`, `search`, and `pricing`.
+- **"Custom domains require Starter or higher."** — choose a plan at `/app/billing`, then retry. Free users can still run `list`, `rename-default`, `suggest-default`, `search`, and `pricing`.
 - **"Domain purchase is not enabled on this account."** — the registered-domains feature flag is off on this API instance. Contact support.
 - **"This URL is not available."** — slug or hostname collides with another project or is reserved.
 - **"That's a Fimo-owned domain."** — user tried `add <something>.fimo.site`. Use `rename-default` instead.

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 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 (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.
 
@@ -24,7 +24,7 @@ The **Compliance** default runs three routines backed by Studio's built-in `fimo
 
 ### Routines
 
-A routine is saved instructions an agent runs in a thread of its own, by hand, on a schedule, or when something happens in the project, so each run sees its earlier runs and the agent's chat never fills with its work. The agent creates, changes, runs and deletes its routines from its chat with its `routines` tool: a person asks in the chat ("check the prices every Monday", "run after each publish"), and Studio only shows routines. A trigger is set in words; Fimo checks them and either says when the routine runs or why it cannot follow them and what it can do instead; for what Fimo cannot see as an event (traffic, rankings, errors) the agent offers a schedule whose run checks it and stops when there is nothing to do. Fimo follows publishes of the site (or only its first publish) and content changes on the main branch by content type, action, locale, changed fields, the entry's current values ("price over 100", "status changes to archived") or a yes/no question about what the content says ("mentions Contentful or Sanity"; for "a competitor" it uses the names given or those in the site knowledge, and asks for them otherwise; a run started on an uncertain answer says so), media files uploaded or changed (by name or file type), the site's code changing through a deploy or a merge (by file path glob, or a yes/no question about the changed files such as "a page was added"), another routine of the same agent finishing (optionally with a yes/no question about its report; never its own end), a visitor submitting a form (optionally with a yes/no question about the answers), a form or content type changing, a branch merged into main, a locale added, removed or made the default, a publish of the site failing, a domain added or removed, and the prices on a page of another web site changing ("tell me when https://example.com/pricing changes its prices": checked daily, a change must hold on three reads before the routine runs, the run lists each plan with its old and new price, the routine page shows the watch as **OK**, **Needs repair**, **Blocked** or **Unstable** with its last check, at most 10 watched pages a project); comparing a field's old and new values is not supported; what a routine changes, publishes or reports can start the agent's other routines, in chains of any length, each routine at most once per change that started the chain (across every routine that change leads to, so routines never loop or multiply; a person's new change, a run by hand or on a schedule starts a new chain); events that come in while a run is busy wait, then run together in one next run (up to 10), which the Runs list shows as one run with its event count; the agent can also make a routine's event runs wait until the changes stop for a set number of minutes (at most 2 hours from the first), then read them all in one run (a yes/no question is then answered once for all the waiting changes, each entry once in its latest version; a waiting change it says no to leaves the queue, and when it says no to all of them no run starts); the default routines that read what changed (Meta tags, Image SEO, Internal linking, Structured data, AI citation optimization, Content lifecycle, Translation, Accessibility, Mobile optimization, Brand compliance) wait 10 minutes after the last change, and those that guard the live site (Technical SEO, Broken links, Hreflang, AI readiness, Cookie consent, Privacy and legal pages) run at once. The agent's settings list its **Routines** as cards (name, when it runs such as its event trigger's title, **Every Monday at 08:00** or **By hand**, next run, an **Active** switch); the default agents come with theirs (a new project's defaults wake on changes from five minutes after it is created, so its first push and seed start no run). A routine's page is read-only: **What it does** (one or two plain sentences the agent writes with the routine, Fimo's for a default routine), with **Instructions** folded under it (the task, run on every trigger; a routine created before descriptions shows only its **Instructions**), **Model** (the model its runs use: Opus 5.5 by default, while most default routines run on Claude Haiku 5.5 or Claude Sonnet 5; the agent sets another when asked), **Triggers** (**By hand** with **Run now**, which starts a run right away; **Schedule** and the event trigger, given a short title by Fimo from the words it was set with and showing those words, shown when set), 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**, **On event**, 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), and the **Active** switch in the header (pauses the schedule and the trigger, not **Run now**). 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 `routines` 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. Routine runs use the plan's agent-hours, from each run's start to its end (Studio chats do not); Billing shows the hours used this period, and each run shows its duration and credits. Once the included hours are used, nothing runs (no schedule, event or Run now, which the routines tool reports to the agent); Studio shows **Routines paused** under the chat list and in the agent's settings with the reset date and the button that resumes them sooner (**Upgrade**), and the routine's page says until when. No run lasts longer than 2 hours.
+A routine is saved instructions an agent runs in a thread of its own, by hand, on a schedule, or when something happens in the project, so each run sees its earlier runs and the agent's chat never fills with its work. The agent creates, changes, runs and deletes its routines from its chat with its `routines` tool: a person asks in the chat ("check the prices every Monday", "run after each publish"), and Studio only shows routines. A trigger is set in words; Fimo checks them and either says when the routine runs or why it cannot follow them and what it can do instead; for what Fimo cannot see as an event (traffic, rankings, errors) the agent offers a schedule whose run checks it and stops when there is nothing to do. Fimo follows publishes of the site (or only its first publish) and content changes on the main branch by content type, action, locale, changed fields, the entry's current values ("price over 100", "status changes to archived") or a yes/no question about what the content says ("mentions Contentful or Sanity"; for "a competitor" it uses the names given or those in the site knowledge, and asks for them otherwise; a run started on an uncertain answer says so), media files uploaded or changed (by name or file type), the site's code changing through a deploy or a merge (by file path glob, or a yes/no question about the changed files such as "a page was added"), another routine of the same agent finishing (optionally with a yes/no question about its report; never its own end), a visitor submitting a form (optionally with a yes/no question about the answers), a form or content type changing, a branch merged into main, a locale added, removed or made the default, a publish of the site failing, a domain added or removed, and the prices on a page of another web site changing ("tell me when https://example.com/pricing changes its prices": checked daily, a change must hold on three reads before the routine runs, the run lists each plan with its old and new price, the routine page shows the watch as **OK**, **Needs repair**, **Blocked** or **Unstable** with its last check, at most 10 watched pages a project); comparing a field's old and new values is not supported; what a routine changes, publishes or reports can start the agent's other routines, in chains of any length, each routine at most once per change that started the chain (across every routine that change leads to, so routines never loop or multiply; a person's new change, a run by hand or on a schedule starts a new chain); events that come in while a run is busy wait, then run together in one next run (up to 10), which the Runs list shows as one run with its event count; the agent can also make a routine's event runs wait until the changes stop for a set number of minutes (at most 2 hours from the first), then read them all in one run (a yes/no question is then answered once for all the waiting changes, each entry once in its latest version; a waiting change it says no to leaves the queue, and when it says no to all of them no run starts); the default routines that read what changed (Meta tags, Image SEO, Internal linking, Structured data, AI citation optimization, Content lifecycle, Translation, Accessibility, Mobile optimization, Brand compliance) wait 10 minutes after the last change, and those that guard the live site (Technical SEO, Broken links, Hreflang, AI readiness, Cookie consent, Privacy and legal pages) run at once. The agent's settings list its **Routines** as cards (name, when it runs such as its event trigger's title, **Every Monday at 08:00** or **By hand**, next run, an **Active** switch); the default agents come with theirs (a new project's defaults wake on changes from five minutes after it is created, so its first push and seed start no run). A routine's page is read-only: **What it does** (one or two plain sentences the agent writes with the routine, Fimo's for a default routine), with **Instructions** folded under it (the task, run on every trigger; a routine created before descriptions shows only its **Instructions**), **Model** (the model its runs use: Opus 5.5 by default, while most default routines run on Claude Haiku 5.5 or Claude Sonnet 5.5; the agent sets another when asked), **Triggers** (**By hand** with **Run now**, which starts a run right away; **Schedule** and the event trigger, given a short title by Fimo from the words it was set with and showing those words, shown when set), 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**, **On event**, 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), and the **Active** switch in the header (pauses the schedule and the trigger, not **Run now**). 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 `routines` 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. Routine runs use the plan's agent-hours, from each run's start to its end (Studio chats do not); Billing shows the hours used this period, and each run shows its duration and credits. Once the included hours are used, nothing runs (no schedule, event or Run now, which the routines tool reports to the agent); Studio shows **Routines paused** under the chat list and in the agent's settings with the reset date and the button that resumes them sooner (**Upgrade**), and the routine's page says until when. No run lasts longer than 2 hours.
 
 ## Sending a Message
 

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

@@ -34,7 +34,7 @@ Buying credits is available while a paid plan is effective, including after sche
 1. Click the credit display near the chat input.
 2. Click **Buy credits**.
 3. Enter a dollar amount (up to $10,000) or pick one of the presets: **$25**, **$50**, **$100**, or **$200**.
-4. Check the rate shown in the dialog. It comes from your current plan, so the same dollar amount can buy a different number of credits on Pay as you go than on Pro.
+4. Check the rate shown in the dialog. It comes from your current plan, so the same dollar amount can buy a different number of credits on different plans.
 5. Confirm the purchase. Your card on file is charged and the credits are added after confirmation; there is no separate checkout page to complete. If confirmation stays pending, retry the same purchase or contact support. Do not start another purchase to replace an unresolved one.
 
 ## Refilling Credits Automatically
@@ -57,29 +57,29 @@ You can upgrade from two places:
 From there:
 
 1. Compare the available plans side by side.
-2. Pro includes more monthly credits, custom domain support, and the ability to hide the Fimo badge on your published site.
+2. Starter and Pro include more monthly credits and custom domain support. Pro has the largest allowances and the ability to hide the Fimo badge on your published site.
 3. Pick a plan and complete checkout.
 4. Your new monthly credit pool is available right away.
 
 ## Extra usage budget
 
-Open **Billing & usage**, then **Details** beside public bandwidth. Billing admins on Pay as you go 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.
+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 Pay as you go or Pro, and Pay as you go to Pro, use checkout and take effect after payment succeeds.
-- Moving down from a paid monthly plan stops auto-refill and paid extra usage immediately, whether the destination is Free or Pay as you go. 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.
+- 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.
-- 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.
-- Review the confirmation before scheduling Pro to Pay as you go. 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 Pay as you go 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 Pay as you go successor.
-- Pay as you go requires an active payment method. Removing its only valid card returns the organization to Free immediately, and a scheduled Pay as you go with no card on file lands on Free on its effective date instead.
-- A failed Pro renewal follows the payment-recovery flow. It never silently changes the organization to Pay as you go.
+- Pro to Starter, or Pro or Starter to Free, takes effect at the end of the current billing period. Billing shows the destination and effective date until then.
+- 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.
+- 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-22T14:44:54.031Z",
+  "bundledAt": "2026-10-23T14:06:49.897Z",
   "cliVersion": "2.9.0",
   "external": [
     "oxc-parser",