reason: Category maintenance must follow backend layer and core module expectations.


reason: Defines book/category data contracts, DAO responsibilities, validation, and DB integrity rules.


reason: Guides safe service errors, field validation, and controller behavior.


reason: Category maintenance is a key book operation and should preserve logging expectations.


reason: Implementation must preserve Servlet-Service-DAO separation and validation checks.


reason: JSP/CSS changes must remain within the server-rendered frontend conventions.


reason: Category pages should reuse existing form, table, empty-state, and navigation patterns.


reason: Check JSP safety, forms, tables, permissions, and accessibility basics.