Transition labels should be built-in Workflow itself

Transition labels from POV is important as it should achieve the following :

1. By defining labels will define also what is possible transitions like "Draft->Reviewed", "Reviewed->Checked" and "Checked->Published" only.So transition like "Draft->Published" if not desirable without defining a label for it shouldn't be available.
2. Also the transition labels will be used in "Workflow Edit" rather than see table with rows and columns cout of workflow stats. As for example if the wok flow has 4 stats then a table with 25 cells ((4+1)^2) will be in edit screen and if workflow has 8 stats then a table with 81 CELLS!!! will be there.
3. And more worst in each cell all roles will be there (really Something not desirable).
   But Using labels in workflow with 8 stats (normaly will be in it less than 15 transition) so this will result in table with 2 columns only with 15 rows (Simpler to read and work with).
4. Also in "admin/build/trigger/workflow" Each workflow combination will limited to Transition labels only. Rather than having all possible cases.
   And it will be more readable will contain workflow name and transtion name.
5. The project workflow_named_transitions Should be built-in Workflow itself