feat(commands): make dispatch files active command handlers

All 25 dispatch files now have name: in frontmatter with Workflow
section that displays sub-commands and prompts for selection.
Bare /noun invocation is now useful instead of a dead end.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

plugins/ops-deploy-pipeline/commands/deploy.md

@@ -1,18 +1,27 @@
 ---
-description: Deployment management — generate configs, validate pipelines, manage environments
+name: deploy
+description: Deployment management — type /deploy <action> for commands
 ---
 
 # /deploy
 
 CI/CD deployment pipeline management for Docker Compose and self-hosted infrastructure.
 
-## Sub-commands
+When invoked without a sub-command, display available actions and ask which to run.
 
-| Sub-command | Description |
-|-------------|-------------|
+## Available Commands
+
+| Command | Description |
+|---------|-------------|
 | `/deploy setup` | Interactive setup wizard for deployment configuration |
 | `/deploy generate` | Generate docker-compose.yml, Caddyfile, and systemd units |
 | `/deploy validate` | Validate deployment configs for correctness and best practices |
 | `/deploy env` | Manage environment-specific config files (.env.development, .env.production) |
 | `/deploy check` | Pre-deployment health check (disk, memory, ports, DNS, Docker) |
 | `/deploy rollback` | Generate rollback plan for a deployment |
+
+## Workflow
+
+1. Display the table above
+2. Ask: "Which command would you like to run?"
+3. Route to the selected sub-command