VX Bridge 0.2.0

VX Bridge 0.2.0

VX Bridge forwards shot data from ProTee Labs to Infinite Tees or GSPro OpenAPI
on the same Windows PC. This release replaces the multi-file installer download
with one self-contained Windows x64 setup EXE.

Changes since v0.1.0

• One installer download. The EXE contains the matching native Setup, MSI,
  support files, metadata and license notices. No ZIP extraction or adjacent
  bridge.msi is needed. Windows Installer still owns installation, repair,
  compatible upgrades and uninstall.
• Two uploaded assets. Download
  vx-bridge-installer-windows-amd64-v0.2.0.exe. Its .exe.sha256 companion
  checks file integrity. Filenames use the tagged version, not a source SHA.
  The separate MSI, application ZIP, installer ZIP and their former checksums
  are no longer uploaded. GitHub still provides source ZIP/tar.gz archives.
• Preserved servicing checks. The outer EXE verifies its embedded files,
  stages a private matching Setup/MSI pair, waits for Setup to finish and
  removes only its owned staging files. Exact source, PackageCode, receipt,
  media hashes, per-user admission and source-first shutdown checks remain.
  Normal repair uses the saved Setup/MSI; normal application startup never
  invokes Windows Installer.
• Updated guides. Installation, recovery, release and contributor
  documentation now describe the self-contained EXE. The README uses the
  latest-release link. Historical v0.1.0 downloads and instructions are unchanged.

The bridge's shot forwarding, remembered game selection and guarded Quit
behavior are unchanged. This is a packaging and documentation release, not
new live-equipment qualification.

Requirements

Use Windows x64, an activated ProTee VX with ProTee Labs already working, and
a licensed Infinite Tees or GSPro installation on the same PC. For GSPro, use
its public OpenAPI / APIv1 Connect application, not the native VX receiver.
VX Bridge supplies neither a game nor a license and needs no separate .NET or
browser runtime.

Install

1. Under Assets, download
   vx-bridge-installer-windows-amd64-v0.2.0.exe.
   The .exe.sha256 file is a checksum, not another installer. Source code
   downloads are for developers.
2. In ProTee Labs, select Game Options > Disconnect. Close any existing
   receiver through its own controls. Do not run two receivers or replace the
   vendor's GSPconnect.exe. Read Existing installations below before
   changing an installed or portable copy.
3. Open the downloaded EXE as the Windows user who will use the bridge, not as
   administrator. Select Install for a fresh installation. Everything
   Setup needs is inside this one file.
4. Leave Auto-launch on Windows Startup off unless the bridge should open
   when you sign in. It is off on a fresh install.
5. Wait for Setup to report success. At Start the bridge now?, select
   Start bridge to open it once, or Not now to open VX Bridge from
   Start later. Starting it once does not enable auto-launch.

If Windows blocks Setup, stop and
report the warning.
Do not disable security protections or bypass the warning.

First use

1. Open the game and enter a playable practice scene. For GSPro, also open
   OpenAPI / APIv1 Connect.
2. Open VX Bridge from Start if it is not running. Find its icon near the
   Windows clock; check the hidden-icons arrow if necessary.
3. Right-click the icon and select Use Infinite Tees or Use GSPro OpenAPI.
   A checkmark shows the applied choice. The bridge remembers it for next time.
4. Use ProTee Labs' normal Connect action if needed. The bridge does not open
   Labs or the game, or connect Labs for you.
5. Check the bridge menu. Labs should be connected and the selected game should
   show Connected (transport only). Then check the game itself before
   swinging. A data connection does not establish that the game is ready.

Wait for each shot's visible result before the next swing. To finish, select
Game Options > Disconnect in ProTee Labs, then Quit in VX Bridge.
Do not force the bridge closed while Labs is attached.

Existing installations and recovery

This release does not establish a supported in-place upgrade from v0.1.0 or
an older portable/pilot build. Compatible upgrade checks require the recorded
native core and source; arbitrary cross-source versions are not adopted.
Disconnect Labs and Quit normally. Keep the old copy's files and startup
registration intact until you have reviewed migration instructions.

For damage to this installed build, open VX Bridge Setup from Start and
select Repair / Reinstall. If the saved source is missing, use the original
verified installer EXE for that build. Normal uninstall uses Windows
Settings > Apps > Installed apps > VX Bridge > Uninstall and does not
need the original download.

A failed operation is not guaranteed to restore the previous version. Keep
the bridge stopped until Setup verifies recovery. Do not delete Windows
Installer records, purge settings or replace files to bypass Repair required.
See the installation and recovery guide
and FAQ.

Contributors

Thanks to David Justice (@devigned) for
the repository's first merged pull request, #1,
the release-independent README, #2,
and the self-contained installer, #3.
These are the merged changes since v0.1.0. No new human first-time contributors
were identified in this range; @devigned was already credited in v0.1.0.

Copilot App is credited as an automated co-author on the change commits, not
as an additional human contributor. Dependency and reference attributions
remain in THIRD_PARTY_NOTICES.txt
and the embedded installer notices.

Verification and limits

The tagged source passed routine CI, including portable tests, race tests,
Windows tests and static MSI authoring/package checks. The release workflow
built the application and matching installer from the exact tagged commit,
then verified and published only that run's EXE and checksum.
Both public files were independently downloaded and matched to the immutable
build artifact and GitHub asset digests. The EXE passed static inspection of
its embedded Setup/MSI, original application archive and exact source/version.

These are build and file-integrity checks. The installer and product were not
run for this release. Windows extraction, interactive installation,
cancellation, servicing, sign-in and live Labs/game behavior remain
unqualified for these binaries. Earlier installer and equipment observations
used different builds and do not qualify v0.2.0.

The installer and application are not publisher-signed (Authenticode).
The signed Git tag and source signatures do not sign Windows binaries.
Checksums detect changed or damaged bytes; they do not authenticate a publisher.
Missed shots are not saved or replayed. If delivery is uncertain, check the
game before swinging again: it may have received the shot.

Files and source

Download	Use
Windows x64 installer EXE	Normal installation. Contains the matching Setup/MSI and required support files.
EXE SHA-256 checksum	Optional integrity check for that exact EXE.
GitHub's automatic Source code ZIP/tar.gz	Source for developers, not a ready-to-run Windows app.

Version: v0.2.0.
Source: 008b410d2a8726145514e76be96d99cc3de3612a.
Signed annotated tag object: fcec0f0e678904fae96cea8e033c1df2f42daed5.
The tag uses @devigned's existing signing key,
F1E46E1FE0B2BEF85D4CDE8F2B44C6BF9F416319, and is verified locally and by GitHub.
The source merge commit also has a verified GitHub signature.

Release build and publication.
Main CI.
Full source comparison.