What

Adds full Java/JADX support end-to-end and hardens large-project compilation.

• Upgraded Java extraction from declaration-only to reference-rich graphing:
  • package-aware qualified names
  • overload-safe callable identities
  • imports/calls/inheritance/interface/type-use/access references
  • synthetic lambda/anonymous class units
• Reworked Java AST traversal to an iterative, heap-backed walker (stack-safe on deep/large JADX trees).
• Improved Java import resolution behavior (dotted paths + wildcard handling), while keeping unresolved SDK/lib symbols unresolved (no fake external nodes).
• Updated CLI/help language to reflect Java support.

Why the search/resolution algorithm is different

Java (especially JADX output) has much higher symbol ambiguity and scale than C++/Rust/Python in this workload:

• same short names across many packages,
• heavy overloads,
• wildcard/static imports,
• very large decompiled files/trees.

Because of this, Java resolution now uses a more package/import-aware lookup path and overload-safe identities instead of simple name-only matching.
This improves correctness (fewer false matches/collisions) and keeps traversal/resolution stable on very large Android decompilations.

Type

• Bug fix
• New feature
• MCP tool
• Documentation

Testing

• Tests added/updated
• All tests pass
• Lints pass