updated settings

.claude/agents/presentation-curator.md

@@ -54,7 +54,7 @@ After changes, verify:
 5. Any `goToSlide()` calls in the TOC point to correct slide numbers
 6. Weighted slide titles in `vibe-to-agentic-framework` match actual `<h1>` titles in `presentation/index.html`
 7. Agent identifiers are consistent across examples (use `frontend-engineer` / `backend-engineer`; do not introduce aliases like `frontend-eng`)
-8. Hook references remain canonical (`15 hook events`) in presentation-facing content
+8. Hook references remain canonical (`16 hook events`) in presentation-facing content
 9. Do not manually insert `.weight-badge` markup in slide HTML (badges are JS-injected)
 10. Settings precedence text must separate user-writable override order from enforced policy (`managed-settings.json`)
 11. If slide 32 is touched, ensure skill frontmatter coverage includes `context: fork`
@@ -97,7 +97,7 @@ If you encountered an edge case, discovered a new pattern, or found that the wor
 
 _Findings from previous executions are recorded here. Add new entries as bullet points._
 
-- Hook-event references drifted across files. Treat `15 hook events` as canonical and sync all docs in the same run.
+- Hook-event references drifted across files. Treat `16 hook events` as canonical and sync all docs in the same run.
 - Do not use shorthand agent names in examples (`frontend-eng`). Keep identifiers exactly aligned with agent definitions.
 - Never hardcode `.weight-badge` in slide HTML; badges are runtime-injected.
 - Keep the framework skill name stable as `vibe-to-agentic-framework` to avoid broken skill references.

.claude/hooks/HOOKS-README.md

@@ -1,7 +1,7 @@
 # HOOKS-README
 contains all the details, scripts, and instructions for the hooks
 
-## Hook Events Overview - [Official 15 Hooks](https://docs.claude.com/en/docs/claude-code/hooks-guide)
+## Hook Events Overview - [Official 16 Hooks](https://docs.claude.com/en/docs/claude-code/hooks-guide)
 Claude Code provides several hook events that run at different points in the workflow:
 1. SessionStart: Runs when Claude Code starts a new session or resumes one
 2. SessionEnd: Runs when a Claude Code session ends
@@ -18,6 +18,7 @@ Claude Code provides several hook events that run at different points in the wor
 13. Setup: Runs during setup/maintenance workflows
 14. TeammateIdle: Runs when an Agent Team teammate goes idle
 15. TaskCompleted: Runs when a tracked task reaches completion
+16. ConfigChange: Fires when configuration files change during a session, for enterprise security auditing
 
 ## Prerequisites
 
@@ -83,6 +84,7 @@ Edit `.claude/hooks/config/hooks-config.json` for team-wide defaults:
   "disableSetupHook": false,
   "disableTeammateIdleHook": false,
   "disableTaskCompletedHook": false,
+  "disableConfigChangeHook": false,
   "disableLogging": true
 }
 ```

.claude/hooks/config/hooks-config.json

@@ -14,5 +14,6 @@
   "disableSetupHook": false,
   "disableTeammateIdleHook": false,
   "disableTaskCompletedHook": false,
+  "disableConfigChangeHook": false,
   "disableLogging": true
 }

.claude/hooks/scripts/hooks.py

@@ -3,7 +3,7 @@
 Claude Code Hook Handler
 =============================================
 This script handles events from Claude Code and plays sounds for different hook events.
-Supports all 15 Claude Code hook event names: https://docs.claude.com/en/docs/claude-code/hooks-guide
+Supports all 16 Claude Code hook event names: https://docs.claude.com/en/docs/claude-code/hooks-guide
 
 Special handling for git commits: plays pretooluse-git-committing.mp3
 """
@@ -39,6 +39,7 @@ HOOK_SOUND_MAP = {
     "Setup": "setup",
     "TeammateIdle": "teammateidle",
     "TaskCompleted": "taskcompleted",
+    "ConfigChange": "configchange",
 }
 
 # ===== BASH COMMAND PATTERNS =====