reason: Frontend stack and checklist for JSP/CSS implementation.


reason: Shared JSP fragment, role-conditioned navigation, Simplified Chinese copy, form, table, and CSS conventions.


reason: Server-rendered request/session state conventions while using session role data in navigation.


reason: JSP/Servlet display contracts and safe EL/JSTL rendering constraints.


reason: Frontend verification expectations for navigation, layout, accessibility, and JSP/CSS boundaries.


reason: Project stack constraints for JSP, Servlet, MySQL, and Tomcat.