SCMU fails to start when there is an instance with corrupt XML configuration files. - #5684

Draft

soujay wants to merge 15 commits into

scmu-corrupt-xml-config

Commits on Aug 1, 2026

gracefully handle the configuration file error
soujay
committed
8689b1f
refresh existing instances
soujay
committed
d9baf1e

Commits on Aug 2, 2026

remove temp logging code
soujay
committed
4687b13
remove logging of xml config error
soujay
committed
184978e
remove unsed log code
soujay
committed
757df2d

Commits on Aug 4, 2026

Add spec and executable spec tests for corrupt instance configuration handling
Christian
committed
53ce8b4

Commits on Aug 5, 2026

Rule 1: never silently skip an instance that fails to load
Christian
committed
860b773
Rule 1: protect monitoring instances from corrupt configs like the other types
Christian
committed
d3ef0d6
Rule 2: error banners name the config file that needs fixing
Christian
committed
f536887
Rule 4: refresh rejects an update from an instance of a different type
Christian
committed
f027f58
Rule 5: make the list-level banner logic testable via an instances-source seam
Christian
committed
34457fb
Rule 5: show the configuration error summary banner above the instance list
Christian
committed
d0a078f
Rule 4: cover both refresh directions through the real UI flows
Christian
committed
4a009f4
Add manual test plan covering what the executable spec cannot reach
Christian
committed
ee3bc3c
Add vocabulary section to the spec
Christian
committed
27acee8