fimo 0.10.0-experimental.1 → 0.10.0-staging.2

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

@@ -187,7 +187,7 @@ Entry bodies use reference objects with target `id` values:
 fimo entries create BlogPost --body '{"data":{"slug":"hello","title":"Hello","author":{"id":"750e8400-e29b-41d4-a716-446655440000"},"contributors":[]}}'
 ```
 
-Do not add `localized` or field-level `i18n` to reference fields. The reference value belongs to the entry variant containing it.
+`localized` is not a supported spelling anywhere. A reference field may carry `"i18n": false` to point every locale of the document at the same target — see Localized and shared content below.
 
 ## Localized and shared content
 
@@ -195,7 +195,42 @@ Schemas are localized by default. Omit `--locale` to use the project default. Pa
 
 When creating a localized variant of an existing entry, pass the source entry's `documentId` with `--document-id`. Keep projects single-locale unless the user asks for multilingual or localized output; when multiple locales are configured, create and update every locale explicitly.
 
-For content shared across locales, define `"i18n": { "enabled": false }` at the schema root and create each entry once. Do not pass `--document-id` to manufacture locale variants. Raw API and CLI responses omit `locale`; generated collection models add the effective active/default locale without creating per-locale variants. No other `i18n` options and no field-level localization settings are supported.
+For content shared across locales, define `"i18n": { "enabled": false }` at the schema root and create each entry once. Do not pass `--document-id` to manufacture locale variants. Raw API and CLI responses omit `locale`; generated collection models add the effective active/default locale without creating per-locale variants. No other schema-root `i18n` options are supported.
+
+### Shared fields inside a localized type
+
+A localized type can still hold fields that are the same in every language. Mark the field `"i18n": false`. Use it for anything that is not translated — a price, a SKU, a product photo, a reference to the same target everywhere. Without it those values are re-entered per locale and drift apart.
+
+```json
+{
+  "uid": "Product",
+  "name": "Products",
+  "fields": {
+    "title": { "type": "string" },
+    "description": { "type": "richtext" },
+    "sku": { "type": "string", "i18n": false, "unique": true },
+    "price": { "type": "number", "i18n": false },
+    "photo": { "type": "media", "i18n": false },
+    "brand": { "type": "reference", "target": "Brand", "i18n": false }
+  }
+}
+```
+
+Writing a shared field through any locale updates every locale of that document:
+
+```bash
+fimo entries update Product <id> --locale es --body '{"data":{"title":"Silla","price":120}}'
+```
+
+That sets the Spanish title and moves the price to `120` for every language. An update that does not mention a shared field leaves it untouched, so partial writes are safe.
+
+Rules:
+
+- `i18n` belongs on top-level scalar and reference fields only. Fields inside `blocks` follow the locale of the entry containing them and are rejected.
+- On a non-localized type the flag is inert — there is one row already.
+- `"i18n": true` is the default and never needs writing.
+
+Turning an existing field shared is destructive when the languages currently hold different values. The push collapses each document to its default-locale value and discards the others; there is no prompt and no undo. Most documents already agree, so most collapses change nothing — but tell the user what will happen before adding `"i18n": false` to a field that already holds content, and check whether the languages differ if you are unsure.
 
 Use `"isSingleton": true` for a type with exactly one logical document. Generated singleton clients expose `get`/`update` and their React Query hooks, not collection create/remove APIs.
 

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

@@ -81,3 +81,5 @@ Labels and content are separate translated surfaces:
 - content: schema entries, managed with `fimo entries`
 
 Omit `--locale` for default-locale writes. Pass `--locale <locale>` for each non-default localized entry you need to create or update. Shared schemas (`i18n.enabled: false`) have one locale-free entry instead.
+
+Inside a localized schema, a single field can still be shared across every language with `"i18n": false` — use it for values that are not translated, such as a price or a SKU, so they are written once instead of per locale. See `content.md` § Shared fields inside a localized type.

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

@@ -27,7 +27,21 @@ This file covers the **package surface**: the JSON shape you write, the generate
 
 **Required**: `uid` (PascalCase, matches filename), `name`, `fields`.
 
-`i18n` is an optional type-level policy. Omit it or use `{ "enabled": true }` for localized content. Use `{ "enabled": false }` for one shared entry that appears in every locale, such as an Author, Category, or Settings type. No other `i18n` keys and no field-level localization settings are supported.
+`i18n` is an optional type-level policy. Omit it or use `{ "enabled": true }` for localized content. Use `{ "enabled": false }` for one shared entry that appears in every locale, such as an Author, Category, or Settings type. No other schema-root `i18n` keys are supported.
+
+Inside a localized type, an individual top-level scalar or reference field may carry `"i18n": false`. That field then holds one value for the whole document: writing it through any locale updates all of them. Use it for values that are not translated, such as a price, a SKU, a product photo, or a reference that should point at the same target everywhere. Fields inside `blocks` follow the locale of the entry containing them and reject the flag.
+
+```json
+{
+  "uid": "Product",
+  "name": "Products",
+  "fields": {
+    "title": { "type": "string" },
+    "sku": { "type": "string", "i18n": false },
+    "price": { "type": "number", "i18n": false }
+  }
+}
+```
 
 ### Reserved field names — do NOT declare these in `fields`
 
@@ -181,7 +195,7 @@ Rules:
 - Self-references are allowed, e.g. a `Category` schema can have `parent: { "type": "reference", "target": "Category" }`.
 - Entry values use the target's stable `id`, never the variant `entryId`: `{ "id": "..." }`.
 - Do not include `contentType` for normal fixed-target references; the schema's `target` already defines it.
-- Do not add `localized` or field-level `i18n` to a reference. The reference value belongs to the entry variant that stores it.
+- `localized` is not a supported spelling. A reference may carry `"i18n": false` so every locale of the document points at the same target; without it the reference belongs to the entry variant that stores it.
 - Use `null` for an empty to-one reference and `[]` for an empty to-many reference.
 - The API validates that referenced target documents exist and rejects duplicate values in to-many reference arrays.
 
@@ -340,7 +354,7 @@ For shared content, set `i18n: { "enabled": false }` on the schema and create ea
 - ignore locale on owner reads and writes;
 - still use the active/requested locale when a populated reference targets a localized schema.
 
-Do not duplicate shared entries across locales or add field-level localization settings.
+Do not duplicate shared entries across locales. This section is about a whole type being shared; a single shared field inside a localized type is the separate `"i18n": false` field flag described above.
 
 A populated reference whose target has no variant in the requested locale resolves to null. Reads accept an opt-in `localeFallbacks: true` that resolves those to the best available variant instead (project default first), marked by its `locale` field — never implement fallbacks by hand; public reads stay strict unless the option is passed.
 

package/assets/skills/fimo-studio/references/cms.md

@@ -64,6 +64,8 @@ Your edits save automatically as you change each field (the save is debounced),
 
 If a field is invalid, the editor keeps the change unsaved and pins a status bar below the header. Choose **Review issues** to jump to the first invalid field, then **Next issue** to move through the remaining fields. Collapsed blocks open automatically. Once every issue is fixed, the editor confirms that all fields are valid and resumes saving.
 
+A field labelled with a padlocked globe is shared across languages: it holds one value for the whole entry, so editing it in any language changes it in all of them. Fields without that marker are per language and only affect the language you are editing. Hover the icon for the same explanation in context.
+
 ## Editing Text
 
 - Short text such as titles, names, and slugs uses one compact line.

package/dist/cli/bundle.json

@@ -1,7 +1,7 @@
 {
   "bundled": true,
   "bundler": "esbuild",
-  "bundledAt": "2026-07-26T16:18:23.038Z",
+  "bundledAt": "2026-07-27T11:17:03.341Z",
   "cliVersion": "0.9.0",
   "external": [
     "oxc-parser",