Platform: PC (Windows), Steam, client 2026.64.0.14517

Steps to reproduce:

1) Have Grist, the Hunger Tide in your library and Birthing Ritual on the battlefield.
2) At your end step, resolve Birthing Ritual's trigger. Grist is among the seven cards looked at but is not chosen, so it goes to the bottom of the library in a random order with the others.
3) Later in the same game, cast Chord of Calling with X = 3.

What happened: Grist is shown in the library while searching but can't be selected. Other creature cards with mana value 3 (Sephiroth, Fabled SOLDIER) can be selected.

What should happen: Grist should be selectable. Grist's first ability says "As long as Grist, the Hunger Tide isn't on the battlefield, it's a 1/1 Insect creature in addition to its other types." The official ruling on the card says Chord of Calling can put it onto the battlefield.

Extra detail from my Player.log:

1) Match ID d625f7b1-70a5-4d97-a4af-2788140205f4, game 2, about 10:56 AM local time (AEDT, UTC+11) on 17/10/2026.
2) In the SearchReq for Chord (gameStateId 211), the Grist object (instanceId 336) has cardTypes Planeswalker only, with no Insect subtype and no power or toughness. It is listed in itemsToSearch but not in itemsSought.
3) That instanceId was created at gameStateId 166, when Birthing Ritual's trigger put the six cards it didn't take on the bottom (Shuffle annotation: old IDs 172 to 178 except 176, the card taken; new IDs 336 to 341).
4) In an earlier game the same day, a Grist that had never been moved showed cardTypes Creature and Planeswalker, subtype Insect, 1/1, and Chord could select it. So the problem seems to start when the card gets a new instance ID in the library.

Workaround: none in game.