Praxis Form Authoring Settings
For authoring a schema form or filter-form inside Page Builder, read
browser-form-widget.md. The same editor
capabilities support custom registration, read-only detail and query screens.
This praxis-form-* skill family is the canonical Codex skill surface for @praxisui/dynamic-form and projects/praxis-dynamic-form; do not create parallel praxis-dynamic-form-* guidance unless this family cannot express a proven contract gap.
Use this skill for Dynamic Form authoring and Settings Panel flows. A change is incomplete when runtime config works but the visual editor cannot show, edit, apply, save, reset, reopen, or round-trip the same semantics.
For the canonical document/apply-plan contract itself, load praxis-form-editor-document-roundtrip. For action or hook editor details, pair with praxis-form-actions-hooks-runtime.
When Dynamic Form opens or embeds FieldMetadataEditorComponent, DynamicEditorRendererComponent,
or CascadeManagerTabComponent, use praxis-metadata-editor-consumer-bridges for the host bridge.
If the behavior belongs to the metadata editor itself, route to
praxis-metadata-editor-renderer-coverage or praxis-metadata-editor-cascade-normalization instead
of patching Dynamic Form locally.
When Dynamic Form appears inside @praxisui/manual-form, route manual host-template/autosave/toolbar
concerns to praxis-manual-form-runtime-bridge or praxis-manual-form-ai-authoring. When Dynamic
Form appears inside @praxisui/editorial-forms, keep editorial journey/snapshot/fallback concerns in
praxis-editorial-forms-runtime / praxis-editorial-forms-journey-snapshot-runtime /
praxis-editorial-forms-presentation-diagnostics and adapter binding in
praxis-editorial-forms-adapters-ai / praxis-editorial-forms-data-collection-adapters.
Source Audit
First resolve the Angular workspace root. In the platform monorepo the files may live under
praxis-ui-angular/projects/...; in a standalone Angular checkout they may live directly under
projects/.... Audit the active praxis-ui-angular workspace, not stale issue worktrees such as
praxis-ui-angular-issue*, unless the user explicitly targets one of those worktrees.
Inspect the authoring surface:
projects/praxis-dynamic-form/AGENTS.md
projects/praxis-dynamic-form/src/lib/settings-panel.providers.ts
projects/praxis-dynamic-form/src/lib/dynamic-form-editor-document.model.ts
projects/praxis-dynamic-form/src/lib/dynamic-form-editor-capability.ts
projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-authoring-protocol.spec.ts
projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.i18n.ts
projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.metadata.ts
projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.metadata.spec.ts
projects/praxis-dynamic-form/src/lib/config-editor/**
projects/praxis-dynamic-form/src/lib/layout-editor/**
projects/praxis-dynamic-form/src/lib/behavior-editor/**
projects/praxis-dynamic-form/src/lib/rules-editor/**
projects/praxis-dynamic-form/src/lib/messages-editor/**
projects/praxis-dynamic-form/src/lib/hooks-editor/**
projects/praxis-dynamic-form/src/lib/actions-editor/**
projects/praxis-dynamic-form/src/lib/json-config-editor/**
projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-widget-config-editor.ts
projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form-widget-config-editor.ts
projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form.metadata.ts
projects/praxis-dynamic-form/src/lib/ai/praxis-dynamic-form-authoring-manifest.ts
projects/praxis-dynamic-form/src/lib/ai/dynamic-form-agentic-authoring-turn-flow.ts
projects/praxis-dynamic-form/src/lib/ai/dynamic-form-rule-authoring-context.ts
projects/praxis-dynamic-form/src/lib/utils/metadata-mappers.ts
projects/praxis-dynamic-form/docs/dynamic-form-authoring-document-semantics.md
projects/praxis-dynamic-form/docs/dynamic-form-visual-builder-parity-audit.md
- platform decision-authoring docs that mention
formRulesState, componentEditPlan, or
rule.visualBlockGuidance.add, especially docs/2026-04-form-rules-state-despromocao-backlog.md
when the platform monorepo is available
- related JSON API docs such as
config-editor/praxis-dynamic-form-config-editor.json-api.md, layout-editor/praxis-layout-editor.json-api.md, and json-config-editor/form-json-config-editor.json-api.md
Also inspect projects/praxis-settings-panel/AGENTS.md when changing SettingsValueProvider, drawer data, apply, save, reset, or persisted config.
For Settings Panel protocol changes, inspect the concrete owner files instead of inferring behavior
from Dynamic Form providers alone:
projects/praxis-settings-panel/src/lib/settings-panel.component.ts
projects/praxis-settings-panel/src/lib/settings-panel.component.spec.ts
projects/praxis-settings-panel/src/lib/settings-panel.ref.ts
projects/praxis-settings-panel/src/lib/settings-panel.service.ts
projects/praxis-settings-panel/src/lib/settings-panel.service.spec.ts
projects/praxis-settings-panel/src/lib/settings-panel-bridge.provider.ts
projects/praxis-settings-panel/src/lib/settings-panel-bridge.provider.spec.ts
projects/praxis-settings-panel/src/lib/ai/settings-panel-ai.adapter.spec.ts
projects/praxis-settings-panel/src/lib/ai/praxis-settings-panel-authoring-manifest.spec.ts
Authoring Document Rules
DynamicFormAuthoringDocument is the canonical complete authoring snapshot:
config replaces the previous config.
bindings replaces previous persistible bindings.
- missing
bindings.mode clears the persisted mode binding.
contextSnapshot replaces previous persisted authoring context.
- missing
backConfig, presentation, or schemaPrefs inside contextSnapshot explicitly removes that block.
- runtime discovery values such as
schemaUrl, submitUrl, and submitMethod are diagnostics only and must not be persisted into bindings or context snapshot.
Legacy partial adapter APIs can keep merge compatibility, but canonical editor apply/save is replace-all.
Settings Panel, widget config editor, embedded config editor, JSON editor, metadata editor bridge, and AI assistant must all target the same authoring document/apply-plan semantics. Do not fix an authoring value in only one tab or host surface when the canonical editor family should own the round-trip.
formRulesState is internal/legacy runtime and visual-builder round-trip state. Do not present it as
the canonical authoring target for business rules, compliance, eligibility, validation policy, or
shared decisions. Those decisions belong to governed semantic authoring such as domain-rules /
shared_rule_authoring and may later materialize into form_config, visual guidance, or runtime
state. Keep componentEditPlan and rule.visualBlockGuidance.add scoped to component/page authoring
or optional UI projection, not primary rule authoring.
Settings Panel Boundary
SettingsPanelService is the canonical authoring drawer for editors that implement
SettingsValueProvider. providePraxisSurfaceDrawerBridge() is the runtime drawer bridge for
surface.open. They may share visual tokens, but they must not share semantics by accident.
- Use
SettingsPanelService only when the hosted editor owns Apply, Save, Reset, Cancel,
dirty/valid/busy state and SettingsValueProvider.
- Use
providePraxisSurfaceDrawerBridge() for runtime surface.open; it must not display authoring
chrome, status, or footer actions unless a governed runtime contract explicitly asks for it.
SettingsPanelConfig.diagnostics controls status visibility, disabled-reason visibility, busy
visibility, and validation exposure in the shell. It does not decide whether Apply or Save are
enabled; those gates come from the hosted editor's isDirty$, isValid$, and isBusy$.
Apply is preview without closing the panel; Save is the final persisted value through
saved$. A host that subscribes only to applied$, only to saved$, or persists a partial value
outside the canonical editor document is incomplete.
- Do not move
Apply/Save gating, confirmation, replacement, or overlay lifecycle into an Ergon
host or component-specific wrapper when the structural behavior belongs to
@praxisui/settings-panel.
For PraxisDynamicFormWidgetConfigEditor, the hosted editor must serialize/parse
DynamicFormAuthoringDocument, then project it back to widget inputs (config, mode,
backConfig, notifyIfOutdated, snoozeMs, autoOpenSettingsOnOutdated). Treat that projection as
a compatibility boundary for hosts, not as a second source of truth. When the document omits a
binding or context snapshot block, follow the canonical replace-all semantics instead of preserving
stale host inputs silently.
For Ergon migration work, if a screen needs an authoring drawer only to tweak runtime URLs,
operation URLs, submit method, resolved metadata, or drawer appearance, classify that as a diagnostic
or host-integration concern first. Promote it to Dynamic Form or Settings Panel authoring only when an
existing FormConfig, bindings, contextSnapshot, metadata bridge, or Settings Panel provider
cannot represent the desired stable platform behavior.
Editor Round-Trip Checklist
For every config or context change, prove or inspect:
- Existing config/document opens in the editor with the correct value.
- The user can change it through the canonical editor surface.
- Apply/save emits the expected
DynamicFormAuthoringDocument or config shape.
- Runtime reflects the applied change.
- Reopening the editor preserves the value.
- Reset removes only the intended config, bindings, or context snapshot.
If no visual editor is affected, state why.
Editor Rules
- Start by identifying the owner path: Settings Panel provider, widget config editor, embedded config editor, layout editor, behavior editor, rules/command rules editor, messages editor, hooks editor, actions editor, JSON editor, metadata editor bridge, or AI authoring.
- Keep
fieldMetadata patches deep-merged where needed, especially entityLookup.optionSource, so editor changes do not erase canonical lookup contracts.
- Keep rules, messages, hooks, actions, behavior, hints, schema preferences, navigation, presentation, and JSON editor in sync.
- Keep authoring text in the dynamic-form i18n catalog; do not add visible hardcoded strings.
- Do not create component-specific local editors in a host when
ComponentDocMeta.configEditor or the owning Dynamic Form editor should handle it.
- Treat
Apply working without Save, or Save working without reopen, as incomplete.
- Treat runtime-only host values shown in the editor, such as schema URL, submit URL, submit method, and resolved metadata, as read-only diagnostics unless the authoring document explicitly owns the field.
- Treat
formRulesState echoes in visual-builder paths as derived state to preserve, not a new
public AI/write contract.
- Treat a stale visual-builder echo, JSON-only advanced path, or tab-local fallback as a partial implementation until reopen and JSON editor paths preserve the same semantics.
- When an editor embeds
FieldMetadataEditorComponent, DynamicEditorRendererComponent, or CascadeManagerTabComponent, use the metadata-editor consumer bridge contract instead of reimplementing metadata editor logic in Dynamic Form.
- Dynamic Form may delegate to manual-form or editorial-forms hosts, but those hosts must not redefine Dynamic Form authoring semantics through local autosave, toolbar, or journey snapshot shortcuts.
Distinguish validation scopes: builder structure, structured-effect editability, sample-data
preview, and form/runtime diagnostics. A successful preview proves only the evaluated branch for
those data; it does not validate targets, grant access, or replace the hosted editor's Apply/Save
gates. JSON replacement, list clearing, and Reset must refresh the same visual draft and effects
panel: canonical formRules wins over valid stale derived state. While conversion fails, retain
the accepted config, hide its stale structured effects panel and accepted-rule diagnostics, and direct repair to the visual
wizard or JSON; restore the panel only after conversion succeeds. Invalid drafts block Apply/Save.
Prove this with
config-editor/praxis-dynamic-form-config-editor.spec.ts and
config-editor/rule-properties-panel.component.spec.ts, then exercise the visible editor flow.
Inventory Before New Contract
ja-suportado-so-ux: the document/apply-plan and runtime support the value, but a tab, Settings Panel affordance, diagnostic, or copy is missing.
ja-suportado-mal-nomeado-ou-mal-materializado: a value exists in FormConfig, bindings, contextSnapshot, metadata editor bridge, or JSON editor but is surfaced under the wrong editor concept or local label.
suportado-parcialmente: one path works while another path, such as Settings Panel, embedded editor, JSON editor, metadata bridge, AI assistant, apply/save/reset, or reopen, drifts.
lacuna-real-de-contrato: no existing authoring document, config field, binding, context snapshot, metadata bridge, or Settings Panel provider can represent the value.
Only lacuna-real-de-contrato justifies a new authoring/settings contract. Otherwise, fix the missing projection, provider, editor tab, i18n copy, JSON path, or validation gate.
Validation
- Settings Panel/document semantics:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/dynamic-form-editor-capability.spec.ts --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-authoring-protocol.spec.ts --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-widget-config-editor.spec.ts --include=projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form-widget-config-editor.spec.ts
- Settings Panel owner protocol:
npx ng test praxis-settings-panel --watch=false --progress=false --include=projects/praxis-settings-panel/src/lib/settings-panel.component.spec.ts --include=projects/praxis-settings-panel/src/lib/settings-panel.service.spec.ts --include=projects/praxis-settings-panel/src/lib/settings-panel-bridge.provider.spec.ts
- Settings Panel AI/protocol manifest:
npx ng test praxis-settings-panel --watch=false --progress=false --include=projects/praxis-settings-panel/src/lib/ai/settings-panel-ai.adapter.spec.ts --include=projects/praxis-settings-panel/src/lib/ai/praxis-settings-panel-authoring-manifest.spec.ts
- Config and JSON editor:
npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form-config-editor.spec.ts --include=projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form.config-editor.cascade.integration.spec.ts --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.config-editor.spec.ts --include=projects/praxis-dynamic-form/src/lib/json-config-editor/json-config-editor.component.spec.ts
- Layout editor: include
layout-editor/layout-editor.component.spec.ts, field-configurator.component.spec.ts, row-configurator.component.spec.ts, section-configurator.component.spec.ts, apply-section-preset.util.spec.ts, and visual-block-presets.spec.ts when layout or visual blocks change.
- Behavior/rules/messages/hooks/actions: include focused editor specs such as
behavior-editor.component.spec.ts, rules-editor.component.spec.ts, messages-editor.component.spec.ts, actions-editor.component.spec.ts, rule-properties-panel.component.spec.ts, and hook specs when present.
- Metadata bridge and coverage: include
praxis-dynamic-form.metadata.spec.ts, filter-form metadata specs, and metadata-editor bridge specs when the Settings Panel embeds metadata-editor controls.
- AI authoring: include
praxis-dynamic-form-authoring-manifest.spec.ts, dynamic-form-agentic-authoring-turn-flow.spec.ts, and dynamic-form-rule-authoring-context.spec.ts when AI assistant or component edit plans change.
- Browser authoring: Playwrights such as
form-config-editor-smoke, form-config-editor-layout, form-config-editor-rules, form-config-editor-messages, form-config-editor-hooks, form-config-editor-actions, form-config-editor-actions-custom, form-config-editor-behavior, form-config-editor-json, form-config-editor-hints, form-config-editor-cascades, and domain demos when visible editor behavior changes.
npm run build:praxis-dynamic-form when public editor APIs, metadata, providers, or exports change.
npm run validate:published-doc-assets and npm run generate:registry:ingestion when JSON API docs, AI manifests, generated docs, or registry surfaces change.
Companion Skills
- Use
praxis-authoring-editors for cross-component Settings Panel and round-trip guidance.
- Use
praxis-form-runtime-submit when authoring changes runtime construction, submit behavior, field metadata, or resource contracts.
- Use
praxis-form-editor-document-roundtrip for DynamicFormAuthoringDocument, bindings, context snapshots, diagnostics, replace-all apply/save/reset, and reopen semantics.
- Use
praxis-form-schema-runtime-modes when authoring changes schema URLs, mode bindings, presentation mode, schema preferences, or metadata reconciliation.
- Use
praxis-form-submit-payload-pipeline when editors expose local/transient fields, submitPolicy, entity lookup payload mode, or payload-affecting metadata.
- Use
praxis-form-actions-hooks-runtime for actions editor, hooks editor, global action refs, surface open payloads, and shortcut/action runtime round-trip.
- Use
praxis-form-layout-canvas for layout editor, visual blocks, canvas, schema-driven layout policy, and presentation.
- Use
praxis-form-ai-rules-validation for AI component edit plans, rules, diagnostics, and registry ingestion.
- Use
praxis-dynamic-fields-editorial for field component coverage and metadata editor chains.
- Use
praxis-metadata-editor-consumer-bridges for Dynamic Form bridge behavior around metadata-editor hosted editors.
- Use
praxis-manual-form-ai-authoring, praxis-editorial-forms-adapters-ai, or praxis-editorial-forms-data-collection-adapters when Dynamic Form is delegated by those package owners.
1---2name: praxis-form-authoring-settings3description: Use when Codex must work on @praxisui/dynamic-form or praxis-dynamic-form package authoring, Settings Panel integration, config editor, layout editor, behavior editor, rules editor, messages editor, hooks editor, actions editor, JSON config editor, widget config editor, apply/save/reset, DynamicFormAuthoringDocument, schema preferences, presentation snapshots, or runtime/editor round-trip.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-form-authoring-settings6---78# Praxis Form Authoring Settings910For authoring a schema form or filter-form inside Page Builder, read11[browser-form-widget.md](references/browser-form-widget.md). The same editor12capabilities support custom registration, read-only detail and query screens.1314This `praxis-form-*` skill family is the canonical Codex skill surface for `@praxisui/dynamic-form` and `projects/praxis-dynamic-form`; do not create parallel `praxis-dynamic-form-*` guidance unless this family cannot express a proven contract gap.1516Use this skill for Dynamic Form authoring and Settings Panel flows. A change is incomplete when runtime config works but the visual editor cannot show, edit, apply, save, reset, reopen, or round-trip the same semantics.17For the canonical document/apply-plan contract itself, load `praxis-form-editor-document-roundtrip`. For action or hook editor details, pair with `praxis-form-actions-hooks-runtime`.1819When Dynamic Form opens or embeds `FieldMetadataEditorComponent`, `DynamicEditorRendererComponent`,20or `CascadeManagerTabComponent`, use `praxis-metadata-editor-consumer-bridges` for the host bridge.21If the behavior belongs to the metadata editor itself, route to22`praxis-metadata-editor-renderer-coverage` or `praxis-metadata-editor-cascade-normalization` instead23of patching Dynamic Form locally.24When Dynamic Form appears inside `@praxisui/manual-form`, route manual host-template/autosave/toolbar25concerns to `praxis-manual-form-runtime-bridge` or `praxis-manual-form-ai-authoring`. When Dynamic26Form appears inside `@praxisui/editorial-forms`, keep editorial journey/snapshot/fallback concerns in27`praxis-editorial-forms-runtime` / `praxis-editorial-forms-journey-snapshot-runtime` /28`praxis-editorial-forms-presentation-diagnostics` and adapter binding in29`praxis-editorial-forms-adapters-ai` / `praxis-editorial-forms-data-collection-adapters`.3031## Source Audit3233First resolve the Angular workspace root. In the platform monorepo the files may live under34`praxis-ui-angular/projects/...`; in a standalone Angular checkout they may live directly under35`projects/...`. Audit the active `praxis-ui-angular` workspace, not stale issue worktrees such as36`praxis-ui-angular-issue*`, unless the user explicitly targets one of those worktrees.3738Inspect the authoring surface:3940- `projects/praxis-dynamic-form/AGENTS.md`41- `projects/praxis-dynamic-form/src/lib/settings-panel.providers.ts`42- `projects/praxis-dynamic-form/src/lib/dynamic-form-editor-document.model.ts`43- `projects/praxis-dynamic-form/src/lib/dynamic-form-editor-capability.ts`44- `projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-authoring-protocol.spec.ts`45- `projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.i18n.ts`46- `projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.metadata.ts`47- `projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.metadata.spec.ts`48- `projects/praxis-dynamic-form/src/lib/config-editor/**`49- `projects/praxis-dynamic-form/src/lib/layout-editor/**`50- `projects/praxis-dynamic-form/src/lib/behavior-editor/**`51- `projects/praxis-dynamic-form/src/lib/rules-editor/**`52- `projects/praxis-dynamic-form/src/lib/messages-editor/**`53- `projects/praxis-dynamic-form/src/lib/hooks-editor/**`54- `projects/praxis-dynamic-form/src/lib/actions-editor/**`55- `projects/praxis-dynamic-form/src/lib/json-config-editor/**`56- `projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-widget-config-editor.ts`57- `projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form-widget-config-editor.ts`58- `projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form.metadata.ts`59- `projects/praxis-dynamic-form/src/lib/ai/praxis-dynamic-form-authoring-manifest.ts`60- `projects/praxis-dynamic-form/src/lib/ai/dynamic-form-agentic-authoring-turn-flow.ts`61- `projects/praxis-dynamic-form/src/lib/ai/dynamic-form-rule-authoring-context.ts`62- `projects/praxis-dynamic-form/src/lib/utils/metadata-mappers.ts`63- `projects/praxis-dynamic-form/docs/dynamic-form-authoring-document-semantics.md`64- `projects/praxis-dynamic-form/docs/dynamic-form-visual-builder-parity-audit.md`65- platform decision-authoring docs that mention `formRulesState`, `componentEditPlan`, or66 `rule.visualBlockGuidance.add`, especially `docs/2026-04-form-rules-state-despromocao-backlog.md`67 when the platform monorepo is available68- related JSON API docs such as `config-editor/praxis-dynamic-form-config-editor.json-api.md`, `layout-editor/praxis-layout-editor.json-api.md`, and `json-config-editor/form-json-config-editor.json-api.md`6970Also inspect `projects/praxis-settings-panel/AGENTS.md` when changing `SettingsValueProvider`, drawer data, `apply`, `save`, `reset`, or persisted config.7172For Settings Panel protocol changes, inspect the concrete owner files instead of inferring behavior73from Dynamic Form providers alone:7475- `projects/praxis-settings-panel/src/lib/settings-panel.component.ts`76- `projects/praxis-settings-panel/src/lib/settings-panel.component.spec.ts`77- `projects/praxis-settings-panel/src/lib/settings-panel.ref.ts`78- `projects/praxis-settings-panel/src/lib/settings-panel.service.ts`79- `projects/praxis-settings-panel/src/lib/settings-panel.service.spec.ts`80- `projects/praxis-settings-panel/src/lib/settings-panel-bridge.provider.ts`81- `projects/praxis-settings-panel/src/lib/settings-panel-bridge.provider.spec.ts`82- `projects/praxis-settings-panel/src/lib/ai/settings-panel-ai.adapter.spec.ts`83- `projects/praxis-settings-panel/src/lib/ai/praxis-settings-panel-authoring-manifest.spec.ts`8485## Authoring Document Rules8687`DynamicFormAuthoringDocument` is the canonical complete authoring snapshot:8889- `config` replaces the previous config.90- `bindings` replaces previous persistible bindings.91- missing `bindings.mode` clears the persisted mode binding.92- `contextSnapshot` replaces previous persisted authoring context.93- missing `backConfig`, `presentation`, or `schemaPrefs` inside `contextSnapshot` explicitly removes that block.94- runtime discovery values such as `schemaUrl`, `submitUrl`, and `submitMethod` are diagnostics only and must not be persisted into bindings or context snapshot.9596Legacy partial adapter APIs can keep merge compatibility, but canonical editor apply/save is replace-all.9798Settings Panel, widget config editor, embedded config editor, JSON editor, metadata editor bridge, and AI assistant must all target the same authoring document/apply-plan semantics. Do not fix an authoring value in only one tab or host surface when the canonical editor family should own the round-trip.99100`formRulesState` is internal/legacy runtime and visual-builder round-trip state. Do not present it as101the canonical authoring target for business rules, compliance, eligibility, validation policy, or102shared decisions. Those decisions belong to governed semantic authoring such as `domain-rules` /103`shared_rule_authoring` and may later materialize into `form_config`, visual guidance, or runtime104state. Keep `componentEditPlan` and `rule.visualBlockGuidance.add` scoped to component/page authoring105or optional UI projection, not primary rule authoring.106107## Settings Panel Boundary108109`SettingsPanelService` is the canonical authoring drawer for editors that implement110`SettingsValueProvider`. `providePraxisSurfaceDrawerBridge()` is the runtime drawer bridge for111`surface.open`. They may share visual tokens, but they must not share semantics by accident.112113- Use `SettingsPanelService` only when the hosted editor owns `Apply`, `Save`, `Reset`, `Cancel`,114 dirty/valid/busy state and `SettingsValueProvider`.115- Use `providePraxisSurfaceDrawerBridge()` for runtime `surface.open`; it must not display authoring116 chrome, status, or footer actions unless a governed runtime contract explicitly asks for it.117- `SettingsPanelConfig.diagnostics` controls status visibility, disabled-reason visibility, busy118 visibility, and validation exposure in the shell. It does not decide whether `Apply` or `Save` are119 enabled; those gates come from the hosted editor's `isDirty$`, `isValid$`, and `isBusy$`.120- `Apply` is preview without closing the panel; `Save` is the final persisted value through121 `saved$`. A host that subscribes only to `applied$`, only to `saved$`, or persists a partial value122 outside the canonical editor document is incomplete.123- Do not move `Apply`/`Save` gating, confirmation, replacement, or overlay lifecycle into an Ergon124 host or component-specific wrapper when the structural behavior belongs to125 `@praxisui/settings-panel`.126127For `PraxisDynamicFormWidgetConfigEditor`, the hosted editor must serialize/parse128`DynamicFormAuthoringDocument`, then project it back to widget `inputs` (`config`, `mode`,129`backConfig`, `notifyIfOutdated`, `snoozeMs`, `autoOpenSettingsOnOutdated`). Treat that projection as130a compatibility boundary for hosts, not as a second source of truth. When the document omits a131binding or context snapshot block, follow the canonical replace-all semantics instead of preserving132stale host inputs silently.133134For Ergon migration work, if a screen needs an authoring drawer only to tweak runtime URLs,135operation URLs, submit method, resolved metadata, or drawer appearance, classify that as a diagnostic136or host-integration concern first. Promote it to Dynamic Form or Settings Panel authoring only when an137existing `FormConfig`, `bindings`, `contextSnapshot`, metadata bridge, or Settings Panel provider138cannot represent the desired stable platform behavior.139140## Editor Round-Trip Checklist141142For every config or context change, prove or inspect:1431441. Existing config/document opens in the editor with the correct value.1452. The user can change it through the canonical editor surface.1463. Apply/save emits the expected `DynamicFormAuthoringDocument` or config shape.1474. Runtime reflects the applied change.1485. Reopening the editor preserves the value.1496. Reset removes only the intended config, bindings, or context snapshot.150151If no visual editor is affected, state why.152153## Editor Rules154155- Start by identifying the owner path: Settings Panel provider, widget config editor, embedded config editor, layout editor, behavior editor, rules/command rules editor, messages editor, hooks editor, actions editor, JSON editor, metadata editor bridge, or AI authoring.156- Keep `fieldMetadata` patches deep-merged where needed, especially `entityLookup.optionSource`, so editor changes do not erase canonical lookup contracts.157- Keep rules, messages, hooks, actions, behavior, hints, schema preferences, navigation, presentation, and JSON editor in sync.158- Keep authoring text in the dynamic-form i18n catalog; do not add visible hardcoded strings.159- Do not create component-specific local editors in a host when `ComponentDocMeta.configEditor` or the owning Dynamic Form editor should handle it.160- Treat `Apply` working without `Save`, or `Save` working without reopen, as incomplete.161- Treat runtime-only host values shown in the editor, such as schema URL, submit URL, submit method, and resolved metadata, as read-only diagnostics unless the authoring document explicitly owns the field.162- Treat `formRulesState` echoes in visual-builder paths as derived state to preserve, not a new163 public AI/write contract.164- Treat a stale visual-builder echo, JSON-only advanced path, or tab-local fallback as a partial implementation until reopen and JSON editor paths preserve the same semantics.165- When an editor embeds `FieldMetadataEditorComponent`, `DynamicEditorRendererComponent`, or `CascadeManagerTabComponent`, use the metadata-editor consumer bridge contract instead of reimplementing metadata editor logic in Dynamic Form.166- Dynamic Form may delegate to manual-form or editorial-forms hosts, but those hosts must not redefine Dynamic Form authoring semantics through local autosave, toolbar, or journey snapshot shortcuts.167168Distinguish validation scopes: builder structure, structured-effect editability, sample-data169preview, and form/runtime diagnostics. A successful preview proves only the evaluated branch for170those data; it does not validate targets, grant access, or replace the hosted editor's Apply/Save171gates. JSON replacement, list clearing, and Reset must refresh the same visual draft and effects172panel: canonical `formRules` wins over valid stale derived state. While conversion fails, retain173the accepted config, hide its stale structured effects panel and accepted-rule diagnostics, and direct repair to the visual174wizard or JSON; restore the panel only after conversion succeeds. Invalid drafts block Apply/Save.175Prove this with176`config-editor/praxis-dynamic-form-config-editor.spec.ts` and177`config-editor/rule-properties-panel.component.spec.ts`, then exercise the visible editor flow.178179## Inventory Before New Contract180181- `ja-suportado-so-ux`: the document/apply-plan and runtime support the value, but a tab, Settings Panel affordance, diagnostic, or copy is missing.182- `ja-suportado-mal-nomeado-ou-mal-materializado`: a value exists in `FormConfig`, `bindings`, `contextSnapshot`, metadata editor bridge, or JSON editor but is surfaced under the wrong editor concept or local label.183- `suportado-parcialmente`: one path works while another path, such as Settings Panel, embedded editor, JSON editor, metadata bridge, AI assistant, apply/save/reset, or reopen, drifts.184- `lacuna-real-de-contrato`: no existing authoring document, config field, binding, context snapshot, metadata bridge, or Settings Panel provider can represent the value.185186Only `lacuna-real-de-contrato` justifies a new authoring/settings contract. Otherwise, fix the missing projection, provider, editor tab, i18n copy, JSON path, or validation gate.187188## Validation189190- Settings Panel/document semantics: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/dynamic-form-editor-capability.spec.ts --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-authoring-protocol.spec.ts --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form-widget-config-editor.spec.ts --include=projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form-widget-config-editor.spec.ts`191- Settings Panel owner protocol: `npx ng test praxis-settings-panel --watch=false --progress=false --include=projects/praxis-settings-panel/src/lib/settings-panel.component.spec.ts --include=projects/praxis-settings-panel/src/lib/settings-panel.service.spec.ts --include=projects/praxis-settings-panel/src/lib/settings-panel-bridge.provider.spec.ts`192- Settings Panel AI/protocol manifest: `npx ng test praxis-settings-panel --watch=false --progress=false --include=projects/praxis-settings-panel/src/lib/ai/settings-panel-ai.adapter.spec.ts --include=projects/praxis-settings-panel/src/lib/ai/praxis-settings-panel-authoring-manifest.spec.ts`193- Config and JSON editor: `npx ng test praxis-dynamic-form --watch=false --progress=false --include=projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form-config-editor.spec.ts --include=projects/praxis-dynamic-form/src/lib/config-editor/praxis-dynamic-form.config-editor.cascade.integration.spec.ts --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.config-editor.spec.ts --include=projects/praxis-dynamic-form/src/lib/json-config-editor/json-config-editor.component.spec.ts`194- Layout editor: include `layout-editor/layout-editor.component.spec.ts`, `field-configurator.component.spec.ts`, `row-configurator.component.spec.ts`, `section-configurator.component.spec.ts`, `apply-section-preset.util.spec.ts`, and `visual-block-presets.spec.ts` when layout or visual blocks change.195- Behavior/rules/messages/hooks/actions: include focused editor specs such as `behavior-editor.component.spec.ts`, `rules-editor.component.spec.ts`, `messages-editor.component.spec.ts`, `actions-editor.component.spec.ts`, `rule-properties-panel.component.spec.ts`, and hook specs when present.196- Metadata bridge and coverage: include `praxis-dynamic-form.metadata.spec.ts`, filter-form metadata specs, and metadata-editor bridge specs when the Settings Panel embeds metadata-editor controls.197- AI authoring: include `praxis-dynamic-form-authoring-manifest.spec.ts`, `dynamic-form-agentic-authoring-turn-flow.spec.ts`, and `dynamic-form-rule-authoring-context.spec.ts` when AI assistant or component edit plans change.198- Browser authoring: Playwrights such as `form-config-editor-smoke`, `form-config-editor-layout`, `form-config-editor-rules`, `form-config-editor-messages`, `form-config-editor-hooks`, `form-config-editor-actions`, `form-config-editor-actions-custom`, `form-config-editor-behavior`, `form-config-editor-json`, `form-config-editor-hints`, `form-config-editor-cascades`, and domain demos when visible editor behavior changes.199- `npm run build:praxis-dynamic-form` when public editor APIs, metadata, providers, or exports change.200- `npm run validate:published-doc-assets` and `npm run generate:registry:ingestion` when JSON API docs, AI manifests, generated docs, or registry surfaces change.201202## Companion Skills203204- Use `praxis-authoring-editors` for cross-component Settings Panel and round-trip guidance.205- Use `praxis-form-runtime-submit` when authoring changes runtime construction, submit behavior, field metadata, or resource contracts.206- Use `praxis-form-editor-document-roundtrip` for `DynamicFormAuthoringDocument`, bindings, context snapshots, diagnostics, replace-all apply/save/reset, and reopen semantics.207- Use `praxis-form-schema-runtime-modes` when authoring changes schema URLs, mode bindings, presentation mode, schema preferences, or metadata reconciliation.208- Use `praxis-form-submit-payload-pipeline` when editors expose local/transient fields, `submitPolicy`, entity lookup payload mode, or payload-affecting metadata.209- Use `praxis-form-actions-hooks-runtime` for actions editor, hooks editor, global action refs, surface open payloads, and shortcut/action runtime round-trip.210- Use `praxis-form-layout-canvas` for layout editor, visual blocks, canvas, schema-driven layout policy, and presentation.211- Use `praxis-form-ai-rules-validation` for AI component edit plans, rules, diagnostics, and registry ingestion.212- Use `praxis-dynamic-fields-editorial` for field component coverage and metadata editor chains.213- Use `praxis-metadata-editor-consumer-bridges` for Dynamic Form bridge behavior around metadata-editor hosted editors.214- Use `praxis-manual-form-ai-authoring`, `praxis-editorial-forms-adapters-ai`, or `praxis-editorial-forms-data-collection-adapters` when Dynamic Form is delegated by those package owners.