So Scott, i finally have a response and after consultation and weeks of debugging assuming i was doing something wrong for something that is so simple,
i am asked (by adobe) to avoid using @reference in abstract classes , and this worked on 6.2 and is something that breaks in 6.4, , with bunch of scr annotation errors and components appear to be in satisfied state
Infact abstract keyword for a service at times sets the component to state "16", solution - remove abstract keyword
If you have nested inheritance and a class that is abstract and implement workflowprocess, keep it simple, take off abstract keyword and avoid inheritance since if a child class(extending parent class that implements workflow process) is invoked the annotations of the parent class is null, so just keep child class that implements workflowprocess and avoid inheritance where the parent class uses annotation and no abstract keyword.
https://forums.adobe.com/thread/2461255