Update messaging across documentation to position Nucleus as \"the Kotlin framework for native desktop apps\" rather than \"the native desktop platform for the JVM\". This better emphasizes Kotlin as the primary language and aligns with the modern developer experience.

- Update site description and main taglines
- Reorganize navigation to prioritize roadmap over changelog
- Maintain technical accuracy while improving developer appeal

Update messaging across documentation to position Nucleus as \"the Kotlin framework for native desktop apps\" rather than \"the native desktop platform for the JVM\". This better emphasizes Kotlin as the primary language and aligns with the modern developer experience.

- Update site description and main taglines
- Reorganize navigation to prioritize roadmap over changelog
- Maintain technical accuracy while improving developer appeal

When macOsSdkVersion is set (default on macOS 26), the run task forks
the JVM via ProcessBuilder through a vtool-patched java binary to
enable Liquid Glass, then throws StopExecutionException to skip the
standard JavaExec action. This bypassed IntelliJ's debugger wiring:
JDWP args on JavaExec.debugOptions were never forwarded, and the
manually-started process was not tied to the task lifecycle, so the
IDE stop button left the app running.

Skip the patched-JVM indirection when debugOptions.enabled is true
(IntelliJ debug button or --debug-jvm). Gradle's standard JavaExec
fork then handles JDWP injection and process lifecycle. Regular run
is unchanged; Liquid Glass is only dropped during active debug
sessions.

Fixes #212

…sions

Replace ProcessBuilder workaround with AbstractPatchMacJvmTask that runs at
execution time via ExecOperations, eliminating config cache serialization
errors. IntelliJ's Gradle debugger now works normally (breakpoints, stop
button) while Liquid Glass remains active. PatchedJavaLauncher delegates
metadata to source JDK and overrides executable path to patched binary.

- New: AbstractPatchMacJvmTask (tasks/), PatchedJavaLauncher (internal/)
- Removed: getOrCreatePatchedJvm (~95 lines), ProcessBuilder + StopExecutionException
- Output: build/nucleus/patched-jvm/ (per-project) instead of ~/Library/Caches/
- Docs: Updated macOS.md to reflect new behavior (debug now compatible)

fix: allow IntelliJ debugger to attach to gradle run task on macOS

PR #208 removed focusProperties { canFocus = false } from the title bar Box
in decorated-window-core to let TextField/TextArea children receive keyboard
input inside a macOS title bar (issue #206). The fix was only validated on
macOS + JNI, but the change applies to every backend on every OS, which lets
Tab navigation enter the Compose-driven title bar drag area on Windows and
Linux — a regression there.

Make the focus block conditional: disable it only on macOS (where traffic
lights are native and the title bar hosts interactive Compose widgets), keep
it on Windows/Linux where the title bar is a Compose-driven drag surface.

…linux

fix(decorated-window): restore title bar focus block on Windows/Linux