Config change plugins not executed in priority order
Config change plugins not executed in priority order: a task in LegoFlow-SWE (Harbor dataset). Observed behavior When multiple ConfigChangePluginService implementations are registered with distinct order() return values (for example, 0, 1, 2), the actual execution order during configuration…
The task
**Observed behavior** When multiple `ConfigChangePluginService` implementations are registered with distinct `order()` return values (for example, 0, 1, 2), the actual execution order during configuration changes (publish, remove, import, etc.) is **not** guaranteed to follow the priority defined by `order()`.…
Part of Lego-X/LegoFlow-SWE.