reason: Backend architecture overview and checklist for JSP/Servlet/MySQL work.


reason: Required package layout and layer boundaries for controllers, services, DAOs, entities, filters, and utilities.


reason: MySQL schema, DAO CRUD, search, permission-code, and test expectations for book/catalog work.


reason: Servlet validation, service failure handling, DAO exception behavior, and safe user-facing errors.


reason: Logging conventions for key operations and failures.


reason: Backend quality gate and layer-boundary constraints.


reason: Frontend architecture overview and checklist for JSP/CSS work.


reason: JSP, fragment, CSS, JS, and image asset placement conventions.


reason: JSP form, table, navigation, and reusable component conventions for catalog/management pages.


reason: Server-rendered request/session/form state conventions.


reason: JSP request attribute and Servlet validation contracts.


reason: Presentation quality checks for JSP/CSS changes.


reason: Original project requirements for book management, catalog search, entities, and layered architecture.