New in 2.0.1 — safer Agoda lookups

• Added a circuit breaker: the moment a rating site blocks us (HTTP 403/429 or
a challenge page), the extension stops sending it ANY new requests for a
cooldown (Booking.com 6h, Agoda 24h) instead of retrying hotel-by-hotel.
This prevents the request floods that can get an IP temporarily banned.
Cached ratings still show while a source is paused; the pause survives a
restart and is cleared by "Clear rating cache".
• Agoda is now OFF by default (opt-in) — it guards its results aggressively.
• Agoda is queried more gently: one request per hotel and a slower throttle.
• Badges show a clear "paused, cooling down" note while a source is in cooldown.

(2.0.0 added Agoda as a second source alongside Booking.com, and made the ⚖
"balanced" score pool both sites' reviews into one number.)

New in 2.0.0

• Added Agoda as a second rating source. Each hotel on plazh.com now gets a
badge per source — Booking.com (navy) and Agoda (orange) — each linking to
that site's page for the hotel.
• The ⚖ "balanced" score now pools BOTH sources into a single number, so a
hotel is judged on all its reviews at once (review-count-weighted Bayesian
average, eased toward a neutral 8.0 baseline). Hover it to see which sources
contributed. With one matched source it equals that source's own weighted
score, so nothing changes if you turn the other off.
• New options: turn Booking.com and/or Agoda on or off independently.
• Lookups are throttled per source, so the two sites are queried in parallel
while each stays polite. Cached results from older versions are refreshed
automatically.
• Renamed to "Plazh × Hotel Ratings" to reflect the second source.

As before, only the hotel name (plus an optional location hint from the result
card) is sent to the rating sites — nothing else leaves your browser.

v1.3.0 — Review-weighted score

Each Booking.com rating badge now shows a second value (⚖) next to it: a review-weighted score. It eases the raw guest score toward a neutral baseline based on how many reviews back it, so a 9.4 from a dozen reviews no longer outranks an 8.9 from thousands. Makes "best by score" comparisons across hotels fairer.
The weighted value is hidden when Booking.com doesn't report a review count.

v1.2.0

• Fixed: Booking.com ratings load again. Booking.com had begun blocking the
  extension's lookups, so hotels were showing "n/a". Rating requests are now
  sent with standard browser-navigation headers so they're no longer blocked.
• Stale cached "blocked" results are cleared automatically on update, so
  ratings refresh instead of staying stuck on the old failure.
• No new data is collected; the extension still only sends a hotel name (and
  an optional location hint) to Booking.com, and nothing else.

Improved hotel name matching accuracy.