@form-engine-ts/react 2.1.0 → 2.2.0

package/README.md

@@ -55,12 +55,23 @@ batch-translation action.
 
 `useFormBuilder({ schema, onChange, policy, idFactory, factories })` exposes controlled field, option, page, condition,
 source-text, and localized-text actions. Core's `FormPolicy` enforces allowed field types, field/option limits, text and
-schema-byte limits, and required locales identically in browser and server code. Every mutation returns a typed
+schema-byte limits, and required/allowed/maximum locale constraints identically in browser and server code. Every mutation returns a typed
 `BuilderActionResult`; invalid, empty, or duplicate generated IDs leave the schema unchanged. `BuilderFactories` injects
 initial field, option, and page shapes. `<FormBuilder>` delegates its UI mutations to this hook and accepts the same
 options. Its completion-message editors cover both source and locale text. `translationOptions` and
 `onTranslationReport` expose automatic-translation policy and reporting.
 
+Visual-builder field creation uses `defaultFieldType` when it is allowed, otherwise the first allowed policy type, then
+`text` when unrestricted. The add button is disabled when no type is allowed or `maxFields` is reached.
+`onActionError` receives typed failures from visual headless actions, and `createManualTranslationMetadata` can attach
+per-locale/property metadata to manual edits. Automatic translation defaults to `overwrite: "missing-only"`; explicitly
+pass `{ overwrite: "all" }` to replace existing translations.
+
+Pass `readOnly` to keep the complete builder visible while disabling every mutation. The `features` prop independently
+controls `pages`, `localization`, and `conditions` authoring surfaces; each defaults to `true`. When `allowedLocales` is
+set, locale addition becomes a selector containing only unregistered allowed locales, and the action is disabled at
+`maxLocales`.
+
 `FormRenderer` can also be used without an explicit provider:
 
 ```tsx