Tidal Observation Card

Added Added the Tidal Spin system: rewards that have been observed but not yet claimed can now be sent into the spin system, where players can lock results, refresh options, and fine-tune symbols to improve or change the final reward. Added supporting mechanics for Tidal Spin, including Tidal Points, moon phase modifiers, reward pool returns, spin entry tickets, and a confirmation popup before entering the spin system. Added multi-page support for Observation Cards and a new random single-tier observation mode. The gameplay mode can now be configured to use either the traditional manually selected tier system or the new random tier system. Added /trs reload for hot-reloading configuration files and /trs doctor for checking configuration issues, making server management and troubleshooting easier. Changed Updated the Observation Card screen to support multiple pages. The Observe All button now only affects cards on the current page. Improved the card reveal animation, spin animation, spin wheel buttons, reward pool return display, and moon phase display through multiple UI iterations. Split and expanded the configuration system. A new tidal_spin.json5 file has been added, allowing Tidal Spin mechanics, entry costs, Tidal Points, moon phase modifiers, and related behavior to be configured. Client-side configuration is now synchronized from the server after joining a server. Actual gameplay behavior follows the server configuration. Fixed Fixed issues in random tier mode where preview cancellation, tier button expansion, and incorrect tier display during card reveal could behave unexpectedly. Fixed several Tidal Spin UI and interaction issues, including lock state handling, settlement popup layering, tooltip passthrough, overly heavy reward pool return backgrounds, and spin wheel text overflow. Fixed compatibility issues when older configuration files are missing newly added fields. Missing fields now automatically fall back to default values. Verified that a dedicated server can start successfully. No server-side crash caused by client-only class loading was found.