refactor: casino table core; fix: stake/migration/validation gaps

1 files changed, 7 insertions, 4 deletions

diff --git a/building_guide/rooms.md b/building_guide/rooms.md
index 568611f..3b9c120 100644
--- a/building_guide/rooms.md
+++ b/building_guide/rooms.md
@@ -354,7 +354,9 @@ casino configurations. Raw file editing is not a validated save endpoint.
   is rejected as unreachable content.
 - Omitted/zero numeric values keep their existing defaults. Negative bets,
   timers, seat counts, split counts, decks, and payouts are rejected.
-- An explicit `max_bet` must be at least `min_bet`; zero still means no cap.
+- An explicit `max_bet` must be at least `min_bet`. An omitted or zero
+  `max_bet` uses the default cap (1,000,000); the explicit sentinel
+  `9223372036854775807` means no cap.
 - A blackjack table that offers `surrender` must set `min_bet` to at least 2:
   a surrendered hand returns half the bet, which rounds down to zero below
   that (the omitted default of 1 is rejected too).
@@ -369,9 +371,10 @@ casino configurations. Raw file editing is not a validated save endpoint.
   is an RTP fraction greater than zero and at most one; zero defaults to 0.97.
 - Unknown casino fields are rejected by the room create/update API.
 
-Existing instantiated games retain their rules until restart; editing a room
-does not hot-reconfigure a live table or machine. Use explicit, modest wager
-limits: validation does not yet make currency arithmetic overflow-safe.
+Editing a room hot-reconfigures an **idle** table or machine on the next
+lookup; an occupied game keeps its live rules until it becomes idle, so a
+committed wager is never discarded. Use explicit, modest wager limits:
+validation does not yet make currency arithmetic overflow-safe.
 
 ### Objects — interactive fixtures