[Bug] Ctrl+P is hijacked in ClawWork and should be customizable

## What happened?
Pressing Ctrl+P inside ClawWork triggers ClawWork's internal shortcut handling (or does not produce the expected behavior), instead of the expected system or app behavior.

The same Ctrl+P shortcut works normally in other applications on the same machine, so this looks like a shortcut conflict inside ClawWork.

In practice, ClawWork appears to capture Ctrl+P unconditionally, without pass-through or user customization.

## Steps to reproduce
1. Open ClawWork.
2. Press Ctrl+P.
3. Observe that ClawWork triggers its own internal behavior (or no expected behavior occurs).

## What did you expect to happen?
Ctrl+P should not be unconditionally hijacked.

At minimum, ClawWork should:
- allow pass-through in appropriate contexts,
- let users remap or disable the default shortcut,
- and provide a visible hint when a shortcut conflict exists.

## Affected area
Renderer UI

## Environment
ClawWork version: 0.0.14
Build: 28
OS: macOS 26.2 (Build 25C56)
Architecture: arm64
Input method / keyboard layout: Tencent Input Method / Pinyin

## Logs, screenshots, or recordings
N/A for now.

## Additional context
This shortcut works as expected in other applications on the same machine, which suggests the conflict is specific to ClawWork rather than the OS or keyboard itself.

Start in the renderer UI and trace how Ctrl+P is captured and routed by ClawWork. Confirm the shortcut can pass through where appropriate, be remapped or disabled, and show a visible conflict hint; verify the behavior on macOS with the reported keyboard setup.

Written by the indexing model from the issue text.