I was thinking about this issue as well, but I haven't figured out anything better, that's why I've described it 'typical'. There is no simple way of how to get such a list without analyzing the ongoing installation in deep details upfront - and such analysis would require to look for yast clients that are going to be called once the user diverges from the simple default workflow.

I see at least two options here:
* to explain in details what a yast client file is, how the checkpoint name is derived from its name, what event is it executed in - but I see all this beyond the scope of this summary and it would take a lot of time to create a comprehensive document with everything clearly explained.

* to put a highlighted notice that this list of checkpoints is really just an example of possible events and let the users/developers ask when their use case does not conform to that list (that's why I put the devel mailing list email below). I think that the number of users that will make use of this feature will be just a few and it will be much easier to target a specific need than to try to cover everything.