Match assignment sets when importing multiple child workflows
When extending a single-participant import to multiple participants, changing only the creation loop is insufficient. Normalize assignment identities and compare them as a set: unchanged sets and reordered slots should be no-ops, additions should append child workflows atomically…