v0.5.9

• stop no longer strands a running LoopTroop it briefly could not reach, leaving it impossible to stop and clean free to delete worktrees it was still using.
• Raising the Node floor no longer requires editing branch protection by hand before the change can merge.
• LoopTroop now builds, packages and installs correctly under npm 12, whose install-script blocking and changed npm pack output silently broke two release checks.
• Automated dependency updates run again, proposed behind a seven-day maturity delay and two days for security advisories, with only non-shipping lint and test tooling allowed to merge itself.
• Dependency pull requests now arrive with their licence notices already regenerated, instead of failing until someone updated the file by hand.

Container image

docker pull looptroopai/looptroop:0.5.9
docker pull ghcr.io/looptroop-ai/looptroop:0.5.9

Both registries serve the same linux/amd64 + linux/arm64 index,
sha256:b081b66d5c8d76b66f5fe5981041264645f2433e98bb0cb622501b130445c37c.

The image ships without OpenCode, so a bare docker run exits at
startup by design — see Run it in a container
for how to point it at a server and reach the interface.