Feature: expose loaded plugin versions in running session

Feature request

Expose loaded plugin versions in the running session so users can verify what is actually active without inspecting the filesystem.

Problem

After running /plugin marketplace update and /reload-plugins, there is no way to confirm which plugin version the session is actually using. The only feedback from /reload-plugins is a count of loaded items (e.g., "Loaded 12 skills, 8 hooks"). This is insufficient to diagnose version mismatches.

Today the only way to verify is to manually inspect the plugin cache directory on disk and compare file contents against observed behavior. For a control-plane component that enforces agent behavior constraints, this is unacceptable.

Proposed solution

Add a command (e.g., /plugin status or /plugin list --verbose) that shows:

• Plugin name
• Loaded version (what the running session is using)
• Available version (what's on disk / in the marketplace)
• Component breakdown: N skills, N hooks, N commands loaded
• Any load errors or warnings

Example output:

standard-tooling-marketplace/standard-tooling
  Loaded:    1.4.12
  Available: 1.4.12
  Components: 6 skills, 10 hooks, 2 commands
  Status: OK

another-plugin
  Loaded:    2.1.0
  Available: 2.2.0
  Components: 3 skills, 0 hooks, 1 command
  Status: UPDATE AVAILABLE

Context

This was discovered alongside a bug where /reload-plugins does not actually reload hooks (filed separately). Even once that bug is fixed, the lack of version visibility makes plugin management error-prone. Users managing plugins that enforce correctness constraints need deterministic, evidence-based confirmation that the right version is loaded.

Environment

• Claude Code CLI (macOS, Darwin 25.3.0)
• Claude Opus 4.6