Praxis Editorial Forms Presentation Diagnostics
Use this skill when editorial runtime health or presentation is in scope. Presentation is a constrained solution.presentation projection; fallback and operational events are technical runtime evidence, not domain shortcuts.
Source Audit
Inspect before editing:
projects/praxis-editorial-forms/AGENTS.md
projects/praxis-editorial-forms/README.md
projects/praxis-editorial-forms/docs/architecture.md
projects/praxis-editorial-forms/docs/recovery-playbook.md
projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-fallback.ts
projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-diagnostics.model.ts
projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-events.model.ts
projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-presentation.helpers.ts
projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-theme.helpers.ts
projects/praxis-editorial-forms/src/lib/runtime/editorial-preset-resolver.ts
projects/praxis-editorial-forms/src/lib/renderers/editorial-stepper.component.ts
projects/praxis-editorial-forms/src/lib/i18n/*
- fallback, theme helper, runtime component, renderer, and E2E specs
Canonical Boundary
solution.presentation owns visual runtime intent. deriveRuntimeFallbackState() owns fallback derivation from snapshot diagnostics. operationalEvent owns technical telemetry for diagnostics, blocking errors, override conflicts, and adapter states.
Do not persist fallback as hidden business truth. Do not move presentation flags into host CSS, dynamic-form layout, journey blocks, FieldMetadata, or collected data.
Presentation Rules
- Supported runtime layout keys include orientation, density, max width, spacing, shell variant, mobile orientation, and collapse breakpoint behavior.
- Supported stepper keys include visibility, orientation, labels/descriptions/connectors, connector style, and step jump policy.
- Theme tokens must flow through
buildRuntimeCssVars() and valid CSS variable inputs.
- Unsupported accepted model keys must emit
presentation-config-unsupported diagnostics instead of pretending support.
- Known diagnosed keys include
presentation.layout.contentAlign, presentation.layout.responsive.tabletOrientation, presentation.stepper.size, presentation.stepper.align, and stepper variants without distinct renderer behavior.
- Presentation changes must not mutate journeys, blocks,
FormConfig, FieldMetadata, or runtimeContext.formData.
Fallback And Event Rules
- Fallback modes are
normal, warning, degraded, and blocked.
- Blocking diagnostics are global errors or active-step errors in the current scope.
- Missing data-collection adapters require engine attention and may degrade or block based on explicit policy.
snapshotChange, fallbackChange, and operationalEvent remain separate host outputs.
operationalEvent is technical telemetry for logs, monitoring, and runbooks; it must not become the primary host UI contract.
- Respect
hostConfig.emitOperationalEvents and hostConfig.forwardAdapterOperationalEvents.
Inventory Before New Contract
Classify requested changes:
ja-suportado-so-ux: diagnostics/fallback exist but badges, docs, lab, or host display is incomplete.
ja-suportado-mal-nomeado-ou-mal-materializado: a host calls a presentation token local CSS while solution.presentation or theme tokens already own it.
suportado-parcialmente: a key exists in the model but renderer support, diagnostics, theme mapping, or validation is incomplete.
lacuna-real-de-contrato: no existing presentation key, diagnostic code, fallback mode, event payload, or helper can express the requirement.
Only a real gap justifies adding public presentation keys, diagnostic codes, or event types.
Validation
Use focused local proof:
- fallback:
src/lib/runtime/editorial-runtime-fallback.spec.ts
- presentation/theme:
src/lib/runtime/editorial-runtime-theme.helpers.spec.ts and presentation helper specs when present
- runtime UI diagnostics:
src/lib/editorial-form-runtime.component.spec.ts
- stepper behavior:
src/lib/renderers/editorial-stepper.component.spec.ts
- i18n: package i18n specs or catalog audit when text changes
- build:
npm run build:praxis-editorial-forms when public presentation/fallback contracts change
- host/lab: E2E labs when operational events or visual runtime behavior changes
Pair with praxis-editorial-forms-journey-snapshot-runtime for snapshot scope and with praxis-editorial-forms-data-collection-adapters for adapter diagnostics.
1---2name: praxis-editorial-forms-presentation-diagnostics3description: Use when implementing or auditing `@praxisui/editorial-forms` fallback states, diagnostics, operational events, `solution.presentation`, layout/theme/stepper helpers, unsupported presentation keys, runtime CSS variables, stepper behavior, i18n, and visual/runtime health reporting.4metadata:5 source: https://skillmd.com/skills/codexrodrigues/praxis-editorial-forms-presentation-diagnostics6---78# Praxis Editorial Forms Presentation Diagnostics910Use this skill when editorial runtime health or presentation is in scope. Presentation is a constrained `solution.presentation` projection; fallback and operational events are technical runtime evidence, not domain shortcuts.1112## Source Audit1314Inspect before editing:1516- `projects/praxis-editorial-forms/AGENTS.md`17- `projects/praxis-editorial-forms/README.md`18- `projects/praxis-editorial-forms/docs/architecture.md`19- `projects/praxis-editorial-forms/docs/recovery-playbook.md`20- `projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-fallback.ts`21- `projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-diagnostics.model.ts`22- `projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-events.model.ts`23- `projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-presentation.helpers.ts`24- `projects/praxis-editorial-forms/src/lib/runtime/editorial-runtime-theme.helpers.ts`25- `projects/praxis-editorial-forms/src/lib/runtime/editorial-preset-resolver.ts`26- `projects/praxis-editorial-forms/src/lib/renderers/editorial-stepper.component.ts`27- `projects/praxis-editorial-forms/src/lib/i18n/*`28- fallback, theme helper, runtime component, renderer, and E2E specs2930## Canonical Boundary3132`solution.presentation` owns visual runtime intent. `deriveRuntimeFallbackState()` owns fallback derivation from snapshot diagnostics. `operationalEvent` owns technical telemetry for diagnostics, blocking errors, override conflicts, and adapter states.3334Do not persist fallback as hidden business truth. Do not move presentation flags into host CSS, dynamic-form layout, journey blocks, `FieldMetadata`, or collected data.3536## Presentation Rules3738- Supported runtime layout keys include orientation, density, max width, spacing, shell variant, mobile orientation, and collapse breakpoint behavior.39- Supported stepper keys include visibility, orientation, labels/descriptions/connectors, connector style, and step jump policy.40- Theme tokens must flow through `buildRuntimeCssVars()` and valid CSS variable inputs.41- Unsupported accepted model keys must emit `presentation-config-unsupported` diagnostics instead of pretending support.42- Known diagnosed keys include `presentation.layout.contentAlign`, `presentation.layout.responsive.tabletOrientation`, `presentation.stepper.size`, `presentation.stepper.align`, and stepper variants without distinct renderer behavior.43- Presentation changes must not mutate journeys, blocks, `FormConfig`, `FieldMetadata`, or `runtimeContext.formData`.4445## Fallback And Event Rules4647- Fallback modes are `normal`, `warning`, `degraded`, and `blocked`.48- Blocking diagnostics are global errors or active-step errors in the current scope.49- Missing data-collection adapters require engine attention and may degrade or block based on explicit policy.50- `snapshotChange`, `fallbackChange`, and `operationalEvent` remain separate host outputs.51- `operationalEvent` is technical telemetry for logs, monitoring, and runbooks; it must not become the primary host UI contract.52- Respect `hostConfig.emitOperationalEvents` and `hostConfig.forwardAdapterOperationalEvents`.5354## Inventory Before New Contract5556Classify requested changes:5758- `ja-suportado-so-ux`: diagnostics/fallback exist but badges, docs, lab, or host display is incomplete.59- `ja-suportado-mal-nomeado-ou-mal-materializado`: a host calls a presentation token local CSS while `solution.presentation` or theme tokens already own it.60- `suportado-parcialmente`: a key exists in the model but renderer support, diagnostics, theme mapping, or validation is incomplete.61- `lacuna-real-de-contrato`: no existing presentation key, diagnostic code, fallback mode, event payload, or helper can express the requirement.6263Only a real gap justifies adding public presentation keys, diagnostic codes, or event types.6465## Validation6667Use focused local proof:6869- fallback: `src/lib/runtime/editorial-runtime-fallback.spec.ts`70- presentation/theme: `src/lib/runtime/editorial-runtime-theme.helpers.spec.ts` and presentation helper specs when present71- runtime UI diagnostics: `src/lib/editorial-form-runtime.component.spec.ts`72- stepper behavior: `src/lib/renderers/editorial-stepper.component.spec.ts`73- i18n: package i18n specs or catalog audit when text changes74- build: `npm run build:praxis-editorial-forms` when public presentation/fallback contracts change75- host/lab: E2E labs when operational events or visual runtime behavior changes7677Pair with `praxis-editorial-forms-journey-snapshot-runtime` for snapshot scope and with `praxis-editorial-forms-data-collection-adapters` for adapter diagnostics.