@praxisui/page-builder 9.0.47 → 9.0.48

package/README.md

@@ -86,6 +86,11 @@ All omitted `authoringCapabilities` entries remain enabled for backward compatib
 never written to `WidgetPageDefinition` and does not authorize AI operations; manifests, backend
 policy, target resolution and validation remain authoritative.
 
+`childCustomization` is a host grant, not a bulk enable switch. A nested component receives
+`enableCustomization=true` only while the builder is in authoring mode, the host grant is enabled,
+and that widget explicitly declares `definition.inputs.enableCustomization=true`. Widgets with an
+absent or false authored opt-in remain presentation-only.
+
 For example, a host that should expose only canvas and shell-identity authoring can declare:
 
 ```ts
@@ -262,6 +267,8 @@ The package exports `PRAXIS_PAGE_BUILDER_AUTHORING_MANIFEST` for governed operat
 
 The visual authoring runtime may project editor-only inputs required by canvas affordances. Page changes emitted by that runtime are normalized back to the canonical `WidgetPageDefinition` before persistence: transient authoring inputs are removed, explicitly authored values are preserved, and a projection-only no-op does not create a new revision.
 
+`saveCurrentPage()` reads the embedded Dynamic Page snapshot only while the editable canvas is active. In presentation mode, composition may hydrate component inputs and derive display layout; those values are runtime projections and must never overwrite the canonical `currentPage` during save. Presentation-mode save therefore emits a clone of the authored page, preserving widgets, links, state, layout and provenance exactly.
+
 `UiCompositionPlan` can carry the complete page-owned envelope required by the runtime: `i18n`, explicit `context`, canonical `layout`, state, presets, responsive variants, governed widget `shell`, component inputs and semantic wiring. The compiler clones these fields into `WidgetPageDefinition`; hosts must not add business copy, tenant context, layout or widget chrome after compilation as an undocumented enrichment step. `context` is page-wide runtime context, while `contextScopes` is an authoring shorthand that expands repeated values into explicit widget inputs and links.
 
 Repeated selection projections can be authored once through `UiCompositionPlan.selectionSyncs`. A sync declares structured component-output sources, a base state target, and a field-to-payload mapping. `compileUiCompositionPlan` expands every source/mapping pair into explicit `page.composition.links` with stable ids, canonical `pick-path` transforms, policy, condition, and `selection-sync` intent. The shorthand is never persisted in `WidgetPageDefinition`, so runtime inspection and audit continue to see the complete executable graph.
@@ -321,16 +328,23 @@ Workspace contributors can exercise this path in the reference host at
 the compact plan, registry-aware preflight, compiled `WidgetPageDefinition`, real
 Dynamic Page, diagnostics, widget-event trail and sanitized runtime observation
 without introducing another compiler or registry. Its scenario catalog reuses the
-same A2-A4 plan fixtures exercised by focused certification specs—forms/filters,
-CRUD lifecycle and parent/related-resource—alongside the certified A5
-Table/shell/global-action contracts. An unknown component proves fail-closed
-behavior. The browser proof for the related-resource scenario requires a real
+same A1-A5 plan fixtures exercised by focused certification specs—List,
+forms/filters, CRUD lifecycle, parent/related-resource and
+Table/shell/global-action. Seven adversarial scenarios prove fail-closed behavior
+for missing component, missing port, invalid direction, incompatible semantic
+kind, unguarded feedback, incomplete master-detail layout and a stale governed
+template hash. The browser proof for the related-resource scenario requires a real
 parent selection, the relationship filter and visible child columns/data derived
 from the remote schema; request success alone is insufficient. The same route's
 People Operations dashboard is authored as a 9-widget/10-binding plan and proves
-filter and governed decision propagation through the compiled graph. The broader
-certification matrix remains tracked in issue #430; issue #431 closed the former
-global-action source limitation.
+filter and governed decision propagation through the compiled graph. The lab also
+executes deterministic runtime reset, verifies JSON persistence invariants for
+every applicable scenario, and invokes the real Page Builder save output before
+reopening the rich People Operations page. Corrupted executable transforms and
+legacy `page.connections` remain Core/page-ingress adversarials because neither is
+a valid `UiCompositionPlan` input; the lab does not duplicate those boundary
+validators. The governed Config Starter + Quickstart gate remains tracked in
+issue #430; issue #431 closed the former global-action source limitation.
 
 For multi-consumer interaction state, author one `event -> state` binding and
 project `state -> component-port` to each consumer. A direct event delivery is

package/ai/component-registry.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": "1.0.0",
-  "generatedAt": "2026-08-30T21:38:22.309Z",
+  "generatedAt": "2026-08-30T23:30:05.791Z",
   "packageName": "@praxisui/page-builder",
-  "packageVersion": "9.0.47",
+  "packageVersion": "9.0.48",
   "sourceRegistry": "praxis-component-registry-ingestion",
   "sourceRegistryVersion": "1.0.0",
   "componentCount": 1,

package/fesm2022/praxisui-page-builder.mjs

@@ -24754,28 +24754,12 @@ class DynamicPageBuilderComponent {
     }
     /**
      * Builds one mode-independent runtime projection for the authored page.
-     * Child authoring chrome is materialized by the embedded dynamic page from
-     * host capabilities, so JSON/Visual mode changes never replace this object.
+     * The authored child opt-in remains in this stable source. The embedded
+     * dynamic page combines it with host mode/capabilities at the loader boundary,
+     * so JSON/Visual changes never replace this object or broaden permissions.
      */
     toRuntimeBasePage(page) {
-        const cloned = this.clonePage(page);
-        cloned.widgets = (cloned.widgets || []).map((widget) => {
-            const metadata = this.componentMetadata.get(widget.definition?.id);
-            if (!metadata?.inputs?.some((input) => input.name === 'enableCustomization')) {
-                return widget;
-            }
-            return {
-                ...widget,
-                definition: {
-                    ...widget.definition,
-                    inputs: {
-                        ...(widget.definition.inputs || {}),
-                        enableCustomization: false,
-                    },
-                },
-            };
-        });
-        return cloned;
+        return this.clonePage(page);
     }
     /** Restores authoring-only child inputs from the canonical builder page. */
     toCanonicalPageFromRuntime(page) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@praxisui/page-builder",
-  "version": "9.0.47",
+  "version": "9.0.48",
   "description": "Page and widget builder utilities for Praxis UI (grid, dynamic widgets, editors).",
   "peerDependencies": {
     "@angular/common": "^21.0.0",
@@ -8,9 +8,9 @@
     "@angular/forms": "^21.0.0",
     "@angular/cdk": "^21.0.0",
     "@angular/material": "^21.0.0",
-    "@praxisui/ai": "^9.0.47",
-    "@praxisui/core": "^9.0.47",
-    "@praxisui/settings-panel": "^9.0.47",
+    "@praxisui/ai": "^9.0.48",
+    "@praxisui/core": "^9.0.48",
+    "@praxisui/settings-panel": "^9.0.48",
     "rxjs": "~7.8.0"
   },
   "dependencies": {

package/types/praxisui-page-builder.d.ts

@@ -2197,8 +2197,9 @@ declare class DynamicPageBuilderComponent implements OnChanges, OnDestroy {
     private enterPreviewMode;
     /**
      * Builds one mode-independent runtime projection for the authored page.
-     * Child authoring chrome is materialized by the embedded dynamic page from
-     * host capabilities, so JSON/Visual mode changes never replace this object.
+     * The authored child opt-in remains in this stable source. The embedded
+     * dynamic page combines it with host mode/capabilities at the loader boundary,
+     * so JSON/Visual changes never replace this object or broaden permissions.
      */
     private toRuntimeBasePage;
     /** Restores authoring-only child inputs from the canonical builder page. */