Upgrade hooks daemon 3.25.0 -> 3.31.1, fix removed thinking_mode handler

The upgrade removed ThinkingModeHandler from status_line handlers; drop the
now-invalid handlers.status_line.thinking_mode entry from
.claude/hooks-daemon.yaml so the daemon config validates cleanly. Also picks
up the redeployed skill files (new upgrade subcommands: regen-docs,
release-notes).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: LTSCommerce

.claude/hooks-daemon.yaml

@@ -137,7 +137,6 @@ handlers:
     model_context: {enabled: true, priority: 10}    # Model name and context %
     usage_tracking: {enabled: true, priority: 15}   # Usage statistics
     git_branch: {enabled: true, priority: 20}       # Current git branch
-    thinking_mode: {enabled: true, priority: 25}    # Current thinking mode
     startup_cleanup: {enabled: true, priority: 28}  # Stale file cleanup indicator
     daemon_stats: {enabled: true, priority: 30}     # Daemon health metrics
 

.claude/skills/hooks-daemon/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: hooks-daemon
 description: Manage Claude Code Hooks Daemon - install, upgrade, check health, restart, and develop project-level handlers
-argument-hint: "[install|upgrade|health|restart|check|dev-handlers|logs] [args...]"
+argument-hint: "[install|upgrade|health|restart|check|dev-handlers|regen-docs|logs|release-notes] [args...]"
 disable-model-invocation: false
 user-invocable: true
 allowed-tools: Bash, Read, Write, Edit
@@ -48,6 +48,26 @@ The daemon caches config at startup — restart picks up any config or handler c
 
 See [restart.md](restart.md) for details.
 
+### Regenerate Generated Docs
+
+Force-regenerate the daemon's generated documentation **without restarting**:
+
+```bash
+/hooks-daemon regen-docs
+```
+
+Rewrites both generated artifacts to their canonical form in one shot:
+
+- `.claude/HOOKS-DAEMON.md` — the active-handler summary.
+- The `<hooksdaemon>` guidance block inside your project `CLAUDE.md`.
+
+This is the explicit way to recover both files after a **git merge/rebase conflict**
+left them stale or conflict-marked — run it, then stage the clean result. (A normal
+`restart` also refreshes these, but `regen-docs` does it as a one-shot with no daemon
+bounce.)
+
+See [regen-docs.md](regen-docs.md) for details.
+
 ### Check Health & Status
 
 Verify daemon is running correctly:
@@ -98,6 +118,24 @@ The report is saved to `./untracked/hooks-daemon-{description}.md` for sharing w
 
 See [report.md](report.md) for details.
 
+### Read Release Notes
+
+Show the daemon's release notes without leaving the terminal. With no flag it
+shows the notes for the version you currently have installed:
+
+```bash
+/hooks-daemon release-notes                       # installed version's notes
+/hooks-daemon release-notes --latest              # newest available version
+/hooks-daemon release-notes --version 3.27.0      # a specific version
+/hooks-daemon release-notes --from 3.20.0 --to 3.27.0   # everything you gained upgrading
+/hooks-daemon release-notes --list                # list available versions
+/hooks-daemon release-notes --version 3.27.0 --format json
+```
+
+Notes are read from the per-version `RELEASES/vX.Y.Z.md` files that ship with
+the install — no network access required. `--from` is exclusive and `--to` is
+inclusive, matching the upgrade semantics (the notes for everything you gained).
+
 ## Quick Start
 
 After editing `.claude/hooks-daemon.yaml`:
@@ -165,7 +203,12 @@ case "$SUBCOMMAND" in
         cat "$SKILL_DIR/report.md" | sed "s/\$ARGUMENTS/$*/"
         ;;
 
-    logs|status|restart|handlers|validate-config|bug-report|check)
+    regen-docs|regenerate-docs)
+        # User-facing alias regen-docs maps to the CLI command regenerate-docs.
+        bash "$SKILL_DIR/scripts/daemon-cli.sh" regenerate-docs "$@"
+        ;;
+
+    logs|status|restart|handlers|validate-config|bug-report|check|release-notes)
         # Forward to daemon CLI wrapper
         bash "$SKILL_DIR/scripts/daemon-cli.sh" "$SUBCOMMAND" "$@"
         ;;
@@ -177,6 +220,7 @@ case "$SUBCOMMAND" in
         echo "Available commands:"
         echo "  install [--force]     Install daemon (fresh clone)"
         echo "  restart               Restart daemon (required after config changes)"
+        echo "  regen-docs            Force-regenerate HOOKS-DAEMON.md + CLAUDE.md block"
         echo "  health                Check daemon health and status"
         echo "  upgrade [VERSION]     Upgrade daemon to new version"
         echo "  dev-handlers          Scaffold new project handlers"
@@ -186,6 +230,7 @@ case "$SUBCOMMAND" in
         echo "  check                 Verbose environment & configuration audit"
         echo "  bug-report DESC       Generate bug report with diagnostics"
         echo "  report DESC           Investigate an issue and generate a detailed report"
+        echo "  release-notes [opts]  Show release notes (installed version by default)"
         echo ""
         echo "After editing .claude/hooks-daemon.yaml, always run: /hooks-daemon restart"
         echo ""

.claude/skills/hooks-daemon/regen-docs.md

@@ -0,0 +1,60 @@
+# Regenerate Generated Docs
+
+Force-regenerate the daemon's generated documentation to its canonical form,
+**without restarting the daemon**.
+
+## Usage
+
+```bash
+/hooks-daemon regen-docs
+```
+
+## What It Regenerates
+
+Two artifacts are rewritten from live config + handler metadata in one shot:
+
+1. **`.claude/HOOKS-DAEMON.md`** — the active-handler summary (priorities, behaviours,
+   per-event handler tables). Same output as `generate-docs`.
+2. **The `<hooksdaemon>` block in your project `CLAUDE.md`** — the active-handler
+   guidance the daemon injects at startup. Surrounding user content is preserved;
+   only the `<hooksdaemon>...</hooksdaemon>` section is replaced.
+
+Both are written in the daemon's canonical (formatter-aligned) form, so a later
+edit will not produce churn diffs.
+
+## When to Use
+
+- **Resolving a git merge/rebase conflict** that left conflict markers or stale
+  content inside `.claude/HOOKS-DAEMON.md` or the `CLAUDE.md` `<hooksdaemon>` block.
+  Run `regen-docs`, then stage the clean result — the regenerated content reflects
+  your merged `.claude/hooks-daemon.yaml`, not either conflicting side.
+- After hand-editing `.claude/hooks-daemon.yaml` when you want the generated docs
+  refreshed but do **not** want to bounce the running daemon.
+- Any time the generated docs have drifted from the live config.
+
+## regen-docs vs restart
+
+| Action       | Refreshes generated docs | Restarts daemon | Use when                                      |
+| ------------ | ------------------------ | --------------- | --------------------------------------------- |
+| `regen-docs` | Yes                      | No              | Fixing/refreshing docs only (e.g. merge fix)  |
+| `restart`    | Yes (on startup)         | Yes             | Applying config/handler changes to the daemon |
+
+A `restart` already regenerates both artifacts on startup. `regen-docs` is the
+explicit one-shot when you want the doc regeneration **without** the restart.
+
+## Options
+
+```bash
+/hooks-daemon regen-docs --include-disabled   # list disabled handlers in HOOKS-DAEMON.md
+/hooks-daemon regen-docs --output PATH         # alternate HOOKS-DAEMON.md output path
+```
+
+## Verify
+
+```bash
+git diff -- .claude/HOOKS-DAEMON.md CLAUDE.md
+```
+
+The diff should show only the regenerated, conflict-free content. If `CLAUDE.md`
+is in a git repo and was changed, the daemon auto-commits the `<hooksdaemon>`
+block on regeneration (only `CLAUDE.md`, no other files are touched).