fix(marketplace): correct stale hook references and migration guide errors

- claude-config-audit-settings.md: update hook inventory to post-Decision #29 state
- maintainer.md: remove PostToolUse references, update to current hook types
- settings-optimization.md: update review layer table and hooks.json format
- claude-config-optimize-settings.md: fix stale doc-guardian PostToolUse reference
- project-hygiene/claude-md-integration.md: rewrite for manual /hygiene check
- doc-guardian: update doc-sync.md and sync-workflow.md hook references
- MIGRATION-v9.md: mark deleted commands as Removed, not renamed
- projman/task-sizing.md: PostToolUse → PreToolUse in example
- scripts/setup.sh: /labels-sync → /labels sync
- docs/CONFIGURATION.md: doc-guardian "Commands and hooks" → "Commands only"
- docs/prompts/INDEX.md: add prompt execution index

Version: 9.0.1

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

plugins/claude-config-maintainer/agents/maintainer.md

@@ -96,7 +96,7 @@ Use this mapping to identify active plugins:
 | `gitea` | projman |
 | `netbox` | cmdb-assistant |
 
-Also check for hook-based plugins (project-hygiene uses `PostToolUse` hooks).
+Also check for hook-based plugins (code-sentinel, git-flow, cmdb-assistant use `PreToolUse` safety hooks; clarity-assist uses `UserPromptSubmit` quality hook).
 
 **Step 2: Check CLAUDE.md for Plugin References**
 
@@ -151,7 +151,7 @@ Evaluate using `skills/settings-optimization.md`:
 Before recommending auto-allow patterns, verify active review layers:
 
 1. Read `plugins/*/hooks/hooks.json` for each installed plugin
-2. Map hook types (PreToolUse, PostToolUse) to tool matchers (Write, Edit, Bash)
+2. Map hook types (PreToolUse, UserPromptSubmit) to tool matchers (Write, Edit, MultiEdit, Bash, MCP patterns)
 3. Confirm plugins are listed in `.claude-plugin/marketplace.json`
 4. Only recommend auto-allow for scopes covered by ≥2 verified review layers
 

plugins/claude-config-maintainer/commands/claude-config-audit-settings.md

@@ -62,21 +62,20 @@ Using `settings-optimization.md` Section 3, detect:
 
 ### Step 4: Detect Active Marketplace Hooks
 
-Read `plugins/*/hooks/hooks.json` files:
+Read `plugins/*/hooks/hooks.json` files (post-Decision #29 — only PreToolUse safety hooks and UserPromptSubmit quality hooks exist):
 
 ```bash
-# Check each plugin's hooks
-plugins/code-sentinel/hooks/hooks.json     # PreToolUse security
-plugins/doc-guardian/hooks/hooks.json      # PostToolUse drift detection
-plugins/project-hygiene/hooks/hooks.json   # PostToolUse cleanup
-plugins/data-platform/hooks/hooks.json     # PostToolUse schema diff
-plugins/contract-validator/hooks/hooks.json # Plugin validation
+# Check each plugin's hooks (exhaustive post-v8.1.0 inventory)
+plugins/code-sentinel/hooks/hooks.json     # PreToolUse: Write|Edit|MultiEdit → security-check.sh
+plugins/git-flow/hooks/hooks.json          # PreToolUse: Bash → branch-check.sh, commit-msg-check.sh
+plugins/cmdb-assistant/hooks/hooks.json    # PreToolUse: MCP create/update → validate-input.sh
+plugins/clarity-assist/hooks/hooks.json    # UserPromptSubmit → vagueness-check.sh
 ```
 
 Parse each to identify:
-- Hook event type (PreToolUse, PostToolUse)
-- Tool matchers (Write, Edit, MultiEdit, Bash)
-- Whether hook is command type (reliable) or prompt type (unreliable)
+- Hook event type (PreToolUse or UserPromptSubmit only — no other types should exist)
+- Tool matchers (Write, Edit, MultiEdit, Bash, MCP patterns)
+- Whether hook is command type (must be — prompt type is forbidden)
 
 ### Step 5: Map Review Layers to Directory Scopes
 
@@ -118,9 +117,9 @@ Issues Found:
 
 Active Review Layers Detected:
   ✓ code-sentinel (PreToolUse: Write|Edit|MultiEdit)
-  ✓ doc-guardian (PostToolUse: Write|Edit|MultiEdit)
-  ✓ project-hygiene (PostToolUse: Write|Edit)
-  ✗ data-platform schema-diff (not detected)
+  ✓ git-flow (PreToolUse: Bash — branch naming + commit format)
+  ✓ cmdb-assistant (PreToolUse: MCP create/update)
+  ✓ clarity-assist (UserPromptSubmit: vagueness detection)
 
 Recommendations:
   1. [specific action with pattern]
@@ -146,7 +145,7 @@ When `--diagram` is specified, generate a Mermaid flowchart showing:
 
 **Color coding:**
 - PreToolUse hooks: Blue
-- PostToolUse hooks: Green
+- UserPromptSubmit hooks: Green
 - Sprint Approval: Amber
 - PR Review: Purple
 
@@ -161,7 +160,7 @@ flowchart LR
 
     subgraph Review Layers
         CS[code-sentinel]
-        DG[doc-guardian]
+        GF[git-flow]
         PR[pr-review]
     end
 
@@ -172,18 +171,17 @@ flowchart LR
     end
 
     W --> CS
-    W --> DG
     E --> CS
-    E --> DG
+    B --> GF
     CS --> A
-    DG --> A
+    GF --> A
     B --> P
 
     classDef preHook fill:#e3f2fd
-    classDef postHook fill:#e8f5e9
+    classDef userPrompt fill:#e8f5e9
     classDef prReview fill:#f3e5f5
     class CS preHook
-    class DG postHook
+    class GF preHook
     class PR prReview
 ```
 

plugins/claude-config-maintainer/commands/claude-config-optimize-settings.md

@@ -171,7 +171,7 @@ Switching to reviewed profile...
 
 Prerequisites verified:
   ✓ code-sentinel hook active (PreToolUse)
-  ✓ doc-guardian hook active (PostToolUse)
+  ✓ git-flow hook active (PreToolUse)
   ✓ 2+ review layers detected
 
 This profile:

plugins/claude-config-maintainer/skills/settings-optimization.md

@@ -351,14 +351,19 @@ To verify which review layers are active, read these files:
 
 ```json
 {
-  "hooks": [
-    {
-      "event": "PreToolUse",
-      "type": "command",
-      "command": "./hooks/security-check.sh",
-      "tools": ["Write", "Edit", "MultiEdit"]
-    }
-  ]
+  "hooks": {
+    "PreToolUse": [
+      {
+        "matcher": "Write|Edit|MultiEdit",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "./hooks/security-check.sh"
+          }
+        ]
+      }
+    ]
+  }
 }
 ```
 

plugins/doc-guardian/commands/doc-sync.md

@@ -5,7 +5,7 @@ description: Synchronize all pending documentation updates in a single commit
 
 # /doc sync
 
-Apply all pending documentation updates detected by doc-guardian hooks.
+Apply all pending documentation updates detected by `/doc audit`.
 
 ## Skills to Load
 

plugins/doc-guardian/skills/sync-workflow.md

@@ -12,7 +12,7 @@ Defines how to synchronize documentation with code changes.
 ## When to Use
 
 - **doc sync**: Apply pending documentation updates
-- **PostToolUse hook**: Queue drift for later sync
+- **doc audit**: Detect drift manually (PostToolUse hook removed per Decision #29)
 
 ---
 

plugins/project-hygiene/claude-md-integration.md

@@ -1,14 +1,23 @@
 ## Project Cleanup (project-hygiene)
 
-This project uses the **project-hygiene** plugin for automated post-task cleanup.
+This project uses the **project-hygiene** plugin for file organization and cleanup checks.
 
 ### How It Works
 
-The plugin automatically runs after file Write or Edit operations to:
+Run `/hygiene check` to scan for common project cleanliness issues:
 
-1. **Delete temporary files** - Removes `*.tmp`, `*.bak`, `__pycache__/`, `.pytest_cache/`, etc.
-2. **Warn about unexpected root files** - Alerts when files are created outside expected locations
-3. **Identify orphaned files** - Detects supporting files that may no longer be needed
+1. **Temp file detection** — finds `*.tmp`, `*.bak`, `*.swp`, `*~` files
+2. **Misplaced files** — files outside their expected directories
+3. **Empty directories** — directories with no files
+4. **Large files** — files exceeding reasonable size thresholds
+5. **Debug artifacts** — leftover debug logs, console.log, print statements
+
+### Usage
+
+```
+/hygiene check              # Run all checks
+/hygiene check --fix        # Auto-fix safe issues (delete temp files, remove empty dirs)
+```
 
 ### Configuration
 
@@ -23,14 +32,7 @@ The plugin can be configured via `.hygiene.json` in the project root:
 }
 ```
 
-### Hook Events
+### Notes
 
-The plugin registers on the following events:
-- `PostToolUse` (matcher: `Write|Edit`) - Runs cleanup after file modifications
-
-### Usage Guidelines
-
-- Let the hook run automatically - no manual intervention needed
-- Review warnings about unexpected root files
-- Configure `.hygiene.json` to customize cleanup behavior for your project
-- Check cleanup output if files seem to disappear unexpectedly
+- This was previously a PostToolUse hook (automatic). Since v8.1.0 (Decision #29), it runs manually via `/hygiene check`.
+- Add `/hygiene check` as an explicit step in your prompt files where project cleanliness matters.

plugins/projman/skills/task-sizing.md

@@ -82,7 +82,7 @@ Labels: Efforts/S
 
 [Sprint 3] chore: Register hook in hooks.json
 Labels: Efforts/XS
-- [ ] Add PostToolUse:Edit hook entry
+- [ ] Add PreToolUse:Edit hook entry
 ```
 
 ---