From ee3c32c1032e14f0653f32721f320619da74022a Mon Sep 17 00:00:00 2001 From: Vincent Koc Date: Fri, 24 Apr 2026 22:21:37 -0700 Subject: [PATCH] docs(plugins): clarify inspector package boundary --- docs/plugins/compatibility.md | 24 ++++++++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/docs/plugins/compatibility.md b/docs/plugins/compatibility.md index ac9e92f536f..819fbe1b568 100644 --- a/docs/plugins/compatibility.md +++ b/docs/plugins/compatibility.md @@ -31,6 +31,30 @@ The registry is the source for maintainer planning and future plugin inspector checks. If a plugin-facing behavior changes, add or update the compatibility record in the same change that adds the adapter. +## Plugin inspector package + +The plugin inspector should live outside the core OpenClaw repo as a separate +package/repository backed by the versioned compatibility and manifest +contracts. + +The day-one CLI should be: + +```sh +openclaw-plugin-inspector ./my-plugin +``` + +It should emit: + +- manifest/schema validation +- the contract compatibility version being checked +- install/source metadata checks +- cold-path import checks +- deprecation and compatibility warnings + +Use `--json` for stable machine-readable output in CI annotations. OpenClaw +core should expose contracts and fixtures the inspector can consume, but should +not publish the inspector binary from the main `openclaw` package. + ## Deprecation policy OpenClaw should not remove a documented plugin contract in the same release