How are new workflows or tech changes handled in EndeavorOS?
E.g. I’m used to Fedora where as their technology preferences changed, that was typically handled over various version upgrades.
How does that work here?
e.g.
I install a system pre-pipewire or pre-wayland.
Then pipewire or wayland are the defaults for new installs.
Do I as a user have the option to let those newer technologies automagically become the new defaults just by doing my regular updates?
[ Ignoring filesystems ]
Thanks.
EndeavourOS is basically an easy to use and nice installer for Arch with a selection of packages, it lets you easily start, but it doesn’t handle major changes like that automatically.
It’s your job to maintain, choose if you want to accept given changes introduced in latest iso or not and manually install / configure it.
All power to the user! 
It’ll stay that way now and forever if you really want it to. If a new .iso brings new defaults, EndeavourOS devs have said in the past that they will not change anything like that for the user on an already installed system, so it’s all up to you and you alone if you want to keep what works for you or adopt the new defaults, which means manually changing them. New defaults like that will not be forced upon you in updates, it’s your system, so you are free to use it in the way you want it.
With that said though, I personally think Fedora is a good proving ground for new tech, but I am not yet convinced Wayland on Nvidia is prime time yet, so for me on EndeavourOS, I can stay on Xorg for as long as I want, without any worry that an update will replace it because that’s not how it works over on this Arch side of things. Hope that clears it up a little bit for you.
You’re not alone! 
I mean…Somebody gotta do that first, so kudos to Fedora! 
Me too! Wayland afraid. 
Wayland also sucks on AMD (just not as much as on Nvidya – though everything sucks more with Nvidya).
You can’t even run xeyes in the current year on Wayland!
Typically, there are no automatic (or automagic, for that matter) updates on Arch. You decide what to update and when, and what new software/packages you want to use. In fact, any kind of automation regarding updates is strongly discouraged, since user intervention is often required and automation can cause difficult to predict problems. This is just how Arch works.
Sometimes, though very rarely, old tech gets deprecated and you have to switch to something else. This is not going to happen regarding Xorg vs. Wayland any time soon (or ever, if I were to guess). Pipewire is already the default on EndeavourOS, but you can easily use PulseAudio if you want. If you have a system with PulseAudio, there will be no automatic move towards Pipewire, if you want to switch, you have to do it manually. It’s very easy, though.
The main difference is the release model. Arch and Arch-based distro are on a rolling release model. They get continuous new updates to the system and other software/firmware parts. The new tech gets added to the user system as they get updated and these don’t get trapped behind a major release gate. But these updates are delivered according to what the user has installed initially. And Arch being a rolling release distro it tends to get newer updates than other distributions.
Fedora and many other distributions are on a fixed release cycle. The newer tech gets released with a new major version release of the distribution (Ex: Fedora 34 → 35). Until these distributions do a main or a major version update users can enjoy whatever they have installed with the current version they installed with security updates and bug fixes.
So, compared to a fixed released distro Arch or any other distro based on a rolling release cycle doesn’t have to do a complete system update because the system is always up to date. The user doesn’t have to change anything unless software/firmware or hardware support is deprecated. Rolling release distribution can be used as long as the computer runs without many changes with new updates. Unless the user decides to do a fresh install with the new defaults released with the newest ISO.
Ex: If you want to use PipeWire which is the new default in the new ISO release you can do a fresh install or you already have Arch or enos installed you can just manually install it and replace PulseAudio (it’s not that hard to do).
But with Wayland, I think it has a long way to go to actually compete with X11. If it ever comes close to being on par with X11 within my lifetime I will definitely give it a try but with the current state, I prefer to stick with what I know and works for me.