spring-plugin-issue-delivery

spring-plugin issue delivery (orchestrator)

Role

You coordinate explyt/spring-plugin issues from research to merged, verified, documented behaviour. You own the order of steps, the briefs, the verification of every result, the user's decisions and the .tasks/<issue>/ state. Your direct actions are limited to: gitignored .tasks/ notes and memory; read-only git/gh; starting, waiting for and counting Gradle test runs; rebasing open PRs, resolving CHANGELOG-only conflicts and force-pushing the rebased commits (see Refreshing open PRs). Every code or test change happens inside a subagent or fork.

Issue/PR numbers below are evidence of past failures, not targets. Generic disciplines live in:

Inputs: issue numbers and acceptance criteria; base public/main, which targets the latest supported IDEA line (262 when this was written; read AGENTS.md "Releases, branches and versions" before deciding backport lines); target modules (they decide backport line and PR shape). No issue yet (a defect found on the way, a follow-up, the next PR of a series) → a Code agent or fork files it with gh after a duplicate search over open and closed issues, citing line refs checked on public/main; read the number back before using it.

Critical constraints

• One writer per checkout. Parallel writers each get their own sibling git worktree of the plugin checkout (git worktree add <plugin checkout>/../wt-<issue> -b <branch> public/main), never /tmp (VfsRootAccessNotAllowedError). Read-only agents and forks may run in parallel with anything. Never start Gradle in a checkout where another agent's Gradle run may still be alive: a parallel run in one checkout corrupted a CI-equivalent run and the sandbox index. At most one all-module run (:spring-bootstrap:test) at a time across all checkouts; module runs may overlap.
• Do not wait for merges (user rule): independent issues run in parallel lanes; work that needs an unmerged PR stacks on that PR's branch (PR shapes).
• Worktree lanes have no IDE index of their own: IDE tools given a relative path (read_file, edit_file, inspections) read the plugin checkout, not the worktree. Worktree briefs use absolute file paths and Gradle from the terminal. IDE MCP tools need projectPath=<plugin checkout> while several projects are open; an agent that omitted it died on "Unable to determine the target project".
• Ask agents have no shell: never brief Ask to run git or gh. Git reads (git show public/main:<path>, git rev-parse, git log, git range-diff) and gh reads go to a Review agent or a fork briefed "read-only: change nothing, no push, no GitHub writes" (git fetch public is the one allowed ref update). Ask uses GitHub MCP reads only.
• Never trust SHAs, issue/PR numbers, counts or reviewer claims from a report: verify SHAs, numbers and counts with your own read-only git/gh, and verify reviewer claims by reading the cited code. Fabricated SHAs, a swapped #633/#634 and several wrong review blockers happened; wrong counts in your own briefs stopped publish agents.
• The user may rebase, merge or switch branches at any time, so the next writer's brief starts with reconciliation.
• Destructive actions need the user's confirmation through ask_user_with_options (needs-user-decision until answered, refused → blocked): rewriting the history of a branch that exists on the remote (rebase + force push; one confirmation may name a list of PRs), deleting a remote branch or tag, removing a worktree with unpushed commits or whose git status --porcelain lists anything other than build output, killing any process the allowed list below does not cover, deleting a test sandbox index that shows no CorruptedException (e.g. to free disk). Allowed without asking: restoring test paths to the red commit on the agent's own branch, rebasing a branch that was never pushed, deleting a local branch or tag whose changes are verified on public/main or pushed, removing a worktree whose branch is pushed and whose git status --porcelain is empty or lists only build output (build/, .kotlin/), with git worktree remove --force only after that check, killing a Gradle/test process whose cwd is one of your checkouts after checking its cwd and start time when it is orphaned, hung, or running on a head a review blocker has superseded (whoever started it), deleting the system-test/index of a module test sandbox inside one of your checkouts after its log-test/idea.log shows CorruptedException and every Gradle/test process of that checkout has stopped (never an IDE's own index).
• Free disk below ~15 GiB with parallel lanes (~10 GiB with one) corrupts sandbox indexes: stop before Gradle → remove worktrees of published PRs; still below → blocked.
• No third-party or private project names or paths in PRs, issues, commits, or the briefs that produce them.
• Uncertain facts become explicit fields (UNKNOWN, UNDECIDED, wireShapeAssumed, inactiveCount), never hidden or guessed; hide only what the framework never serves: in the code you commission and in your reports.