Docs: what the 1.0.1 window remembers, and the window checks

The changelog and release notes said ShadowCode "still remembers where the
window was" under a Wayland heading, where the compositor ignores the
position, and the release notes' heading said the window keeps its size,
the opposite of the fix. They now say the size is no longer remembered on
any desktop, that maximized and full screen are, and the place only on
X11, and describe the fit as it now works (1229x691 with the title bar on
1366x768; the screen it reopens on, or every screen on Wayland).
NATIVE_DESKTOP no longer says window geometry is retained. RELEASING notes
that the scripts need Node 22.12 or newer and lists the X11 and private
Wayland window tests for window changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: ShadowfetchStudio

CHANGELOG.md

@@ -6,17 +6,21 @@
   such as KDE Plasma, every launch opened the window about 52 px wider and
   99 px taller, until it no longer fit on the screen. The window draws its
   own title bar there, and the saved size included that title bar and the
-  window's shadow, so restoring it added them again. ShadowCode still
-  remembers where the window was and whether it was maximized or full
-  screen, but no longer its size. A window that already grew opens at its
+  window's shadow, so restoring it added them again. ShadowCode no longer
+  remembers the window's size on any desktop, so it opens at its default
+  size, fitted to the screen. It still reopens maximized or full screen if
+  you left it that way, and on X11 at the same place; on Wayland the desktop
+  chooses where the window opens. A window that already grew opens at its
   normal size again.
 - **The window fits small screens.** The window opened at 1380x920 even on a
   1366x768 screen, so the composer and status bar sat under the panel. It
-  now opens at no more than 90% of the screen it opens on, less room for the
-  title bar (1229x643 on a 1366x768 screen), and still at 1380x920 on larger
-  screens. On a screen too small for the smallest window (520x640) it opens
-  maximized. A window that was maximized when you closed it opens maximized
-  again.
+  now opens at no more than 90% of the screen, title bar included (1229x691
+  on a 1366x768 screen), and still at 1380x920 on larger screens. On X11 it
+  fits the screen it reopens on, and a window last left low on the screen
+  moves up until it fits. On Wayland, where the desktop picks the screen, it
+  fits every screen. It opens maximized only when no screen can hold the
+  smallest window (520x640). A window that was maximized when you closed it
+  opens maximized again.
 
 ## 1.0.0: Easy to start, ready for real work
 

docs/NATIVE_DESKTOP.md

@@ -197,7 +197,14 @@ Prove it with `node --test scripts/test-native-packaging-env.mjs`.
   HTTP/HTTPS links open through the OS; remote pages cannot replace the app view.
 - Default-profile launches focus the existing instance. Isolated profiles have
   separate webview storage and still enforce their own profile locks.
-- Window geometry is retained for the default profile. Desktop notifications
+- For the default profile the window reopens maximized or full screen if it
+  was, and on X11 at its last place (moved up or left until it fits that
+  screen's work area); a Wayland compositor chooses the place itself. Its
+  size is not remembered (`window_size.rs`): it opens at 1380x920, or at 90%
+  of a smaller screen with room for the title bar (the X11 window manager's
+  frame, or GTK's header bar inside the size on Wayland), on the screen it
+  reopens on (X11) or fitting every screen (Wayland). It opens maximized only
+  when no such screen holds the 520x640 minimum. Desktop notifications
   cover approvals waiting (and a warning 2 minutes before a vendor approval is
   denied), failed tasks, plan limits and finished tasks, each switchable in
   Settings › Appearance with an optional sound. They appear while the window

docs/RELEASE_NOTES.md

@@ -5,16 +5,20 @@ it opens on Wayland, and it fits small screens. The 1.0.0 notes follow below.
 
 ## Fixed
 
-- **The window keeps its size.** On Wayland desktops such as KDE Plasma, the
-  window opened a little bigger every time (about 50 pixels wider and 100
-  taller) until it no longer fit on the screen. ShadowCode now remembers
-  where the window was and whether it was maximized, but not its size. If
-  your window already grew, it opens at its normal size again.
+- **The window no longer grows each time it opens.** On Wayland desktops
+  such as KDE Plasma, the window opened a little bigger every time (about 50
+  pixels wider and 100 taller) until it no longer fit on the screen.
+  ShadowCode no longer remembers the window's size on any desktop, so it
+  opens at its default size, fitted to the screen. It still reopens
+  maximized or full screen if you left it that way, and on X11 at the same
+  place. If your window already grew, it opens at its normal size again.
 - **The window fits small screens.** On a 1366x768 screen the window used to
   be taller than the screen, so the composer and the status bar were hidden
   under the panel. The window now opens at a size that fits the screen, with
-  room for the title bar and the panel. Larger screens still get the full
-  size, a very small screen gets a maximized window, and a window you left
+  room for the title bar and the panel. With more than one screen it fits
+  the screen it reopens on (X11), or every screen (Wayland, where the
+  desktop chooses). Larger screens still get the full size, the window opens
+  maximized only when no screen is big enough for it, and a window you left
   maximized opens maximized.
 
 ## Download

docs/RELEASING.md

@@ -76,7 +76,19 @@ node scripts/check-secrets.mjs
 ```
 
 Build the desktop executable before running the Rust suite: the process tests
-launch `target/debug/shadowcode`. `check-secrets.mjs` also runs in the CI
+launch `target/debug/shadowcode`. The scripts need Node.js 22.12 or newer,
+like the UI: with an older `node` first on `PATH`, `test-native-cli.mjs`
+stops with `ERR_UNKNOWN_BUILTIN_MODULE` (`node:sqlite`). A change to the
+window also needs the window test on X11 and on a private Wayland
+compositor (see [NATIVE_DESKTOP.md](NATIVE_DESKTOP.md); Weston 13 and
+WebKitWebDriver can be unpacked copies):
+
+```sh
+node scripts/run-native-x11.mjs node scripts/test-native-desktop.mjs
+node scripts/run-native-wayland.mjs node scripts/test-native-desktop.mjs
+```
+
+`check-secrets.mjs` also runs in the CI
 "Checks" workflow, not in `release.yml`; run it before pushing the tag.
 Live turns against real accounts (`live_vendor_turn`) are described under
 [Tests](../README.md#tests) in the README.