For real. All the stuff that person complained about is something a manager should be handling. Mine do. It's very rare for requirements to change for things I'm working on. There's typically going to be some small changes, e.g. wording of a message or moving things around in the UI, that happen but that's to be expected and one of the better parts of working in agile. You make something and find it doesn't work as well as you hoped? Tweak it.

I think the only time things can change drastically is when I'm working on a priority event, AKA something really bad happened for a customer and we've got to fix it ASAP. There's no time to do in depth research beforehand. You just dive in and sometimes you think it's one thing but it's really something else or it's just more involved than you thought.

I guess every job I've ever had has been toxic then. Juniors and to some degree mid-levels don't usually have any say in things like when to meet

Nah, I think you're mixing things up here.

"Toxic" is just a label you're putting on everything you don't like and you're also putting a ton of implications behind it.

If Stacy wants a feature, and she's the official representative, I need to clarify what that feature means. A manager can't shield me from having to research the technical implications, that's my job.

Also, you can ignore calls all you want, if there is a genuine need to communicate, you need to have that call at some point. That's actually your first point in the list above.

I think you never worked in a role above code grunt. As a senior developer, my job is to do all what I described above. I need to do all the technical legwork a manager can't. I need to write everything down. I need to get feedback from stakeholders. That's nothing a manager can do and that's nothing a junior can do.

I code something like half an hour a day.