fix(bots): make engineer poetry install resilient to a stale lock

The engineer author/followup run  to get a test env for
self-verify. Modern poetry refuses install when pyproject.toml has drifted from
poetry.lock ('changed significantly since poetry.lock was last generated') — a
pre-existing repo-maintenance state the bot must not hard-fail on. Fall back to
 + retry on the runner (ephemeral; nothing committed unless the
agent's own fix touches deps). Applied to engineer-bot.yml, -followup, and the
temp e2e workflow.

Co-authored-by: Isaac

Author: eric-wang-1990

.github/workflows/engineer-bot-e2e.yml

@@ -68,7 +68,11 @@ jobs:
       - name: Install connector deps (for pytest self-verify)
         run: |
           python -m pip install --upgrade poetry
-          poetry install --no-interaction
+          poetry install --no-interaction || {
+            echo "::warning::poetry install failed (likely a stale lock); relocking on the runner and retrying."
+            poetry lock --no-interaction
+            poetry install --no-interaction
+          }
 
       - name: Resolve test issue #864 + gather context
         id: ctx

.github/workflows/engineer-bot-followup.yml

@@ -126,9 +126,16 @@ jobs:
       # verified with `poetry run python -m pytest`. Analog of a driver repo's
       # build/restore step.
       - name: Install connector deps (for pytest self-verify)
+        # Resilient to a stale poetry.lock (see engineer-bot.yml): try the locked
+        # install, and if pyproject/lock have drifted, relock on the runner and
+        # retry so the agent still gets a working test env.
         run: |
           python -m pip install --upgrade poetry
-          poetry install --no-interaction
+          poetry install --no-interaction || {
+            echo "::warning::poetry install failed (likely a stale lock); relocking on the runner and retrying."
+            poetry lock --no-interaction
+            poetry install --no-interaction
+          }
 
       # Run the follow-up. Inlines the engine's bot-run env contract for
       # engineer:followup, plus the authenticated push remote bot-run would set

.github/workflows/engineer-bot.yml

@@ -140,9 +140,19 @@ jobs:
       # → static reasoning). This is the Python analog of a driver repo's
       # `dotnet restore` / build step.
       - name: Install connector deps (for pytest self-verify)
+        # Resilient to a stale poetry.lock: modern poetry refuses `install` when
+        # pyproject.toml has drifted from the lock. That's a repo-maintenance
+        # state the bot must not hard-fail on — it just needs a working env to
+        # run tests. So try the locked install first, and if it fails, relock and
+        # retry. (A relock only affects this ephemeral runner; nothing is
+        # committed unless the agent's fix itself touches deps.)
         run: |
           python -m pip install --upgrade poetry
-          poetry install --no-interaction
+          poetry install --no-interaction || {
+            echo "::warning::poetry install failed (likely a stale lock); relocking on the runner and retrying."
+            poetry lock --no-interaction
+            poetry install --no-interaction
+          }
 
       - name: Run author (bug-fix)
         id: author