fimo 0.14.0-staging.1 → 0.14.0-staging.3

package/README.md

@@ -27,7 +27,8 @@ Run the CLI with `npx` — no global install, always the latest:
 
 ```bash
 npx fimo@latest login
-npx fimo@latest init my-site
+npx fimo@latest init my-site                 # default React Router scaffold
+# or: npx fimo@latest init my-next-site --framework nextjs
 cd my-site
 ```
 
@@ -43,7 +44,7 @@ npx fimo@latest skills install --mode=copy
 
 ## Local development
 
-A Fimo project is a standard Vite app — run it like any other:
+A Fimo project is a standard framework application. Run its normal package scripts:
 
 ```bash
 npm install

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

@@ -52,6 +52,7 @@ A project can have multiple **envs** — each is a git branch _plus_ its own DB,
 npx fimo@latest login                          # authenticate via browser
 npx fimo@latest skills install                 # install the global Fimo skill for your AI tools
 npx fimo@latest init my-site --org <id>        # one-stop setup: sign in, create/link a project, install deps + skills. Use the org **id** from `fimo orgs list`, NOT the slug.
+npx fimo@latest init my-next-site --framework nextjs --org <id>  # opt-in Next.js App Router scaffold
 npx fimo@latest init my-site --starter fimo-site@1 --org <id> --yes --no-skills  # opt-in content-led starter for a new project
 npx fimo@latest init --project-id <id> my-site # link an EXISTING project instead of creating one
 npx fimo@latest clone                          # interactively choose an existing project to clone locally

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

@@ -83,6 +83,7 @@ There is no all-capabilities wildcard; keeping the list explicit makes each agen
 | `fimo:logs:read`             | Read production logs                        | Low          |
 | `fimo:analytics:read`        | Read analytics data                         | Low          |
 | `fimo:preview:read`          | Read a current preview URL                  | Low          |
+| `fimo:history:read`          | Read project restore points                 | Low          |
 | `fimo:deploy`                | Trigger a production deploy                 | Critical     |
 | `net:fetch`                  | Make outbound HTTP requests                 | Medium       |
 | `agent:delegate`             | Invoke declared sub-agents                  | Medium       |

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

@@ -13,6 +13,8 @@ fimo history create "Before content migration"
 fimo history restore <version-id>
 ```
 
+Studio chat can run `history list` and `history show`. Create and restore remain available through the standalone CLI and Studio's History page.
+
 Use the global `--env <name>` option to target a different environment. Use `--project <id>` when there is no local `.fimo/project.json`.
 
 ## Pagination and usage

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

@@ -13,7 +13,7 @@ fimo init [dir] [options]
 `fimo init` runs the full onboarding in one shot:
 
 1. **Signs in automatically** — if there's no session it opens the browser loopback login. In `--json` / non-TTY with no session it fails with `NOT_AUTHENTICATED` (run `fimo login` first).
-2. **Resolves the project** — with `--project-id <id>` it links an EXISTING project (clones it); without it, it creates a NEW project. An interactive TTY shows a "Create new / Link existing" picker; non-interactive shells default to create-new. An optional `--starter fimo-site@1` adds a content-led starter only to a newly created project.
+2. **Resolves the project** — with `--project-id <id>` it links an EXISTING project (clones it); without it, it creates a NEW project. An interactive TTY shows a "Create new / Link existing" picker; non-interactive shells default to create-new. New projects use React Router by default; `--framework nextjs` selects the minimal Next.js App Router scaffold. An optional `--starter fimo-site@1` adds a React-Router content starter only to a newly created project.
 3. **Installs dependencies** — prompts for the package manager, or honor `--package-manager <pm>` / `--no-install`.
 4. **Optionally sets up Fimo skills** — confirm prompt, or `--skills` / `--no-skills`.
 
@@ -23,6 +23,7 @@ fimo init [dir] [options]
 | `--project-id <id>`          | no                            | Link an EXISTING project instead of creating one (clones it).                                                                                                  |
 | `--org <id>`                 | no                            | Target organization **id** when creating (use the `ID` column from `fimo orgs list`, NOT the slug). Picker shown interactively if omitted and TTY.             |
 | `--env <name>`               | no                            | Env to check out when linking an existing project (defaults to `main`).                                                                                        |
+| `--framework <framework>`    | no                            | New-project scaffold: `react-router` (default) or `nextjs` (App Router). Existing repositories are preserved.                                                  |
 | `--starter <id>`             | no                            | Opt-in project starter for create-new (currently `fimo-site@1`). It seeds CMS content, labels, a contact form, and manual-only agents. Rejects `--project-id`. |
 | `--package-manager <pm>`     | no                            | `npm` \| `pnpm` \| `yarn` \| `bun`.                                                                                                                            |
 | `--install` / `--no-install` | yes in non-TTY                | Install deps after checkout (or skip it).                                                                                                                      |
@@ -60,6 +61,21 @@ writing anything. If dependencies were skipped, install them and run
 
 > **Zero-install:** run `npx fimo@latest init` — no global install needed. `fimo projects create` is also an alias of `fimo init` (create-new path).
 
+### Choose the application framework
+
+Omit `--framework` for the existing React Router scaffold, or select the
+minimal Next.js App Router shell explicitly:
+
+```bash
+npx fimo@latest init my-next-site --framework nextjs --org <organizationId>
+```
+
+The Next scaffold includes `src/app`, `FimoProvider`, the hosted-preview config,
+and `.fimo/config.json#runtime.framework`. It intentionally contains no schema,
+labels, or designed website. After init, load the project rules and `fimo-code`
+to build the requested site. The current `fimo-site@1` content starter supports
+React Router only.
+
 For `--agents`, pass the AI tool you're running in: `--agents=claude-code` for Claude Code, `--agents=cursor` for Cursor, `--agents=codex` for Codex, etc. When the flag is omitted, env-var detection of the invoking harness (e.g. `CLAUDECODE` / `CLAUDE_CODE_ENTRYPOINT` → claude-code) auto-targets that agent; other agents must be selected explicitly via `--agents`/`-a` or the interactive picker.
 
 ## Linking an existing project
@@ -70,7 +86,7 @@ Pass `--project-id <id>` to link an EXISTING project instead of creating one. Th
 
 `fimo init` (create-new path) scaffolds:
 
-- The project template (Vite + React 19 + TypeScript + Tailwind v4 + shadcn/ui + react-router)
+- The selected project shell: React Router by default, or Next.js App Router with `--framework nextjs`
 - `.fimo/project.json` — links this directory to the remote project (read-only after creation)
 - `.fimo/config.json` — project, route, locale, SEO, and agent policy
 - `.fimo/agents/` — versioned agent bundles

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

@@ -15,6 +15,8 @@ fimo locales set-default es --yes --json
 fimo locales remove es --yes --json
 ```
 
+Studio chat can run `locales list`. Manage the locale lifecycle through Studio Settings or the standalone CLI.
+
 These commands update the selected environment through the locale lifecycle API. The API commits `.fimo/config.json` to the Fimo branch, then the CLI synchronizes the **whole local branch** to that commit. They refuse a dirty config, a local-ahead branch, or a diverged branch before applying the remote change. `--yes` bypasses only the explanatory prompt.
 
 If a mutation exits with code `2` and `data.code` is `LOCALE_APPLIED_SYNC_REQUIRED`, the remote operation succeeded (`data.applied` is `true`) but the local fast-forward did not. **Do not retry the locale command.** Run the commands in `data.sync.recovery`, resolve the checkout, and confirm with `fimo status` or `fimo locales list`.

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

@@ -8,7 +8,7 @@ Commands for listing projects across an org, cloning a remote project locally, a
 
 ```bash
 fimo projects list [--org <id>]                 # list projects in an org (defaults to active org)
-fimo projects create [dir] [--org <id>] [--install|--no-install]   # alias of `fimo init` (create-new path)
+fimo projects create [dir] [--org <id>] [--framework react-router|nextjs] [--install|--no-install]
 fimo projects clone [projectId] [dir] [--env <name>] # clone an existing project locally
 fimo projects delete [projectId] [-C <dir>] [-y] # delete (defaults to current project)
 fimo projects publish [projectId] [-C <dir>]     # make the project live (publish from main)

package/assets/skills/fimo-code/references/frameworks/next/locales.md

@@ -35,7 +35,7 @@ When labels are not needed at that boundary, use `<FimoProvider locale={locale}>
 
 With `next-i18next`, keep its routing and translation provider for the strings it owns. Pass the same resolved locale to Fimo; do not replace the library or duplicate its route structure.
 
-Before creating non-default Fimo labels or content variants, confirm that those locales are enabled for the linked Fimo project. `.fimo/config.json` documents the application's locale policy, but `fimo validate` does not currently add project locales.
+Before creating non-default Fimo labels or content variants, confirm that those locales are enabled for the linked Fimo project. Load `fimo-cli` with its `locales` reference and run `fimo locales add <locale> --yes --json`; `.fimo/config.json` documents the application's locale policy, but `fimo validate` does not add project locales.
 
 ## Ownership boundary
 

package/assets/skills/fimo-code/references/frameworks/react-router.md

@@ -1,7 +1,7 @@
 # Setup Fimo on React Router 8
 
 This recipe describes the canonical Fimo + React Router framework-mode setup.
-It mirrors what `fimo init` scaffolds today; you can also apply it to an
+It mirrors the default `fimo init` scaffold; you can also apply it to an
 existing RR project.
 
 ## Prerequisites

package/assets/skills/fimo-code/references/locales.md

@@ -15,7 +15,7 @@ The application owns locale resolution and routing. Fimo consumes the resolved l
 
 Keep one locale unless the product asks for multilingual output. Locale tags should be structurally valid, such as `en`, `pt-BR`, or `zh-Hans`.
 
-For an already linked project, the same locales must also be enabled in Fimo before writing non-default label or content variants. Local config and `fimo validate` do not currently provision project locales. If the API says a locale is not configured, enable it in Fimo Studio; do not change the application's route strategy to work around it.
+For an already linked project, enable each locale in Fimo before writing non-default label or content variants. Load `fimo-cli` with its `locales` reference and run `fimo locales add <locale> --yes --json`; local config and `fimo validate` do not provision project locales. Do not change the application's route strategy to work around a missing locale.
 
 ## Application responsibilities
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-13T17:07:37.274Z",
+  "bundledAt": "2026-08-14T07:57:59.355Z",
   "cliVersion": "0.13.0",
   "external": [
     "oxc-parser",