One trap is to trust it as a means to accomodate unreasonable schedule pressure.

Sure - this thing looks like it works, hell it probably does work, do you really want to launch a probably works product? If your management does - consider shopping around for a raise/promotion under different management. It's never easy to move, but if you're moving on your own terms you can often make the effort worth your while.

Another note: I find the LLMs to be wickedly detail oriented code reviewers - like, they'll point out the tiniest little discrepancies and edge cases, and what they (Claude, at least) report is usually "real." Now, that doesn't mean they find everything that's wrong on the first pass, but once you've addressed everything in the first pass, you can make a second pass, and a third, etc. each time with different focus: documentation complete? implementation functions as intended? technical debt? test coverage? security issues? issues with maintainability? documentation in sync with implementation? specific aspect of implementation functions as intended? etc. - if you address all the findings after each review cycle (and addressing a finding can be clarifying a requirement to relax about certain unimportant aspects...) eventually the findings slow down / only find ridiculously unimportant things.