Honor remoteControlEnabled in workspace setup.sh

[dhilgaertner]

Summary

• /crow-workspace and /crow-batch-workspace now launch Claude Code with --rc --name '<session-name>' whenever the global Settings → Remote Control is on, closing the gap left by Add auto-enable Claude Code remote control setting #163 which only wired RC into app-initiated launches.
• Adds two small helpers to skills/crow-workspace/setup.sh: posix_quote (mirrors Swift's ClaudeLaunchArgs.shellQuote byte-for-byte — including the '\'' apostrophe escape) and is_remote_control_enabled (reads {devRoot}/.claude/config.json; missing file / absent key / malformed JSON all default to off, matching AppConfig.decodeIfPresent).
• No Swift/app changes needed. /crow-batch-workspace inherits the fix automatically since it delegates to this script.

Closes #164

Test plan

• Unit-verified posix_quote output matches ClaudeLaunchArgsTests (Manager → 'Manager'; Bob's session → 'Bob'\''s session').
• Unit-verified is_remote_control_enabled across six config states: key=true, key=false, key absent, file missing, pretty-printed+true, malformed.
• bash -n syntax check.
• Manual: with Remote Control off, run /crow-workspace on a test ticket and confirm the launched command is claude --permission-mode plan "$(cat …)" (no --rc).
• Manual: with Remote Control on, run /crow-workspace on a test ticket and confirm the command includes --rc --name '<session-name>' and the session appears in Claude.ai's Remote Control panel with the antenna badge.
• Manual: /crow-batch-workspace with two tickets while RC is on — both terminals launch with --rc --name '…'.

🤖 Generated with Claude Code