reason: Backend architecture and pre-development checklist for JSP/Servlet/MySQL implementation


reason: Expected controller/service/DAO/entity package layout


reason: Schema, JDBC DAO, and migration safety rules for users and system logs


reason: ServiceResult and validation/error behavior for admin workflows


reason: System-log/audit-log behavior and Java logging conventions


reason: Backend quality bar before coding and build checks


reason: Frontend JSP/CSS conventions and checklist


reason: JSP placement and static asset organization


reason: Existing UI patterns for forms, tables, alerts, and navigation


reason: Servlet-to-JSP request attribute and validation contracts


reason: Original project scope and library-management requirements