Personal Open ID Launcher 1.0.0 - Windows x64

FIRST INSTALL
1. Download this ZIP only from https://openid.rbnebula.com
2. Right-click the ZIP and select Extract All. Do not run inside the ZIP.
3. Open install.cmd as your normal Windows user (not Run as administrator).
4. Keep the installer open until Installation completed appears.
   First setup downloads Node.js and Chrome for Testing; internet is required.
5. Open https://openid.rbnebula.com and sign in with your approved Google account.
6. Reload accounts, then click Open ID. Allow Personal Open ID to open.

DAILY USE
Use the website or the Personal Open ID desktop shortcut. No Mac needs to stay on.
The launcher opens through the account Proxy and fills login fields only.
It does not click Login, accept agreements, capture images or place bets.
Mode is read from the Sheet: PC/blank = desktop; Mobile = mobile emulation in a
large PC window. Existing browser windows keep their previous Mode.

REQUIREMENTS
64-bit Windows with a supported Playwright/Chromium environment (Windows 11 x64
recommended). No separate Node installation, Google JSON or API key is required.
This package is NOT a signed commercial Windows installer. Only run it if you
trust the source. Organizational security policy may block scripts or Chromium.
Windows ARM64/native packaging is not provided by this x64 package.

SECURITY
Account passwords and Proxy credentials are not included in this ZIP.
The protocol URL contains a one-time 90-second ticket, not the password.
Runtime and Chromium are installed under your private LOCALAPPDATA folder.
No raw credential/error log is created by the launcher. TLS checks and browser
sandbox stay enabled. Proxy failure stops the opening; no direct fallback.
This registers only personalopenid:, not the old rbnebula: protocol.

If opening fails, click Open ID again to get a fresh ticket. Check that your
Google account has Sheet access, is a Google Test user and is on the web allowlist.
Some websites redirect or have different login fields; manual filling may be
necessary. Mobile emulation is not a guarantee of real-device eligibility.

VERIFICATION LIMIT
Package logic and protocol/security tests run on Mac using dummy data.
Installation on real Windows must still be verified before wider rollout.
