| Node | Covers | Measured |
|---|---|---|
| Development setup | Getting a plugin running, making edits take effect, where credentials come from | 3 verified |
| Plugin anatomy | What each manifest field does, and what engines really enforces | 2 verified |
| MCP and tool definitions | Registering internal capability as a tool; diagnosing a rejected name | 1 verified / 1 pending |
| Release and versioning | Writing a CHANGELOG, shipping for two host generations | 1 verified / 1 pending |
| Developer index | Navigation for this group | (this page) |
If you have ten minutes
- Start with the minimal plugin — three files, copyable.
- Then the hot-reload item, which saves you fifteen minutes of confusion.
- Then the over-narrow engines item, which overturns what you expect a version gate to do.
Every measurement here ran under an isolated
DSH_HOME; the real configuration was untouched. That is also the right way to experiment with plugins: a temp directory plus your own key, deletable when something goes wrong.