chore(deps): bump Terminal.Gui 2.4.12→2.4.17-develop and WinGet COM to 1.29.280

- Terminal.Gui 2.4.12-develop.7 -> 2.4.17-develop.6 (stays on the develop
  track per this repo's parity-tracking intent). Verified: clean build,
  109/109 tests pass, and a mock-backend TUI smoke (main list, detail
  panel, Help dialog, Search/Installed tabs) showed no rendering
  regressions on Linux.
- Microsoft.WindowsPackageManager.ComInterop + .InProcCom 1.29.190-preview
  -> 1.29.280, kept in lockstep as required by the in-proc Native-AOT COM
  activation fix (HANDOFF.md session 3). First time this lands on an
  actual stable (non-preview) release; packaging shape and upstream
  activation-surface behavior are unchanged per release notes, but this
  is Windows/AOT-only functionality that can't be verified from Linux.
- Added WINDOWS-TESTING.md items to re-run the P0 COM smoke suite and a
  light Terminal.Gui spot-check on real Windows hardware before shipping.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

Author: harder

WINDOWS-TESTING.md

@@ -208,6 +208,8 @@ but these paths need a real terminal / real winget to confirm end-to-end.
 - [x] **Measure the AOT binary size** of the COM (Windows) build and compare to the CLI/mock build, to budget the COM backend's cost. *(Session 3: **AOT win-x64 single exe = 22.4 MB** (no `coreclr.dll`) + the in-proc engine **`WindowsPackageManager.dll` ~7.3 MB** beside it ≈ **~30 MB deployed** — this is the **ship target** now that COM activates under AOT. For comparison, the abandoned JIT self-contained fallback was **112.7 MB** for the whole folder (~4× larger).)*
 - [ ] **(Optional) win-arm64**: repeat the P0 smoke on an arm64 host or arm64 cross-target.
 - [ ] **Terminal.Gui bump `2.4.3-develop.9` → `2.4.7-develop.1`.** Spot-check the Windows-only input/render fixes that landed in the 2.4.4 release line (can't be verified from Linux): (a) type a **non-ASCII search query** (e.g. accented chars / IME) into `/` search and confirm it renders correctly (Windows VT input encoding fix #5453); (b) **paste** a Unicode string into search via bracketed paste and confirm no mojibake (clipboard fixes #5449/#5451); (c) **resize the terminal** mid-use and confirm no garbled frame at the wrong dimensions (#5461). No app code changed — these are upstream fixes the bump picks up for free.
+- [ ] **Terminal.Gui bump `2.4.12-develop.7` → `2.4.17-develop.6`.** Mock-backend smoke on Linux (main list, detail panel, Help dialog, Search/Installed tab switch) showed no rendering regressions. Nothing in this range looks Windows/input-specific, but do a normal pass anyway since it wasn't previously exercised on this host.
+- [ ] **WinGet COM packages bumped `1.29.190-preview` → `1.29.280`** (`Microsoft.WindowsPackageManager.ComInterop` + `.InProcCom`, kept in lockstep). This is now a **stable** (non-preview) release for the first time. The in-proc AOT-activation trick from session 3 (P0 above) is version-sensitive, so **re-run the full P0 smoke on this build specifically**: `--comdiag` (activation OK, no `0x80073D54`), badge now reads **`COM · winget 1.29.280`**, and the read-only COM smoke suite (search / installed / upgrades / versions / detail / `Verify`). Upstream release notes for 1.29.280 don't mention any COM/activation-surface changes, so this is expected to just work, but it's exactly the kind of bump that broke AOT activation before — don't skip it.
 
 ---
 

WingetTuiSharp.csproj

@@ -60,7 +60,7 @@
       prereleases; this is intentionally a moving target since the project's purpose is
       to evaluate parity against current Terminal.Gui behavior.
     -->
-    <PackageReference Include="Terminal.Gui" Version="2.4.12-develop.7" />
+    <PackageReference Include="Terminal.Gui" Version="2.4.17-develop.6" />
   </ItemGroup>
 
   <ItemGroup Condition="'$(TargetFramework)' == 'net10.0-windows10.0.26100.0'">
@@ -69,13 +69,13 @@
       projected collection) — see spikes/ComBackendSpike/SPIKE-RESULTS.md for why. No
       CsWinRT optimizer package is needed for the indexing pattern.
     -->
-    <PackageReference Include="Microsoft.WindowsPackageManager.ComInterop" Version="1.29.190-preview" />
+    <PackageReference Include="Microsoft.WindowsPackageManager.ComInterop" Version="1.29.280" />
     <!--
       In-process WinGet COM server (WindowsPackageManager.dll + Microsoft.Management.Deployment.InProc.dll).
       ExcludeAssets=compile so its bundled .winmd doesn't collide with ComInterop's managed projection;
       we only want its native runtime assets copied next to the exe. app.manifest routes activation here.
     -->
-    <PackageReference Include="Microsoft.WindowsPackageManager.InProcCom" Version="1.29.190-preview" ExcludeAssets="compile" NoWarn="NU1701" />
+    <PackageReference Include="Microsoft.WindowsPackageManager.InProcCom" Version="1.29.280" ExcludeAssets="compile" NoWarn="NU1701" />
   </ItemGroup>
 
   <ItemGroup>