Fix: closing the window does nothing on 2.1.0

[broisnischal]

The bug

Closing Stroke does nothing on 2.1.0. Clicking the title bar X leaves the window on screen and the process alive. That release ships no tray icon and no native window decorations, so the X is the only close affordance there is, and the app cannot be quit from its own UI at all.

Cause

src-tauri/capabilities/default.json granted core:window:allow-close but never core:window:allow-destroy.

The gap has been in the file for a while, but it was unreachable: the tray build intercepted CloseRequested and hid the window, so close() never ran through to destroy. Removing the tray in 3ea0c80 let it through for the first time, the ACL refused the call, and the rejected promise went nowhere.

Caught live in a dev run:

[vite] (client) [Unhandled rejection] Unknown Error: window.destroy not allowed.
Permissions associated with this command: core:window:allow-destroy

The capability also scoped to "windows": ["main"] only, so every control on a second window (Ctrl/Cmd+Shift+N, labelled main-2 onward) was denied the same way: close, minimize, maximize, and dragging the title bar.

Fix

• Add core:window:allow-destroy.
• Widen the capability to ["main", "main-*"] so second windows get the same window chrome permissions.
• WindowControls.svelte awaits its core call and logs a failure instead of discarding the promise, so the next gap in the capability file surfaces somewhere rather than nowhere.

Verification

Reproduced and fixed against a dev build:

	before	after
window.destroy not allowed per run	9+	0
app process after close	survives (needed kill -9)	exits cleanly
npm run tauri dev exit code	killed	0
Stroke windows left	1	0

Driven through closeWindow() itself on a fresh boot, so it exercises the same path as the title bar X.