KDED phases
kded modules belong to one of three phases: 0, 1, or 2
From the ksmserver README:
The exact way autoloading works is controlled by X-KDE-Kded-phase=, which may be 0, 1 or 2 (the default). Kded phase 0 means the module is always loaded by kded, even outside of KDE session. It should used only by kded modules which must be always running. Kded phase 1 modules are loaded right after kded startup, but only during KDE startup, i.e. it is for modules that are always needed by the KDE session. Phase 2 modules will be loaded later.
093a673f and !35 (merged) drop the second phase as it was not useful.
A few modules still specify phase 2 in their metadata while the rest specifies 1. I could not find any usages of phase 0. That one is questionable in the first place as kded is mostly only relevant together with Plasma. Any project targeting non-Plasma systems should not rely on kded.
With that in mind I'd suggest to drop the whole phases concept