🧹 Refactor overly long hotkey function into platform-specific helpers

[undivisible]

🎯 What: The hotkey function in src/lib.rs was overly long and complex, containing inline logic for handling hotkeys on Windows and macOS. This change extracts that platform-specific code into separate win_hotkey and mac_hotkey functions.
💡 Why: Breaking down the 98-line hotkey method into modular functions significantly improves code maintainability and readability, adhering to the codebase's pattern of using prefixed helper functions for OS-specific behavior.
✅ Verification: Verified by running cargo check, formatting via cargo fmt, linting via cargo clippy, and running the test suites (cargo test --lib and cargo test --test conformance in an isolated directory) with no failures or regressions.
✨ Result: The hotkey function is now concise and readable, simply delegating calls to the appropriate platform-specific logic helpers.

---

PR created automatically by Jules for task 8826274499004670539 started by @undivisible

---

Note

Low Risk
Mechanical extraction with equivalent logic; low risk aside from normal regression risk for input simulation on Windows and macOS.

Overview
Refactors NativeRuntime::hotkey by moving Windows and macOS keyboard shortcut simulation out of the trait method into dedicated helpers, matching how Linux already delegates to linux_input::native_hotkey.

win_hotkey uses SendInput with modifier down/up sequencing; mac_hotkey keeps the same accessibility check, modifier flag mapping, and mac_post_key call. hotkey now only dispatches per OS with no intended behavior change.

tests/cli.rs fixes indentation in the run helper’s stdin write block.

^{Reviewed by Cursor Bugbot for commit 62d59a4. Configure here.}

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[undivisible]

Closing: CONFLICTING after sibling merges (#47/#50/#49/#44/#30); Jules extract/split superseded — prefer close over rebase fight.

[google-labs-jules]

Closing: CONFLICTING after sibling merges (#47/#50/#49/#44/#30); Jules extract/split superseded — prefer close over rebase fight.

Understood. Acknowledging that this work is now obsolete and stopping work on this task.