Lets an extension ship site-facing components as a bundle, the same way the Chelekom UI kit does (§22, Path A).

Why this is a wrapper and not a mechanism

MishkaCmsCore.Runtime.Handlers.UiKitHandler already installs a mishka.ui_kit.bundle.v3 bundle: idempotent upserts, archived-row protection, defer_runtime batching and a single sync_after_bulk at the end. An extension that ships template-shaped components — a post card, a tag cloud, a hero — needs exactly that and nothing more, and once its components are ordinary Component rows the palette, the inspector, the examples modal and the compiler all work with no editor changes at all.

So this module is deliberately thin. It finds the extension's bundle, names it, and hands it to the handler. Everything that could go wrong on install is already handled one layer down.

The other path

A component that cannot be a stored template — one that streams live data — is not this. That is MishkaCmsCore.Builder.PaletteEntry on the builder:components hook.

Shipping a bundle

Put it at priv/cms_components/<name>.json in the extension, then install on setup:

MishkaCmsCore.Runtime.ExtensionKit.install!(:mishka_blog)

and remove it on teardown with uninstall!/2.