reason: Backend pre-development checklist and layered architecture overview for JSP/Servlet/MySQL work.


reason: Backend package layout and responsibility boundaries for controller, service, DAO, entity, filter, and util classes.


reason: Schema, DAO, query, and existing book-module scenario conventions relevant to adding readers.


reason: Service/DAO/controller error-handling conventions for user-facing failures and logging.


reason: Logging boundaries for protected workflows and DAO/service failures.


reason: Backend checks and review expectations for layered feature work.


reason: Frontend pre-development checklist for JSP/CSS work.


reason: JSP and static asset placement conventions for reader-management pages.


reason: JSP fragment, form, table, and reusable UI conventions.


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


reason: JSP/Servlet validation and JavaBean display contracts.


reason: Frontend quality checks for JSP pages and static assets.


reason: Original project requirements listing reader information management as a core module.