Does WireDoctor detect all bean cycles?

[ddsha441981]

My app starts fine but I suspect there are circular dependencies resolved by Spring silently. Will WireDoctor find every cycle, including ones that would crash the app?

[ddsha441981]

Honest answer: it finds silently-resolved cycles, not every theoretically possible one. Three cases:

1. Crashing cycles (constructor↔constructor): the app dies with BeanCurrentlyInCreationException before WireDoctor can run — nothing to report, Spring already told you.
2. Silently-resolved cycles (setter injection, proxies): ✅ this is WireDoctor's target. Tarjan SCC on the resolved graph (getDependenciesForBean()) finds cycles that succeed silently and reports them as structural design smells — plus lazySuggestions ranking which @Lazy breaks the most cycles with the smallest blast radius.
3. Early-reference blindspot (allow-circular-references=true): cycles resolved via Spring's 3-level cache (earlySingletonObjects pathway) may not appear in getDependenciesForBean() — only explicit @DependsOn and fully-registered constructor/setter dependencies are captured. Some silently resolved cycles can go unreported.

This is documented in the README's Epistemic Honesty section and KNOWN_ISSUES.md — WireDoctor prefers honest heuristics over false certainty. Practical upshot: pair the cycle report with fail-on=new-cycle in CI so the detectable set at least never grows.