fix: normalize path slashes in PostToolUse hook to prevent session_id write failure

When CLAUDE_PLUGIN_ROOT has a trailing slash, the command template
produces double slashes (e.g. "humania//scripts/setup-rlcr-loop.sh").
The setup script normalizes its own path via cd+pwd (single slash),
but tool_input.command preserves the original double-slash string.
This causes the boundary-aware string match in loop-post-bash-hook.sh
to always fail, so the .pending-session-id signal is never consumed
and session_id is never written to state.md.

With an empty session_id, find_active_loop() backward-compat logic
matches any session, causing cross-instance stop hook hijacking when
multiple Claude Code sessions run concurrently.

Fix: normalize consecutive slashes with tr -s '/' before comparison.

Fixes: #67

Author: SihaoLiu

.claude-plugin/marketplace.json

@@ -8,7 +8,7 @@
       "name": "humanize",
       "source": "./",
       "description": "Humanize - An iterative development plugin that uses Codex to review Claude's work. Creates a feedback loop where Claude implements plans and Codex independently reviews progress, ensuring quality through continuous refinement.",
-      "version": "1.15.1"
+      "version": "1.15.2"
     }
   ]
 }

.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "humanize",
   "description": "Humanize - An iterative development plugin that uses Codex to review Claude's work. Creates a feedback loop where Claude implements plans and Codex independently reviews progress, ensuring quality through continuous refinement.",
-  "version": "1.15.1",
+  "version": "1.15.2",
   "author": {
     "name": "humania-org"
   },

README.md

@@ -1,6 +1,6 @@
 # Humanize
 
-**Current Version: 1.15.1**
+**Current Version: 1.15.2**
 
 > Derived from the [GAAC (GitHub-as-a-Context)](https://github.com/SihaoLiu/gaac) project.
 

hooks/loop-post-bash-hook.sh

@@ -67,6 +67,16 @@ if [[ -n "$COMMAND_SIGNATURE" ]]; then
         exit 0
     fi
 
+    # Normalize consecutive slashes (e.g. "humania//scripts" -> "humania/scripts").
+    # CLAUDE_PLUGIN_ROOT may have a trailing slash, producing double slashes when
+    # concatenated with "/scripts/..." in the command template. The setup script
+    # normalizes its own path via cd+pwd (removing double slashes), but the
+    # tool_input.command preserves the original string. Without normalization,
+    # the string comparison below always fails and session_id is never written.
+    # See: https://github.com/humania-org/humanize/issues/67
+    HOOK_COMMAND=$(printf '%s' "$HOOK_COMMAND" | tr -s '/')
+    COMMAND_SIGNATURE=$(printf '%s' "$COMMAND_SIGNATURE" | tr -s '/')
+
     # Boundary-aware match: command must be a valid setup invocation form.
     # Requires the script path to be followed by end-of-string or any POSIX
     # whitespace ([[:space:]]), preventing concatenated forms.