jaipilot-generate-testslisted

# Add meaningful Java tests Tests should exercise useful contracts, not inflate a score. Use the user's requested class, package, module, behavior, or coverage scope; do not silently expand a bounded request into a repository-wide campaign. ## Establish the scope 1. Confirm the selected root is a Java Maven or Gradle repository. Otherwise report that this skill is not applicable and stop. 2. Read repository instructions, build files, existing tests, fixtures, production contracts, source sets, profiles, and test conventions. Record Git status and preserve unrelated work. 3. Identify the production classes and useful cases in scope: normal inputs, nulls, boundaries, errors, ordering, identity, state transitions, transactions, serialization, security, concurrency, and framework lifecycle where relevant. 4. For collection transformations, assess empty input, duplicates and multiplicity, null containers and elements, encounter order, locale or normalization, mutable inputs, and missing values. 5. Inspect JaCoCo or PIT declarations, executions, profiles, and lifecycle bindings. A report goal bound to `package` or `verify` is configured even when `test` emits no report. Only after this inspection may configured evidence be called unavailable; never use stale reports. 6. Run the existing focused tests before editing tests. Record existing failures without weakening tests, build gates, dependencies, exclusions, suppressions, or timeouts. ## Add tests 1. F