Wayland/Linux: default WebKit safe flags can hurt responsiveness and decoration behavior #1192

Problem\nOn pure Wayland systems, apps packaged with Pake can feel laggy (text input delays, less snappy UI), and window controls (min/max/close) can become non-interactive depending on compositor/session timing.\n\nCurrent Linux runtime path in sets these env vars by default:\n- \n- \n\nThese help blank-screen cases, but on some Wayland setups they trade off too much interactivity/performance.\n\n## Repro notes\n- Launching with:\n \n noticeably improves responsiveness on my host.\n\n## Suggested direction\nMake the conservative Linux WebKit flags opt-in (or dynamically gated), rather than always-on defaults.\n\nOne practical option:\n- Only set those vars when a dedicated env toggle is present (example: )\n\nAlso consider Linux-specific window visibility/state restore behavior for Wayland to avoid non-interactive decorations during startup.\n\n## Patch reference\nI validated a local patch with:\n- Linux WebKit safe mode made opt-in\n- Linux state flags preserving during restore path\n\nPatch in my fork:\nhttps://github.com/mestadler/Pake/commit/cf519dc