v3.0.0

feat!: add lazy Java artifact inspection

v2.3.1

Patch release: method overload support

• extractMethod now accepts optional paramTypes to filter overloads
• Without paramTypes, returns ALL overloads joined by delimiter
• Fix param type parsing (strip variable names, final, annotations)
• Fix generic type matching

v2.3.0

What's Changed

• test: add 189 unit tests across 12 suites and fix 4 production bugs
• ci: add PR testing, improve workflow triggers
• docs: add MCP config examples and troubleshooting section
• feat(locking): add cross-process file locking with proper-lockfile

Full Changelog: v2.2.0...v2.3.0

v2.2.0 — Toon Format, Structured JSON, Method Line Maps

What's New

New Response Formats

• text (default): Human-readable markdown, tables, code blocks
• json: Pure structuredContent — no text wrapper, ideal for programmatic consumption
• toon: Token-Oriented Object Notation via @toon-format/toon — ~40% fewer tokens than JSON, LLM-friendly

Enhanced Tool Responses

• decompile_class: Now includes method line ranges (startLine, endLine, signature) for every method in the decompiled source
• get_inheritance_tree: Each hierarchy entry now has a
  esolved flag — rue if the class was found in indexed dependencies, alse if it's a JDK/system class
• search_class: JSON results no longer include jarPath (only jarName) — less noise, same utility
• scan_dependencies: Removed indexPath from all responses — cache paths are internal implementation detail

Documentation

• Added QUICKSTART.md — 1-page self-contained brief for presentations and onboarding
• Updated README.md with format comparison table
• Listed Codex and Opencode alongside Claude/Cursor as supported MCP clients

Dependencies

• Added @toon-format/toon for TOON encoding

Breaking Changes

• json format no longer includes a content text wrapper — it returns only structuredContent
• indexPath removed from scan_dependencies responses
• jarPath removed from search_class JSON results

v2.1.1

Bug Fix

• fix(cli): Add shebang line (#!/usr/bin/env node) to \cli.ts\ for Windows compatibility

Without the shebang, npm generates Windows .cmd\ wrappers that invoke \cli.js\ directly instead of via
ode, causing Windows Script Host (JScript) to run it and fail with error \800A03EA.

This fixes the issue where the MCP server could not start on Windows via
px\ since v2.1.0.

Release v2.1.0

Use git tag for versioning