Git works in your repos, and old engines step aside
In a folder that is already a Git repository the agent can run git again, with Versions still recording. A stuck older engine no longer holds Team.
Git where you already use it
Bandicot keeps every folder's history in Versions. Until now that also meant the agent could not run git anywhere, even in a project you manage with Git. Now git runs in any folder that is already a Git repository, including subfolders and linked worktrees, and Versions keeps recording alongside it.
A folder without Git still keeps its history in Versions alone, and the agent is told to use the Versions tools there.
One engine after an update
When a new build opens, it asks the older engine to hand over your data. An older engine that hands over now stops its Team right away, so the new one can start yours.
An older engine that stops answering is asked to quit after two minutes and is stopped if it still does not answer. Any engine that cannot finish shutting down within 20 seconds now exits, so Team never reports crashes because a previous build is still holding on.
If the previous engine is still letting go of Team when the new one starts, the new one now waits a moment and tries again instead of showing Team as open in another window.