v1.8.9 - launcher survives a path containing parentheses (TESTING)

TESTING ONLY - not production. v1.8.5 remains the approved latest release.

Fixes the reported failure: START-HERE.bat closed instantly, with no UAC prompt, when the extracted folder name contained parentheses (e.g. the 'name (1)' folder Windows Explorer creates on a second extract).

[1.8.9] - 2026-10-11

TESTING CANDIDATE - launcher fix for paths containing parentheses.

• START-HERE.bat now survives a folder name containing ( or ) - e.g.
  screenconnect-cleanup-v1.8.8 (1), which is what Windows Explorer creates
  when the same ZIP is extracted twice. cmd expands %~dp0/%~f0 at PARSE
  time, so the ( ) inside a ( ... ) block ended the block early and the
  batch aborted with no message and no UAC prompt: the window opened and closed
  instantly. Every path/argument expansion now happens once, before delayed
  expansion is enabled, and is referenced afterwards as !SCC_DP0! / !SCC_F0!
  / !SCC_ARG1! / !SCC_ARGS!, which cmd substitutes at run time (after
  parsing) and therefore cannot be broken by brackets in the path.
• New regression tests/ci/Test-LauncherPathWithParens.ps1: runs the real
  launcher from a paren-named directory and requires it to create its run root,
  with a negative control proving the old construct does abort from such a path.
  Wired into both CI editions.

Exact source: 76bbc7b557b78de02a39df05d40c7cf68566bb7f.

Windows CI (Server 2022 + 2025, PowerShell 5.1 and pwsh, including the extracted-ZIP fixtures) passed on both runners. The attached ZIP is the tested Windows 2022 CI artifact, published byte-identical - not rebuilt. relay/ and tests/ are not part of this bundle (server-side / dev only).