DDD4J Javalin Production Hardening

Purpose

Turn a ddd4j-javalin hardening request into an evidence-backed delivery without collapsing review, planning, implementation, CI, publication, and production acceptance into one status.

When to Use

• Reviewing production-readiness gaps across the three Javalin branches (feature/6.7.x, feature/7.1.x, feature/7.2.x) against their line contracts — 6.7.x → Javalin 6.7/ddd4j 1/JDK 17/Maven 3; 7.1.x → Javalin 7.1/ddd4j 2/JDK 17/Maven 3; 7.2.x → Javalin 7.2/ddd4j 3/JDK 21/Maven 4.
• Updating an approved specification or Superpowers plan and then executing it contract-first (TDD), with review, plan approval, and implementation kept as separate states.
• Carrying one approved behavior change across all three maintenance lines while preserving each line's toolchain and Javalin 6/7 API differences.
• Hardening runtime lifecycle, readiness, configuration validation, idempotency, or CORS where evidence tiers must stay separate.
• Inspecting CI on the three branches and executing an explicitly authorized private Maven release with remote-consumer proof.
• Verifying — challenging — claimed evidence without pushing or publishing.

When NOT to Use

Do not use this skill when: