feat(marketplace): hook migration, projman commands, optimizations [BREAKING]

Remove all SessionStart and PostToolUse hooks across the marketplace,
retaining only PreToolUse safety hooks and UserPromptSubmit quality hooks.
Add /project and /adr command families, /hygiene check, /cv status.
Create 7 new projman skills for project lifecycle management.
Remove /pm-debug, /suggest-version, /proposal-status commands.

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

plugins/projman/agents/planner.md

@@ -30,7 +30,6 @@ You are the **Planner Agent** - a methodical architect who thoroughly analyzes r
 - skills/issue-conventions.md
 - skills/planning-workflow.md
 - skills/label-taxonomy/labels-reference.md
-- skills/domain-consultation.md
 
 **Phase 3 skills — read ONCE before requesting approval:**
 - skills/sprint-approval.md
@@ -78,25 +77,10 @@ Execute `skills/wiki-conventions.md` - Create proposal and implementation pages.
 ### 6. Task Sizing
 Execute `skills/task-sizing.md` - **REFUSE to create L/XL tasks without breakdown.**
 
-### 7. Domain Consultation
-
-Execute `skills/domain-consultation.md` (Planning Protocol section):
-
-1. **After drafting issues but BEFORE creating them in Gitea**
-2. **Analyze each issue for domain signals:**
-   - Check planned labels for `Component/Frontend`, `Component/UI` -> Domain/Viz
-   - Check planned labels for `Component/Database`, `Component/Data` -> Domain/Data
-   - Scan issue description for domain keywords (see skill for full list)
-3. **For detected domains, append acceptance criteria:**
-   - Domain/Viz: Design System Compliance checklist
-   - Domain/Data: Data Integrity checklist
-4. **Add corresponding `Domain/*` label** to the issue's label set
-5. **Document in planning summary** which issues have domain gates active
-
-### 8. Issue Creation
+### 7. Issue Creation
 Execute `skills/issue-conventions.md` - Use proper format with wiki references.
 
-### 9. Request Approval
+### 8. Request Approval
 Execute `skills/sprint-approval.md` - Planning DOES NOT equal execution permission.
 
 ## Critical Reminders
@@ -108,7 +92,7 @@ Execute `skills/sprint-approval.md` - Planning DOES NOT equal execution permissi
 5. **ALWAYS search lessons** - Past experience informs better planning
 6. **ALWAYS include wiki reference** - Every issue links to implementation wiki page
 7. **ALWAYS use proper title format** - `[Sprint XX] <type>: <description>`
-8. **ALWAYS check domain signals** - Every issue gets checked for viz/data domain applicability before creation
+8. **ALWAYS use proper labels** - Apply relevant labels from the label taxonomy
 
 ## Your Mission