VX Bridge 0.3.0

VX Bridge 0.3.0

VX Bridge forwards shot data from ProTee Labs to Infinite Tees or GSPro OpenAPI
on the same Windows PC. This release adds local diagnostic reports and a
clearer way to report bugs or request features.

Changes since v0.2.0

• Save one diagnostic ZIP. Choose Save diagnostic report... from the
  bridge menu. The ZIP contains a readable summary, a source manifest, typed
  status/settings/installation observations and sanitized bridge events.
  Reporter, running-host and installed-receipt versions are kept separate.
• Report without a working host. Open VX Bridge Diagnostics from Start
  when the bridge will not start, its icon is missing or admission is refused.
  It uses the same exporter without starting or repairing the host or calling
  Windows Installer. Missing, corrupt or unavailable sources produce an
  explicitly partial report.
• Use the reporting forms. Report a bug opens the
  bug form.
  The separate
  feature form
  asks about the task, workaround and desired outcome, not a demanded implementation.
  A diagnostic ZIP and redacted screenshots are optional.
• Identify the actual build. Logs and reports now carry the release
  version separately from the retained prototype/protocol label, together
  with source revision, toolchain and architecture.
• Keep collection bounded and local. Collection has fixed source limits,
  an eight-second wait budget, a one-second status query and a 2 MiB ZIP cap.
  Existing logs are not cleared or rotated. Export creates a new local file
  and does not silently overwrite an existing one.

The distinct control client also provides
vxbridge.exe --diagnostics <new-absolute-local-file.zip> and
--diagnostics-dialog for support. See the
reporting guide
and command reference.

Shot forwarding, remembered game selection and source-first Quit are unchanged.
There is no new service, updater or runtime. The installed application still
has six payload files, and the release still has only the installer EXE and
its checksum.

Install

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.

1. Download
   vx-bridge-installer-windows-amd64-v0.3.0.exe
   under Assets. The .exe.sha256 file is an optional checksum, not a
   second installer. Source code downloads are for developers.
2. In ProTee Labs, select Game Options > Disconnect. Close an 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 EXE as the Windows user who will use the bridge, not as
   administrator. Choose Install for a fresh installation. The EXE contains
   the matching native Setup, MSI and support files; no ZIP extraction or
   adjacent MSI is needed.
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 verified Setup success. Choose Start bridge to open it once,
   or Not now to open VX Bridge from Start later. Starting it once does
   not enable sign-in 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. Find its icon near the clock, including the
   hidden-icons area. Right-click it and select Use Infinite Tees or
   Use GSPro OpenAPI. The checkmark shows the applied choice.
3. Use Labs' normal Connect action if needed. The bridge does not start Labs
   or the game, or connect Labs for you.
4. Check the bridge menu and the game. Connected (transport only) is not
   proof that the game is ready. Wait for each shot's visible result before
   the next swing.

Finish with Game Options > Disconnect in ProTee Labs, then Quit in
VX Bridge. Do not force the bridge closed while Labs is attached. Missed shots
are not saved or replayed; if delivery is uncertain, check the game first.

Report a problem

Choose Save diagnostic report..., or open VX Bridge Diagnostics from
Start if the host is unavailable. Choose a new filename in a writable local
folder. Cancel saves nothing. A saved or partial report is local:
nothing was sent.

Open the ZIP and review summary.txt, manifest.json, report.json and
events.jsonl. Then choose Report a bug and attach it only if you wish.
Include steps, expected and observed behavior, approximate time/time zone,
selected game and versions you know. Labs/game versions are not scanned;
write unknown if needed.

If export fails, submit the form without a ZIP and describe the save error.
Do not attach raw vendor/MSI logs, captures, shot/player/device/license/account
details, credentials or unredacted screenshots. See
report contents and privacy.

Existing installations

This release does not establish a supported in-place upgrade from v0.2.0,
v0.1.0 or a portable/pilot build. Setup retains exact native-core/source and
ownership checks; arbitrary cross-source versions are not adopted.
Disconnect Labs and Quit normally before changing an existing installation.
Keep the old copy's files and startup registration intact until you have
reviewed migration instructions.

For damage to this installed build, use VX Bridge Setup > Repair / Reinstall.
If its saved source is missing, use the original verified installer for that
build. Normal Uninstall uses Windows Settings > Apps > Installed apps >
VX Bridge > Uninstall. Full Uninstall removes bridge-owned settings and logs,
not vendor data, independently saved reports or original downloads.

A failed operation need not restore the previous version. Do not replace
files, purge Windows Installer records or delete settings to bypass a refusal.
See the
installation and recovery guide.

Contributors

Thanks to David Justice (@devigned) for
#4: bug reporting, feature forms and privacy-safe diagnostic ZIPs,
the merged change since v0.2.0. No new human first-time contributors were
identified in this range; @devigned contributed to earlier releases.

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

Verification and limits

The exact tagged source passed routine CI: portable and Windows tests, race
tests, vet, workflow lint and static installer/package checks. The release
workflow built and verified the matching application and installer from this
tag, then published only its own run's EXE and checksum. Both public files
were independently downloaded and checked against the original immutable
build artifact, GitHub asset digests and the EXE checksum. Static inspection
verified the embedded Setup/MSI, application archive and source/version.

These are source and file-integrity checks, not interactive qualification.
The installer and product were not run for this release. Native
save/cancel/accessibility/DPI behavior, Windows extraction and servicing,
sign-in and live Labs/game behavior remain unqualified for these binaries.
Earlier observations used different builds and do not qualify v0.3.0.
Reports are best-effort observations, not proof of game readiness, complete
shot history or installation health.

The installer and application are not Authenticode-signed. Signed Git
source and tags do not sign Windows binaries. Checksums bind file contents;
they do not authenticate a publisher.

Files and source

The only uploaded assets are
the Windows x64 installer EXE
and its SHA-256 checksum.
GitHub also provides automatic source ZIP/tar.gz archives.

Source: d83d8c7e01ecb0cbb59ff33b39a23d0c77dbb7f8.
Signed annotated tag object: 182982c3664e1e4dc1fabbb373007f7c44394ddd.
The tag uses @devigned's existing signing key,
F1E46E1FE0B2BEF85D4CDE8F2B44C6BF9F416319, verified locally and by GitHub.
GitHub also verifies the source merge commit's signature.

Release build and publication.
Exact-main CI.
Changes since v0.2.0.

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.

v0.1.0

v0.1.0 - unsigned Windows application and installer. Source: 5401cf2
Tag-ref object: 48a9f0b02ae214135b6b999bdb424b6496f9924d
Download the installer ZIP, extract it to one folder, and run setup.exe.
Keep its matching bridge.msi beside setup.exe; the direct MSI asset is not a standalone installer.
The separate application ZIP contains the six-file portable application distribution.
Installer metadata records the actual emitted PackageCode, full MSI hash and native owner identity.
Toolchain/license notices and checksums are included. No signing or automatic-update claim is made.
Publication does not qualify hardware, games, startup or lifecycle behavior on your machine.
Checksums detect corruption; they do not authenticate a publisher.
Build workflow: https://github.com/devigned/vx-bridge/actions/runs/41832770003