a4feb65161
On a server, single player's server thread included, the inventory had no recipe book: the window ignored the recipe book packets, and the server ignored a guest's ServerboundPlaceRecipePacket. - horizon-protocol decodes the recipe book's packets and the recipe displays they carry: RecipeBookAdd / Remove / Settings, PlaceGhostRecipe and the serverbound PlaceRecipe. Every 26.3 `recipe_display` and `slot_display` type is decoded (shaped, shapeless, furnace, stonecutter and smithing displays; empty, any_fuel, with_any_potion, only_with_component, item, item_stack, tag, dyed, smithing_trim, with_remainder and composite slots). - The remote client keeps the book the server sends (ClientRecipeBook: added, highlighted, removed, replaced), shows the unlock toast, applies the open and filter settings, and counts the menu the server last sent for the craftable filter. Clicking a recipe sends PlaceRecipe; a ghost recipe from the server fades in. - The server handles a guest's PlaceRecipe in the inventory grid and the crafting table (ServerPlaceRecipe on the menu engine, for known recipes only) and answers with the slots, or a ghost recipe when the items are missing. - The screen state reports the recipe book's buttons. lan_e2e.py gains a `recipes` check: the guest gets oak logs, opens the book, clicks the planks recipe, and a log lands in the grid. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>