Use when planning, implementing, auditing, reviewing, or closing a PAW TP final migration to REST API plus SPA/frontend, especially when the user says TP final, final delivery, pass the app to final, replace MVC/JSP with API+SPA, add Jersey/JAX-RS resources, stateless auth, frontend build, routing/state/forms/i18n/testing, Maven/WAR integration, PostgreSQL data preservation, prior-feedback closure, performance/cache, deployment, or delivery readiness.
Use when planning, implementing, auditing, or reviewing PAW Forkd features in a PAW app checkout across TP1, TP2, or TP final; routes by project stage, Maven modules, PAW-Wiki rules, Superpowers workflows, layer-specific skills, and migration skills.
Use when creating, changing, auditing, or reviewing PAW TP final SPA frontend source, routes, API clients, stores/composables, forms, auth state, i18n catalogs, frontend tests, build config, static assets, or context-path/base-path behavior.
Use when creating, changing, auditing, or reviewing PAW Forkd service interfaces, command DTOs, public service contracts, business exceptions, mail service contracts, or API-facing service boundaries across TP1, TP2, and TP final.
Use when creating, changing, auditing, or reviewing PAW Forkd service implementations, business rules, transactions, scheduler jobs, mail rendering/sending, services-layer tests, or service behavior affected by TP2 JPA/TP final API migrations.
Use when creating, changing, auditing, or repairing PAW Forkd blackbox tests, Maven verification gates, test fixtures, HSQLDB/JPA persistence tests, service tests, MVC/security/API tests, template/frontend tests, or test failures.
Use when creating, changing, auditing, or reviewing PAW Forkd webapp controllers, forms, validators, JSP/JSTL views, i18n bundles, Spring Security routes, webapp CSS/JS, uploads, redirects, MVC tests, REST resources, API error mapping, CORS, WAR asset integration, or SPA static-hosting work across TP1 and TP final.
Use when creating, changing, auditing, or reviewing PAW Forkd persistence: TP1 SQL schemas, migrations, JDBC DAO implementations, HSQLDB fixtures, DAO tests, or TPE2/TP2 JPA/Hibernate persistence implementation after migration routing, including data-loss and schema-migration risk.