jaipilot-remote-javalisted

# Run substantial Java work remotely Use JAIPilot as execution hardware while the host agent retains reasoning, edits, Git, command selection, and user interaction. JAIPilot Remote is not another coding agent. ## Decide whether remote execution helps 1. Read repository instructions, build files, wrappers, modules, toolchain declarations, and required services before selecting a command. 2. Prefer local execution for quick checks. Use remote hardware for long clean builds, broad test suites, mutation testing, static analysis, profiling, benchmarks, or missing local JDK capacity. 3. Keep work local when it needs a corporate VPN/VPC, private artifact repository, internal database, licensed service, hardware peripheral, or secret that is not explicitly available. 4. Tell the user when JAIPilot starts, what state is uploaded, and why offloading is useful. Never claim that remote hardware itself makes a command semantically stronger. ## Prepare the exact working tree 1. Confirm this is a Java Maven or Gradle Git repository. Record `git status --short` and preserve every unrelated change. Never fetch, commit, push, reset, clean, stash, or switch branches merely to use remote hardware. 2. Before the first upload for this repository in the current conversation, show the repository root and explain that tracked plus unignored staged, unstaged, and untracked files will run in a managed workspace with outbound network access; `.git`, ignored build output, and