Follow-up to #60, whose container setup script leaves out three tools the agents image may still want.
What to build
- kotlin-lsp and jdtls: the estate is largely Kotlin, so Agent Sessions lose code intelligence without them. Neither publishes a Linux artifact at a single pinnable URL. kotlin-lsp ships a
.vsix whose name carries two version numbers, and jdtls milestones carry a build timestamp. Each needs a container: block whose install derives its URL from one Renovate-tracked version, plus a version_command that proves the server, not just a JDK, is present.
- oras: the old runner image used it to fetch the agent-kit runtime-home. Decide whether the agents image still needs runtime-home. If it does, add oras with a pin. If not, record why it was dropped.
Acceptance criteria
Blocked by
Follow-up to #60, whose container setup script leaves out three tools the agents image may still want.
What to build
.vsixwhose name carries two version numbers, and jdtls milestones carry a build timestamp. Each needs acontainer:block whose install derives its URL from one Renovate-tracked version, plus aversion_commandthat proves the server, not just a JDK, is present.Acceptance criteria
setup-container.sh --checkverifies each at its pin.Blocked by