Outline: (1) goal and the two modules; (2) clean architecture and parsers; (3) controller (interface); (4) service skeleton; (5) containerization; (6) repository: JPA, Flyway; (7) run, verify, pitfalls.
Stress that business rules never see JSON or JPA annotations: that is the decoupling Clean Architecture asks for.
In hands-on 3 this interface gains POST /accounts/login, which the auth service calls to check an email and a password.
Name format: V<version>__<description>.sql. A new change is a new script, never an edit of an applied one.
The simulator opens on the lab's endpoints; play or → sends them one by one.