fix(hooks): use socket-based Kitty remote control to prevent escape sequence leaks

[Mutdogus]

Summary

Fixes P@kitty-cmd escape sequence artifacts appearing in terminal when using PAI with Kitty terminal.

Problem

When PAI hooks use kitty @ commands without a socket, Kitty responds via escape sequences. Since hooks run as subprocesses, these sequences cannot be properly consumed and leak into the terminal as visible garbage:

P@kitty-cmd{"ok": false, "error": "Remote control is disabled"}

This affects anyone using PAI with Kitty terminal.

Root Cause

Kitty's allow_remote_control yes mode uses escape sequences for IPC. When hooks run as detached subprocesses:

1. They send commands via escape sequences to the PTY
2. Kitty writes responses back to the PTY
3. The subprocess can't read from the PTY
4. Response leaks as visible text

Solution

• Added getKittySocket() helper to all tab-related hooks
• All kitty/kitten commands now use --to <socket> flag for socket-based communication
• Gracefully skips tab updates if no socket available (prevents leaks on misconfigured systems)

Files Changed

• Packs/pai-hook-system/src/hooks/UpdateTabTitle.hook.ts
• Packs/pai-hook-system/src/hooks/SetQuestionTab.hook.ts
• Packs/pai-hook-system/src/hooks/QuestionAnswered.hook.ts
• Packs/pai-hook-system/src/hooks/handlers/tab-state.ts

User Configuration Required

Users need to configure Kitty for socket-based remote control by adding to ~/.config/kitty/kitty.conf:

allow_remote_control socket-only
listen_on unix:/tmp/kitty-$USER

Then restart Kitty for changes to take effect.

Testing

Tested on macOS with Kitty terminal - artifacts no longer appear after fix.

---

🤖 Generated with Claude Code

[A13xSM]

This solution worked perfectly for me. It not only resolved the escape sequence leaks but also resolved a buffering issue where PAI would hang when loading, requiring input to refresh the buffer. Great fix.