There are still a few ways that the proof might be incorrect. Of these, the most likely is that the proof was generated by a misaligned AI system that found and intentionally exploited a lean bug in order to fool its human evaluators (i.e. shades of the HuggingFace attack). I personally don't think this is very likely, but you'd have to understand a bit more about the agent systems used in generating the proof to come up with a more informed estimate.
Another possibility is that an aligned system came up with a plausible but incorrect idea along the way, and simultaneously stumbled across a lean bug that led to an incorrect verification of this idea. I'd put the likelihood here as vanishingly small due to the requirement of serendipitous factors, but it's nonzero.
You could also ask whether an aligned AI system could "p-hack" its way into finding a serendipitous lean bug by trying a large number of approaches. I think this is also vanishingly unlikely because the AI system is trained on and therefore "thinking in" natural language, and presumably only translating results into lean after it believes them to be correct.
And of course there's the possibility that the lean proof isn't faithful to the natural language description we've been given, but that is ruled out in this case due to the use of the canonical problem statement in mathlib. Otherwise, this would certainly seem like the most likely way the proof could be incorrect.
How exactly do any of these weirdly misinformed what-ifs help us? Do you have any evidence of such lean bugs?
> There are still a few ways that the proof might be incorrect
I hear there's a teapot kicking around between us and Mars, too
For the other readers: the above are the random thoughts of a guy on the internet.
The experts in computer proofs are quite satisfied.
Regarding bugs in lean; the proof has been tested on multiple independent lean implementations.
They would all have to have the same bug.
This is considered very unlikely for good reasons.