Preserve valid WDDM process memory rows

[xptea]

What changed

• invalidate only the individual WDDM dedicated-memory rows that are impossible
• preserve every other process VRAM value instead of blanking the entire column
• use current NVIDIA board allocation plus bounded sampling slack to catch the reported stale DWM value as well as the 75+ GiB Zen value
• bump the corrective release to 1.3.2 and update the accounting documentation

Root cause

The 1.3.1 fallback deliberately quarantined the entire dedicated-memory snapshot after detecting one corrupt counter. That behavior was tested, but it was the wrong product behavior because it destroyed the primary per-process view.

Live verification on the reported machine

The installed 1.3.2 candidate reports 4.54 GiB board usage and preserves 41 valid rows while rejecting only dwm.exe, zen.exe, and NVIDIA Overlay.exe. The first rows include:

• DiscordPTB.exe: 522 MiB
• wallpaper64.exe: 473 MiB
• ChatGPT.exe: 184 MiB
• msedge.exe: 194 MiB
• System: 4.29 MiB

Validation

• Debug native/unit/CLI/ConPTY tests
• optimized Release native/unit/CLI/ConPTY tests
• AddressSanitizer tests
• MSVC static analysis
• PE mitigation and static-runtime verification
• package and Inno Setup build
• full installer, curl bootstrap, PATH, upgrade, and uninstall lifecycle
• installed-executable JSON: 41 valid dedicated rows, 3 rejected rows
• regression test explicitly asserts that corrupt rows do not erase valid rows