Verify meeting stones on a real client, across two shards #532

Expected (1.12.1). A type-23 Meeting Stone at a dungeon entrance lets a player queue alone, or a party leader queue the whole party, for that dungeon. The client shows a level-range tooltip, a minimap button while queued, and the full SMSG_MEETINGSTONE_* flow: join refusals, member added, complete, a leave/kick/disband set, and the button surviving a loading screen or a Transfer.

Actual (at 87109e3c). The code is done. The queue and matching live on Realm-core (module/src/meeting_stone), with a Roster Revision Relay keeping each World Shard's party mirror current and the Gateway handlers at gateway/src/world/handlers/meeting_stone.rs. CI runs both new cross-shard Gateway durable tests (gateway/src/stdb/subscriptions_meeting_stone_durable_tests.rs). Nobody has run the flow on a real 1.12.1 client.

How to check. Follow docs/meeting-stone-client-check.md end to end: three Alliance characters on two clients, a sharded ./lyracore dev up stack with the gameobjects family imported, and debug_repair_after_publish run by hand after publish so queued parties hear IN_PROGRESS. The doc's checklist covers the tooltip, level refusal, join and leave, surviving a loading screen and a Transfer, logout dropping a solo Seeker, leader-only queuing with the not-leader and full-group refusals, a cross-shard party join, and lead-pass and raid-conversion behavior.

Done when. The doc's checklist is run and its "Execution status" line is updated from "outstanding" to the result, with the client build and the commit recorded.