docs: refresh plugin cli and inspect refs

docs/cli/plugins.md

@@ -21,8 +21,14 @@ Related:
 
 ```bash
 openclaw plugins list
+openclaw plugins list --enabled
+openclaw plugins list --verbose
+openclaw plugins list --json
 openclaw plugins install <path-or-spec>
 openclaw plugins inspect <id>
+openclaw plugins inspect <id> --json
+openclaw plugins inspect --all
+openclaw plugins info <id>
 openclaw plugins enable <id>
 openclaw plugins disable <id>
 openclaw plugins uninstall <id>
@@ -30,6 +36,7 @@ openclaw plugins doctor
 openclaw plugins update <id>
 openclaw plugins update --all
 openclaw plugins marketplace list <marketplace>
+openclaw plugins marketplace list <marketplace> --json
 ```
 
 Bundled plugins ship with OpenClaw. Some are enabled by default (for example
@@ -153,9 +160,24 @@ For local paths and archives, OpenClaw auto-detects:
 
 Compatible bundles install into the normal extensions root and participate in
 the same list/info/enable/disable flow. Today, bundle skills, Claude
-command-skills, Claude `settings.json` defaults, Cursor command-skills, and compatible Codex hook
-directories are supported; other detected bundle capabilities are shown in
-diagnostics/info but are not yet wired into runtime execution.
+command-skills, Claude `settings.json` defaults, Claude `.lsp.json` /
+manifest-declared `lspServers` defaults, Cursor command-skills, and compatible
+Codex hook directories are supported; other detected bundle capabilities are
+shown in diagnostics/info but are not yet wired into runtime execution.
+
+### List
+
+```bash
+openclaw plugins list
+openclaw plugins list --enabled
+openclaw plugins list --verbose
+openclaw plugins list --json
+```
+
+Use `--enabled` to show only loaded plugins. Use `--verbose` to switch from the
+table view to per-plugin detail lines with source/origin/version/activation
+metadata. Use `--json` for machine-readable inventory plus registry
+diagnostics.
 
 Use `--link` to avoid copying a local directory (adds to `plugins.load.paths`):
 
@@ -228,7 +250,8 @@ openclaw plugins inspect <id> --json
 
 Deep introspection for a single plugin. Shows identity, load status, source,
 registered capabilities, hooks, tools, commands, services, gateway methods,
-HTTP routes, policy flags, diagnostics, and install metadata.
+HTTP routes, policy flags, diagnostics, install metadata, bundle capabilities,
+and any detected MCP or LSP server support.
 
 Each plugin is classified by what it actually registers at runtime:
 
@@ -242,4 +265,28 @@ See [Plugin shapes](/plugins/architecture#plugin-shapes) for more on the capabil
 The `--json` flag outputs a machine-readable report suitable for scripting and
 auditing.
 
+`inspect --all` renders a fleet-wide table with shape, capability kinds,
+compatibility notices, bundle capabilities, and hook summary columns.
+
 `info` is an alias for `inspect`.
+
+### Doctor
+
+```bash
+openclaw plugins doctor
+```
+
+`doctor` reports plugin load errors, manifest/discovery diagnostics, and
+compatibility notices. When everything is clean it prints `No plugin issues
+detected.`
+
+### Marketplace
+
+```bash
+openclaw plugins marketplace list <source>
+openclaw plugins marketplace list <source> --json
+```
+
+Marketplace list accepts a local marketplace path, a `marketplace.json` path, a
+GitHub shorthand like `owner/repo`, or a git URL. `--json` prints the resolved
+source label plus the parsed marketplace manifest and plugin entries.

docs/plugins/manifest.md

@@ -23,8 +23,9 @@ OpenClaw auto-detects those bundle layouts too, but they are not validated
 against the `openclaw.plugin.json` schema described here.
 
 For compatible bundles, OpenClaw currently reads bundle metadata plus declared
-skill roots, Claude command roots, Claude bundle `settings.json` defaults, and
-supported hook packs when the layout matches OpenClaw runtime expectations.
+skill roots, Claude command roots, Claude bundle `settings.json` defaults,
+Claude bundle LSP defaults, and supported hook packs when the layout matches
+OpenClaw runtime expectations.
 
 Every native OpenClaw plugin **must** ship a `openclaw.plugin.json` file in the
 **plugin root**. OpenClaw uses this manifest to validate configuration

docs/tools/plugin.md

@@ -201,16 +201,23 @@ Some categories are exclusive (only one active at a time):
 ## CLI reference
 
 ```bash
-openclaw plugins list                    # compact inventory
-openclaw plugins inspect <id>            # deep detail
-openclaw plugins inspect <id> --json     # machine-readable
-openclaw plugins doctor                  # diagnostics
+openclaw plugins list                       # compact inventory
+openclaw plugins list --enabled            # only loaded plugins
+openclaw plugins list --verbose            # per-plugin detail lines
+openclaw plugins list --json               # machine-readable inventory
+openclaw plugins inspect <id>              # deep detail
+openclaw plugins inspect <id> --json       # machine-readable
+openclaw plugins inspect --all             # fleet-wide table
+openclaw plugins info <id>                 # inspect alias
+openclaw plugins doctor                    # diagnostics
 
-openclaw plugins install <package>        # install (ClawHub first, then npm)
-openclaw plugins install clawhub:<pkg>   # install from ClawHub only
-openclaw plugins install <spec> --force  # overwrite existing install
-openclaw plugins install <path>          # install from local path
-openclaw plugins install -l <path>       # link (no copy) for dev
+openclaw plugins install <package>         # install (ClawHub first, then npm)
+openclaw plugins install clawhub:<pkg>     # install from ClawHub only
+openclaw plugins install <spec> --force    # overwrite existing install
+openclaw plugins install <path>            # install from local path
+openclaw plugins install -l <path>         # link (no copy) for dev
+openclaw plugins install <plugin> --marketplace <source>
+openclaw plugins install <spec> --pin      # record exact resolved npm spec
 openclaw plugins install <spec> --dangerously-force-unsafe-install
 openclaw plugins update <id>             # update one plugin
 openclaw plugins update <id> --dangerously-force-unsafe-install
@@ -218,6 +225,7 @@ openclaw plugins update --all            # update all
 openclaw plugins uninstall <id>          # remove config/install records
 openclaw plugins uninstall <id> --keep-files
 openclaw plugins marketplace list <source>
+openclaw plugins marketplace list <source> --json
 
 openclaw plugins enable <id>
 openclaw plugins disable <id>
@@ -241,6 +249,15 @@ dependency installs use the matching `dangerouslyForceUnsafeInstall` request
 override instead, while `openclaw skills install` remains the separate ClawHub
 skill download/install flow.
 
+Compatible bundles participate in the same plugin list/inspect/enable/disable
+flow. Current runtime support includes bundle skills, Claude command-skills,
+Claude `settings.json` defaults, Claude `.lsp.json` and manifest-declared
+`lspServers` defaults, Cursor command-skills, and compatible Codex hook
+directories.
+
+`openclaw plugins inspect <id>` also reports detected bundle capabilities plus
+supported or unsupported MCP and LSP server entries for bundle-backed plugins.
+
 See [`openclaw plugins` CLI reference](/cli/plugins) for full details.
 
 ## Plugin API overview