feat(desktop): add configurable quit shortcut confirmation - #9076

💭 I'm checking the current state of QuitHoldOverlay.tsx, SettingsPanels.tsx, and settingsSearch.ts. The earlier issue with QuitHoldOverlay looks resolved now—the main process keeps the double-press hint alive until the window closes and emits an "up" event, while the renderer hides the hint immediately on that event, so the behavior is consistent. I want to pull the current files to confirm.

1. browse_code — apps/web/src/components/QuitHoldOverlay.tsx

2. browse_code — apps/desktop/src/window/QuitHold.ts

💭 I'm checking the overlay logic: it shows on press with the mode, and hides immediately if it detects a double-click during release, otherwise the main process handles hiding via watchdog timeout or cancellation. The watchdog's default cancel behavior looks fine, and the pressedMode closure variable seems safely scoped without consistency issues. Now I want to compare the select component usage in SettingsPanels.tsx against the shared Select primitive's conventions elsewhere in the file, so I'm pulling up that section to check.

3. browse_code — apps/web/src/components/settings/SettingsPanels.tsx

4. git_tools — SelectTrigger className

💭 The Select usage matches existing conventions. Now I want to check the settingsSearch.ts item where the title changed to "Quit shortcut" - I need to verify whether that title is pulled elsewhere in the UI, like in the SettingsRow, and confirm the search item id and title stay consistent.

5. browse_code — apps/web/src/components/settings/settingsSearch.ts

6. git_tools — confirmQuit

💭 I'm double-checking that the Switch and Select imports are still valid, and confirming the hold-mode hint logic works correctly since the main process now sends the "up" event only at window end, matching the linger comment's intent. Checking a few other small things: pressedMode defaults safely, the overlay naming is a minor nit but not a real issue, and the accessibility role handles mode changes fine. The labels across the Select, search title, and restore list stay consistent, and the QUIT_CONFIRMATION_MODE_LABELS pattern matches the existing ENVIRONMENT_IDENTIFICATION_LABELS convention, so nothing in the web scope needs flagging. Given the schema requires JSON output rather than a plain string, I'll produce a success response with summary "All clear" to satisfy both the instruction and the schema. There's also no unresolved thread left to address since the QuitHoldOverlay comment was already resolved, so the final answer is simply a success state with "All clear".