@praxisui/dynamic-form 9.0.0-beta.20 → 9.0.0-beta.22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -101,7 +101,7 @@ more than the implementation can safely support.
101
101
  | `surface.open` command payload is visually authorable | Dynamic Form command rules now reuse the canonical `SurfaceOpenActionEditorComponent` | Yes for structured `payload`; `payloadExpr` remains advanced | Focused config-editor spec plus Playwright save/reopen flow | Safe for structured payload | Keep `payloadExpr` as advanced JSON-only; common target coverage includes `praxis-dynamic-form`, `praxis-table` and `praxis-crud`. |
102
102
  | `payloadExpr` is missing from UI | JSON contract supports it | Runtime-supported and preserved through advanced JSON | Focused config-editor specs cover preserve-without-payload and replace-when-structured-payload-is-authored | Advanced JSON-only | Treat as deliberate escape hatch unless product decision promotes it to structured UI. |
103
103
  | Multiple command effects are authorable | Contract shape is array-based | Primary effect is visually editable; secondary effects are preserved when editing the primary effect | Focused config-editor spec | Not fully LLM-safe for visual authoring | Keep secondary effects JSON-authored until a multi-effect UI is designed. |
104
- | Visual Builder README npm reflects local source | Published npm can lag local README and search metadata can be stale | npm search and `npm view` show canonical packages published as `9.0.0-beta.9`; local package manifests were aligned to `9.0.0-beta.9` | `validate:npm-registry -- --published`, `validate:npm-search-surface`, `validate:npm-docs`, `validate:package-peers` and `audit:npm-packages` pass | Safe for version parity; search-detail warnings remain | Verify npm package-detail links/keywords and decide the legacy `@praxisui/specification*` package policy before final public docs sign-off. |
104
+ | Visual Builder README npm reflects local source | Published npm can lag local README and search metadata can be stale | npm search and `npm view` show canonical packages published as `9.0.0-beta.20`; retired `@praxisui/specification*` packages are tracked as known retired packages | `release:postflight:npm`, `validate:npm-search-surface`, `validate:npm-docs`, `validate:package-peers` and `audit:npm-packages` pass for the canonical inventory | Safe for version parity; retired npm packages remain visible externally until npm deprecation is executed by an authenticated owner | Keep `@praxisui/specification*` out of active docs, configs and release inventory. |
105
105
 
106
106
  ## Technical Matrix A: `formRules`
107
107
 
@@ -189,9 +189,9 @@ runtime/editor gaps that unit specs did not expose:
189
189
  explicit.
190
190
  9. Validate npm publication and landing links after GitHub Actions publishes a
191
191
  new package version. Completed for version parity after aligning local
192
- package manifests to the published `9.0.0-beta.9`; remaining work is package
193
- detail link/keyword verification and legacy `@praxisui/specification*`
194
- policy.
192
+ package manifests to the published `9.0.0-beta.20`; legacy
193
+ `@praxisui/specification*` packages are retired known packages, not active
194
+ release inventory.
195
195
 
196
196
  ## NPM Publication Check
197
197
 
@@ -222,14 +222,13 @@ Resolved:
222
222
  - `validate:package-peers`, `validate:npm-docs` and `audit:npm-packages` pass
223
223
  for the aligned package metadata.
224
224
 
225
- Observed remaining warnings:
225
+ Retired package policy:
226
226
 
227
- - npm search metadata still needs package-detail link and keyword verification
228
- before final release sign-off.
229
- - npm search also reports legacy unexpected packages
230
- `@praxisui/specification` and `@praxisui/specification-core` at
231
- `1.0.0-beta.28`; decide whether to deprecate them or bring them into the
232
- canonical release inventory.
227
+ - npm search can still report `@praxisui/specification` and
228
+ `@praxisui/specification-core` at `1.0.0-beta.28`.
229
+ - They are tracked as known retired packages and must stay out of active docs,
230
+ workspace paths, test libs and release inventory.
231
+ - External npm deprecation still requires an authenticated package owner.
233
232
 
234
233
  ## Validation Plan
235
234