PyCForge 1.1.7 — native Windows acceptance

STATUS: PENDING. None of these native Windows checks was executed in the Linux
offscreen test environment. Automated results accompany the release separately.

Record: Windows build, Python/PySide6 versions, CPU, RAM, GPU, display scaling,
monitor layout, keyboard layout, input method and the exact wheel SHA-256.
Install the supplied wheel in a fresh virtual environment. Check both
python -m pycforge.ide and the pycforge-workspace GUI launcher.

1. Startup and process lifecycle
   Confirm splash progress, cancellation, six Ting agents, and all Help pages.
   Open/close the last tab repeatedly with split view active, then exit during
   outline parsing, completion, regex search and conversion. Check Task Manager
   for stranded workers. Reopen and repeat. Exercise pythonw/process spawning.

2. Real keyboard and input methods
   Press/release physical Ctrl+D repeatedly; use Ctrl+Alt+L, Alt+click, Shift
   movement, Ctrl+C/X/V and Escape with 1/16/64/128/256 carets. Check selection
   direction and Undo/Redo. Exercise AltGr, dead keys, an IME, emoji and accented
   identifiers. Compare normal typing with automatic suggestions on and off.

3. Long typing and large documents
   Run the supplied timing probe on the installed wheel. Also type, paste,
   scroll, resize and switch tabs in 20k/200k/300k-character files, long lines,
   dense functions, invalid Python and a maximum practical open workspace.
   Trigger outline and conversion while typing. Record real visible input
   latency, CPU, memory and process count; do not equate dispatch-only timing
   with input-to-display latency. Leave the app open for at least an hour,
   repeatedly edit/undo/close/reopen documents, and look for sustained growth.

4. Editing correctness
   Check smart quotes in comments/strings, wrapping and newline indentation.
   Complete a name from its middle and confirm no duplicate suffix or '='.
   Format selected lines and verify unchanged surrounding text plus one Undo.
   Rename ordinary locals and imported aliases; verify safe refusal for the
   documented inheritance/private/Unicode-alias/decorated-parameter cases.
   Change source while a result or replacement preview is open; stale edits
   must never apply. Verify CRLF/form-feed definition navigation and return.

5. Save and workspace state
   Save/reload normal, read-only, non-ASCII and linked paths; verify link
   identity and Windows ACL behavior. Check modified buffers, external changes,
   cancellation, failed writes, explicit Save As and per-document Undo. POSIX
   permission-mode tests do not establish Windows ACL preservation.

6. Native presentation and release smoke
   Test 100/125/150/200% scaling, small work areas and mixed-DPI monitors.
   Reach every compact Edit submenu by keyboard and mouse. Check clipboard,
   focus, popups, maximization, taskbar identity and split-pane font settings.
   Select Typed and Runtime without starting conversion, then convert known
   examples with the toolbar/Ctrl+Enter. Verify fresh C output, diagnostics,
   normal C scrollbar, mappings and Help. Run verify_installed.py from the bundle.

7. Gutter Classes & Functions navigator
   Right-click both the line numbers and fold markers in either split view.
   Opening, selecting and Copy must preserve cursor, selection, both scrollbars,
   folds and Undo in both views. Copy decorated classes, methods and nested
   functions; paste into a separate scratch document and check exact source.
   Confirm the Copy icon is on the title bar's left and temporary feedback is
   immediately beside it. Check long names at 100/125/150/200% DPI and narrow
   sizes without controls shifting. Double-click/Enter must reveal covering
   folds and navigate in the originating pane. Reopen after edits, try invalid
   syntax, close during loading, and exit while a worker is starting/running.

Acceptance requires recording the observations and any remaining defects.
Passing the supplied automated suite alone does not complete this checklist.
