Developers & plugin dev

From running the source, writing the manifest and wiring tools, to shipping a version someone else can install.

Technical group5 nodesUntested

For people changing code. Only the shortest path that works locally, plus the spots that break around a release. The official developer docs are not repeated here.

Dev setup & scaffolding Untested

Running from source, how a local plugin gets loaded, and the smallest debuggable setup.

Required：Host version · Runtime version · Load method · Debug entry · Verify command

First topics 2

Plugin anatomy & manifest Untested

Plugin layout, manifest fields, and how engines.dsh declares a host gate.

Required：Host version · Manifest field · Version-gate declaration · Sample repo · Verification status

First topics 2

MCP & tool definitions Untested

How tools register, tool names and call formats, and where UNKNOWN_TOOL comes from.

Required：Host version · Tool name · Call format · Gateway support · Raw error

First topics 2

Release & versioning Untested

How plugins are released, how to keep a CHANGELOG, and shipping builds for different host lines.

Required：Plugin version · Target host range · Release channel · Changelog · Rollback method

First topics 2

Developer index Untested

Node notes, dev-term links and the open tutorial list for this group.

Required：Node count · Last updated · Open claims · External-source labels

First topics 2

How missing content gets filled

If you have a run record, an error text or a working recipe, post it in the matching board. If you are unsure about the format, the submission note lists the fields.

Claim one DSH directory