mcp-java-dev-tools

Create or update deterministic regression plans (`metadata.json`, `contract.json`, `plan.md`) under `.mcpjvm/.../plans/regression`, including ordered trigger steps, optional Watchers for downstream completion checks, and optional external verification for downstream data validity.

Render regression run results from artifacts into deterministic summaries and tables.

Run MCP-first HTTP regression suites (endpoint, service, or API scope) with optional strict probe-hit verification, bounded Watchers for downstream completion checks, and external verification for downstream data validity across HTTP or SQL targets.

Run strict single-line JVM probe verification. Use for line-hit checks, route validation, and fail-closed probe execution.

Manage `.mcpjvm/<project>/projects.json` project context artifacts (read/validate/upsert/list) for runtime contexts, external systems, and health checks.

Create or update deterministic performance plans (`metadata.json`, `contract.json`, `plan.md`) under `.mcpjvm/.../plans/performance`. Use when authoring workload-centric Java performance-suite Artifacts with required strict line-hit verification.

Render performance run results from Artifacts under `.mcpjvm/.../plans/performance/.../runs` into deterministic summaries and threshold tables. Use when summarizing completed Java performance-suite runs.

Run MCP-first Java performance suites with required strict line-hit verification, concurrency-based workload contracts, and deterministic threshold evaluation. Use when executing or reviewing performance-suite Artifacts under `.mcpjvm/.../plans/performance` or execution profiles with `suiteType=performance`.

Export performance execution profiles to runnable workload replay artifacts (ps1, sh). Use for export, share, replay, or handoff of performance execution flows.

Export regression execution profiles to runnable replay artifacts (ps1, sh, postman). Use for export, share, replay, or handoff of regression execution flows.

Manage probe registry configuration (`probe-config.json`): add/update/list probes, validate config, reload runtime state, and generate MCP run snippets.

Create sanitized, reproducible bug/issue reports from session evidence. Use for issue tickets, failure summaries, repro steps, exceptions, or failing endpoints.