nw-tdd-review-enforcement

# TDD Review Enforcement Domain knowledge for reviewing TDD implementations against 5 test design mandates, test budget, 5-phase validation, and external validity. --- ## 5 Test Design Mandates ### Mandate 1: Observable Behavioral Outcomes All assertions validate observable outcomes, never internal structure. Observable: return values from driving ports | state changes via queries | side effects at driven port boundaries | exceptions from public API | business invariants Violations: asserting private fields | verifying internal method call order | inspecting intermediate calculations | checking internal class instantiation Severity: Blocker. Rewrite to assert observable outcomes only. ### Mandate 2: No Domain Layer Unit Tests Zero unit tests of domain entities/value objects/services directly. Test indirectly through application service (driving port) tests. Violations: imports domain entity (Order, Customer) | instantiates value object (Money, Email) | invokes domain service method Exception: complex standalone algorithm with stable public interface (rare). Severity: Blocker. Delete domain tests, add application service test. ### Mandate 3: Test Through Driving Ports All unit tests enter through driving ports (application services, controllers, CLI handlers, event handlers). Never internal classes. Detection: grep for internal imports (`from domain.entity`, `from internal.validator`). Severity: Blocker. Rewrite through driving port. ### Mandate 4: Integration Tes...