Detect the constraint causing a score corruption

[rsynek]

Is your feature request related to a problem? Please describe. When the solver hits a score corruption coming from constraints, it's often tedious to minimize the dataset and active constraints to isolate it.

Describe the solution you'd like Imagine hitting a score corruption (e.g. with a TRACKED_FULL_ASSERT mode) and getting the score analysis diff (last state before and after a SC). Instead of trying which constraints (or their combination) create the SC, the diff would already report the suspects.

Moreover, if we can also get the matches, that would simplify even minimizing the dataset.