Bug: API Doc - Parser not parsing abstract class docblocks

Problem Statement

The API documentation generator in Hazaar is able to parse the docblock comments at the start of a class, but it fails to do so when the class is declared as abstract. This inconsistency leads to incomplete documentation for abstract classes, which are often used to define common functionality and interfaces.

Steps to Reproduce

1. Create an abstract class in the codebase with a docblock comment at the beginning.
2. Run the API documentation generator.
3. Observe that the abstract class’s docblock comment is not parsed or included in the generated documentation.

Expected Behavior

• The API documentation generator should correctly parse and include the docblock comment for both concrete and abstract classes.

Actual Behavior

• While the generator successfully parses the docblock comment for concrete classes, it fails to process or include the docblock comment for abstract classes.

Benefits and Risks

Benefits

• Resolving this issue will ensure comprehensive documentation that includes all class types, enhancing the utility and accuracy of the generated API documentation.
• Developers will have complete and consistent documentation for both abstract and concrete classes.

Risks

• Adjustments to the parsing logic may affect existing functionality; careful testing is required to ensure no regressions occur in other parts of the documentation generator.

Proposed Solution

1. Update the parsing logic in the API documentation generator to recognize and process docblock comments for abstract classes.
2. Test the changes across various class types to ensure that both abstract and concrete classes are documented correctly.
3. Update documentation and examples to reflect the improved handling of abstract classes.