fimo 2.2.0-staging.7 → 2.2.0-staging.9

package/assets/agent-templates/_default/config.yaml

@@ -2,5 +2,6 @@
 # See https://fimo.dev/docs/agents/bundle for the full reference.
 version: 1
 description: 'A new Fimo agent. Edit this tagline to describe what it does.'
+model: openai/gpt-5.6-luna
 triggers:
   - type: manual

package/assets/agent-templates/broken-link-sweeper/config.yaml

@@ -1,5 +1,6 @@
 version: 1
 description: 'Crawl the published site and flag broken outbound links in a weekly report.'
+model: openai/gpt-5.6-luna
 
 runtime:
   cloud: true

package/assets/agent-templates/content-translator/config.yaml

@@ -1,5 +1,6 @@
 version: 1
 description: 'Translate CMS content into the project locales whenever an entry is published.'
+model: openai/gpt-5.6-luna
 data_sources:
   - main
 

package/assets/agent-templates/post-deploy-check/config.yaml

@@ -1,5 +1,6 @@
 version: 1
 description: 'Probe routes and inspect logs after a deploy; report any issues to email recipients.'
+model: openai/gpt-5.6-luna
 data_sources:
   - prod
 

package/assets/agent-templates/seo-audit/config.yaml

@@ -1,5 +1,6 @@
 version: 1
 description: "Audit the project's pages for SEO health and write a markdown report."
+model: openai/gpt-5.6-luna
 # Read from main env. Switch to prod when running the audit against the
 # live site (M13 keeps data_sources here so M16's sandbox adapter can
 # bind the right Fimo API base URL).

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

@@ -40,6 +40,7 @@ fimo agents secrets remove <name> <KEY> [-C <dir>]
 
 - **`list-templates`** — list the bundled starter templates with the first line of each template's `GOAL.md` as a summary. Ships with the CLI binary; no API call. The five bundled templates are `_default`, `seo-audit`, `content-translator`, `broken-link-sweeper`, `post-deploy-check`.
 - **`create <name>`** — scaffold `.fimo/agents/<name>/` from a template (default `_default`, a minimal valid bundle with a manual trigger). `--description <text>` writes a one-line tagline into the scaffolded `config.yaml` (surfaces in the dashboard's agents list). When run **without** `-C`, it requires the cwd to be inside a real Fimo project (walks up for `.fimo/project.json` or legacy `.fimo.settings.json`) and errors out cleanly otherwise, so it never leaks an agent bundle into a stray cwd. If the template declares capabilities, an install-consent flow runs after the copy (`--quiet` skips it; critical caps still abort).
+- Every generated `config.yaml` includes `model: openai/gpt-5.6-luna`. Change that top-level value to another supported Fimo text model when needed; bundles without `model` keep the Luna fallback. Deploy after changing it because cloud runs use the deployed bundle.
 - **`list`** — list the agents declared under `<project>/.fimo/agents/` (or legacy root `agents/`), with each one's trigger types and capability count. Local — the bundle list is the source of truth even if the project isn't linked yet.
 - **`validate [name]`** — run the full validation pipeline: parse → capability vocabulary → composition (cycle / missing sub-agents / invalid grants) → semantic + Fimo project config policy checks. Omit `name` to validate every bundle. `--json` emits a structured `ValidationReport` for CI; exit code is non-zero on any failure.
 - **`secrets add/remove/list`** — edit or inspect the agent's requested secret names in `.fimo/agents/<name>/config.yaml` (or legacy root). These commands do not create, rotate, or reveal secret values. Store values with `fimo secrets add`; run `fimo agents validate` to check that required requested secrets exist in the project. See `references/project-vars-and-secrets.md`.
@@ -241,7 +242,7 @@ Example for a content editor that can read and update entries but cannot change
 
 ```bash
 fimo agents run <name> [--branch <branch>] [--project <id>] [--skip-drift-check] [-C <dir>]
-fimo agents runs <name> [--limit <n>] [--branch <branch>] [--project <id>] [-C <dir>]
+fimo agents runs <name> [--limit <n>] [--cursor <cursor>] [--all-pages] [--branch <branch>] [--project <id>] [-C <dir>]
 fimo agents report <name> [--session <id>] [--branch <branch>] [--project <id>] [-C <dir>]
 fimo agents logs <name> [--session <id>] [--project <id>] [-C <dir>]
 ```

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

@@ -96,9 +96,12 @@ fimo assets list --search "wolf"
 fimo assets list --search "hero" --image
 fimo assets list --search "logo" --type file --sort-by createdAt
 
-fimo assets list --limit 50 --offset 0                    # paging
+fimo assets list --limit 50 --cursor <next-cursor>        # next page
+fimo assets list --all-pages                              # every remaining page
 ```
 
+The response includes `nextCursor` when another page exists. Keep the same filters when continuing. `--offset` remains a compatibility alias for existing scripts.
+
 The `--search` query matches:
 
 - `name` (file name)

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

@@ -69,7 +69,7 @@ Use singular commands for one entry. Bulk create and per-entry bulk update also
 ```bash
 fimo entries create <TypeName> --body '<json>'
 fimo entries create <TypeName> --locale es --document-id <documentId> --body '<json>'
-fimo entries list <TypeName> [--limit N] [--offset N] [--search Q] [--where JSON] [--sort F] [--fields FIELDS] [--populate FIELDS]
+fimo entries list <TypeName> [--limit N] [--cursor CURSOR] [--all-pages] [--search Q] [--where JSON] [--sort F] [--fields FIELDS] [--populate FIELDS]
 fimo entries list <TypeName> --locale es
 fimo entries get <TypeName> <id> [--locale es]
 fimo entries update <TypeName> <id> [--locale es] --body '<json>'
@@ -90,12 +90,12 @@ fimo entries list BlogPost --where '{"featured":true}' --sort -publishedAt
 fimo entries list BlogPost --where '{"rank":{"$gte":3}}' --sort rank
 fimo entries list BlogPost --where '{"__fimo":{"contentType":{"$eq":"BlogPost"}}}'
 fimo entries list BlogPost --search "launch"
-fimo entries list BlogPost --limit 10 --offset 20 --sort title
+fimo entries list BlogPost --limit 10 --cursor <next-cursor> --sort title
 fimo entries list BlogPost --fields slug,title,excerpt,coverImage --sort -publishedAt --limit 12
 fimo entries list BlogPost --fields slug,title,author --populate author
 ```
 
-Use the canonical read query flags: `--search`, `--sort`, `--where`, `--limit`, `--offset`, `--fields`, and `--populate`.
+Use the canonical read query flags: `--search`, `--sort`, `--where`, `--limit`, `--cursor`, `--all-pages`, `--fields`, and `--populate`. `--offset` remains a compatibility alias for existing scripts.
 `--where` is a JSON object keyed by schema field name. Simple values mean equality and stay typed inside the JSON (`{"featured":true}`, `{"category":"react"}`, `{"rank":{"$gte":3}}`); operator objects support `$eq`, `$ne`, `$gt`, `$gte`, `$lt`, `$lte`, `$in`, `$nin`, `$contains`, `$startsWith`, and `$null`, subject to the field type. Public Fimo-owned metadata lives under `__fimo`; currently `__fimo.contentType` is filterable.
 
 Reference filters take the target `id` string (`{"author":"750e..."}`). On a to-many field, `$eq` and `$contains` mean membership, `$in` means any listed target is present, `$ne` and `$nin` mean none are present, and `$null: true` means empty or missing. Reference fields cannot be sorted; use `--sort field` / `--sort -field` on scalar fields.

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

@@ -50,11 +50,11 @@ Public project variables managed with `fimo vars add` and `fimo vars update` are
 
 ## Diagnose a failed publication
 
-Use the publication ID returned by the failed command: run `fimo publish inspect <id> --json` for its durable status, then `fimo publish logs <id> --json` for a bounded build-log tail. Logs come from the hosting provider and may be unavailable after its deployment is reclaimed.
+Use the publication ID returned by the failed command: run `fimo publish inspect <id> --json` for its durable status, then `fimo publish logs <id> --json` for a bounded build-log tail. Use `fimo publish list --cursor <cursor>` to continue through older attempts or `--all-pages` to fetch the complete retained history. `--before` remains a compatibility alias. Logs come from the hosting provider and may be unavailable after its deployment is reclaimed.
 
 ## Diagnose a failed preview deploy
 
-If the sandbox fails to install dependencies or start the app, run `fimo logs --json` before retrying. Read the newest install and dev-server events first; when the response is truncated, use its `previousCursor` as `fimo logs --before <cursor> --json` to fetch the preceding page. Do not recreate or replace the sandbox before collecting logs, because that can discard the failure evidence.
+If the sandbox fails to install dependencies or start the app, run `fimo logs --json` before retrying. Read the newest install and dev-server events first; when the response is truncated, use its `previousCursor` as `fimo logs --cursor <cursor> --json` to fetch the preceding page, or use `--all-pages` to fetch every retained page. `--before` remains a compatibility alias. Do not recreate or replace the sandbox before collecting logs, because that can discard the failure evidence.
 
 When Preview reports blocked dependency build scripts, treat that as a project security-policy repair, not a transient sandbox failure. Review every named package before approving it, then use the package manager's narrow project-owned mechanism:
 

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

@@ -29,11 +29,13 @@ Notification recipients for form submissions are configured in the Fimo web UI,
 After a form is live and users have filled it out, inspect submissions from the terminal:
 
 ```bash
-fimo forms submissions list <formIdOrName> [--limit 50] [--offset 0] [--search "<q>"] [--sort asc|desc]
+fimo forms submissions list <formIdOrName> [--limit 50] [--cursor CURSOR] [--all-pages] [--search "<q>"] [--sort asc|desc]
 fimo forms submissions get  <formIdOrName> <submissionId>
 fimo forms submissions stats <formIdOrName>
 ```
 
+The list response includes `nextCursor` when another page exists. `--offset` remains a compatibility alias for existing scripts.
+
 - `<formIdOrName>` accepts either the form's UUID or its `name` (the same name in the JSON file). Names that don't resolve to exactly one form return an error.
 - `list` returns `{ data: [...], total }`. Newest-first by default; pass `--sort asc` to reverse.
 - `search` matches against submission contents server-side.

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

@@ -28,6 +28,7 @@ there is no local `.fimo/project.json`.
 
 ```bash
 fimo history list --limit 20 --cursor <cursor>
+fimo history list --all-pages
 ```
 
 The list also reports compressed snapshot usage and the current retention period. Restore points expire after 14 days on Free and pay-as-you-go plans, or 90 days on Premium. The expiry is fixed when each point is created.

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

@@ -22,7 +22,7 @@ fimo schedules resume <schedule>
 fimo schedules run <schedule>
 fimo schedules run <schedule> --no-wait
 fimo schedules runs <schedule> --limit 25 --status failed
-fimo schedules runs <schedule> --all
+fimo schedules runs <schedule> --all-pages
 fimo schedules runs show <run-id>
 fimo schedules delete <schedule>
 ```
@@ -59,9 +59,11 @@ Run history is cursor-paginated:
 fimo schedules runs nightly --limit 50
 fimo schedules runs nightly --cursor <cursor>
 fimo schedules runs nightly --status succeeded
-fimo schedules runs nightly --all
+fimo schedules runs nightly --all-pages
 ```
 
+`--all` remains a compatibility alias for existing scripts.
+
 Run detail includes status, timing, trigger, exit/error information, retained output, output retention metadata, and secret snapshot metadata. Output is capped and redacted before it is returned.
 
 ## JSON

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

@@ -121,6 +121,8 @@ fimo webhooks list
 fimo webhooks get <webhook-id>
 fimo webhooks test <webhook-id> --wait
 fimo webhooks deliveries <webhook-id> --limit 20
+fimo webhooks deliveries <webhook-id> --cursor <next-cursor>
+fimo webhooks deliveries <webhook-id> --all-pages
 fimo webhooks delivery <webhook-id> <delivery-id>
 ```
 

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

@@ -8,7 +8,15 @@ Once in edit mode, click on any element in the preview -- text, buttons, images,
 
 ### Editing Content
 
-For text elements, the side panel shows editable fields where you can change the text directly. This covers CMS-managed content, hardcoded text, and hardcoded images. Changes save automatically, and the preview updates as you type.
+For text elements, the side panel opens the selected field immediately with its current value. This covers CMS-managed content, hardcoded text, and hardcoded images. Changes save automatically, and the preview updates as you type.
+
+For CMS content, choose **All fields** 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.
+
+### References and Components
+
+Selecting a field rendered from a referenced entry edits that entry. For example, selecting an author's name opens the Author entry, not the Post relation that links to it. The header shows the relation path. Select the owning entry in that path to return to its complete form with the relation field focused; use that relation field to open, replace, or clear the linked entry.
+
+Selecting a field inside a component focuses that nested field. Choose **All fields** to see it in the complete entry form without moving it out of schema order. The shared CMS form provides the existing add, duplicate, remove, and reorder controls for repeatable components and blocks.
 
 ### Editing Styles
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-08-27T09:44:07.414Z",
+  "bundledAt": "2026-08-27T16:29:36.581Z",
   "cliVersion": "2.1.0",
   "external": [
     "oxc-parser",