feat(kit): adopt @devframes/json-render (devframe v0.7.9)

[antfubot]

Description

devframe 0.7.6 extracted the json-render layer out of @devframes/hub into the opt-in @devframes/json-render package. This PR rewires Vite DevTools onto the new package (now upgraded through 0.7.9) while keeping the kit's public API stable and without pulling in @devframes/json-render-ui — the in-house webcomponents registry stays.

Kit (node/types)

• ctx.createJsonRenderer(spec) is now backed by createJsonRenderView from @devframes/json-render/node. The returned handle keeps updateSpec / updateState / _stateKey, and its methods are defined non-enumerably so the handle stays fully serializable when carried on a json-render dock entry's ui field.
• JsonRenderSpec / JsonRenderElement re-map onto @devframes/json-render; defineJsonRenderSpec becomes a kit-local identity helper (the hub dropped it).
• The kit contributes its json-render dock entry into the hub's open dock registry.
• 0.7.9 adaptation: hub 0.7.9 re-added its own deprecated createJsonRenderer/JsonRenderSpec/JsonRenderer on DevframeHubContext as a back-compat shim for pre-0.7 call sites ("kept working... will be removed in 0.8"), typed against a looser (optional props) spec shape than ours. KitNodeContext now extends Omit<DevframeHubContext, 'createJsonRenderer'> before redeclaring its own (stricter, non-deprecated) factory, and createPluginFromDevframe casts through DevframeHubContext at the mountDevframe call site (which never calls createJsonRenderer) instead of widening the kit's own type. No other functional change was needed between hub/devframe 0.7.6 and 0.7.9 — verified by diffing the published dist/ of both.

Core (client)

• Provide the client-side dock-renderer registry now required by the hub 0.7.6+ DocksContext.
• The hand-rolled webcomponents registry is retained, but its components now speak the @devframes/json-render base-catalog vocabulary — createJsonRenderView validates element props against that catalog at ingress, so specs must use the base prop names (e.g. Stack direction: 'row' | 'column', Text text, Badge variant: 'danger', KeyValueTable data, DataTable/CodeBlock height, Tree defaultExpanded).
• New: an element type with no entry in the registry (a spec authored against a newer base-catalog version than this client implements, a third-party catalog extension, or a typo) previously rendered nothing — @json-render/vue's <Renderer> only logs a console warning and returns null. Added UnsupportedComponent, wired as <Renderer>'s upstream fallback prop, so an unrenderable element now degrades to a visible, inspectable placeholder instead of silently disappearing. Includes a dedicated Storybook story and a docs note.
• The now-unused in-house catalog.ts / index.ts are removed.

Example / docs / stories updated to the base-catalog prop names.

Verified with pnpm typecheck && pnpm test && pnpm lint && pnpm build (export API snapshots for @vitejs/devtools-kit refreshed to match the new surface).

Linked Issues

Additional context

Reviewers may want to focus on: the serializability of the JsonRenderer handle on dock entries (non-enumerable methods), the base-catalog vocabulary alignment of the in-house components, and the Omit<DevframeHubContext, 'createJsonRenderer'> type fix for hub 0.7.9's back-compat shim.

This PR was created with the help of an agent.

[pkg-pr-new]

Open in StackBlitz

@vitejs/devtools

npm i https://pkg.pr.new/@vitejs/devtools@454

@vitejs/devtools-kit

npm i https://pkg.pr.new/@vitejs/devtools-kit@454

@vitejs/devtools-oxc

npm i https://pkg.pr.new/@vitejs/devtools-oxc@454

@vitejs/devtools-rolldown

npm i https://pkg.pr.new/@vitejs/devtools-rolldown@454

@vitejs/devtools-vite

npm i https://pkg.pr.new/@vitejs/devtools-vite@454

@vitejs/devtools-vitest

npm i https://pkg.pr.new/@vitejs/devtools-vitest@454

commit: 199bbef