Now, within the last 6-12 months of AI advancement, I think you could lay off half or even 3/4 of the team if I was explicitly allowed to implement features myself using AI. But that is not the current policy.
As for worries "ending up on a codebase you can't manage without AI" - my personal take is: No, I am not worried. Because going forward AI will always be available in the development workflow. That is my own opinion, not the corporation standpoint, however.
So your AI subscription is basically a subscription to your own code. Are you sure the tokens will always flow for you?
A way bigger problem is a codebase that you can't effectively work on with AI, which is a lot of legacy humanslop. And things that make a codebase more suited for AI, like documentation that provides relevant domain knowledge and context for requirements, automated quality control, and test coverage, also make a codebase easier to work on for a human too.
And that whole "legacy humanslop" paragraph is just stating the obvious with an air of spite towards humans.
People who can't bother to reason get angry when you say "hey, why put all eggs into one basket", episode N. Boring.
It's not even a matter of incompetence, most of the humanslop came from the fact that you could just never implement anything properly in the time you were expected to do it.