[Windows] 147% text scaling makes minimum window height 882px and clips the composer on a 768px display

Finding: In an external report on the Windows ChatGPT/Codex desktop MSIX package 26.1007.2314.0 (internal 26.1007.21434, Electron 42.3.0, Windows 10.0.26200), Windows Accessibility Text size of 147% reportedly pushes the main window's native minimum size to 706x882. On a 1366x768 display at 100% monitor DPI (work area 1318x768), the maximized window is 1318x882, extends 114 physical pixels below the work area, and clips the composer (https://github.com/openai/codex/issues/52826). Reported evidence: the reporter queried geometry from a per-monitor-DPI-aware thread. They measured GetDpiForWindow of 96 and WM_GETMINMAXINFO minTrackSize of 706x882. Read-only inspection of the installed main-process bundle found a fixed minimum of 480x600. Multiplying by 1.47 gives about 706x882, matching the native constraints. A newly opened main window reproduced the issue. Changing the wired display scaling from 150% to 100% did not help. F11 fullscreen widened the window to 1366 but kept the 882 height, so clipping remained (same issue). Controlled workaround, reported by the user: launching the installed executable with --force-device-scale-factor=1 changed minTrackSize to 480x600 and the maximized rectangle to 1318x768, and the full composer became visible and usable. The reporter says this strongly links the failure to scaling-dependent minimum-size handling. It bypasses the 147% text scaling for the whole app and is not offered as a permanent fix. Cause status: this is a hypothesis, not a maintainer-confirmed cause. The reporter says the failing internal component and update commit are not established. They cite Chromium's current screen_win.cc, which multiplies device scaling by the UWP text scale factor and bypasses it under a forced scale factor, but only as supporting context, not proof of an exact commit (https://chromium.googlesource.com/chromium/src/+/master/ui/display/win/screen_win.cc is cited in the issue; it was not independently supplied or checked). Regression: the user reports no symptom before the update registered 2026-10-10 15:31 JST, replacing package 26.1002.7124.0. No direct old-version comparison was run, so the introduction point is unverified. Status: the issue is open with no comments supplied, no maintainer response, and no fix commit or release identified. A separate Repair failure (0x80073D02, app in use) is reported as unrelated to the clipping. Limitation: this is a single external report prepared with Codex assistance. KFA did not reproduce it, and the sources do not independently confirm the findings.