Shopware 6 with dockware or devenv: which stack should a team standardize on for a reproducible local setup?

Our team is setting up a shared Shopware 6 development environment and needs one repeatable stack that every developer can spin up identically. Two documented options are on the table: dockware, which ships prebuilt Docker images bundling Shopware with its PHP, database, and web server runtime, and the newer devenv-based setup, which uses Nix to declaratively pin tool versions (PHP, Node.js, services) on the host.

The two approaches differ in ways that matter to us. dockware gives container isolation but changes how IDEs, Xdebug, and file syncing behave, while devenv runs tooling natively with pinned versions but reportedly behaves differently on macOS versus Linux, and our Windows developers would need WSL2 either way. We also know PHP and Node version requirements shift between Shopware minor releases, so whatever we pin must survive upgrades.

Beyond the runtime, we plan to pin the Shopware version via Composer constraints and keep .env configuration consistent, since cache handling and feature flags vary by environment.

Which option is the currently recommended path in the official Shopware developer documentation? What are the practical trade-offs for debugging and IDE integration between the two? How should we revalidate the pinned toolchain when upgrading Shopware minor versions?