Testnizer v1.4.17

v1.4.17

Packaging fix: macOS (and Windows) auto-update works again. No app changes —
this release only repairs the release pipeline that produced broken update
metadata in v1.4.16.

• macOS auto-update fixed (v1.4.16 regression): in v1.4.16 the macOS update
  failed with sha512 checksum mismatch. Root cause: macOS and Windows builds
  produced a zip with the same filename (Testnizer-<version>-<arch>.zip)
  and published it to the same GitHub release, so the Windows arm64 zip
  overwrote the macOS arm64 zip — the updater then downloaded a Windows file
  where it expected the macOS app. The Windows zip target has been removed
  (Windows ships the NSIS installer; the portable zip was unused), eliminating
  the collision.

• Both architectures update again (mac + Windows): each platform now builds
  both arches (arm64 + x64) in a single packaging step, emitting one
  complete latest-mac.yml / latest.yml. Previously the two per-arch jobs each
  wrote their own manifest and clobbered each other on the release, so only one
  architecture was ever listed — the other arch's users silently got "no
  update". Apple-Silicon and Intel Macs, and x64 and arm64 Windows, can all
  auto-update now.

• Runner now refreshes script-written variables: after a folder/collection
  Run, a variable a post-response script captured (e.g. pm.environment.set ("accessToken", …) in a Create-Token request) now shows up immediately in the
  environment editor and resolves on the next Send — previously the value was
  saved to disk but the in-app environment stayed stale, so it looked empty and
  had to be retyped by hand. The "Keep variable values" toggle is also honored
  on these run paths now.

Upgrading from v1.4.16 on macOS: because v1.4.16's update metadata is
broken, the in-app updater can't carry you to v1.4.17 automatically. Download
the v1.4.17 .dmg from the releases page once; auto-update will work normally
from v1.4.17 onward.