feat(marketplace): command consolidation + 8 new plugins (v8.1.0 → v9.0.0) [BREAKING]

Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action>
sub-command pattern. Git-flow consolidated from 8→5 commands (commit
variants absorbed into --push/--merge/--sync flags). Dispatch files,
name: frontmatter, and cross-reference updates for all plugins.

Phase 2: Design documents for 8 new plugins in docs/designs/.

Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate,
saas-react-platform, saas-test-pilot, data-seed, ops-release-manager,
ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents,
skills, README, and claude-md-integration. Marketplace grows from 12→20.

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

plugins/projman/skills/label-taxonomy/labels-reference.md

@@ -317,21 +317,21 @@ Most issues should have multiple labels from different categories:
 
 This skill is loaded when agents need to suggest labels:
 
-**In /sprint-plan:**
+**In /sprint plan:**
 The planner agent uses this reference along with `suggest_labels` MCP tool to recommend appropriate labels for newly created issues.
 
-**In /labels-sync:**
+**In /labels sync:**
 The command updates this file with the latest taxonomy from Gitea.
 
 ## Keeping This Updated
 
-**IMPORTANT:** Run `/labels-sync` to:
+**IMPORTANT:** Run `/labels sync` to:
 1. Fetch actual labels from Gitea
 2. Update this reference file
 3. Ensure suggestion logic matches current taxonomy
 
 **Update frequency:**
-- First time setup: Run `/labels-sync` immediately
+- First time setup: Run `/labels sync` immediately
 - Regular updates: Monthly or when taxonomy changes
 - Team notification: When new labels are added to Gitea
 
@@ -341,6 +341,6 @@ The command updates this file with the latest taxonomy from Gitea.
 1. Fetch labels dynamically using `get_labels` MCP tool
 2. Use `suggest_labels` for intelligent suggestions
 3. Reference this skill for context and patterns
-4. Update this file via `/labels-sync` when taxonomy changes
+4. Update this file via `/labels sync` when taxonomy changes
 
 This ensures the plugin adapts to taxonomy evolution without code changes.