There have been multiple issues because lifecycle events which would allow for forward ports to go forward were missed, sometimes leading to the forward ports being dropped entirely (#766, #1407). The forward port triggers during batch / pr lifecycle being completely ad-hoc is definitely a factor, so would probably be a good idea to formalise the conditions for forward porting, maybe model the logic (quint?), and possibly condense the entire thing into a single location (with a few hooks added onto other objects) so that it can be verified more easily.
There have been multiple issues because lifecycle events which would allow for forward ports to go forward were missed, sometimes leading to the forward ports being dropped entirely (#766, #1407). The forward port triggers during batch / pr lifecycle being completely ad-hoc is definitely a factor, so would probably be a good idea to formalise the conditions for forward porting, maybe model the logic (quint?), and possibly condense the entire thing into a single location (with a few hooks added onto other objects) so that it can be verified more easily.