These requests use customer profiles and subscription changes that differ from the worked lessons. Some need another historical version. Others need the existing version to stay open because the changed field is outside the requested history. Read the comparison scope before editing the snapshot.
Every task checks the stored result after execution. When a baseline is supplied, it's recorded before the stated source change; your command must preserve that earlier evidence. The command then repeats to expose duplicate versions caused by an unsafe key or change rule.
Keep source duplicates separate from historical versions: an older raw customer record doesn't justify two current snapshot rows. The final tasks also use NULL transitions and an exact change boundary, where an inclusive valid-to comparison would return both neighboring versions.