reason: Backend checklist and architecture expectations for verifying the reader-management slice.


reason: Schema, DAO, service, permission, and test expectations to check against.


reason: Verify controller/service/DAO failures are handled consistently.


reason: Verify server-side failure logging and protected workflow logging expectations.


reason: Backend quality gate and review checklist.


reason: Frontend checklist for JSP/CSS verification.


reason: Verify reader JSP forms/tables follow local component conventions.


reason: Verify request/session/form state handling remains server-rendered.


reason: Verify JSP/Servlet validation and display contracts.


reason: Verify implemented reader management satisfies the original project requirement.