core/buf.yaml
Alex Dunmow 35436581b9 feat(proto): consume canonical block/proto as a submodule
Remove core's local proto/ fork and pull the canonical block/proto repo in
as a submodule at the same path. buf.yaml now sources from the submodule's
orchestrator/v1 namespace; everything outside that (blockninja, helpdesk)
is excluded from generation.

This brings the orchestrator's local-only RPCs (PluginScopeService.ListMyPlugins,
PluginRegistryService.SubmitForReview, the full PluginModerationService) into
core's bindings — harmless surface area for the CLI, prerequisite for the
orchestrator to also stop forking the proto.

Side effect: the CLI's account picker now uses the canonical
AccountService.ListMyAccounts in accounts.proto rather than the duplicate
PluginAuthService.ListMyAccounts that lived only in core's fork. The
existing Account message uses Name (no DisplayName / Role), so the picker
output collapses to "slug — Name".

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-06-04 20:45:47 +08:00

21 lines
644 B
YAML

version: v2
# proto/ is a git submodule pointing at block/proto (the canonical shared
# proto repo). The CLI in this module consumes the orchestrator v1 API
# surface; everything else under the submodule (blockninja, helpdesk) is
# excluded from generation. Within orchestrator/v1 only plugin_registry and
# accounts are wired through the CLI today, but generating the rest is cheap
# and lets us add new callers without retouching this config.
modules:
- path: proto
includes:
- proto/orchestrator/v1
lint:
use:
- STANDARD
except:
- PACKAGE_SAME_GO_PACKAGE
- RPC_REQUEST_RESPONSE_UNIQUE
breaking:
use:
- FILE