What does a change cycle do in a QGM scenario, and how are unfinished transports carried over?

It segments the scenario's lifecycle — completing one lets you open a new one so dev/config continues.

Unfinished transports at cycle end can carry into a new cycle (the tool auto-decouples then reattaches, safeguarded by the deploy-to-scope Q-Gate, which starts a new cycle). The end-of-deployment Q-Gate ends the whole scenario.