Praxis Metadata Editor AI Validation
Use this skill for AI-assisted metadata authoring. The AI contract is the executable metadata-editor manifest and capabilities catalog, not free-form patches over field JSON.
Use praxis-ai-authoring-manifests, praxis-ai-registry-ingestion, praxis-ai-semantic-intent, and the metadata-editor renderer/cascade skills as companions.
When locating files, first resolve the Angular workspace root. Paths below are relative to
praxis-ui-angular/projects/praxis-metadata-editor unless another package is explicitly named.
Required Source Audit
Inspect:
projects/praxis-metadata-editor/AGENTS.mdsrc/lib/ai/praxis-metadata-editor-authoring-manifest.tssrc/lib/ai/praxis-metadata-editor-authoring-manifest.spec.tssrc/lib/ai/metadata-editor-ai-capabilities.tssrc/lib/ai/metadata-editor-ai.adapter.tssrc/lib/ai/metadata-editor-ai.adapter.spec.tssrc/lib/ai/metadata-editor-context-pack.tssrc/lib/ai/*.spec.tssrc/lib/praxis-metadata-editor.metadata.tssrc/lib/components/field-metadata-editor/field-metadata-editor.component.tssrc/lib/services/schema-normalizer.service.tssrc/lib/services/dynamic-form-factory.service.tssrc/lib/registry/config-registry.service.tsdocs/praxis-docs.manifest.json- renderer/cascade docs if manifest operations touch those paths
Canonical AI Boundary
AI edits must compile to manifest-backed operations:
fieldMetadata.property.setcontrolType.setoptionSource.configurecascade.configurerenderer.configure- validation/hint/normalization operations declared by the manifest
Do not let assistant flows route intent by keywords or emit arbitrary JSON patch shapes. Ground the operation in canonical FieldMetadata, dynamic-fields discovery, metadata-editor config registry, cascade rules, schema normalizer, and backend x-ui semantics where present.
MetadataEditorAiAdapter must expose preferredResponse: componentEditPlan, publish the manifest
operation ids, and reject free-form patch responses over seed or controlType. Context packs may
provide options and hints, but actionCatalog must not become a keyword/template router.
Some manifest operations are intentionally not materialized as local patch shortcuts. For example,
renderer.configure and normalization.apply require specialized runtime/editor handlers and must
return an error if an assistant tries to compile them into a simple local seed patch.
normalization.apply is especially not a cleanup patch over arbitrary metadata JSON: it is a
SchemaNormalizerService/DynamicFormFactoryService operation over normalizedSeed, form, and
fieldMetadata, with explicit failure modes for lost advanced properties and runtime/editor drift.
When migration friction points to normalization, fix or invoke the normalizer/factory contract and
focused specs instead of teaching the assistant to rewrite one consumer's seed.
Operation Safety
For each changed authorable path:
- verify the input schema can express the intended value
- verify the handler contract names reads/writes, identity keys, failure modes, and validation
- verify the path has visual renderer coverage when visual coverage is required
- verify operation validators include round-trip and canonical shape checks
- verify option-source and cascade operations preserve backend
x-ui.optionSourcesemantics - verify cascade operations keep backend
x-ui.optionSource.dependsOnandx-ui.optionSource.dependencyFilterMapas read/hydration/grounding inputs unless the operation is explicitly an option-source migration/configuration operation. Ordinarycascade.configureoperations should write the metadata-editor runtime cascade paths produced byCascadeRulesService.dehydratePatch()/clearPatch(), not silently promote backend grounding paths into AI writes. - verify control type changes require dynamic-fields discovery and metadata-editor coverage
- verify
affectedPathsand handler writes stay within canonical metadata-editor paths such asfieldMetadata.*,properties,editorCoverage,normalizedSeed, orform - verify every compile-domain-patch effect has a handler contract with reads, writes, identity keys, input schema, failure modes, and operational description
- verify
submissionImpactis typed honestly: option source/cascade affect remote binding, validation affects submission, context hints are visual-only, renderer/normalization are config-only
Broad parent paths are not enough. If the manifest exposes a nested path, focused specs must prove the operation can express and validate it.
Date range shortcut authoring must stay static and governed. Built-in ids and static business periods
are allowed, but executable metadata such as calculateRange, fiscal/legal/electoral rules, holiday
logic, or business-day counting must not be embedded in field metadata.
Registry And Docs
Run or require registry ingestion when manifest, component metadata, component docs, or AI capability catalogs change. Review docs/praxis-docs.manifest.json and public docs when authoring behavior is published.
Validation
Minimum gates:
- manifest changes:
src/lib/ai/praxis-metadata-editor-authoring-manifest.spec.ts - adapter changes:
src/lib/ai/metadata-editor-ai.adapter.spec.ts - capability/context changes:
src/lib/ai/metadata-editor-ai.adapter.spec.tsplus targeted checks formetadata-editor-ai-capabilities.tsormetadata-editor-context-pack.ts - renderer/visual coverage operation changes:
src/lib/components/dynamic-editor-renderer/dynamic-editor-renderer.component.spec.ts,src/lib/components/field-metadata-editor/field-metadata-editor.component.spec.ts, andsrc/lib/config/inline-editor-coverage.spec.tsas applicable - normalization changes:
src/lib/testing/schema-normalizer.service.spec.ts - form/control creation changes:
src/lib/testing/dynamic-form-factory.service.spec.ts - metadata component projection: focused metadata specs if present
- registry projection:
npm run generate:registry:ingestionwhen AI registry artifacts are affected - renderer/cascade operation changes: also run the focused renderer/cascade specs named by the companion skills
- cascade AI boundary changes: pair manifest/adapter specs with
praxis-metadata-editor-cascade-normalizationexpectations, including a focused assertion thatcascade.configurewrites root-level cascade paths and treatsoptionSource.*dependency paths as preserved/read-only unless the operation is explicitly option-source migration/configuration
Use praxis-angular-validation-gates to select the smallest proof and state clearly if registry ingestion, consumer E2E, or backend sync was not run.