Advertise the jackpot that will actually be paid (B-65)

participant_count and jackpot_sats were computed over every round_participants
row, while the draw only picks from confirmed participants and the payout only
spends their sats. So the advertised jackpot could exceed the one paid out, and a
player whose bet was later abandoned appeared in the count and then vanished
again.

Counting only confirmed rows would have fixed the arithmetic and broken something
else: the player who just bet would see neither themselves nor their money for a
whole block. So this is the same confirmed/in-flight split the balance already
exposes (balance_sats vs pending_balance_sats): participant_count and
jackpot_sats are now the confirmed, authoritative figures, and
pending_participant_count/pending_jackpot_sats/has_pending_bets report what is in
flight — inclusive figures, not deltas, matching the balance pair's convention.

/'s round card shows the confirmed numbers big and the difference as an amber
"+N in attesa" suffix, reusing .balance-pending's colour for the same "not
settled yet" meaning. The two new spans render from server data through t(), so
they carry no data-i18n and onLanguageChange() repaints them from the last
response — the one-mechanism-per-element rule. Both strings are in all 7
languages.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

BUGS.md

@@ -40,19 +40,6 @@ remains the last prerequisite for running unattended.
 
 ## Medium — correctness and robustness
 
-### B-65 — `/rounds/current` counts unconfirmed participants; the draw and payout do not
-
-`app/api/routes/rounds.py:131-143` vs `app/rounds/scheduler.py:126`.
-
-`participant_count` and `jackpot_sats` are computed over *all* `round_participants`
-rows, while the draw and the payout only use `status == "confirmed"`. So the
-advertised jackpot can exceed what is actually paid out, and a participant whose
-bet is later abandoned appears in the count and then vanishes from it.
-
-Fix: either count only `confirmed` (and accept that a fresh bet takes a block to
-show up), or expose the two figures separately (confirmed vs in-flight) so the
-number on screen and the number that gets paid agree by construction.
-
 ### B-66 — nothing stops rounds from opening with no `fee_address` configured
 
 `app/rounds/config.py:12-17`, `app/rounds/scheduler.py:330-335`.