WireDoctor 1.2.0 — Architectural Boundaries & Dev Feedback

WireDoctor 1.2.0 — Architectural Boundaries & Dev Feedback

✨ New

• Module Boundaries (opt-in). Declare your modules by package prefix and WireDoctor flags every edge that reaches from one module into another module's internal (non-API) package — hidden coupling that compiles fine but quietly erodes modularity. Read from the resolved bean graph; surfaced in the console, in wiredoctor-report.json (boundaryViolations), and a new Boundaries tab in the HTML report. Zero overhead when off.
• boundary-violation CI gate. wiredoctor.fail-on=boundary-violation fails the build on a cross-module violation — no baseline needed, it trips on the current graph the first time one appears. The verdict is also written to wiredoctor-gate.status, so CI can gate even where the JVM exit code is unreliable (e.g. spring-boot:run).
• DevTools restart diff. With spring-boot-devtools on the classpath, each restart logs a one-line diff vs the previous run — new/resolved cycles, new slow beans, startup-time delta, bean-count change — architectural drift caught as you type. Console-only, dev-only.

🔧 Fixed

• Deterministic boundaryViolations ordering — stable order (by module, then bean), so committed reports and build logs no longer reshuffle between runs.
• Publisher metadata — the POM now declares <organization>, so the artifact carries a proper Implementation-Vendor instead of "unknown".

📖 Docs

• Full report tour recaptured from a real, unmodified run of start.spring.io (394 beans, 0 cycles, 3 boundary violations) — view it live: https://ddsha441981.github.io/wiredoctor/sample/v1.2.0/wiredoctor-report.html
• New Module Boundaries guide; updated CI-gating & configuration docs.

✅ Compatibility

Spring Boot 2.7.18 → 4.1.1 × Java 17 / 21 / 25 — 294 tests green.

Maven: io.github.ddsha441981:wiredoctor-autoconfigure:1.2.0 · Docs → https://ddsha441981.github.io/wiredoctor/