jaipilot-optimize-javalisted

# Optimize one bounded Java change Produce the smallest coherent improvement the repository can prove. "Optimize" means evaluating the applicable passes below; it does not require an edit in every pass or justify unrelated work. Prefer no production change to a plausible change with incomplete proof. ## Establish the boundary 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, contribution guidance, build files, supported runtimes, affected modules, tests, profiles, generated-source rules, and public API policy. 3. Record the current revision, comparison base, `git status --short`, tracked diff, and relevant untracked files. Never fetch, switch branches, reset, clean, stash, or overwrite unrelated work. 4. Use the user's explicit scope. Otherwise use the current Java/build diff when one exists; do not silently turn a changed-code request into a repository-wide rewrite. 5. Define the downstream-consumer boundary, expected contract, and normal clean verification. Record known pre-existing failures instead of attributing them to the candidate. ## Evaluate the passes in order 1. **Remove and simplify.** Use the unused and consolidation modes of the `jaipilot-clean-java` skill. Remove only repository-proven waste. Reduce real decisions, concepts, duplication, indirection, and generated-looking ceremony without moving complexity elsewhere or erasing