Praxis Core Component Registry Contracts
Use this skill when work depends on ComponentMetadataRegistry or component metadata that builders, dynamic widgets, AI authoring, or surface hosts consume.
The registry is a shared Angular catalog for materialized components. It is not a local builder-only registry and should not duplicate semantic contracts owned by resource metadata, domain governance, or a vertical component package.
Source Audit
When selecting widgets for an authored page, inspect registered ID, insertion
preset inputs, public ports and hosted configEditor as separate capabilities.
A selectable palette item can lack a child editor; a standalone editor can be
absent from its widget wrapper. Resolve each from the installed registry before
claiming it can be composed. Do not guess aliases or port names from display copy.
Use the Page Builder authoring/composition skills for operating the chosen widgets.
Inspect before editing:
projects/praxis-core/AGENTS.md
projects/praxis-core/src/public-api.ts when registry models, services, widget metadata contracts, ports, presets, or AI context contracts are exported or public consumption changes.
projects/praxis-core/docs/connection-editor.md
projects/praxis-core/docs/rfc-dynamic-page-canvas-runtime.md
projects/praxis-core/src/lib/services/component-metadata-registry.service.ts
projects/praxis-core/src/lib/models/component-doc-metadata.interface.ts
projects/praxis-core/src/lib/models/component-editorial-metadata.model.ts
projects/praxis-core/src/lib/models/port-contract.model.ts
projects/praxis-core/src/lib/ai/component-context.schema.ts
projects/praxis-core/src/lib/helpers/metadata-normalizer.ts
tools/ai-registry/component-docs.json and tools/ai-registry/schemas/*.json when registry facts are projected to AI ingestion.
- component metadata files in the owning vertical package.
- focused specs for registry, metadata model, AI context, and the direct builder/runtime consumer.
Canonical Boundary
Core owns the registry mechanics and shared metadata contracts:
- component doc metadata lookup by normalized id and fixed compatibility aliases.
- editorial descriptor registration and resolution.
- normalized input/output defaults for common bindings.
- component type aliases only as compatibility lookup, not as intent routing.
- port contracts, insertion presets, and registry projections consumed by builders.
- i18n resolution for editorial descriptors; legacy doc metadata remains string-based.
Vertical packages own their component-specific metadata entries. Page Builder and Visual Builder author and display registry data but should not redefine the registry contract.
Registration And Lookup Semantics
- Register vertical metadata through the owning package provider such as
providePraxisRichContentMetadata(). Importing a component class does not populate ComponentMetadataRegistry; the host must install the provider so its ENVIRONMENT_INITIALIZER runs.
- Treat the registry as an in-memory, injector-scoped governed catalog. Duplicate normalized metadata ids, duplicate legacy
componentType indexes for different metadata ids, duplicate editorial componentMetaId, and duplicate editorial controlType registrations fail closed instead of relying on provider order.
get(id) resolves a normalized metadata id plus the fixed exact aliases table, chart, form, crud, tabs, stepper, list, and expansion. It does not perform arbitrary selector, component class, fuzzy, case-insensitive, or general componentType lookup.
resolveEditorial() uses a different precedence: editorial descriptor by id/control type first, then raw legacy ComponentDocMeta by normalized id or legacy componentType. Do not assume its result is the same normalized object returned by get().
- Use aliases only after the component scope is already known. The alias map is compatibility lookup, not extensible vocabulary or semantic intent routing.
register() clones ports and insertion-preset inputs at ingress, and registry reads (get(), getAll(), getEditorial() and getAllEditorial()) return defensive snapshots. Consumers must still treat results as read-only projections and clone preset/config payloads before materializing or editing them. Never mutate registry metadata to store builder state.
Metadata And I18n Boundaries
Keep the two metadata paths distinct:
ComponentDocMeta is the runtime/catalog contract for component refs, inputs, outputs, actions, commands, ports, config editor, authoring manifest ref, insertion presets, layout hints, owner-authored runtimeProfiles, tags, and owner lib. Its labels/descriptions are plain strings.
ComponentMetadataEditorialDescriptor is the localized editorial projection. Its PraxisTextValue fields are resolved by PraxisI18nService through resolveEditorial().
- Common input/output defaults injected by
normalizeMeta() are resolved from the core componentMetadataRegistry i18n namespace, with built-in pt-BR and en-US catalog entries and clean textual fallback. Keep explicit component labels/descriptions authoritative over these defaults, and do not add component-specific business copy to the shared registry catalog.
When a localized builder/editor experience is required, register and resolve the editorial descriptor with its namespace. Do not copy localized labels into host palettes or reinterpret a raw ComponentDocMeta string as an i18n key.
Projection Fidelity
Every consumer is a projection with its own fidelity; verify the target instead of assuming the whole registry travels intact:
DynamicWidgetLoaderDirective looks up normalized metadata and validates only declared inputs/outputs. Missing metadata emits metadata-missing; strict mode throws for unknown bindings, while non-strict mode warns and drops them. Ports do not replace Angular input/output declarations at this boundary.
NestedPortCatalogService consumes ports plus nested component metadata. A valid Angular output without a canonical port is not sufficient grounding for semantic composition.
- Page Builder palette reads runtime metadata to project entries, presets, and readiness badges, and clones preset inputs before insertion. Its palette entry is still a consumer projection, not a mutable registry record.
PageBuilderAiAdapter projects runtimeState.componentCatalog as a bounded registry grounding surface. It must preserve ids, display copy, tags, input/output descriptors, compatibility name arrays, semantic ports, insertion presets, actions, commands, config editor availability, authoring manifest references, and layout hints without exposing mutable registry entries or Angular component classes as serializable truth.
component-context.schema defines component-specific options/actions/field resolvers and merge patches. It is not an automatic ComponentDocMeta registry projection, and a component context pack may maintain its own explicit option enum.
- Generated
tools/ai-registry/component-docs.json preserves a bounded registry subset for AI ingestion, including inputs/outputs, semantic ports, actions, commands, config editor reference, authoring manifest reference, layout hints, and insertion presets. Pair registry ingestion work with praxis-ai-registry-ingestion and inspect the generated schema/artifact instead of assuming the runtime adapter, generated docs, and backend ingestion have identical fidelity.
- Runtime-profile projections must preserve the stable profile id, audience,
structural constraints, complete declared effects, owner package, and source
metadata. A profile describes an audited input/effect shape; it never grants
authorization or replaces backend capabilities. Pair profile authoring and
host policy with
praxis-core-component-runtime-profiles.
- Treat registry projections as component-grounding evidence, not action authorization.
actions, commands, insertion presets, labels, aliases, tags, and intentExamples may help rank an already scoped component operation, but preview/apply/execute still requires the owning authoring manifest, capability, global-action handler, or backend/domain contract to authorize the operation.
- When projecting registry data to agents, preserve
componentId, normalized registry id, selector, owner package/lib, ports, presets, authoringManifestRef, config editor capability, and source artifact. If any of these are missing, report projection loss or missing provider instead of synthesizing a prompt-only component catalog.
Classify a missing fact in a projection as suportado-parcialmente until the canonical metadata exists and the target consumer demonstrably preserves it. Do not compensate with a second palette array, prompt-only component catalog, selector switch, or host metadata overlay.
Registry Rules
- Register metadata with stable component ids, selectors, component refs, inputs, outputs, ports, insertion presets, owner package, and tags.
- Use
registerEditorial for editorial descriptors with componentMetaId, controlType, localized text, family/track/tags, and binding descriptors.
- Keep aliases limited to resolving already-scoped component type compatibility. Do not route user intent by aliases or labels.
- Preserve port and insertion preset semantics when copying or projecting metadata; do not strip inputs, outputs, cardinality, semantic kinds, or diagnostics.
- Use the target consumer's explicit registry projection, component AI capabilities, and authoring manifest when an agent needs grounding; inspect their schemas instead of scraping rendered controls or assuming
component-context.schema contains ComponentDocMeta.
- If metadata looks missing in a builder, first check whether the owning package registered it before adding fallback local registry data.
- Treat
registry.get(...) returning undefined, missing palette entries, or absent AI registry projection as missing bootstrap/projection
evidence, not proof that the component, package capability, authoring manifest, or backend/domain support does not exist.
Verify the owning package provider, normalized component id, fixed alias scope, generated registry artifact, and direct consumer
projection before declaring a platform contract gap.
- Treat duplicate normalized ids, legacy component types or editorial control types as a governance error. Runtime registration now rejects these collisions, and generated catalog governance should continue rejecting duplicate component ids/selectors before runtime bootstrap.
Aderence Inventory
Classify requests before adding registry contracts:
ja-suportado-so-ux: registry entry exists but builder/editor/docs do not expose it well.
ja-suportado-mal-nomeado-ou-mal-materializado: local alias, selector switch, or hardcoded palette entry should normalize to registry metadata.
suportado-parcialmente: metadata exists but inputs, outputs, ports, insertion presets, i18n, AI projection, or consumer proof is incomplete.
lacuna-real-de-contrato: no registry field/model/AI context can carry the component fact.
Only real gaps justify changing core registry models or public API. Component-specific facts usually belong in the owning vertical package metadata.
Validation
Use focused proof:
component-metadata-registry.service.spec.ts
- component metadata model specs.
- component AI context/schema specs.
- Page Builder, Visual Builder, dynamic widget page, or surface host consumer spec when registry projection is user-visible.
- owning component package build/spec when metadata comes from that package.
For first-step issue resolution, audit a concrete registry entry: raw registration, normalized id, alias/controlType lookup, i18n text, inputs/outputs, ports, insertion presets, AI projection, and builder/runtime consumer visibility.
Prove three scenarios:
- Happy path: an owning provider registers metadata;
get() preserves normalized inputs/outputs, cloned ports and presets; palette/loader consume the intended subset.
- Risk path: missing provider and unknown bindings emit their expected loader diagnostics; duplicate id/control type registrations fail closed; lossy AI projection is identified by source/catalog audit instead of being accepted as complete runtime behavior.
- Adversarial path: reject keyword/label routing, selector switches, mutable host overlays, prompt-only catalogs, and assumptions that every projection contains ports/presets/actions.
Use focused gates from the praxis-ui-angular root:
npm run test:core -- \
--include=projects/praxis-core/src/lib/services/component-metadata-registry.service.spec.ts \
--include=projects/praxis-core/src/lib/models/component-editorial-metadata.model.spec.ts \
--include=projects/praxis-core/src/lib/helpers/metadata-normalizer.spec.ts \
--include=projects/praxis-core/src/lib/widgets/dynamic-widget-loader.directive.spec.ts \
--include=projects/praxis-core/src/lib/composition/nested-port-catalog.service.spec.ts
npm run ng -- test praxis-page-builder --watch=false --progress=false \
--include=projects/praxis-page-builder/src/lib/editor/component-palette-dialog.component.spec.ts \
--include=projects/praxis-page-builder/src/lib/ai/page-builder-ai.adapter.spec.ts
npm run ng -- test praxis-rich-content --watch=false --progress=false \
--include=projects/praxis-rich-content/src/lib/praxis-rich-content.metadata.spec.ts
npm run build:praxis-core
npm run ng -- build praxis-page-builder --configuration production
These gates prove representative runtime, builder, and owner-package paths. Record registry ingestion generation, Visual Builder, a real host bootstrap, browser palette UX, and metadata from other vertical packages as unverified unless they were also exercised.
When changing registry extraction or AI ingestion artifacts, add the generated-artifact proof:
npm run generate:registry:ingestion
node tools/ai-registry/extract-component-docs.spec.js
node tools/ai-registry/validate-catalog-governance.spec.js
node tools/ai-registry/generate-registry.spec.js
node tools/ai-registry/generate-registry-rag.spec.js
When the owning package is not Rich Content, replace the owner-package gate with that package's metadata spec, for example:
npm run test:table -- --include=projects/praxis-table/src/lib/praxis-table.metadata.spec.ts --include=projects/praxis-table/src/lib/components/praxis-filter/praxis-filter.metadata.spec.ts
npm run test:form -- --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.metadata.spec.ts --include=projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form.metadata.spec.ts
npm run ng -- test praxis-crud --watch=false --progress=false --include=projects/praxis-crud/src/lib/praxis-crud.metadata.spec.ts
Companion Skills
- Use
praxis-core-widget-observations for dynamic widgets, runtime observations, and widget event evidence.
- Use
praxis-core-composition-runtime for dynamic page, ports, links, and surface host execution.
- Use
praxis-page-builder-composition or praxis-page-builder-ai-agentic when the registry is consumed by Page Builder.
- Use
praxis-core-domain-governance-runtime when metadata is grounded in governed domain decisions.
- Use
praxis-angular-public-api-governance for exported registry/model changes.
- Use
praxis-ai-registry-ingestion when changing extraction, generated component docs, ingestion schemas, or backend registry artifacts.
- Use
praxis-core-component-runtime-profiles when authoring, resolving, projecting, or enforcing owner-authored execution profiles.
1---2name: praxis-core-component-registry-contracts3description: "Use when Codex must implement, audit, or consume @praxisui/core ComponentMetadataRegistry contracts: component docs metadata, editorial descriptors, component type aliases, input/output defaults, ports, insertion presets, i18n resolution, widget catalog discovery, Page Builder/Visual Builder registry projection, or AI component context grounding."4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-core-component-registry-contracts6---78# Praxis Core Component Registry Contracts910Use this skill when work depends on `ComponentMetadataRegistry` or component metadata that builders, dynamic widgets, AI authoring, or surface hosts consume.1112The registry is a shared Angular catalog for materialized components. It is not a local builder-only registry and should not duplicate semantic contracts owned by resource metadata, domain governance, or a vertical component package.1314## Source Audit1516When selecting widgets for an authored page, inspect registered ID, insertion17preset inputs, public ports and hosted `configEditor` as separate capabilities.18A selectable palette item can lack a child editor; a standalone editor can be19absent from its widget wrapper. Resolve each from the installed registry before20claiming it can be composed. Do not guess aliases or port names from display copy.21Use the Page Builder authoring/composition skills for operating the chosen widgets.2223Inspect before editing:2425- `projects/praxis-core/AGENTS.md`26- `projects/praxis-core/src/public-api.ts` when registry models, services, widget metadata contracts, ports, presets, or AI context contracts are exported or public consumption changes.27- `projects/praxis-core/docs/connection-editor.md`28- `projects/praxis-core/docs/rfc-dynamic-page-canvas-runtime.md`29- `projects/praxis-core/src/lib/services/component-metadata-registry.service.ts`30- `projects/praxis-core/src/lib/models/component-doc-metadata.interface.ts`31- `projects/praxis-core/src/lib/models/component-editorial-metadata.model.ts`32- `projects/praxis-core/src/lib/models/port-contract.model.ts`33- `projects/praxis-core/src/lib/ai/component-context.schema.ts`34- `projects/praxis-core/src/lib/helpers/metadata-normalizer.ts`35- `tools/ai-registry/component-docs.json` and `tools/ai-registry/schemas/*.json` when registry facts are projected to AI ingestion.36- component metadata files in the owning vertical package.37- focused specs for registry, metadata model, AI context, and the direct builder/runtime consumer.3839## Canonical Boundary4041Core owns the registry mechanics and shared metadata contracts:4243- component doc metadata lookup by normalized id and fixed compatibility aliases.44- editorial descriptor registration and resolution.45- normalized input/output defaults for common bindings.46- component type aliases only as compatibility lookup, not as intent routing.47- port contracts, insertion presets, and registry projections consumed by builders.48- i18n resolution for editorial descriptors; legacy doc metadata remains string-based.4950Vertical packages own their component-specific metadata entries. Page Builder and Visual Builder author and display registry data but should not redefine the registry contract.5152## Registration And Lookup Semantics5354- Register vertical metadata through the owning package provider such as `providePraxisRichContentMetadata()`. Importing a component class does not populate `ComponentMetadataRegistry`; the host must install the provider so its `ENVIRONMENT_INITIALIZER` runs.55- Treat the registry as an in-memory, injector-scoped governed catalog. Duplicate normalized metadata ids, duplicate legacy `componentType` indexes for different metadata ids, duplicate editorial `componentMetaId`, and duplicate editorial `controlType` registrations fail closed instead of relying on provider order.56- `get(id)` resolves a normalized metadata id plus the fixed exact aliases `table`, `chart`, `form`, `crud`, `tabs`, `stepper`, `list`, and `expansion`. It does not perform arbitrary selector, component class, fuzzy, case-insensitive, or general `componentType` lookup.57- `resolveEditorial()` uses a different precedence: editorial descriptor by id/control type first, then raw legacy `ComponentDocMeta` by normalized id or legacy `componentType`. Do not assume its result is the same normalized object returned by `get()`.58- Use aliases only after the component scope is already known. The alias map is compatibility lookup, not extensible vocabulary or semantic intent routing.5960`register()` clones ports and insertion-preset inputs at ingress, and registry reads (`get()`, `getAll()`, `getEditorial()` and `getAllEditorial()`) return defensive snapshots. Consumers must still treat results as read-only projections and clone preset/config payloads before materializing or editing them. Never mutate registry metadata to store builder state.6162## Metadata And I18n Boundaries6364Keep the two metadata paths distinct:6566- `ComponentDocMeta` is the runtime/catalog contract for component refs, inputs, outputs, actions, commands, ports, config editor, authoring manifest ref, insertion presets, layout hints, owner-authored `runtimeProfiles`, tags, and owner lib. Its labels/descriptions are plain strings.67- `ComponentMetadataEditorialDescriptor` is the localized editorial projection. Its `PraxisTextValue` fields are resolved by `PraxisI18nService` through `resolveEditorial()`.68- Common input/output defaults injected by `normalizeMeta()` are resolved from the core `componentMetadataRegistry` i18n namespace, with built-in `pt-BR` and `en-US` catalog entries and clean textual fallback. Keep explicit component labels/descriptions authoritative over these defaults, and do not add component-specific business copy to the shared registry catalog.6970When a localized builder/editor experience is required, register and resolve the editorial descriptor with its namespace. Do not copy localized labels into host palettes or reinterpret a raw `ComponentDocMeta` string as an i18n key.7172## Projection Fidelity7374Every consumer is a projection with its own fidelity; verify the target instead of assuming the whole registry travels intact:7576- `DynamicWidgetLoaderDirective` looks up normalized metadata and validates only declared inputs/outputs. Missing metadata emits `metadata-missing`; strict mode throws for unknown bindings, while non-strict mode warns and drops them. Ports do not replace Angular input/output declarations at this boundary.77- `NestedPortCatalogService` consumes `ports` plus nested component metadata. A valid Angular output without a canonical port is not sufficient grounding for semantic composition.78- Page Builder palette reads runtime metadata to project entries, presets, and readiness badges, and clones preset inputs before insertion. Its palette entry is still a consumer projection, not a mutable registry record.79- `PageBuilderAiAdapter` projects `runtimeState.componentCatalog` as a bounded registry grounding surface. It must preserve ids, display copy, tags, input/output descriptors, compatibility name arrays, semantic ports, insertion presets, actions, commands, config editor availability, authoring manifest references, and layout hints without exposing mutable registry entries or Angular component classes as serializable truth.80- `component-context.schema` defines component-specific options/actions/field resolvers and merge patches. It is not an automatic `ComponentDocMeta` registry projection, and a component context pack may maintain its own explicit option enum.81- Generated `tools/ai-registry/component-docs.json` preserves a bounded registry subset for AI ingestion, including inputs/outputs, semantic ports, actions, commands, config editor reference, authoring manifest reference, layout hints, and insertion presets. Pair registry ingestion work with `praxis-ai-registry-ingestion` and inspect the generated schema/artifact instead of assuming the runtime adapter, generated docs, and backend ingestion have identical fidelity.82- Runtime-profile projections must preserve the stable profile id, audience,83 structural constraints, complete declared effects, owner package, and source84 metadata. A profile describes an audited input/effect shape; it never grants85 authorization or replaces backend capabilities. Pair profile authoring and86 host policy with `praxis-core-component-runtime-profiles`.87- Treat registry projections as component-grounding evidence, not action authorization. `actions`, `commands`, insertion presets, labels, aliases, tags, and `intentExamples` may help rank an already scoped component operation, but preview/apply/execute still requires the owning authoring manifest, capability, global-action handler, or backend/domain contract to authorize the operation.88- When projecting registry data to agents, preserve `componentId`, normalized registry id, selector, owner package/lib, ports, presets, `authoringManifestRef`, config editor capability, and source artifact. If any of these are missing, report projection loss or missing provider instead of synthesizing a prompt-only component catalog.8990Classify a missing fact in a projection as `suportado-parcialmente` until the canonical metadata exists and the target consumer demonstrably preserves it. Do not compensate with a second palette array, prompt-only component catalog, selector switch, or host metadata overlay.9192## Registry Rules9394- Register metadata with stable component ids, selectors, component refs, inputs, outputs, ports, insertion presets, owner package, and tags.95- Use `registerEditorial` for editorial descriptors with `componentMetaId`, `controlType`, localized text, family/track/tags, and binding descriptors.96- Keep aliases limited to resolving already-scoped component type compatibility. Do not route user intent by aliases or labels.97- Preserve port and insertion preset semantics when copying or projecting metadata; do not strip inputs, outputs, cardinality, semantic kinds, or diagnostics.98- Use the target consumer's explicit registry projection, component AI capabilities, and authoring manifest when an agent needs grounding; inspect their schemas instead of scraping rendered controls or assuming `component-context.schema` contains `ComponentDocMeta`.99- If metadata looks missing in a builder, first check whether the owning package registered it before adding fallback local registry data.100- Treat `registry.get(...)` returning `undefined`, missing palette entries, or absent AI registry projection as missing bootstrap/projection101 evidence, not proof that the component, package capability, authoring manifest, or backend/domain support does not exist.102 Verify the owning package provider, normalized component id, fixed alias scope, generated registry artifact, and direct consumer103 projection before declaring a platform contract gap.104- Treat duplicate normalized ids, legacy component types or editorial control types as a governance error. Runtime registration now rejects these collisions, and generated catalog governance should continue rejecting duplicate component ids/selectors before runtime bootstrap.105106## Aderence Inventory107108Classify requests before adding registry contracts:109110- `ja-suportado-so-ux`: registry entry exists but builder/editor/docs do not expose it well.111- `ja-suportado-mal-nomeado-ou-mal-materializado`: local alias, selector switch, or hardcoded palette entry should normalize to registry metadata.112- `suportado-parcialmente`: metadata exists but inputs, outputs, ports, insertion presets, i18n, AI projection, or consumer proof is incomplete.113- `lacuna-real-de-contrato`: no registry field/model/AI context can carry the component fact.114115Only real gaps justify changing core registry models or public API. Component-specific facts usually belong in the owning vertical package metadata.116117## Validation118119Use focused proof:120121- `component-metadata-registry.service.spec.ts`122- component metadata model specs.123- component AI context/schema specs.124- Page Builder, Visual Builder, dynamic widget page, or surface host consumer spec when registry projection is user-visible.125- owning component package build/spec when metadata comes from that package.126127For first-step issue resolution, audit a concrete registry entry: raw registration, normalized id, alias/controlType lookup, i18n text, inputs/outputs, ports, insertion presets, AI projection, and builder/runtime consumer visibility.128129Prove three scenarios:1301311. Happy path: an owning provider registers metadata; `get()` preserves normalized inputs/outputs, cloned ports and presets; palette/loader consume the intended subset.1322. Risk path: missing provider and unknown bindings emit their expected loader diagnostics; duplicate id/control type registrations fail closed; lossy AI projection is identified by source/catalog audit instead of being accepted as complete runtime behavior.1333. Adversarial path: reject keyword/label routing, selector switches, mutable host overlays, prompt-only catalogs, and assumptions that every projection contains ports/presets/actions.134135Use focused gates from the `praxis-ui-angular` root:136137```bash138npm run test:core -- \139 --include=projects/praxis-core/src/lib/services/component-metadata-registry.service.spec.ts \140 --include=projects/praxis-core/src/lib/models/component-editorial-metadata.model.spec.ts \141 --include=projects/praxis-core/src/lib/helpers/metadata-normalizer.spec.ts \142 --include=projects/praxis-core/src/lib/widgets/dynamic-widget-loader.directive.spec.ts \143 --include=projects/praxis-core/src/lib/composition/nested-port-catalog.service.spec.ts144npm run ng -- test praxis-page-builder --watch=false --progress=false \145 --include=projects/praxis-page-builder/src/lib/editor/component-palette-dialog.component.spec.ts \146 --include=projects/praxis-page-builder/src/lib/ai/page-builder-ai.adapter.spec.ts147npm run ng -- test praxis-rich-content --watch=false --progress=false \148 --include=projects/praxis-rich-content/src/lib/praxis-rich-content.metadata.spec.ts149npm run build:praxis-core150npm run ng -- build praxis-page-builder --configuration production151```152153These gates prove representative runtime, builder, and owner-package paths. Record registry ingestion generation, Visual Builder, a real host bootstrap, browser palette UX, and metadata from other vertical packages as unverified unless they were also exercised.154155When changing registry extraction or AI ingestion artifacts, add the generated-artifact proof:156157```bash158npm run generate:registry:ingestion159node tools/ai-registry/extract-component-docs.spec.js160node tools/ai-registry/validate-catalog-governance.spec.js161node tools/ai-registry/generate-registry.spec.js162node tools/ai-registry/generate-registry-rag.spec.js163```164165When the owning package is not Rich Content, replace the owner-package gate with that package's metadata spec, for example:166167```bash168npm run test:table -- --include=projects/praxis-table/src/lib/praxis-table.metadata.spec.ts --include=projects/praxis-table/src/lib/components/praxis-filter/praxis-filter.metadata.spec.ts169npm run test:form -- --include=projects/praxis-dynamic-form/src/lib/praxis-dynamic-form.metadata.spec.ts --include=projects/praxis-dynamic-form/src/lib/filter-form/praxis-filter-form.metadata.spec.ts170npm run ng -- test praxis-crud --watch=false --progress=false --include=projects/praxis-crud/src/lib/praxis-crud.metadata.spec.ts171```172173## Companion Skills174175- Use `praxis-core-widget-observations` for dynamic widgets, runtime observations, and widget event evidence.176- Use `praxis-core-composition-runtime` for dynamic page, ports, links, and surface host execution.177- Use `praxis-page-builder-composition` or `praxis-page-builder-ai-agentic` when the registry is consumed by Page Builder.178- Use `praxis-core-domain-governance-runtime` when metadata is grounded in governed domain decisions.179- Use `praxis-angular-public-api-governance` for exported registry/model changes.180- Use `praxis-ai-registry-ingestion` when changing extraction, generated component docs, ingestion schemas, or backend registry artifacts.181- Use `praxis-core-component-runtime-profiles` when authoring, resolving, projecting, or enforcing owner-authored execution profiles.