PluginsSource
What the app knows about its plugins, read from the same places the kernel reads. `DeclaredPlugins` (config/plugins.php, as `ActivePlugins::wire()` left it) says what was declared; `PluginRegistryInterface` (storage/plugins.json) says what was installed or toggled. Both are optional — the panel degrades to "declared only" — and the metadata comes from each class's own `#[PluginMetadata]`, never from a second list. Capabilities come from `milpa/app-runtime` when it is installed, and are simply absent when it is not.
PluginsSource::__construct()
public function __construct(Milpa\Interfaces\Di\DIContainerInterface $container):Parameters
| Name | Type | Description |
|---|---|---|
| $container | Milpa\Interfaces\Di\DIContainerInterface |
PluginsSource::snapshot()
public function snapshot(): arrayThe plugins table plus, when available, the capability catalogue.