fix(bots): revert poetry lock/pyproject churn before author/followup publish

The engineer-bot author run on issue #860 failed at "Open / update fix PR":
publish's leftover safety-net found poetry.lock + pyproject.toml unstaged and
not in the agent's touched_files, so it refused to open the PR — even though the
agent's fix + tests were correct (494 passed).

Root cause: the shared setup-poetry action runs `poetry lock` (to reconcile the
lock with the internal JFrog source it injects), which REWRITES the tracked
poetry.lock / pyproject.toml in the working tree. That churn is harmless for the
5 real-CI consumers of the action (they commit nothing) but poisons the two
engineer-bot workflows, which publish a PR from the working tree.

Fix (engineer-bot side only — leave the shared action untouched): after the
Poetry setup, `git checkout -- poetry.lock pyproject.toml` to drop the churn once
the venv is built, so only the agent's edits remain in the tree at publish time.
Applied to both engineer-bot.yml (author) and engineer-bot-followup.yml.

Signed-off-by: eric-wang-1990 <e.wang@databricks.com>
Co-authored-by: Isaac

Author: eric-wang-1990

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

@@ -94,6 +94,15 @@ jobs:
         with:
           python-version: '3.11'
 
+      # setup-poetry runs `poetry lock` (to reconcile the lock with the internal
+      # JFrog source it injects), which REWRITES tracked poetry.lock / pyproject.toml
+      # in the working tree. The venv is already built, so the tree no longer needs
+      # that churn — revert it, else the followup's fixup commit (or its leftover
+      # check) would sweep up these bot-untouched dirty files. Keep ONLY the
+      # agent's edits in the tree.
+      - name: Revert poetry lock/pyproject churn (keep only the agent's edits)
+        run: git checkout -- poetry.lock pyproject.toml || true
+
       # Shared prelude: mint the engineer-bot token (pushes fixup commits, posts
       # replies) + the engine-scoped token, set up Node, install the engine.
       - name: Bot prelude (tokens + Node + engine install)

.github/workflows/engineer-bot.yml

@@ -81,6 +81,15 @@ jobs:
         with:
           python-version: '3.11'
 
+      # setup-poetry runs `poetry lock` (to reconcile the lock with the internal
+      # JFrog source it injects), which REWRITES tracked poetry.lock / pyproject.toml
+      # in the working tree. The venv is already built, so the tree no longer needs
+      # that churn — revert it, else publish's leftover safety-net sees these
+      # bot-untouched dirty files and refuses to open the PR (they aren't in the
+      # agent's touched_files). Keep ONLY the agent's edits in the tree.
+      - name: Revert poetry lock/pyproject churn (keep only the agent's edits)
+        run: git checkout -- poetry.lock pyproject.toml || true
+
       # Shared prelude: mint the engineer-bot token (pushes the fix branch,
       # comments) + the engine-scoped token, set up Node, install the pinned
       # engine (PAT-free). `token` output is used by the steps below.