Authoring SDK for Vox code plugins: re-exports the stable plugin ABI + the declare_plugin! glue macro so plugins drop ~25 lines of identical dylib-export boilerplate. ABI-neutral (byte-identical exports).
Ergonomic authoring surface for Vox code plugins. It re-exports the stable
plugin ABI ([vox_plugin_api]) plus the [abi_stable] types plugin authors need,
and provides the [declare_plugin!] macro that emits the dylib export glue
(root_module / manifest_json / init) every plugin otherwise hand-copies.
The SDK adds zero new ABI surface — declare_plugin! expands to exactly the
#[export_root_module] + #[sabi_extern_fn] pattern plugins write by hand today, so a
macro-built plugin and a hand-built one produce byte-identical exports. Because the
macro stamps [vox_plugin_api::VOX_PLUGIN_ABI_VERSION] (not a hard-coded number) and
plugins implement the [VoxPlugin] trait from vox-plugin-api directly, new extension
points are picked up on recompile without touching the SDK. See
docs/superpowers/plans/2026-06-06-plugin-sdk-and-abi-sync.md.
Wrap a concrete [VoxPlugin] value into the stable-ABI trait object the host loads. Equivalent to the hand-written VoxPlugin_TO::from_value(plugin, TD_Opaque).
manifest_id_version_json
Build the manifest_json ABI probe ({"id":..,"version":..}) from an embedded Plugin.toml string. Used by [declare_plugin!] so id/version have a single authoring site (the manifest) rather than being re-typed as macro arguments. On a parse failure or a missing [plugin] id/version, falls back to empty/0.0.0 — the host reads the real Plugin.toml from disk anyway; this probe is advisory.
Wrap a concrete [VoxPlugin] value into the stable-ABI trait object the host loads. Equivalent to the hand-written VoxPlugin_TO::from_value(plugin, TD_Opaque).
Build the manifest_json ABI probe ({"id":..,"version":..}) from an embedded Plugin.toml string. Used by [declare_plugin!] so id/version have a single authoring site (the manifest) rather than being re-typed as macro arguments. On a parse failure or a missing [plugin] id/version, falls back to empty/0.0.0 — the host reads the real Plugin.toml from disk anyway; this probe is advisory.