fimo 0.11.0-staging.2 → 0.11.0-staging.4

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

@@ -34,6 +34,8 @@ The command is `fimo schemas` (plural). There is no singular `fimo schema` alias
 
 All commands accept `-C, --cwd <dir>` to point at a different project directory.
 
+Blocks schemas support at most 7 nested `blocks` levels, 40 variants in one `schema.oneOf`, and `min` or `max` values up to 200 items per blocks field. Load `fimo/references/content.md` for the complete blocks JSON shape.
+
 Schema transitions are automatic. Adding optional fields and changing labels preserve content. A new required field backfills its `default` only where existing values need it; the push fails safely when no default can satisfy existing content. Removing a nested field or block variant removes only those values. `string` and `text` preserve values in both directions. Other primitive changes convert safe values and reject unsafe ones without changing the schema or entries. Lowering block `max` trims from the end; raising `min` fills from the blocks `default` templates. A reference target change clears its connections. Use repeatable `--rename old.path=new.path` arguments when a field moved by name so the one-time migration preserves its values; the operation is not stored in schema JSON. Collection-to-Single removes that type's entries and cleans inbound references; Single-to-collection preserves its entry. Run `fimo validate` after pushing.
 
 ## Singles CLI commands

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

@@ -163,6 +163,7 @@ A field may declare `showIf` (every clause must match) or `showIfAny` (one claus
 
 - `blocks.schema.fields` repeats one homogeneous shape.
 - `blocks.schema.oneOf` lets the editor choose exactly one variant per item.
+- Blocks schemas support at most 7 nested `blocks` levels, 40 variants in one `schema.oneOf`, and `min` or `max` values up to 200 items per blocks field.
 - Blocks always read and write arrays. A field with `max: 1` is `[]` or `[item]`, never a bare object.
 - `min` and `max` constrain the total number of blocks. Use `min: 1` to require at least one block; `required: true` has the same minimum-one behavior.
 - Fimo creates a stable `_key` for each item. A `oneOf` item also carries `_type`, matching the variant `uid`.

package/assets/skills/fimo-code/references/setup-plain-vite.md

@@ -90,11 +90,11 @@ The `seo` plugin rewrites `<title>`, og, twitter, canonical tags from
 
 ## File: `src/main.tsx`
 
-`FimoProviders` (and the runtime primitives it wraps) require **two** contexts:
-a React Router `<Router>` ancestor (it reads `useLocation`/`useNavigate`) and a
-`@tanstack/react-query` `<QueryClientProvider>` (its internal
-`RefreshContentProvider` calls `useQueryClient`). Mount both around
-`<FimoProviders>`:
+`FimoProviders` requires a React Router `<Router>` ancestor (it reads
+`useLocation`/`useNavigate`). It reuses a host app's
+`@tanstack/react-query` client when one exists and supplies a stable fallback
+for adopted SPAs. This recipe still mounts an explicit provider so the app owns
+the shared cache and its configuration:
 
 ```tsx
 import { FimoProviders } from 'fimo/react-router';
@@ -122,8 +122,9 @@ createRoot(document.getElementById('root')!).render(
 
 `react-router` and `@tanstack/react-query` are peer dependencies of `fimo`;
 both are in the install command above. `FimoProviders` is exported only from
-the `fimo/react-router` adapter barrel — there is no router-free (or
-react-query-free) provider surface in the package today.
+the `fimo/react-router` adapter barrel. Keep the explicit QueryClientProvider
+when the app needs custom query defaults or shared cache access; adopted SPAs
+can omit it.
 
 ## File: `src/App.tsx`
 

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

@@ -100,6 +100,11 @@ when to render them, and how.
 
 ## File: `src/root.tsx`
 
+The explicit `QueryClientProvider` below is the canonical template shape so the
+app can configure query defaults such as `staleTime`. Adopted SPAs can omit it:
+`FimoProviders` reuses an ancestor client when present and supplies a stable
+fallback otherwise.
+
 ```tsx
 import { QueryClient, QueryClientProvider } from '@tanstack/react-query';
 import { FimoProviders, FimoScripts, loadFimoMetaData, buildFimoMeta, fimoHtmlProps } from 'fimo/react-router';

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

@@ -9,6 +9,12 @@ The AI chat opens as a floating panel by default. You can dock it to the left or
 3. Press **Enter** or click the **send button**.
 4. The AI responds in a stream. You see tool status badges appear as it works, and the preview updates automatically.
 
+## Responding to Choices and Forms
+
+The AI can place choices, cards, tables, images, and contextual actions directly in its reply. Optional suggestions do not interrupt the conversation.
+
+When the AI needs an answer before it can continue, it shows a form in the chat and waits for your response. Complete the form for a structured answer, or reply normally in the chat to answer in your own words.
+
 ## Attaching Context
 
 Give the AI more to work with:
@@ -37,9 +43,9 @@ While the AI works, you see small badges in the chat showing what it is doing. E
 
 Chat changes are prepared separately and then applied to the environment you are viewing. Most changes merge automatically.
 
-If the project changed in the same place while the AI was working, the response shows a **Review changes** card instead. Open it to inspect the proposal, resolve any conflicts, and merge when it is ready. Until you merge it, the proposal is not part of the environment and later chat messages will not see it.
+If the project changed in the same place while the AI was working, the response shows a **Review changes** card and an attention banner above the chat input. The banner remains visible when floating chat history is collapsed.
 
-Discarding the merge leaves the current environment unchanged and keeps the proposal separate.
+Choose **Auto fix** or keep chatting to let Fimo continue in the retained proposal, resolve the conflict, and retry the merge. Choose **Review manually** to inspect and resolve the proposal yourself. Discarding leaves the current environment unchanged and permanently removes the proposal.
 
 ## Tips for Better Results
 

package/assets/skills/fimo-studio/references/publish-and-deploy.md

@@ -14,7 +14,7 @@ Every change you make is automatically saved to your project, but saved changes
 
 To push your latest changes live, open the publish panel from the header **Publish** button and click **Publish** inside it again. It redeploys with your latest code and content.
 
-> **Tip:** Before your site has ever been published, the chat shows a one-click **Publish** button that deploys immediately without opening the panel.
+> **Tip:** After completing relevant work, the AI may offer a one-click **Publish** callout in chat. It appears only when publishing is available; the header **Publish** control remains the reliable path at any time.
 
 ## Publishing Changes That Need Review
 
@@ -29,6 +29,7 @@ The header **Publish** button itself only shows the label "Publish" (or a spinne
 - **"Not published yet"** — Your site has never been published. The **Publish** button inside the panel is ready to click.
 - **"Publishing"** — Publishing is in progress. A spinner and a **Publishing** status badge show while it builds, and the button is disabled.
 - **"Published"** — Your site is live. A **Published** status badge appears, your live URL is listed under a **Published site** heading as a clickable link, and a **Last published** date and time is shown.
+- **"Couldn't publish · N issues"** — Project validation found issues that must be fixed first. Choose **Fix with Fimo** to send the safe issue list to the project chat and ask Fimo to repair it.
 
 ## Key Concepts
 

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-07-30T16:52:56.741Z",
+  "bundledAt": "2026-08-02T09:47:16.199Z",
   "cliVersion": "0.10.0",
   "external": [
     "oxc-parser",