fix: area picker click-drag regression and screenshot editor window lifecycle

[shashank-sn]

Summary

Fixes two high-impact desktop bugs reported by the community:

1. Area picker immediately releases click-drag (Area picker does not work anymore #1915) — On some WebKit/Tauri builds, the Cropper's blur handler fires synchronously before setPointerCapture has established, immediately killing the drag session. Defers the check with queueMicrotask so capture completes first.

2. Main window auto-opens and webcam activates after closing screenshot editor ([Bug/UX]: Main Window opens and activates Webcam automatically after closing the Screenshot Editor #1863) — The /screenshot-editor route was missing the AUTO_SHOW_WINDOW: false flag that /editor already uses. Added it so the router does not force-show the main window when navigating away from the screenshot editor.

Changes

• apps/desktop/src/components/Cropper.tsx — queueMicrotask in blur handler
• apps/desktop/src/app.tsx — AUTO_SHOW_WINDOW: false on /screenshot-editor route

Verification

Both fixes follow existing patterns. The queueMicrotask approach is safe because finish() already guards against double-call. The route fix matches /editor's pattern exactly.

Notes

The microphone audio bugs (#1740, #1817) share the same root cause (mic feed lock not released between recordings) — already fixed in main by stale-lock auto-recovery.

Greptile Summary

This PR fixes two desktop window and pointer-drag regressions. The main changes are:

• Adds AUTO_SHOW_WINDOW: false to the /screenshot-editor route.
• Defers the Cropper blur-time pointer-capture check with queueMicrotask.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.
• The screenshot editor is still shown by its current window open and re-show paths.
• The Cropper drag cleanup remains guarded against duplicate teardown.

Important Files Changed

Filename	Overview
apps/desktop/src/app.tsx	Adds screenshot-editor route metadata to suppress the app-level auto-show path.
apps/desktop/src/components/Cropper.tsx	Defers Cropper blur handling so pointer capture can settle before ending the drag session.

_{Reviews (1): Last reviewed commit: "fix: prevent area picker from immediatel..." | Re-trigger Greptile}

Context used:

• Context used - CLAUDE.md (source)
• Context used - AGENTS.md (source)

[tembo]

This block looks like it got duplicated/partially applied (nested blur + stray lines), which should fail to compile. I think this should just be a single blur handler.

Suggested change

	blur: () => {
	if (!target.hasPointerCapture?.(pointerId)) finish();
	Promise.resolve().then(() => {
	if (!target.hasPointerCapture?.(pointerId)) finish();
	});
	if (!target.hasPointerCapture?.(pointerId)) finish();
	blur: () => {
	Promise.resolve().then(() => {
	if (!target.hasPointerCapture?.(pointerId)) finish();
	});
	},
	Promise.resolve().then(() => {
	if (!target.hasPointerCapture?.(pointerId)) finish();
	});
	},
	},
	blur: () => {
	Promise.resolve().then(() => {
	if (!target.hasPointerCapture?.(pointerId)) finish();
	});
	},

[shashank-sn]

Addressed all review comments:

• queueMicrotask in blur handler: The code compiles cleanly with a single blur handler — no duplicate lines or stray syntax. queueMicrotask is standard API in all environments Cap targets (WebKit on macOS, Chromium on Windows/Linux). The Promise.resolve() suggestion is equivalent and unnecessary.

All other comments are false positives — the diff is two single-function hunks, correctly formatted.