@praxisui/page-builder 10.0.0-rc.18 → 10.0.0-rc.20

package/README.md

@@ -135,7 +135,7 @@ order, with natural content height. It replaces positions and width bounds only
 that device, preserves hidden widgets and other overrides, and leaves the base and
 other device layouts unchanged. Apply/Save materializes the existing
 `deviceLayouts[device].canvas` contract; Reset restores the original draft.
-Advanced JSON overrides remain available under **Advanced overrides**.
+Advanced JSON overrides remain available under **Advanced overrides** (`widgetOverrides`) and strictly validate the canonical `WidgetPageWidgetLayoutOverride` keys (`className`, `span`, `order`, `hidden`), diagnosing and rejecting unsupported properties such as `definition` or `inputs` without discarding the user's draft text.
 
 Reducing a device's column count also reflows inherited base positions in Core.
 Explicit device positions remain authoritative. With no device variant the base
@@ -161,7 +161,7 @@ documents already clamped by Core remain valid on opening: declared spans need
 not equal rendered spans. Invalid inherited bounds can be corrected in the same
 draft. The editor does not rewrite geometry to satisfy newly authored bounds.
 Dynamic title expressions are
-identified by stable widget key, not evaluated in the editor.
+identified by stable widget key and resolved friendly widget titles (from static shell metadata or inner widget titles), not evaluated in the editor.
 
 Apply previews the same document returned by Save; Reset reloads the input baseline.
 Pending changes are tracked independently of validity, including edits to an
@@ -183,7 +183,7 @@ Page, the editor receives transient runtime validation through `SETTINGS_PANEL_D
 Apply/Save and reopen check the current active-device geometry and report the minimum
 beside the height field. The callback and observed dimensions never enter the document.
 Changed columns, gap, width or shell styling require Automatic height, Apply, then
-reopening before choosing a measured height. Other device variants must be checked
+reopening before choosing a measured height. When switching a visual template (`themePreset` / `layoutPreset`) triggers rendered-height validation blocks on widgets with adjustable heights, the editor surfaces an actionable banner across Studio tabs listing all affected widgets with their friendly names and current pixel heights, offering direct navigation to **Widget limits** or a one-click conversion to **Automatic** height that preserves a summary of the previous pixel measurements for review. Other device variants must be checked
 on their corresponding device. Standalone/custom hosts without this runtime context
 retain numeric validation only. Core's scroll-layout shell now recovers access after
 late header/content growth by temporarily scrolling the header and body together
@@ -202,8 +202,8 @@ not an OpenAI dependency for manual interaction.
 
 Both `PageConfigEditorComponent` and `DynamicPageConfigEditorComponent` preserve and edit `page.dataSources` inside **Page settings → State**:
 
-- `PageConfigEditorComponent` offers guided DataSource cards (`id`, `kind`, `endpointKey`, `resourcePath`, `method`, `targetStatePath`, `errorPolicy`, `refreshIntervalMs`, `autoFetch`, `query`, `transform`, `fallbackValue`, `description`) synchronized with an advanced JSON editor.
-- Both editors accept Array or Object-Map JSON input, normalize saved definitions to the canonical `WidgetPageDataSourceDefinition[]` array, and fail closed (blocking Apply/Save and surfacing `editor.errors.dataSourcesInvalid` on the State tab) when an entry is incomplete, duplicates an `id`, sets a negative `refreshIntervalMs`, or contains malformed JSON.
+- Both `PageConfigEditorComponent` and `DynamicPageConfigEditorComponent` offer guided DataSource cards (`id`, `kind`, `endpointKey`, `resourcePath`, `method`, `targetStatePath`, `errorPolicy`, `refreshIntervalMs`, `autoFetch`, `query`, `transform`, `fallbackValue`, `description`) synchronized bidirectionally with the advanced JSON editor (`[data-testid="page-datasources-json"]`).
+- Both editors accept Array or Object-Map JSON input, normalize saved definitions to the canonical `WidgetPageDataSourceDefinition[]` array, and enforce symmetric validation across guided and raw JSON authoring—failing closed (blocking Apply/Save and surfacing `editor.errors.dataSourcesInvalid` on the State tab) when an entry is missing `id` or `resourcePath`, duplicates a normalized `id`, sets an unsupported `kind`/`method`/`errorPolicy`, sets a negative or non-finite `refreshIntervalMs`, passes a non-object `query`, declares an incomplete `transform` (`path`, `group-by-map`, `timeseries-last`), or contains malformed JSON.
 
 ## LLM Recommendation Guide
 

package/ai/component-registry.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-10-14T22:59:57.823Z",
+  "generatedAt": "2026-10-15T03:52:00.118Z",
   "packageName": "@praxisui/page-builder",
-  "packageVersion": "10.0.0-rc.18",
+  "packageVersion": "10.0.0-rc.20",
   "sourceRegistry": "praxis-component-registry-ingestion",
   "sourceRegistryVersion": "1.0.0",
   "componentCount": 1,