IMO its when you don't understand the codebase and the problems it's dealing that your reviews become trivial and non valuable. You end up focusing on trivialities which don't matter. I became a team lead in my last job and that's exactly what happened to me.
Just as we don't care too much about how AI does the little things, one has to make space for human engineers to be different from each other and from oneself. I felt I wasn't delivering much value by asking "did you use a list comprehension" or even the spotting of small mistakes. The value I needed to bring was a level up - whether the change hangs together logically with the rest of the codebase and whether the tests really test that and how will this fit the requirement or complicate the future.
As a non coding manager I could still program but I really didn't understand the technical problems my team was facing in the codebase until I got in there and learned it by doing work. It was very difficult to do this while doing the management side of things that eat up time - like hiring people or trying to extract the actual requirements from the wider business but in the end I was able to shelve some of that and get back to code which turned out to be essential.
When I understood the technical problems I could plan and make reasonable team lead type decisions. I could also give my management better information too which they obviously didn't like because it was about things like "that's logically nonsensical and therefore technically impossible."