Brings module.yaml in line with F∆I 0.12.0's capability naming convention. The legacy schema_version 1 (with implicit provider) still loads in 0.12.0 via the grace-period default, but this bump makes the publisher identity explicit and unblocks storage-layout migration via 'fai migrate'. See fai/platform docs/reference/capability-namespaces.yaml + docs/operations/migration-to-0.12.md. Signed-off-by: flemming-it <sf@flemming.it>
29 lines
905 B
YAML
29 lines
905 B
YAML
schema_version: 2
|
|
provider: fai
|
|
name: studio-theme-solarized
|
|
version: 0.1.0
|
|
|
|
# Capability provided by this plugin. Studio plugins live in
|
|
# the `studio.*` namespace; the host filters list_capabilities()
|
|
# on this prefix to find plugins to load.
|
|
provides:
|
|
- capability: studio.theme.solarized
|
|
version: 0.1.0
|
|
|
|
# No inputs / outputs — plugins are called via WIT exports,
|
|
# not via the flow-engine `invoke` path. These two sections
|
|
# stay empty so the hub's manifest validator doesn't trip.
|
|
inputs: {}
|
|
outputs: {}
|
|
|
|
# No permissions required. A theme plugin is pure data — two
|
|
# color schemes, no I/O.
|
|
permissions: []
|
|
|
|
# Studio-side extension declaration. Read by Studio's
|
|
# plugin-host at discovery time so it knows which WIT export
|
|
# interfaces to expect on this component. Must match what the
|
|
# crate actually exports; the hub rejects mismatches at install.
|
|
studio_extension:
|
|
hooks:
|
|
- theme
|