User Edition APT pinning vs Developer Edition Docker images for repeatable KDE Neon dev with custom Qt PPA

Goal

Create a repeatable KDE Neon development environment that includes a custom Qt build from a third‑party PPA while keeping the Plasma stack stable and reproducible across CI runs.

Constraint

KDE Neon offers two documented paths: pinning the User Edition APT repositories to a specific Plasma release, or using exact‑tag Developer Edition Docker images. Neither path publishes a compatibility matrix for external PPAs, so it is unclear whether adding a custom Qt PPA will break Plasma ABI or introduce version drift when combined with either approach.

Questions

• Does pinning the User Edition repositories allow safe inclusion of a custom Qt PPA without destabilizing Plasma?
• Can a fixed‑digest Developer Edition Docker image be combined with a custom Qt PPA without causing nondeterministic builds?
• Which strategy provides better long‑term repeatability when security updates to the base Ubuntu LTS are required?