fix(commands): wire dispatch files to real sub-command names via Skill tool

All dispatch files referenced display names (e.g., `/doc audit`) that don't
correspond to real slash commands. Claude Code resolves commands by filename,
so `/doc audit` loads `doc.md` with $ARGUMENTS but never routes to `doc-audit.md`.

Changes:
- Updated 24 dispatch files with explicit Skill tool routing
- Added "Command to Invoke" column with plugin-prefixed names
- Added $ARGUMENTS matching for automatic routing
- RFC dispatch file uses inline handling (no separate command files)
- Updated COMMANDS-CHEATSHEET.md with invocation methods
- Updated MIGRATION-v9.md with command name mapping explanation

Affects: 25 dispatch files across 12 plugins (core, data, saas, ops, debug)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

plugins/debug-mcp/commands/debug-mcp.md

@@ -10,16 +10,24 @@ When invoked without a sub-command, display available actions and ask which to r
 
 ## Available Commands
 
-| Command | Description |
-|-------------|-------------|
-| `/debug-mcp status` | Show all MCP servers with health status |
-| `/debug-mcp test` | Test a specific MCP tool call |
-| `/debug-mcp logs` | View recent MCP server logs and errors |
-| `/debug-mcp inspect` | Inspect MCP server config and dependencies |
-| `/debug-mcp scaffold` | Generate MCP server skeleton project |
+| Action | Command to Invoke | Description |
+|--------|-------------------|-------------|
+| `status` | `/debug-mcp:debug-mcp-status` | Show all MCP servers with health status |
+| `test` | `/debug-mcp:debug-mcp-test` | Test a specific MCP tool call |
+| `logs` | `/debug-mcp:debug-mcp-logs` | View recent MCP server logs and errors |
+| `inspect` | `/debug-mcp:debug-mcp-inspect` | Inspect MCP server config and dependencies |
+| `scaffold` | `/debug-mcp:debug-mcp-scaffold` | Generate MCP server skeleton project |
 
-## Workflow
+## Routing
 
-1. Display the table above
-2. Ask: "Which command would you like to run?"
-3. Route to the selected sub-command
+If `$ARGUMENTS` is provided (e.g., user typed `/debug-mcp status`):
+1. Match the first word of `$ARGUMENTS` against the **Action** column above
+2. **Invoke the corresponding command** from the "Command to Invoke" column using the Skill tool
+3. Pass any remaining arguments to the invoked command
+
+If no arguments provided:
+1. Display the Available Commands table
+2. Ask: "Which action would you like to run?"
+3. When the user responds, invoke the matching command using the Skill tool
+
+**Note:** Commands can also be invoked directly using their plugin-prefixed names (e.g., `/debug-mcp:debug-mcp-status`)