fix(terminal): protect held Ctrl/Cmd+W close shortcut - #5322

💭 Looking at the changed files to understand what's happening with the Effect-related code. The new helper file is straightforward, but I need to check whether the webContents listener added to DesktopWindow.ts violates any Effect service patterns, so I'm examining the imports in both the main file and its test. Looking at the new code context in DesktopWindow.ts around that section to see what's been added or changed. The pattern here is consistent with existing runtime boundaries using runPromise. The terminalCloseShortcut helper is a pure module with no Effect dependencies, and its usage in ChatView and ThreadTerminalDrawer doesn't require platform arguments—everything checks out so far. Now I need to verify that ThreadTerminalDrawer still compiles after removing the isTerminalCloseShortcut condition from the multi-condition check and updating the imports. The key question is whether the new call using currentKeybindings is sufficient, or if it was relying on additional context from the options object that the previous version had access to. The Effect service changes look legitimate—just a native event listener added to DesktopWindow.ts, nothing that violates the refactor guidelines. The test file size is justified since there's actual behavior change, not just mechanical refactoring. I need to respond with JSON following the schema, so I'll structure it as a title field with "All clear" rather than returning that as plain text.