What problem does it solve?
Maintaining the mesh-llm plugin web UI projection requires keeping the manifest contract, backend routes, UI mounting logic, exemplar package, and documentation in sync, and drift between any of these breaks plugin authors' ability to ship working web UIs.
Core Features & Use Cases
- Contract Baseline Checks: Verifies the manifest
web_ui field, lifecycle states (none, ready, disabled, invalid, plugin_not_running), and the /api/plugins/:plugin/web-ui route namespace against the current implementation.
- Ownership Boundary Enforcement: Keeps plugin process state separate from web UI projection state so invalid bundles never break non-UI capabilities like MCP tools.
- Exemplar Drift Guard: Uses the maintained exemplar under
docs/plugins/exemplars/web-ui/ to validate manifest, bundle, and settings persistence behavior end to end.
- Use Case: When a report says a plugin's web UI is broken, follow the ordered triage flow—process running, projection state, bundle root, entry script, config tab, settings endpoint—to isolate the fault without disabling the plugin process.
Quick Start
Use the plugin-web-ui-extension skill to triage why my mesh-llm plugin's web UI page is not mounting and verify the projection contract still matches the implementation.