Not a debugger. A runtime documentation tool.

Explorer walks the same chain the runtime itself executes:

• Plugin list — every registered plugin, its name, version, and description.
• Workflow visualization — the ordered steps of every workflow, and the allowedguard that controls who can run it.
• Step dependencies — which steps depend on which, resolved from dependsOn.
• Capability registry — every capability, with its input/output schema if declared.

Explorer auto-generates when the dev runtime registers plugins — a./explorer folder appears at your project root, and in the browser it can pop out on its own or be opened manually. Production runtime never includes it — Explorer is a development-time mirror of your runtime, not a shipped dependency.