Item 8: docs + version 1.4.2

- READMEs: tool count 71 -> 75 (intro, architecture diagram, section
  tables); Analysis section grows to 20 tools with the four new tools
  and the extended analyze_change_impact / analyze_data_flow
  descriptions; LSP comparison gains the reachability and
  affected-tests rows; npm README feature summaries updated.
- CHANGELOG: 1.4.2 entry (reachability graph + three impact
  capabilities, interprocedural data flow, framework extractors, the
  two cap-contract fixes) and compare link.
- Version 1.4.1 -> 1.4.2 via tycho-versions:set-version.

Author: pzalutski-pixel

CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [1.4.2] - 2026-06-10
+
+### Added
+
+- Whole-program reachability graph (built lazily per loaded project, cached until reload) powering three impact-analysis capabilities:
+  - `find_unreachable_code`: project-wide dead code — types, methods, and fields unreachable from any `main` method or test (disabled tests still count as roots; a call through an interface or superclass reaches every override). Results mean "unreachable from declared entry points", not "safe to delete" — reflection/DI entry points are invisible to the graph.
+  - `find_affected_tests`: the test methods (JUnit 4/5, TestNG) that exercise a symbol, directly or transitively through non-test helpers and interface dispatch — the set to run after changing it. Disabled covering tests are flagged.
+  - `analyze_change_impact` gains `transitive=true`: the full reverse closure over the project graph (no depth ceiling, crosses override declarations) as `affectedMethods` + `affectedFiles`. The depth-mode contract is unchanged.
+- `analyze_data_flow` gains opt-in interprocedural tracking (`followCalls`, bounded by `maxCallDepth`): null facts followed through argument-to-parameter hops to dereference sinks in callees, and parameter-taint facts propagated through aliases and concatenation to escape points into non-project callees. May-analysis; returned values are not tracked back.
+- Framework-semantic extractors: `get_jpa_model` (entities with table names, id fields, and relationships — targets resolved through collection type arguments, mappedBy sides) and `get_http_endpoints` (route table with class-prefix/method-path composition for Spring verb shortcuts and JAX-RS). Frameworks absent from the classpath return empty results.
+
+### Fixed
+
+- `get_diagnostics` flagged `truncated` whenever the collected count reached `maxResults`, even when nothing was dropped. The flag now means items were actually dropped.
+- `suggest_imports` overflowed its internal collection budget at `maxResults=Integer.MAX_VALUE` and silently returned nothing.
+
 ## [1.4.1] - 2026-06-09
 
 ### Added
@@ -321,6 +337,7 @@ Initial release of JavaLens MCP Server.
 - Maven and Gradle project support
 - 347 tests
 
+[1.4.2]: https://github.com/pzalutski-pixel/javalens-mcp/compare/v1.4.1...v1.4.2
 [1.4.1]: https://github.com/pzalutski-pixel/javalens-mcp/compare/v1.4.0...v1.4.1
 [1.4.0]: https://github.com/pzalutski-pixel/javalens-mcp/compare/v1.3.6...v1.4.0
 [1.3.6]: https://github.com/pzalutski-pixel/javalens-mcp/compare/v1.3.5...v1.3.6

README.md

@@ -4,7 +4,7 @@
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
 [![Java 21](https://img.shields.io/badge/Java-21-orange.svg)](https://openjdk.org/projects/jdk/21/)
 
-An MCP server providing 71 semantic analysis tools for Java, built directly on Eclipse JDT for compiler-accurate code understanding.
+An MCP server providing 75 semantic analysis tools for Java, built directly on Eclipse JDT for compiler-accurate code understanding.
 
 ## Built for AI Agents
 
@@ -80,6 +80,8 @@ Language Server Protocol was designed for IDE autocomplete and basic navigation
 | Calculate cyclomatic complexity | ❌ | ✅ |
 | Find unused private methods | ❌ | ✅ |
 | Detect possible null pointer bugs | ❌ | ✅ |
+| Project-wide dead-code reachability from entry points | ❌ | ✅ |
+| Find the tests that exercise a symbol, transitively | ❌ | ✅ |
 
 JavaLens wraps **Eclipse JDT Core** directly via OSGi, providing:
 
@@ -232,7 +234,7 @@ These use JDT's unique reference type constants—not available through LSP:
 | `find_type_arguments` | Find all `List<Type>` usages |
 | `find_reflection_usage` | Find `Class.forName()`, `Method.invoke()`, and other reflection calls |
 
-### Analysis (16 tools)
+### Analysis (20 tools)
 
 | Tool | Description |
 |------|-------------|
@@ -243,15 +245,19 @@ These use JDT's unique reference type constants—not available through LSP:
 | `find_field_writes` | Find where fields are mutated |
 | `find_tests` | Discover JUnit/TestNG test methods |
 | `find_unused_code` | Find unused private members |
+| `find_unreachable_code` | Project-wide dead code — members unreachable from any main method or test, over the whole-program call graph |
+| `find_affected_tests` | The tests that exercise a symbol, directly or transitively — the set to run after changing it |
 | `find_possible_bugs` | Detect null risks, empty catches, resource leaks |
 | `get_hover_info` | Get documentation/signature for symbol |
 | `get_javadoc` | Get parsed Javadoc |
 | `get_signature_help` | Get method signature at call site |
 | `get_enclosing_element` | Get containing method/class at position |
-| `analyze_change_impact` | Blast radius — all files and call sites affected by changing a symbol |
-| `analyze_data_flow` | Variable read/write/declaration tracking within a method |
+| `analyze_change_impact` | Blast radius — direct call sites by depth, or the full transitive closure over the project graph (`transitive=true`) |
+| `analyze_data_flow` | Variable read/write/declaration tracking within a method; opt-in `followCalls` tracks null/taint facts across calls to sinks |
 | `analyze_control_flow` | Branching, loops, return/throw points, nesting depth |
 | `get_di_registrations` | Find Spring DI registrations (@Component, @Bean, @Autowired, @Inject) |
+| `get_jpa_model` | Assembled JPA entity model — tables, id fields, relationships with resolved targets and mappedBy sides |
+| `get_http_endpoints` | Assembled HTTP route table — Spring and JAX-RS paths composed from class prefixes, mapped to handler methods |
 
 ### Compound Analysis (4 tools)
 
@@ -437,7 +443,7 @@ Build-system coverage is structured as focused per-bug tests plus realistic end-
 ```mermaid
 flowchart TD
     Client["<b>MCP Client</b>"]
-    MCP["<b>org.javalens.mcp</b><br/>McpProtocolHandler → ToolRegistry → 71 Tools"]
+    MCP["<b>org.javalens.mcp</b><br/>McpProtocolHandler → ToolRegistry → 75 Tools"]
     Core["<b>org.javalens.core</b><br/>JdtServiceImpl → WorkspaceManager, SearchService"]
     JDT["<b>Eclipse JDT Core</b> (via OSGi / Equinox)<br/>IWorkspace, IJavaProject, SearchEngine, ASTParser"]
 

npm/README.md

@@ -4,7 +4,7 @@
 [![npm](https://img.shields.io/npm/v/javalens-mcp.svg)](https://www.npmjs.com/package/javalens-mcp)
 [![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/pzalutski-pixel/javalens-mcp/blob/master/LICENSE)
 
-An MCP server providing **71 semantic analysis tools** for Java, built directly on Eclipse JDT for compiler-accurate code understanding.
+An MCP server providing **75 semantic analysis tools** for Java, built directly on Eclipse JDT for compiler-accurate code understanding.
 
 ## Requirements
 
@@ -54,8 +54,8 @@ Search symbols, go to definition, find references, find implementations, type hi
 ### Fine-Grained Reference Search (9 tools)
 JDT-unique capabilities not available through LSP: find annotation usages, type instantiations, casts, instanceof checks, throws declarations, catch blocks, method references, type arguments, and reflection usage detection.
 
-### Analysis (16 tools)
-Diagnostics, syntax validation, call hierarchy (incoming/outgoing), field write tracking, test discovery, unused code detection, possible bug detection, change impact analysis, data flow analysis, control flow analysis, and Spring DI registration scanning.
+### Analysis (20 tools)
+Diagnostics, syntax validation, call hierarchy (incoming/outgoing), field write tracking, test discovery, unused code detection, project-wide unreachable-code detection over the whole-program call graph, affected-test discovery (which tests exercise a symbol, transitively), possible bug detection, change impact analysis (with a full transitive mode), data flow analysis (with opt-in cross-method null/taint tracking), control flow analysis, Spring DI registration scanning, JPA entity-model assembly, and HTTP route-table assembly (Spring and JAX-RS).
 
 ### Compound Analysis (4 tools)
 Combine multiple queries to reduce round-trips: analyze file, analyze type, analyze method, and type usage summary.

org.javalens.core.tests/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: JavaLens Core Tests
 Bundle-SymbolicName: org.javalens.core.tests
-Bundle-Version: 1.4.1
+Bundle-Version: 1.4.2
 Bundle-Vendor: JavaLens
 Fragment-Host: org.javalens.core;bundle-version="1.3.0"
 Bundle-RequiredExecutionEnvironment: JavaSE-21

org.javalens.core.tests/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>org.javalens</groupId>
         <artifactId>org.javalens.parent</artifactId>
-        <version>1.4.1</version>
+        <version>1.4.2</version>
         <relativePath>../pom.xml</relativePath>
     </parent>
 

org.javalens.core/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: JavaLens Core
 Bundle-SymbolicName: org.javalens.core
-Bundle-Version: 1.4.1
+Bundle-Version: 1.4.2
 Bundle-Vendor: JavaLens
 Bundle-RequiredExecutionEnvironment: JavaSE-21
 Bundle-ActivationPolicy: lazy

org.javalens.core/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>org.javalens</groupId>
         <artifactId>org.javalens.parent</artifactId>
-        <version>1.4.1</version>
+        <version>1.4.2</version>
         <relativePath>../pom.xml</relativePath>
     </parent>
 

org.javalens.launcher/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>org.javalens</groupId>
         <artifactId>org.javalens.parent</artifactId>
-        <version>1.4.1</version>
+        <version>1.4.2</version>
     </parent>
 
     <artifactId>org.javalens.launcher</artifactId>

org.javalens.mcp.tests/META-INF/MANIFEST.MF

@@ -2,7 +2,7 @@ Manifest-Version: 1.0
 Bundle-ManifestVersion: 2
 Bundle-Name: JavaLens MCP Tests
 Bundle-SymbolicName: org.javalens.mcp.tests
-Bundle-Version: 1.4.1
+Bundle-Version: 1.4.2
 Bundle-Vendor: JavaLens
 Fragment-Host: org.javalens.mcp;bundle-version="1.3.0"
 Bundle-RequiredExecutionEnvironment: JavaSE-21

org.javalens.mcp.tests/pom.xml

@@ -7,7 +7,7 @@
     <parent>
         <groupId>org.javalens</groupId>
         <artifactId>org.javalens.parent</artifactId>
-        <version>1.4.1</version>
+        <version>1.4.2</version>
         <relativePath>../pom.xml</relativePath>
     </parent>