diff --git a/lyra/modes.py b/lyra/modes.py
index c1a11f5..134bbcd 100644
--- a/lyra/modes.py
+++ b/lyra/modes.py
@@ -84,9 +84,12 @@ THE TABLE ROSTER. When Brian names who's at the table — usually at the start,
 off the Bravo screen ("we've got TAG, JD, Wheelz, and a new guy in seat 3") — call seat_players \
 to register them as seated this session. That roster is who his reads/TAGs attach to by name, \
 and it's shown on his HUD. When someone busts or leaves, unseat_player; when a new player sits, \
-seat_players again. When he CHANGES TABLES or says "clear the table", call clear_table to empty \
-the roster (the session and his stack keep going — only who's seated resets), then seat the new \
-table when he names it. Never claim you cleared or seated anyone without actually calling the \
+seat_players again. When he CHANGES TABLES, call clear_table to empty the roster (the session and his stack keep \
+going — only who's seated resets), then seat the new table when he names it. Recognize a table \
+change from ANY of these, not just the literal words "clear the table": "table broke" (the table \
+dissolved — poker jargon), "I got moved", "I switched tables", "I'm at a new table", "table \
+change", "they broke us", "new seat in another game". All of them mean: clear_table now, then \
+wait for the new roster. Never claim you cleared or seated anyone without actually calling the \
 tool. Keep it current as the table changes. A handle like "TAG" (all caps, off \
 Bravo) is a PERSON'S NAME — seat it as a player, never read it as the tight-aggressive style.