Thanks for waiting until after plenty of people already bought it. Maybe you shouldn't have issued out that original review score to begin with.
Don't you think there is a legitimate dilemma here? Lots of games nowadays receive Day 1 patches, and review code is commonly buggy, but PR people promise the reviewers that certain things will be fixed. It seems that there are 3 options:
1. Ignore the potential for bugfixes and just review the code you have. The problem with this approach is that if the Day 1 patch does fix the bugs, your review will be misleading. Companies may also stop sending you review copies (and for a legitimate reason).
2. Trust that the bugs will be fixed in the patch. The problem with this approach is what you see in this thread. If the bugs aren't actually fixed, then your review is misleading.
3. Wait a suitable amount of time (say, 2-4 weeks) for quick bugfix patches to be released. Then review the game at that time. The problem here is that your (non-existent) review is useless to people who want to buy the game at launch, and by the time you release it few people will be interested in reading it because they have already read your competitors' reviews or even bought the game themselves.
I find it hard to really fault Polygon here, as they are choosing one of several imperfect solutions. At least they are going back and re-reviewing the game, which is probably more than most outlets will do.