Praxis Metadata Editor Consumer Bridges
Use this skill when another Praxis lib opens or delegates to @praxisui/metadata-editor. Consumers should bridge to the canonical editor; they should not redefine FieldMetadata editing, cascade semantics, or dynamic-fields coverage locally.
Resolve paths from praxis-ui-angular/ unless another root is named.
Canonical Consumers
Known consumers include:
@praxisui/dynamic-form: canvas/form builder field metadata editing and all-fields-metadata-editor E2E coverage.
@praxisui/table: filter settings, praxis-filter, always-visible field override editing, and filter-inline-metadata-editor E2E coverage.
@praxisui/manual-form: ManualFieldMetadataBridgeService delegates advanced field metadata edits.
@praxisui/crud: owns CRUD shell metadata but delegates FormConfig and FieldMetadata edits to dynamic-form/metadata-editor manifests.
@praxisui/page-builder: hosts child component config editors and must delegate child metadata semantics through child component manifests/config editors instead of editing child input semantics locally.
@praxisui/editorial-forms: delegates FieldMetadata authoring to metadata-editor/dynamic-fields and owns only editorial binding/orchestration.
Required Source Audit
Inspect the metadata-editor sources plus the affected consumer:
projects/praxis-metadata-editor/AGENTS.md
docs/metadata-editors-architecture.praxis.md
src/public-api.ts
- consumer
AGENTS.md
- dynamic-form:
projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.ts, src/lib/layout-editor/layout-editor.component.ts, src/lib/config-editor/praxis-dynamic-form-config-editor.ts, src/lib/utils/metadata-mappers.ts, and test-dev/e2e/all-fields-metadata-editor.playwright.spec.ts
- table:
projects/praxis-table/src/lib/filter-settings/filter-settings.component.ts, src/lib/components/praxis-filter/praxis-filter.component.ts, src/lib/ai/table-component-edit-plan.ts, and test-dev/e2e/filter-inline-metadata-editor.playwright.spec.ts
- manual-form:
projects/praxis-manual-form/src/lib/services/manual-field-metadata-bridge.service.ts, src/lib/ai/praxis-manual-form-authoring-manifest.ts, plus praxis-manual-form-toolbar-metadata-bridge for field toolbar, pdxManualEdit, Settings Panel, metadata-editor lazy loading, patch diagnostics, and draft persistence side effects
- CRUD:
projects/praxis-crud/src/lib/open-crud-metadata-editor.ts, src/lib/crud-metadata-editor.component.ts, src/lib/ai/praxis-crud-authoring-manifest.ts, and focused authoring entrypoint specs
- Page Builder:
projects/praxis-page-builder/src/lib/dynamic-page-builder.component.ts, src/lib/ai/praxis-page-builder-authoring-manifest.ts, widget config editor hosting, child component manifest resolution, and SETTINGS_PANEL_BRIDGE
- editorial forms:
projects/praxis-editorial-forms/src/lib/ai/praxis-editorial-forms-authoring-manifest.ts when a flow wants to change field metadata from editorial contexts
Bridge Rules
- Use
FieldMetadataEditorComponent for advanced FieldMetadata edits.
- Pass canonical
controlType and seed; normalize aliases through core helpers before opening.
- Build the seed from a defensive clone of the complete current canonical field document,
including specialized properties such as
colorLabelOptions and inlineOverlay.
Do not reconstruct it from an INPUT/common-property allowlist. Keep explicit editor
representation adapters, but normalize their accepted values back to the owner's paths
without persisting duplicate aliases or discarding supported specialized metadata.
- Lazy-load
@praxisui/metadata-editor when the consumer should avoid a hard authoring dependency in the runtime path, but fail visibly through diagnostics/snackbar/logging when the module or FieldMetadataEditorComponent export is unavailable.
- Wire at least one canonical patch path, and preferably both when supported by the host:
hostBridge.applyPatch for immediate editor-to-host application and Settings Panel applied$/saved$ subscriptions for Apply/Save.
- Receive delta patch from
hostBridge, applied$, or Settings Panel save and apply JSON Merge Patch semantics, including null removal where the consumer stores metadata overrides.
- Treat
hostBridge.applyPatch, applied$, and saved$ as accepted patch channels,
not as proof that every intermediate editor draft belongs in the consumer model. Draft,
dirty, valid, busy, reset, and cancel state belong to the hosted editor/Settings Panel
contract until an accepted patch event is emitted.
- Do not copy metadata-editor configs into consumers.
- Do not add consumer-only fields for metadata that belongs to
FieldMetadata, dynamic-fields descriptors, or backend x-ui.
- Do not reinterpret cascade patches in consumers. If metadata-editor emits
dependencyFields, dependencyFilterMap, dependencyValuePath, dependencyMergeStrategy,
dependencyDebounceMs, dependencyLoadOnChange, enableDependencyCascade, or
resetOnDependentChange, apply those paths as metadata-editor/runtime cascade semantics. Do not
translate them into optionSource.dependsOn or optionSource.dependencyFilterMap unless the
consumer task is explicitly an option-source migration/configuration flow.
- Preserve host/product responsibility: consumers may choose when to open the editor and where to persist accepted patches, but the edited semantics belong to metadata-editor/core/dynamic-fields.
- Preserve immutable identity in consumers. Field edits may change metadata properties, but field lookup identity such as
name must be kept unless the task is explicitly a rename flow with downstream layout/rule/reference migration.
- Keep consumer transforms narrow and evidence-backed. For example, dynamic-form may map rating-specific metadata, and table may sanitize override values, but neither may redefine the metadata-editor schema.
Current Consumer Patterns
Use the existing implementation as the default pattern:
- dynamic-form
praxis-dynamic-form.ts: lazy import, Settings Panel id field-meta.<formId>.<fieldName>, hostBridge.applyPatch, applied$/saved$, applyNullDeletionPatch, stripNullMarkersFromPatch, and form rebuild after patch.
- dynamic-form
layout-editor.component.ts: lazy import, Settings Panel id layout.fieldMetadata.<fieldName>, hostBridge.applyPatch, applied$/saved$, patch merged into config.fieldMetadata, and name preserved.
- table
filter-settings.component.ts: optional module id override, fallback to static @praxisui/metadata-editor, Settings Panel id filter-field-meta.<configKey>.<fieldName>, applied$/saved$, JSON Merge Patch into alwaysVisibleFieldMetadataOverrides, and empty override removal.
- table
praxis-filter.component.ts: lazy import, Settings Panel id filter-field-meta.<formId|filterId>.<fieldName>, applied$/saved$, sanitized field override merge, schema re-application, and saveConfig().
- manual-form
ManualFieldMetadataBridgeService: lazy import, Settings Panel id manual-field.<formId>.<fieldName>, hostBridge.applyPatch, applied$/saved$, duplicate patch suppression, instance.patchFieldMetadata(...), and draft persistence.
- CRUD and Page Builder: treat child component configuration as delegated authoring. CRUD must not locally write FormConfig/TableConfig/FieldMetadata semantics; Page Builder must use child manifests/config editors and Settings Panel bridge for widget inputs.
Older architecture docs or examples may show direct import/open snippets or manual
property-by-property patch mapping. Treat those snippets as historical integration
evidence only when they conflict with the current bridge implementations. The
canonical pattern is the current source: lazy load where appropriate, stable Settings
Panel id, hostBridge and/or Settings Panel accepted patch events, JSON Merge Patch
semantics, identity preservation, and focused consumer rebuild/persistence.
Settings Panel
When hosted in Settings Panel:
- Verify open, apply, save, reset/cancel, and reopen.
- Use the editor's dirty/valid/busy state when exposed.
- Do not swallow
applied$ or saved$ events; bridge them to the consumer's canonical patch application.
- If both
hostBridge.applyPatch and applied$/saved$ can emit the same patch, use idempotent application or duplicate suppression where necessary.
- Treat duplicate patch handling as part of the bridge contract, not a cosmetic optimization. A consumer that wires both
hostBridge.applyPatch and Settings Panel events must either prove the same JSON Merge Patch is idempotent in its storage model or suppress short-window duplicate signatures like ManualFieldMetadataBridgeService; otherwise Apply/Save can double-persist, double-rebuild, or double-trigger side effects.
- If lazy import fails, surface a diagnostic instead of silently falling back to incomplete local editing.
- Settings Panel ids should be stable and field-scoped so reopen/dirty state does not cross-contaminate unrelated fields.
Patch Application
Consumer patch application must respect the consumer storage model without changing metadata-editor semantics:
- Direct
fieldMetadata[] owners update the matching field by name, preserve name, emit config changes, and rebuild/re-render as required.
- Override-map owners merge into the field-specific override entry and remove the entry when a JSON Merge Patch leaves it empty.
- Manual-form owners patch the
ManualFormInstance and persist draft after accepted patch.
- If a consumer cannot represent
null removal correctly, fix the bridge/helper before changing metadata-editor output.
- Do not treat
undefined and null as equivalent without checking the local helper contract. In metadata-editor patch semantics, null is explicit removal.
- Preserve the cascade/option-source boundary from
praxis-metadata-editor-cascade-normalization:
optionSource.dependsOn and optionSource.dependencyFilterMap may appear in seeds or option-source
authoring patches, while ordinary cascade edits should persist root-level cascade paths. Consumers
must not silently promote hydrated backend x-ui dependencies into local override semantics.
Opening Baseline And Cumulative Deltas
FieldMetadataEditorComponent.getSettingsValue() is a cumulative delta relative to
its opening seed. For the direct PraxisDynamicForm field bridge, Layout Editor
and Filter Settings, capture an immutable field-scoped opening baseline and apply
every accepted delta to that baseline. In Dynamic Form, capture the stored field
document rather than a seed augmented with editor-only defaults.
Applying a cumulative delta to the already patched value loses reversions:
A -> B -> Apply -> A -> Conclude must restore A even when the final delta is {}.
Keep unrelated fields from the current parent document; do not restore the entire
parent snapshot while accepting one field. Preserve nested siblings, replace arrays,
and delete only paths explicitly marked null. A shallow object spread is not a
recursive merge patch. Reuse the owning consumer's internal helper without making
another public library a transitive facade.
Do not change the canonical editor to emit incremental patches to fix one consumer:
other consumers, including PraxisFilter, already capture opening override baselines.
Prove the real child getSettingsValue() through parent accepted events for nested
option-source edits, null removal, A -> B -> A, repeated Apply and another field
changed while the child is open. Handwritten patch fixtures alone cannot prove the
emitter/consumer baseline agreement.
Dynamic Form also caches runtime metadata and column field projections separately
from FormConfig. Invalidate both after an accepted metadata update so a
presentation-only FieldShell receives the new declarative loader input even when
there is no editable input component. Warm getColumnFields before Apply and
assert the next projection changes while the opening projection remains intact.
For persistence, combine the real child delta proof with Save, close/reopen and
reload through the official storage adapter; accepted events alone do not prove
the standalone initialization lane restores the saved document. Pair that path
with praxis-form-schema-runtime-modes.
Consumer Validation
Exercise the consumer's public open method or visible field action and inspect the seed
passed by that bridge before driving the real child. Supplying a complete handcrafted
seed directly to the child or private bridge cannot detect properties lost by the public
opening path. Prove specialized values survive open, accepted Apply/Save and runtime
projection. When changing patch forwarding, also cover an existing representation
adapter (for example autoResize -> autoSize without an alias residue), immutable
field identity and preservation of nested unmanaged siblings.
Choose the consumer proof:
- dynamic-form field editor:
- cumulative baseline, null removal, warmed projection and standalone hydration:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.field-metadata-roundtrip.spec.ts
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.spec.ts
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/layout-editor/layout-editor.component.spec.ts
- cascade bridge proof when cascade patches cross into form config:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form.config-editor.cascade.integration.spec.ts
- E2E when visual editor coverage changes:
projects/praxis-dynamic-form/test-dev/e2e/all-fields-metadata-editor.playwright.spec.ts
- table filters:
- focused
filter-settings or praxis-filter specs
- E2E when inline filter editor coverage changes:
projects/praxis-table/test-dev/e2e/filter-inline-metadata-editor.playwright.spec.ts
- manual-form bridge:
- focused manual-form bridge/specs with
praxis-manual-form-toolbar-metadata-bridge
projects/praxis-manual-form/src/lib/ai/praxis-manual-form-authoring-manifest.spec.ts when delegation semantics change
- CRUD delegation:
npx ng test praxis-crud --watch=false --progress=false --include=projects/praxis-crud/src/lib/crud-metadata-editor.component.spec.ts
- authoring entrypoint specs when Settings Panel open/apply behavior changes
- Page Builder hosting:
- component palette/config editor round-trip E2E or focused
dynamic-page-builder.component.spec.ts when widget hosting or child-operation delegation changes
- Editorial forms:
projects/praxis-editorial-forms/src/lib/ai/praxis-editorial-forms-authoring-manifest.spec.ts when FieldMetadata delegation is touched
Also run metadata-editor focused specs for the changed owner behavior. Use praxis-manual-form-toolbar-metadata-bridge for manual-form bridge side effects, praxis-manual-form-field-detection-instance for field resolution, and praxis-authoring-editors/praxis-settings-roundtrip-authoring for shared round-trip expectations.
1---2name: praxis-metadata-editor-consumer-bridges3description: Use when integrating or reviewing consumers of `@praxisui/metadata-editor`, including dynamic-form canvas/layout editor, table filter settings, manual-form metadata bridge, Page Builder hosted editors, Settings Panel open/apply/save flows, lazy imports of `FieldMetadataEditorComponent`, cascade tab hosting, JSON Merge Patch application, and avoiding duplicate metadata semantics in consumers.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-metadata-editor-consumer-bridges6---78# Praxis Metadata Editor Consumer Bridges910Use this skill when another Praxis lib opens or delegates to `@praxisui/metadata-editor`. Consumers should bridge to the canonical editor; they should not redefine FieldMetadata editing, cascade semantics, or dynamic-fields coverage locally.1112Resolve paths from `praxis-ui-angular/` unless another root is named.1314## Canonical Consumers1516Known consumers include:1718- `@praxisui/dynamic-form`: canvas/form builder field metadata editing and `all-fields-metadata-editor` E2E coverage.19- `@praxisui/table`: filter settings, `praxis-filter`, always-visible field override editing, and `filter-inline-metadata-editor` E2E coverage.20- `@praxisui/manual-form`: `ManualFieldMetadataBridgeService` delegates advanced field metadata edits.21- `@praxisui/crud`: owns CRUD shell metadata but delegates FormConfig and FieldMetadata edits to dynamic-form/metadata-editor manifests.22- `@praxisui/page-builder`: hosts child component config editors and must delegate child metadata semantics through child component manifests/config editors instead of editing child input semantics locally.23- `@praxisui/editorial-forms`: delegates FieldMetadata authoring to metadata-editor/dynamic-fields and owns only editorial binding/orchestration.2425## Required Source Audit2627Inspect the metadata-editor sources plus the affected consumer:2829- `projects/praxis-metadata-editor/AGENTS.md`30- `docs/metadata-editors-architecture.praxis.md`31- `src/public-api.ts`32- consumer `AGENTS.md`33- dynamic-form: `projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.ts`, `src/lib/layout-editor/layout-editor.component.ts`, `src/lib/config-editor/praxis-dynamic-form-config-editor.ts`, `src/lib/utils/metadata-mappers.ts`, and `test-dev/e2e/all-fields-metadata-editor.playwright.spec.ts`34- table: `projects/praxis-table/src/lib/filter-settings/filter-settings.component.ts`, `src/lib/components/praxis-filter/praxis-filter.component.ts`, `src/lib/ai/table-component-edit-plan.ts`, and `test-dev/e2e/filter-inline-metadata-editor.playwright.spec.ts`35- manual-form: `projects/praxis-manual-form/src/lib/services/manual-field-metadata-bridge.service.ts`, `src/lib/ai/praxis-manual-form-authoring-manifest.ts`, plus `praxis-manual-form-toolbar-metadata-bridge` for field toolbar, `pdxManualEdit`, Settings Panel, metadata-editor lazy loading, patch diagnostics, and draft persistence side effects36- CRUD: `projects/praxis-crud/src/lib/open-crud-metadata-editor.ts`, `src/lib/crud-metadata-editor.component.ts`, `src/lib/ai/praxis-crud-authoring-manifest.ts`, and focused authoring entrypoint specs37- Page Builder: `projects/praxis-page-builder/src/lib/dynamic-page-builder.component.ts`, `src/lib/ai/praxis-page-builder-authoring-manifest.ts`, widget config editor hosting, child component manifest resolution, and `SETTINGS_PANEL_BRIDGE`38- editorial forms: `projects/praxis-editorial-forms/src/lib/ai/praxis-editorial-forms-authoring-manifest.ts` when a flow wants to change field metadata from editorial contexts3940## Bridge Rules4142- Use `FieldMetadataEditorComponent` for advanced FieldMetadata edits.43- Pass canonical `controlType` and `seed`; normalize aliases through core helpers before opening.44- Build the seed from a defensive clone of the complete current canonical field document,45 including specialized properties such as `colorLabelOptions` and `inlineOverlay`.46 Do not reconstruct it from an INPUT/common-property allowlist. Keep explicit editor47 representation adapters, but normalize their accepted values back to the owner's paths48 without persisting duplicate aliases or discarding supported specialized metadata.49- Lazy-load `@praxisui/metadata-editor` when the consumer should avoid a hard authoring dependency in the runtime path, but fail visibly through diagnostics/snackbar/logging when the module or `FieldMetadataEditorComponent` export is unavailable.50- Wire at least one canonical patch path, and preferably both when supported by the host: `hostBridge.applyPatch` for immediate editor-to-host application and Settings Panel `applied$`/`saved$` subscriptions for Apply/Save.51- Receive delta patch from `hostBridge`, `applied$`, or Settings Panel save and apply JSON Merge Patch semantics, including `null` removal where the consumer stores metadata overrides.52- Treat `hostBridge.applyPatch`, `applied$`, and `saved$` as accepted patch channels,53 not as proof that every intermediate editor draft belongs in the consumer model. Draft,54 dirty, valid, busy, reset, and cancel state belong to the hosted editor/Settings Panel55 contract until an accepted patch event is emitted.56- Do not copy metadata-editor configs into consumers.57- Do not add consumer-only fields for metadata that belongs to `FieldMetadata`, dynamic-fields descriptors, or backend `x-ui`.58- Do not reinterpret cascade patches in consumers. If metadata-editor emits59 `dependencyFields`, `dependencyFilterMap`, `dependencyValuePath`, `dependencyMergeStrategy`,60 `dependencyDebounceMs`, `dependencyLoadOnChange`, `enableDependencyCascade`, or61 `resetOnDependentChange`, apply those paths as metadata-editor/runtime cascade semantics. Do not62 translate them into `optionSource.dependsOn` or `optionSource.dependencyFilterMap` unless the63 consumer task is explicitly an option-source migration/configuration flow.64- Preserve host/product responsibility: consumers may choose when to open the editor and where to persist accepted patches, but the edited semantics belong to metadata-editor/core/dynamic-fields.65- Preserve immutable identity in consumers. Field edits may change metadata properties, but field lookup identity such as `name` must be kept unless the task is explicitly a rename flow with downstream layout/rule/reference migration.66- Keep consumer transforms narrow and evidence-backed. For example, dynamic-form may map rating-specific metadata, and table may sanitize override values, but neither may redefine the metadata-editor schema.6768## Current Consumer Patterns6970Use the existing implementation as the default pattern:7172- dynamic-form `praxis-dynamic-form.ts`: lazy import, Settings Panel id `field-meta.<formId>.<fieldName>`, `hostBridge.applyPatch`, `applied$`/`saved$`, `applyNullDeletionPatch`, `stripNullMarkersFromPatch`, and form rebuild after patch.73- dynamic-form `layout-editor.component.ts`: lazy import, Settings Panel id `layout.fieldMetadata.<fieldName>`, `hostBridge.applyPatch`, `applied$`/`saved$`, patch merged into `config.fieldMetadata`, and `name` preserved.74- table `filter-settings.component.ts`: optional module id override, fallback to static `@praxisui/metadata-editor`, Settings Panel id `filter-field-meta.<configKey>.<fieldName>`, `applied$`/`saved$`, JSON Merge Patch into `alwaysVisibleFieldMetadataOverrides`, and empty override removal.75- table `praxis-filter.component.ts`: lazy import, Settings Panel id `filter-field-meta.<formId|filterId>.<fieldName>`, `applied$`/`saved$`, sanitized field override merge, schema re-application, and `saveConfig()`.76- manual-form `ManualFieldMetadataBridgeService`: lazy import, Settings Panel id `manual-field.<formId>.<fieldName>`, `hostBridge.applyPatch`, `applied$`/`saved$`, duplicate patch suppression, `instance.patchFieldMetadata(...)`, and draft persistence.77- CRUD and Page Builder: treat child component configuration as delegated authoring. CRUD must not locally write FormConfig/TableConfig/FieldMetadata semantics; Page Builder must use child manifests/config editors and Settings Panel bridge for widget inputs.7879Older architecture docs or examples may show direct import/open snippets or manual80property-by-property patch mapping. Treat those snippets as historical integration81evidence only when they conflict with the current bridge implementations. The82canonical pattern is the current source: lazy load where appropriate, stable Settings83Panel id, `hostBridge` and/or Settings Panel accepted patch events, JSON Merge Patch84semantics, identity preservation, and focused consumer rebuild/persistence.8586## Settings Panel8788When hosted in Settings Panel:8990- Verify open, apply, save, reset/cancel, and reopen.91- Use the editor's dirty/valid/busy state when exposed.92- Do not swallow `applied$` or `saved$` events; bridge them to the consumer's canonical patch application.93- If both `hostBridge.applyPatch` and `applied$`/`saved$` can emit the same patch, use idempotent application or duplicate suppression where necessary.94- Treat duplicate patch handling as part of the bridge contract, not a cosmetic optimization. A consumer that wires both `hostBridge.applyPatch` and Settings Panel events must either prove the same JSON Merge Patch is idempotent in its storage model or suppress short-window duplicate signatures like `ManualFieldMetadataBridgeService`; otherwise Apply/Save can double-persist, double-rebuild, or double-trigger side effects.95- If lazy import fails, surface a diagnostic instead of silently falling back to incomplete local editing.96- Settings Panel ids should be stable and field-scoped so reopen/dirty state does not cross-contaminate unrelated fields.9798## Patch Application99100Consumer patch application must respect the consumer storage model without changing metadata-editor semantics:101102- Direct `fieldMetadata[]` owners update the matching field by `name`, preserve `name`, emit config changes, and rebuild/re-render as required.103- Override-map owners merge into the field-specific override entry and remove the entry when a JSON Merge Patch leaves it empty.104- Manual-form owners patch the `ManualFormInstance` and persist draft after accepted patch.105- If a consumer cannot represent `null` removal correctly, fix the bridge/helper before changing metadata-editor output.106- Do not treat `undefined` and `null` as equivalent without checking the local helper contract. In metadata-editor patch semantics, `null` is explicit removal.107- Preserve the cascade/option-source boundary from `praxis-metadata-editor-cascade-normalization`:108 `optionSource.dependsOn` and `optionSource.dependencyFilterMap` may appear in seeds or option-source109 authoring patches, while ordinary cascade edits should persist root-level cascade paths. Consumers110 must not silently promote hydrated backend `x-ui` dependencies into local override semantics.111112## Opening Baseline And Cumulative Deltas113114`FieldMetadataEditorComponent.getSettingsValue()` is a cumulative delta relative to115its opening seed. For the direct `PraxisDynamicForm` field bridge, Layout Editor116and Filter Settings, capture an immutable field-scoped opening baseline and apply117every accepted delta to that baseline. In Dynamic Form, capture the stored field118document rather than a seed augmented with editor-only defaults.119Applying a cumulative delta to the already patched value loses reversions:120A -> B -> Apply -> A -> Conclude must restore A even when the final delta is `{}`.121Keep unrelated fields from the current parent document; do not restore the entire122parent snapshot while accepting one field. Preserve nested siblings, replace arrays,123and delete only paths explicitly marked `null`. A shallow object spread is not a124recursive merge patch. Reuse the owning consumer's internal helper without making125another public library a transitive facade.126127Do not change the canonical editor to emit incremental patches to fix one consumer:128other consumers, including PraxisFilter, already capture opening override baselines.129Prove the real child `getSettingsValue()` through parent accepted events for nested130option-source edits, null removal, A -> B -> A, repeated Apply and another field131changed while the child is open. Handwritten patch fixtures alone cannot prove the132emitter/consumer baseline agreement.133134Dynamic Form also caches runtime metadata and column field projections separately135from `FormConfig`. Invalidate both after an accepted metadata update so a136presentation-only FieldShell receives the new declarative loader input even when137there is no editable input component. Warm `getColumnFields` before Apply and138assert the next projection changes while the opening projection remains intact.139For persistence, combine the real child delta proof with Save, close/reopen and140reload through the official storage adapter; accepted events alone do not prove141the standalone initialization lane restores the saved document. Pair that path142with `praxis-form-schema-runtime-modes`.143144## Consumer Validation145146Exercise the consumer's public open method or visible field action and inspect the seed147passed by that bridge before driving the real child. Supplying a complete handcrafted148seed directly to the child or private bridge cannot detect properties lost by the public149opening path. Prove specialized values survive open, accepted Apply/Save and runtime150projection. When changing patch forwarding, also cover an existing representation151adapter (for example `autoResize` -> `autoSize` without an alias residue), immutable152field identity and preservation of nested unmanaged siblings.153154Choose the consumer proof:155156- dynamic-form field editor:157 - cumulative baseline, null removal, warmed projection and standalone hydration: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.field-metadata-roundtrip.spec.ts`158 - `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.spec.ts`159 - `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/layout-editor/layout-editor.component.spec.ts`160 - cascade bridge proof when cascade patches cross into form config: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form.config-editor.cascade.integration.spec.ts`161 - E2E when visual editor coverage changes: `projects/praxis-dynamic-form/test-dev/e2e/all-fields-metadata-editor.playwright.spec.ts`162- table filters:163 - focused `filter-settings` or `praxis-filter` specs164 - E2E when inline filter editor coverage changes: `projects/praxis-table/test-dev/e2e/filter-inline-metadata-editor.playwright.spec.ts`165- manual-form bridge:166 - focused manual-form bridge/specs with `praxis-manual-form-toolbar-metadata-bridge`167 - `projects/praxis-manual-form/src/lib/ai/praxis-manual-form-authoring-manifest.spec.ts` when delegation semantics change168- CRUD delegation:169 - `npx ng test praxis-crud --watch=false --progress=false --include=projects/praxis-crud/src/lib/crud-metadata-editor.component.spec.ts`170 - authoring entrypoint specs when Settings Panel open/apply behavior changes171- Page Builder hosting:172 - component palette/config editor round-trip E2E or focused `dynamic-page-builder.component.spec.ts` when widget hosting or child-operation delegation changes173- Editorial forms:174 - `projects/praxis-editorial-forms/src/lib/ai/praxis-editorial-forms-authoring-manifest.spec.ts` when FieldMetadata delegation is touched175176Also run metadata-editor focused specs for the changed owner behavior. Use `praxis-manual-form-toolbar-metadata-bridge` for manual-form bridge side effects, `praxis-manual-form-field-detection-instance` for field resolution, and `praxis-authoring-editors`/`praxis-settings-roundtrip-authoring` for shared round-trip expectations.