feat: Windows hook support with --windows flag (opt-in Node.js hooks)

[Pamacea]

Summary

Adds Windows support for rtk init via an opt-in --windows flag that installs Node.js hooks instead of shell scripts.

Problem

RTK's rtk init only worked on Unix (macOS/Linux) because:

• Hooks were written in bash (rtk-rewrite.sh)
• Code used #[cfg(unix)] guards to block Windows
• chmod +x and PermissionsExt are Unix-only

Windows users got this error:

[warn] Hook-based mode requires Unix (macOS/Linux).
    Windows: use --claude-md mode for full injection.

Solution

Conservative approach - keeps existing behavior as default and adds opt-in flag:

New files:

• hooks/rtk-rewrite.cjs - Claude Code Node.js hook (cross-platform)
• hooks/cursor-rtk-rewrite.cjs - Cursor IDE Node.js hook (cross-platform)

Changes to src/init.rs:

• Add --windows flag to Init command
• Add REWRITE_HOOK_CJS and CURSOR_REWRITE_HOOK_CJS constants
• Modify prepare_hook_paths() to accept use_windows parameter
• Modify ensure_hook_installed() to write .cjs when use_windows=true
• Update run_default_mode() and run_hook_only_mode() to pass flag through
• Update install_cursor_hooks() to support Windows mode
• Update tests to include new windows parameter

Usage

# Default behavior (Unix/macOS/Linux) - uses .sh hooks
rtk init -g

# New Windows mode - uses .cjs hooks (works on all platforms)
rtk init -g --windows

Key Differences from PR #726

Aspect	PR #726 (replacement)	This PR (opt-in flag)
Default behavior	.cjs for everyone	.sh for Unix, error for Windows
User choice	None	--windows flag opts in
Backward compatibility	Breaking (removes .sh)	Non-breaking
Migration path	Forced (auto-switch to .cjs)	User-controlled

Token Savings

Same 60-90% savings on all platforms (with --windows flag).

Testing

cargo check    # ✅ passes
cargo test     # ✅ 981 passed, 1 unrelated failure (Windows path issue)
cargo test init::  # ✅ 42 passed

Checklist

• Code compiles (cargo check)
• Init tests pass (cargo test init::)
• No clippy warnings
• Cross-platform compatible
• Tests updated for new parameter

---

Alternative to PR #726 - Maintainers can choose either:

• PR feat: Windows hook support - cross-platform Node.js hooks #726: Full replacement (simpler, one hook type)
• This PR: Opt-in flag (conservative, preserves existing behavior)

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[MarlonPassos-git]

@Pamacea please sign the CLA

[aeppling]

Hey

We are cleaning up the codebase and improving the project structure for better onboarding. As part of this effort, PR #826 reorganizes src/ from a flat layout into subfolders.

No logic changes — only file moves and import path updates.

What you need to do

Rebase your branch on develop when receiving this comment:

git fetch origin && git rebase origin/develop

Git detects renames automatically. If you get import conflicts, update the paths:

use crate::git;        // now: use crate::cmds::git::git;
use crate::tracking;   // now: use crate::core::tracking;
use crate::config;     // now: use crate::core::config;
use crate::init;       // now: use crate::hooks::init;
use crate::gain;       // now: use crate::analytics::gain;

Need help rebasing? Tag @aeppling

[aeppling]

Thanks for contributing @Pamacea — the --windows flag and .cjs hooks were a practical approach.

This is now superseded by the v0.37.x releases: the native binary hook (rtk hook claude) is inherently cross-platform, no platform flag needed. Closing as resolved.