fimo 0.8.0 → 0.9.0-staging.1

package/dist/runtime/content/client/createContentClient.js

@@ -100,10 +100,11 @@ export function createContentClient(config) {
         return (await list(params)).items;
     }
     async function create(payload) {
+        const localizedPayload = info.localized ? withMutationLocale(payload, readCollectionLocale({})) : payload;
         const res = await fetch(`${apiBase()}/entries/${info.uid}`, {
             method: 'POST',
             headers: fimoHeaders({ 'Content-Type': 'application/json' }),
-            body: JSON.stringify(splitWritePayload(payload)),
+            body: JSON.stringify(splitWritePayload(localizedPayload)),
         });
         if (!res.ok) {
             throw new Error(await res.text());

package/dist/runtime/content/client/internal.js

@@ -179,6 +179,7 @@ function wrapReference(value, uid, resolve) {
 function wrapField(field, value, source, resolve) {
     switch (field.type) {
         case 'string':
+        case 'text':
             return value != null ? new FimoString(value, source) : value;
         case 'richtext':
             return value != null ? new FimoRichText(value, source) : value;

package/dist/runtime/content/client/types.d.ts

@@ -18,6 +18,7 @@ export type ContentResult<T extends {
 export interface ContentSchemaField {
     type?: string;
     required?: boolean;
+    default?: unknown;
     /** Media fields: multiple assets. */
     multiple?: boolean;
     /** Reference fields: to-many. */
@@ -26,6 +27,21 @@ export interface ContentSchemaField {
     target?: string;
     /** Polymorphic reference fields: allowed target schema uids. */
     targets?: readonly string[];
+    min?: number;
+    max?: number;
+    minLength?: number;
+    maxLength?: number;
+    regex?: string;
+    schema?: {
+        fields: Readonly<Record<string, ContentSchemaField>>;
+    } | {
+        oneOf: readonly {
+            uid: string;
+            label: string;
+            description?: string;
+            fields: Readonly<Record<string, ContentSchemaField>>;
+        }[];
+    };
 }
 export interface ContentSchema {
     uid: string;

package/dist/scripts/validate-schemas.js

@@ -1,6 +1,6 @@
 import { existsSync, readFileSync, readdirSync } from 'node:fs';
 import { basename, join, resolve } from 'node:path';
-import { CONTENT_FIELD_NAME_PATTERN, CONTENT_FIELD_NAME_PATTERN_DESCRIPTION, CONTENT_TYPE_NAME_PATTERN, CONTENT_TYPE_NAME_PATTERN_DESCRIPTION, FieldTypeSchema, RESERVED_CONTENT_FIELD_NAMES, } from '@fimo/api-contracts';
+import { CONTENT_FIELD_NAME_PATTERN, CONTENT_FIELD_NAME_PATTERN_DESCRIPTION, CONTENT_TYPE_NAME_PATTERN, CONTENT_TYPE_NAME_PATTERN_DESCRIPTION, ContentFieldDefinitionSchema, FieldTypeSchema, MAX_STRUCTURED_CONTENT_DEPTH, RESERVED_CONTENT_FIELD_NAMES, walkContentFields, } from '@fimo/api-contracts';
 /**
  * Validate `src/schemas/*.json` locally against the same rules the API's
  * schema validator enforces (field types, reserved field names, required
@@ -169,6 +169,47 @@ export function validateSchemaFile(absolutePath, file, schemaUids = new Set()) {
                 file,
             });
         }
+        if (type === 'blocks') {
+            const parsed = ContentFieldDefinitionSchema.safeParse(definition);
+            if (!parsed.success) {
+                for (const issue of parsed.error.issues) {
+                    errors.push({
+                        rule: 'schemas/structured-content-shape',
+                        message: `Field "${fieldName}"${issue.path.length > 0 ? ` at ${issue.path.join('.')}` : ''}: ${issue.message}`,
+                        file,
+                    });
+                }
+                continue;
+            }
+            walkContentFields({ [fieldName]: parsed.data }, ({ field, path, structuredDepth, insideStructuredContent }) => {
+                if (field.type === 'blocks' && structuredDepth >= MAX_STRUCTURED_CONTENT_DEPTH) {
+                    errors.push({
+                        rule: 'schemas/structured-content-depth',
+                        message: `Field "${path.join('.')}" exceeds the ${MAX_STRUCTURED_CONTENT_DEPTH}-level blocks limit.`,
+                        file,
+                    });
+                }
+                if (!insideStructuredContent || field.type !== 'reference') {
+                    return;
+                }
+                if (field.targets) {
+                    errors.push({
+                        rule: 'schemas/structured-content-reference',
+                        message: `Reference field "${path.join('.')}" must use one fixed "target" inside blocks.`,
+                        file,
+                    });
+                    return;
+                }
+                if (field.target && schemaUids.size > 0 && !schemaUids.has(field.target)) {
+                    errors.push({
+                        rule: 'schemas/reference-target',
+                        message: `Reference field "${path.join('.')}" targets unknown schema "${field.target}".`,
+                        file,
+                    });
+                }
+            });
+            continue;
+        }
         if (type === 'reference') {
             const { target, targets, many } = definition;
             if (targets !== undefined && target !== undefined) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fimo",
-  "version": "0.8.0",
+  "version": "0.9.0-staging.1",
   "description": "Fimo CLI - create, deploy, and manage Fimo projects",
   "bin": {
     "fimo": "dist/cli/index.js"

package/release.json

@@ -1,5 +1,5 @@
 {
   "source": "npm",
-  "apiUrl": "https://api.fimo.ai",
-  "webUrl": "https://fimo.ai"
+  "apiUrl": "https://api.staging.fimo.team",
+  "webUrl": "https://staging.fimo.team"
 }

package/scripts/postinstall.mjs

@@ -1,39 +1,17 @@
 #!/usr/bin/env node
-// Two paths:
+// GLOBAL install (`npm i -g fimo`, `pnpm add -g fimo`, etc.)
+//   → print a short, non-blocking hint. We steer users toward `npx fimo@latest`
+//     (always current) and `fimo init`, and don't run any interactive prompt
+//     from a package lifecycle script.
 //
-//  1) GLOBAL install (`npm i -g fimo`, `pnpm add -g fimo`, etc.)
-//     → print a short, non-blocking hint. We steer users toward
-//       `npx fimo@latest` (always current) and `fimo init`, and don't run any
-//       interactive prompt from a package lifecycle script.
-//
-//  2) LOCAL / project install (`pnpm install` in a project that has `fimo`
-//     in its dependencies)
-//     → if the install was inside a Fimo project (`.fimo.settings.json`
-//       found by walking up from `INIT_CWD`), re-sync the project-scope
-//       `fimo` skill into every per-agent dir the project is set up for.
-//       The skill source is `node_modules/fimo/assets/skills/fimo/`, version-
-//       locked to the installed package.
-//
-//       Silent on no-op; non-fatal on any failure (a skill copy must
-//       never break the user's install).
-//
-// pnpm caveat: by default, pnpm strips build scripts from non-approved deps.
-// Fimo-controlled installs (`fimo init --install`, sandbox `fimopm install`,
-// and E2E helper installs) pass a scoped allow-all-builds flag for pnpm so the
-// fimo postinstall hook can refresh project skills. The template intentionally
-// does not persist allowlists in package.json / pnpm-workspace.yaml because
-// those conflict with sandbox install flags and drift when deps change. npm /
-// yarn run lifecycle scripts by default and need no extra config.
-
-import fs from 'node:fs';
-import path from 'node:path';
-import { fileURLToPath } from 'node:url';
+// LOCAL / project install (`pnpm install` in a project that depends on `fimo`)
+//   → nothing to do. Fimo no longer writes skills into projects: the only skill
+//     is a tiny global `fimo` bootstrap installed by `fimo skills install`, and
+//     the rich skills are fetched on demand via `fimo skills get`. Keeping this
+//     path a no-op means `pnpm install` never touches the working tree.
 
 import { isGlobalInstall } from './lib/postinstall-onboarding.mjs';
 
-const THIS_FILE = fileURLToPath(import.meta.url);
-const CLI_ROOT = path.resolve(path.dirname(THIS_FILE), '..');
-
 const ESC = String.fromCharCode(27);
 const green = (s) => `${ESC}[32m${s}${ESC}[0m`;
 const bold = (s) => `${ESC}[1m${s}${ESC}[0m`;
@@ -49,40 +27,8 @@ if (isGlobalInstall(process.env)) {
   console.log();
   console.log(`  Get started:`);
   console.log(`       ${cyan('fimo init')}            ${dim('# sign in, create or link a project')}`);
-  console.log(`       ${cyan('fimo skills install')}  ${dim('# set up skills for your AI coding tools')}`);
+  console.log(`       ${cyan('fimo skills install')}  ${dim('# set up Fimo skills for your AI coding tools')}`);
   console.log();
-  process.exit(0);
 }
 
-// Project-install path: dynamic-import the built helper and re-sync the
-// project-scope `fimo` skill if we resolve to a Fimo project root.
-// Skipped silently when:
-//   - The CLI hasn't been built yet (workspace dev install before `pnpm build`)
-//   - `INIT_CWD` isn't inside a Fimo project (helper returns 'not-a-fimo-project')
-//   - The project has no per-agent rule files yet (helper returns 'no-agents')
-const helperPath = path.join(CLI_ROOT, 'dist', 'cli', 'project-skill.js');
-if (!fs.existsSync(helperPath)) {
-  process.exit(0);
-}
-
-try {
-  const { syncProjectFimoSkill } = await import(helperPath);
-  const initCwd = process.env.INIT_CWD ?? process.cwd();
-  const result = await syncProjectFimoSkill({ cwd: initCwd });
-
-  if (result.status === 'installed' && !result.skillSourceMissing) {
-    const skillDest =
-      result.agents.length === 1 ? result.agents[0] : `${result.agents.length} agents (${result.agents.join(', ')})`;
-    console.log(`${green('✓')} fimo skill synced for ${skillDest}`);
-    for (const failure of result.failures) {
-      console.error(`  ! fimo skill failed for ${failure.agent}: ${failure.error}`);
-    }
-  }
-  // Other statuses (not-a-fimo-project, no-agents, skill-source-missing)
-  // are silent — they're expected for non-Fimo deps and pre-create installs.
-} catch (err) {
-  // Never break the user's install over a skill-sync failure.
-  if (process.env.FIMO_DEBUG_POSTINSTALL === '1') {
-    console.error('[fimo postinstall] sync failed:', err);
-  }
-}
+process.exit(0);

package/templates/react-router/AGENTS.md

@@ -0,0 +1,44 @@
+# Fimo project
+
+This is a Fimo project — a content + media + forms + analytics platform for React websites with a CMS
+dashboard. Fimo owns everything after the build: content, editing, environments, and hosting stay
+editable by the whole team.
+
+## Load the Fimo skills before doing Fimo work
+
+Fimo ships its skills through its CLI so they always match this project's installed version. Before
+writing schema-driven code, running CLI/deploy workflows, or migrating content, load the relevant skill:
+
+```bash
+npx fimo@latest skills list          # what's available
+npx fimo@latest skills get fimo-code  # writing code: schemas, forms, labels, fimo/ui
+npx fimo@latest skills get fimo-cli   # CLI + workflows: push, deploy, sync, labels, domains
+```
+
+Add `--ref <doc>` for a skill's reference docs. Always fetch fresh from the CLI rather than trusting a
+cached copy.
+
+## Critical: never hardcode user-facing things
+
+Fimo's whole point is that editors change content in the dashboard, not in code. Anything hardcoded
+breaks that. Load `fimo-code` for the exact primitives, but the rule is:
+
+- **Content** → declare a schema, render with the generated `useList()` / `useGet()` hooks + `fimo/ui`. Never `const posts = [...]` in JSX.
+- **Strings** → `t('key')` + `fimo labels set`. Never `<h1>Welcome</h1>`.
+- **Media** → `<Image>` / `<Video>` from `fimo/ui`. Never `<img src>`.
+- **Forms** → the generated Zod schema + `submitX` helper. Never hand-roll fetch/validation.
+
+## Development loop
+
+1. Start the dev server with the project's package manager (`pnpm dev`, `npm run dev`, …) — live reload on localhost.
+2. Make edits; the running server shows them instantly. No deploy needed to see local changes.
+3. When a unit of work is done, **offer** to deploy: `fimo deploy` for a hosted preview / shareable link, or `fimo deploy --publish` to go live. Only after the developer confirms — never deploy on your own.
+
+## Project rules
+
+- **Deploy is on-demand**, not a save step. Batch related edits into one deploy.
+- Do not add a second deploy tool (Vercel, Netlify, etc.).
+- **Never edit `.fimo.settings.json`** — it links this folder to the remote project.
+- The scaffolded homepage is disposable starter content. Replace it on the first real generation.
+- **Secrets live in the Fimo dashboard**, not in a committed `.env`.
+- When scripting, pass flags to `fimo` commands (`fimo deploy -m "…"`, `fimo delete -y`) — bare interactive forms hang in non-TTY shells.

package/templates/react-router/CLAUDE.md

@@ -0,0 +1,5 @@
+# Fimo project
+
+Instructions for this project live in `AGENTS.md` (the cross-tool standard). Read it:
+
+@AGENTS.md

package/templates/react-router/package.json

@@ -21,7 +21,7 @@
     "cmdk": "^1.1.1",
     "date-fns": "^4.1.0",
     "embla-carousel-react": "^8.6.0",
-    "fimo": "0.8.0",
+    "fimo": "0.9.0-staging.1",
     "input-otp": "^1.4.2",
     "isbot": "^5",
     "lucide-react": "^0.577.0",

package/assets/agents-starter/AGENTS.md

@@ -1,66 +0,0 @@
-# Fimo project rules
-
-This is a Fimo project. Fimo is a content + media + forms + analytics platform for React websites with a CMS dashboard.
-
-## Working with this project
-
-When generating or modifying code in this Fimo project, your AI tool's `fimo` skill should load these references up front (they define the load-bearing primitives):
-
-- `content.md` — schemas + entries
-- `forms.md` — forms
-- `assets.md` — media + AI image generation
-- `translations.md` — `t()` and i18n
-- `ui.md` — `fimo/ui` components + JSX conventions
-
-The `fimo` skill describes how to build inside this project; the `fimo-cli` skill covers the `fimo` CLI itself (create, account, agent setup).
-
-**If your AI tool doesn't seem to know about Fimo, install the skills:**
-
-```bash
-fimo skills install
-# or, without a global fimo install, copy skills out of the npx cache:
-npx fimo@latest skills install --mode=copy
-```
-
-To add another AI tool to this project (e.g., a teammate joins on Cursor or Windsurf) — global skill + project skill + rule file in one shot:
-
-```bash
-fimo skills install --agents=cursor   # explicit
-fimo skills install                   # interactive: pick agents to add
-```
-
-If you later edit this `AGENTS.md` and want the per-agent variants (`CLAUDE.md`, `.cursor/rules/fimo.mdc`, `.windsurfrules`, `GEMINI.md`) regenerated from it, delete the stale variant file and run `fimo rules sync`. Sync is purely additive — it never overwrites existing files, so project-specific edits are preserved unless you remove the file first.
-
-## Development loop
-
-Work with the developer locally, not through deploys:
-
-1. Start the app with the project's package-manager `dev` script — `pnpm dev`, `npm run dev`, `yarn dev`, or `bun dev` (match the lockfile). Run it in the background; it serves the site on localhost with live reload.
-2. Ask the developer what they want to build or change.
-3. Make the edits — the running dev server shows them instantly. You do not need to deploy to see local changes.
-4. Iterate until they are happy with it locally.
-5. When a unit of work looks done, **offer** to deploy: `fimo deploy` for a hosted preview / shareable link, or `fimo deploy --publish` to go live. Run it only after they confirm (or when they ask). Never deploy on your own.
-
-The local dev server is local (localhost). The Fimo dashboard preview and the shareable preview URL come from `fimo deploy` — so if the developer wants to see it in the dashboard or share a link, that needs a deploy.
-
-## Critical project rules
-
-- **Deploy is on-demand — not a save step and not a mandatory final step.** `fimo deploy` commits everything, pushes to the current env's branch, and round-trips the sandbox. Iterate locally with the dev server; deploy only when the developer wants a hosted preview, a shareable link, or to go live — and only after they confirm. Batch related edits into one deploy; never deploy after every change.
-- **Run `fimo deploy --publish` only when the developer signals "ship it"** — an explicit "publish" / "go live" request. Plain `fimo deploy` (preview) is the default; `--publish` is the visible, externally-facing step.
-- Do not add a second deploy tool (Vercel, Netlify, etc.).
-- **Never edit `.fimo.settings.json`.** It is the link between this folder and the remote project — it is written once by `fimo create`.
-- The scaffolded homepage is disposable starter content. On the first real generation, replace its copy, layout, and visual style instead of extending the Fimo-branded design. Keep only the technical shell and required legal pages unless the user explicitly asks to preserve the starter.
-- **Secrets live in the Fimo dashboard**, not in `.env` committed to git.
-- **Read before writing backend code.** Check the `fimo` skill's `references/<topic>.md` before calling the tenant API; the shape may have changed.
-- **Always pass flags to `fimo` commands when scripting** — `fimo deploy -m "<msg>"`, `fimo create <dir> --org <id> --no-install --agents=<list>`, `fimo switch --org <id>`, `fimo delete -y`. Bare interactive forms hang in non-TTY shells.
-
-## Design system (optional)
-
-If a `design.md` file exists at the project root, treat it as the source of truth for all visual decisions:
-
-- Use only the colors, fonts, spacing, and radius tokens defined there.
-- Do not invent new values or fall back to framework defaults (Tailwind defaults, shadcn defaults, etc.).
-- Match component states (hover, focus, active, disabled) to the patterns specified.
-- Follow the typographic scale and weight assignments verbatim.
-
-If `design.md` is absent, fall back to the `frontend-design` skill's guidance.