Audience: Plugin authors and host implementors needing strict, normative tables. Engine baseline: v12.1.0 "Living DreamGraph". Companion: see the Plugin Developer Guide for task-oriented walkthroughs.
This reference is the source of truth. Where the guide and the reference disagree, the reference wins. Where the reference and the SDK source disagree, the SDK source wins (and a doc bug should be filed).
- Manifest schema — every field, every constraint.
- Capabilities — the locked vocabulary.
- Effects — observable cognitive effects.
- Reject reasons — every
plugin.output.rejected.reason. - PluginContext API — TypeScript surface.
- Events — stable kinds, experimental kinds, payload schemas.
- CLI —
dg pluginsubcommands. - Host configuration — env vars and
instance.json. - Telemetry events — the
plugin.*stream. - Architect tabs — declarative tab contract, plan state, routes, lifecycle, and telemetry.
- MUST / MUST NOT / SHOULD are used in the RFC 2119 sense.
- Tables are exhaustive unless explicitly marked "non-exhaustive".
- Source-code references link to the canonical file at the repo root.