ITSM task fail due to potentially incorrect verifiers

[YuqiHuai]

Summary

A task from itsm split has 2 verifiers that cannot be satisfied at the same time.

Analysis

task_20251210_205620_593_391f1eff_ad65c160 from itsm has duplicate verifiers and 2 of them are mutually exclusive:

SELECT COUNT(*) FROM incident WHERE incident_id = \"INC_024\" AND configuration_item = \"CI_005\" AND caller_id = \"USER_005\" AND channel = \"phone\" AND status = \"new\" AND category = \"hardware\" AND impact = \"low\" AND urgency = \"high\" AND priority = \"moderate\";

SELECT COUNT(*) FROM incident WHERE incident_id = \"INC_024\" AND configuration_item = \"CI_005\" AND caller_id = \"USER_005\" AND channel = \"chat\" AND status = \"new\" AND category = \"hardware\" AND impact = \"low\" AND urgency = \"high\" AND priority = \"moderate\";

some verifiers check for INC_024 with channel "phone" and some check for INC_024 with channel "chat". A single incident row cannot have channel = "chat" and channel = "phone" simultaneously, and creating a second incident doesn't help since both variants hardcode incident_id = "INC_024" (a second incident would be INC_025, matching neither).