reason: Backend architecture and checklist for reviewing Servlet-Service-DAO report changes.


reason: Verify report classes are placed consistently with backend structure.


reason: Review JDBC aggregate queries and DAO boundaries for report data.


reason: Verify servlet/service validation and failure behavior.


reason: Check maintainability, focused tests, and layer boundaries.


reason: Review JSP report page against frontend conventions.


reason: Verify JSP placement and shared layout usage.


reason: Check dashboard cards, tables, and report UI consistency.


reason: Verify servlet-to-JSP request state is explicit and null-safe.


reason: Check UI consistency and responsive/server-rendered page quality.


reason: Reports span DAO, service, servlet, JSP, and permissions.


reason: Original project requirements include reports and statistics expectations.