Separate items, rewards, milestones, and code claims
The safest workflow is simple: identify the item family you are testing, record the reward or outcome the game visibly shows, keep milestone claims such as Wave 20 or Crafting Machine in watch status until the UI matches them, and treat every code claim as unconfirmed until a working redeem path appears. That keeps items useful, rewards honest, and copied lists from polluting the route.