I’m left wondering what the profession is turning into for other people.

All the code I review looks good at first glance and makes shit up as it goes once you read into it more. We use two different HTTP libraries - one sync, one async - in our asynchronous codebase. There's a directory full of unreadable, obsolete markdown files that are essentially used as state. Most of my coworkers don't know what their own code does. The project barely works. There's tons of dead code, including dead broken code. There are barely any tests. Some tests assert true with extra steps. Documentation is full of obsolete implementation details and pointers to files that no longer exist. The README has a list of all the files in the repo at the top of it for some reason.

I will admit that I’m more in the naysayers camp, but perhaps that’s from a fear of losing my livelihood?

People are being laid off because of poor management and a shitty economy. No software devs are losing their jobs because AI replaced them. CEOs are just lying about that because it's convenient. If software devs truly were more effective with these tools, you'd hire more.

Am I predisposed to see how these tools are lacking? Have I not given them a fair chance?

That's up to you to decide. Try using them if you want. But don't force yourself to become obsessed with them. If you find yourself more productive, then that's that. If not, then you don't. It's just a tool, albeit a fallible one.