HevraVPN Chrome Browser Beta 0.2.2 — Account access

New installation:
1. Extract this ZIP into a permanent folder.
2. Open chrome://extensions and enable Developer mode.
3. Click Load unpacked and choose the folder containing manifest.json.
4. Open HevraVPN. Click Create an account, or sign in with your existing Hevra
   email and password. If your account uses MFA, expand the authenticator field.
5. Choose Germany or United States and enable the browser proxy.
   Gateway authentication is automatic; no separate proxy password is needed.
6. Disable the proxy to restore normal routing, or Sign out to disconnect and
   remove this Chrome profile's saved session. Mobile sessions stay signed in.

Updating an existing installation:
Disable the old browser proxy first. Replace the old extracted files with this
ZIP's files, then click Reload for HevraVPN at chrome://extensions. Alternatively,
remove the old extension and load this new folder. Check that the version is 0.2.2.
The old browser credentials JSON is no longer used.

Browser only: regular-profile supported browsing, destination ports 80/443.
Incognito and other applications are outside scope. Direct WebRTC UDP is disabled
while enabled. This is not an OS kill switch. An unavailable gateway does not
silently fall back to direct browsing. The account API uses its own direct HTTPS
connection so login and renewal can work when a gateway is unavailable.

Chrome may show broader site permission prompts in this update because automatic
proxy authentication needs HTTP/HTTPS host access. The extension handles only
proxy challenges for its selected Hevra gateway, never website passwords. It
stores account session tokens and short-lived browser credentials locally in this
Chrome profile, but never your account password or browsing history.

Share only this ZIP. Each person signs up or uses their own Hevra account.
Email delivery is not currently configured; signup does not promise a verification
email. This beta is not published in the Chrome Web Store.

Online Users: while enabled, the extension reports its account, selected gateway and a random session ID once a minute. No browsing destinations are reported. Disconnect removes presence; an abruptly closed browser expires after the server-configured timeout (three minutes by default).

Version 0.2.2 renews gateway credentials before their server-provided expiry.
Browser sessions share your account connection limit with mobile devices. If the
limit is reached, disconnect another session and retry. If a running session is
rejected, the popup and toolbar show a warning and new proxy authentication is
blocked until a retry succeeds. Existing connections may continue. Routing stays
on the proxy until you disable it; temporary API failures retry automatically.
