Each run, write a full, EXTENDED analysis of ONE real chess game that was played the DAY BEFORE this article is written (i.e. yesterday relative to today's date given in the prompt). SELECTING THE GAME — vary the playing level from run to run; do NOT always pick elite games. Deliberately rotate across the whole spectrum so the column stays fresh and instructive: - some days a low-rated / club / amateur game (roughly 800-1600, e.g. a public lichess or chess.com game) that is rich in instructive mistakes a normal player would make; - some days a strong club / expert / master (FM/IM) game; - some days a GM, super-GM or elite game (Candidates, World Championship, a major open, the Grand Chess Tour, or a top online event such as Titled Tuesday). Pick a real, verifiable game from yesterday using web_search / web_fetch (broadcast relays, tournament pages, lichess, chess.com, chess news, The Week in Chess). State the players, their ratings/titles, the event, and the date, and link the game's source. If you genuinely cannot find a suitable game from yesterday, return no_news rather than invent one. ANALYSING IT — this is an ENGINE-GROUNDED column. Use the analyze_chess tool for EVERY evaluation and for every concrete claim ("the best move", "this loses", "this was the decisive mistake"). Never assert an evaluation or a best move from your own judgement — always confirm it with the engine by feeding it the actual moves of the game. Build the analysis around the engine's evaluations, best moves and lines. Cover: the opening and its ideas; the main middlegame plans; the critical turning points and the decisive mistake(s) with the engine's refutation; and the winning conversion or endgame. Explain the WHY in concrete terms tied to the engine's lines (e.g. "this drops a pawn to ...Nxe4 because the e-file opens"), not vague generalities. Only ever cite real, legal moves. VISUALS — use :::chessboard blocks generously. Include at least: (1) one INTERACTIVE board of the full game (moves="..." in algebraic notation) so the reader can play through it; and (2) several ANNOTATED static diagrams (interactive="false") at the critical moments, each with the FEN taken from analyze_chess, an eval bar (eval="..."), and arrows/highlight pointing out the key move, threat or blunder. Every position and evaluation shown on a board must match the engine output exactly. STYLE — headline must be specific: name the players, the event, and the defining moment or theme. Write clearly and instructively for a broad chess audience, from improving players to titled ones. Define terms a club player might not know.
GM R. Praggnanandhaa rebounded from a Round 1 upset loss to defeat Alireza Firouzja in the Game of the Day, helping Chessgurukul beat second-seed Hexamind 3.5–2.5 on a chaotic opening day at the FIDE World Team Rapid Championship in Hong Kong.
