[Bug] ralph-loop plugin: Windows path corruption in stop hook execution

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Body:
## Description

The ralph-loop@claude-plugins-official plugin fails on Windows due to path corruption when executing the stop hook.

## Expected Behavior

The path should be properly escaped/formatted as:
C:\Users\adminclaude\plugins\cache\claude-plugins-official\ralph-loop\96276205880a\hooks\stop-hook.sh

## Actual Behavior

The backslashes are stripped from the Windows path when passed to bash, resulting in:
C:Usersadmin.claudepluginscacheclaude-plugins-officialralph-loop96276205880a/hooks/stop-hook.sh

## Environment

• OS: Windows 10
• Shell: Git Bash available, WSL2 with Ubuntu 24.04 installed
• Claude Code: Latest version
• Plugin: ralph-loop@claude-plugins-official

## Additional Context

The stop-hook.sh script uses Unix-specific tools (sed, awk, perl, jq) which may need Windows alternatives or WSL integration.

## Suggested Fix

1. Fix path escaping when invoking bash hooks on Windows
2. Consider adding PowerShell version or proper WSL path translation

Labels: bug

What Should Happen?

The path should be properly escaped/formatted as:
C:\Users\adminclaude\plugins\cache\claude-plugins-official\ralph-loop\96276205880a\hooks\stop-hook.sh

Error Messages/Logs

Stop hook error: Failed with non-blocking status code: /bin/bash:
  C:Usersadmin.claudepluginscacheclaude-plugins-officialralph-loop96276205880a/hooks/stop-hook.sh: No such file or directory

Steps to Reproduce

1. Install Claude Code on Windows
2. Enable ralph-loop@claude-plugins-official plugin
3. Start a session and let it complete/stop
4. Observe the stop hook error

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.11

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

The stop-hook.sh script uses Unix-specific tools (sed, awk, perl, jq) which may need Windows alternatives or WSL integration.

## Suggested Fix

1. Fix path escaping when invoking bash hooks on Windows
2. Consider adding PowerShell version or proper WSL path translation