UZB Ops 0.6.3 - Company website beta - 1 November 2026
https://uzbekistanairwaysvirtual.com/ops/

This separate beta adds an opt-in connection between the real UZB Ops interface
on the company website and the existing Windows companion. The current 0.6.2
download remains available in the Company Flight Bag.

SETUP
1. Close the previous UZB Ops console with Ctrl+C. Closing a browser tab alone
   does not stop it. Extract this complete ZIP into a new folder. Do not copy a
   data folder, runtime file or credentials from another pilot's installation.
2. Run SETUP_WINDOWS.cmd, then START_UZB_OPS.cmd. Existing personal history stays
   in your Windows user data folder. This package does not migrate or delete it.
3. In the local browser window, select Generate connection code. Open the website
   link and enter that one-use code there within five minutes, on this same PC.
   Use the port printed by the companion (normally 7414; supported 7414-7423).
4. Allow local network / loopback access when the browser requests it. Pairing
   does not itself connect MSFS. Load the intended OFP and connect MSFS as usual.
5. Disconnect clears this tab's key. To revoke every website tab immediately,
   use Disconnect website tabs in the local companion, or stop its console.
   Reloading the website requires a fresh code. Sessions expire within 12 hours.

SCOPE AND PRIVACY
- The server listens on 127.0.0.1 only. Only the exact canonical HTTPS company
  website is permitted to pair; it uses a temporary bearer key held in tab memory.
- State and commands travel directly between that tab and your own companion.
  There is no public flight-data relay, company account login or cloud history.
- MSFS/SimConnect, local scenery inventory, Fenix Documents and optional Hoppie
  remain functions of the running Windows companion. The website cannot replace
  those integrations. Do not expose the port to the Internet or your LAN.
- A separate iPad cannot reach 127.0.0.1 on the simulator PC. Use the existing
  local Crew Deck instructions for a tablet. Mobile layout does not imply a
  remotely connected cockpit.
- Bookings, PIREPs and VA progression continue through vAMSYS and Pegasus.
  Network acceptance is not proof of an aircraft message being received. Scenery
  checks do not validate aircraft fit, live occupancy or gate allocation.

VALIDATION
The website and bridge have automated offline checks. Browser pairing is tested
where available. Windows/MSFS/Fenix, actual aircraft telemetry, Hoppie reception,
audio and real browser permission prompts on the simulator PC still need a local
acceptance check. This is a beta, not a claim of simulator-qualified operation.

LOCAL ACCEPTANCE
Open the same OFP in the local app and website. Verify flight number, route and
UTC/ETA source. Connect MSFS and confirm changing, current aircraft data. Record
a harmless preview while dispatch is disarmed; check it appears locally too.
Test one Fenix document refresh. Revoke website access and confirm live controls
stop. Reconnect using a fresh code. Do not send a live Hoppie test unintentionally.

ROLLBACK
Stop this console. Open START_UZB_OPS.cmd from the unchanged 0.6.2 folder. The
previous release and personal data are retained; only the website pairing needs
the beta. Do not run both companions at once.