Merge #612: Windows mixed-DPI drag keeps the window's size; GPU surface up to the adapter's texture limit

win-mixed-dpi 38dad0fb. Cargo.lock: next's lock plus the winit git source and the dpi 0.1.1 it brings (merged clean; cargo metadata --offline leaves it unchanged).

Conflict: apps/designcraft/src/main.rs: next's startup (adapter selection, catch_unwind, apple events) with log_uncaptured_errors at the top of its wgpu_render_state block; request_adapter_texture_size and mod gpu_limits merged clean
Conflict: ROADMAP.md: progress log both
Conflict: docs/hardware-parity.md: header keeps next's change list plus the mixed-DPI note

Cargo.toml

@@ -102,3 +102,13 @@ opt-level = 3
 lto = "thin"
 codegen-units = 16
 debug = 0
+
+# Windows 11: winit 0.30.13 resizes a window wrongly while it is dragged across monitors with
+# different display scales (rust-windowing/winit#4041, #4600). It flips between the two scales,
+# grows by the scale ratio (3600×2250 → 9048×5757 between 250 % and 100 %) and outgrows the GPU
+# surface. Pinned to the one commit of rust-windowing/winit#4694, the 0.30.x backport of the fix
+# winit master has had since 488c036a (#4341): during a live drag it applies the rect Windows
+# suggests (+21/−34 lines in src/platform_impl/windows/event_loop.rs on top of v0.30.13). Remove
+# once eframe depends on a winit release with the fix.
+[patch.crates-io]
+winit = { git = "https://github.com/rust-windowing/winit", rev = "39c4009c41e5977d779cf8a365792c8153ca77c5" }