fix(desktop): isolate new-session windows

[deniqlab]

Closes #65601\n\n## Summary\n- Skip remembered-route/session restoration in standalone new-session windows\n- Add a regression test proving the window stays on /new instead of jumping to the last session\n\n## Verification\n- npm run test:ui -- --run src/app/contrib/hooks/use-desktop-integrations.test.tsx\n- npm run typecheck\n- npx eslint src/app/contrib/hooks/use-desktop-integrations.ts src/app/contrib/hooks/use-desktop-integrations.test.tsx\n- git diff --check

[alt-glitch]

This was generated by AI during triage.

Duplicate of #66270: both prevent standalone new-session windows from restoring or persisting the remembered route/session state.

[teknium1]

Thanks for the focused regression fix. Current main has the reported path: apps/desktop/src/app/contrib/hooks/use-desktop-integrations.ts:64-72 persists shared remembered state, then :79-100 restores it when the renderer starts at /. Electron deliberately starts standalone drafts at ?win=secondary&new=1#/ (apps/desktop/electron/session-windows.ts:45-47), and isNewSessionWindow() already recognizes that flag (apps/desktop/src/store/windows.ts:33-49).

The patch gates both effects and the regression test exercises the hook with a new-session window, asserting that neither remembered-state reads/writes nor navigation occur. The current hook blob matches the PR preimage, so salvage is mechanically clean.

Automated hermes-sweeper review.