b6d40ed8ac
Bootstrap the plugin-facing SDK module so the fleet migration (P2) becomes a mechanical block/core/X -> block/pluginsdk/X import rewrite. - abi/proto/v1: the single source-of-truth ABI proto tree, copied from the cms authoring source (cms/backend/abi/proto/v1) with go_package retargeted to git.dev.alexdunmow.com/block/pluginsdk/abi/v1;abiv1. Kills the hand-kept cms/core proto duplication (audit gap 4). - abi/v1: generated Go bindings (buf generate); byte-identical to core's abi/v1 save the embedded go_package path. - plugin/ (registration + DI surface), plugin/wasmguest/** (transport shim, caps stubs, bnwasm db driver, testdata fixtures + golden .pb), and the guest-facing type packages: blocks (+builtin/shared/tags), templates (+pongo/bn), auth, settings, content, gating, crypto, rbac, video, ai, subscriptions, menus, datasources. Internal imports rewritten core -> pluginsdk; zero block/core references remain. - README/AGENTS(+CLAUDE symlink)/Makefile: proto is the contract, Go is one binding; no replace directives; templates/bn is a synced copy authored in cms. Spec: cms docs/superpowers/specs/2026-07-07-proto-first-plugin-sdk-design.md Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
14 lines
481 B
Go
14 lines
481 B
Go
package plugin
|
|
|
|
import (
|
|
"git.dev.alexdunmow.com/block/pluginsdk/rbac"
|
|
)
|
|
|
|
// CoreServiceBindings provides pre-built CMS service bindings that plugins
|
|
// can include in their ServiceRegistration with custom RBAC role mappings.
|
|
// The CMS constructs the actual service handlers — plugins just specify which
|
|
// services to mount and what roles apply.
|
|
type CoreServiceBindings interface {
|
|
Bind(serviceName string, methodRoles map[string]rbac.Role) (ConnectServiceBinding, error)
|
|
}
|