ai: apply changes for #870 (2 review threads)

Addresses:
  - #3600243617 at .github/workflows/engineer-bot.yml:194
  - #3600243618 at .bot/prompts/engineer/system.md:48

Signed-off-by: peco-engineer-bot[bot] <peco-engineer-bot[bot]@users.noreply.github.com>

Author: peco-engineer-bot[bot]

.bot/prompts/engineer/system.md

@@ -45,11 +45,16 @@ server should Y"), do NOT infer the expected behavior from the current connector
 code — that's how a plausible-but-wrong fix gets a test written to agree with it.
 Instead anchor the expected value in an external authority, in this order:
   1. the issue's stated expectation and any spec/PEP (e.g. DB-API) it cites;
-  2. the **reference driver** — for parity questions, `fetch_context_repo
-     databricks-jdbc` then `grep_context_repo` / `read_context_repo` for the
-     class/method the issue names, and mirror how the official JDBC driver behaves
-     (it's the parity ground truth for retry/metadata/type/error semantics). The
-     clone is lazy + read-only; fetch only when you need it.
+  2. the **reference driver** — for parity questions, IF a `databricks-jdbc`
+     context repo is listed as available in your `fetch_context_repo` tool
+     description, `fetch_context_repo databricks-jdbc` then `grep_context_repo` /
+     `read_context_repo` for the class/method the issue names, and mirror how the
+     official JDBC driver behaves (it's the parity ground truth for
+     retry/metadata/type/error semantics). The clone is lazy + read-only; fetch
+     only when you need it. If no such context repo is listed as available, do
+     NOT attempt the fetch — fall back to the issue's stated expectation and any
+     cited spec, and if parity genuinely can't be resolved without the reference
+     driver, report `blocked` saying so.
 Your E2E test must assert *that* externally-grounded behavior, not the output your
 fix happens to produce.
 

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

@@ -99,6 +99,12 @@ jobs:
         uses: ./.github/actions/setup-poetry
         with:
           python-version: '3.11'
+          # Match code-coverage.yml's e2e job: install optional extras (notably
+          # pyarrow, declared optional=true behind the `pyarrow` extra) so the
+          # agent's REQUIRED live E2E repro test runs against the same runtime as
+          # the e2e suite it mirrors. Without this, arrow-touching e2e tests
+          # ModuleNotFoundError/skip instead of failing red-for-the-right-reason.
+          install-args: "--all-extras"
 
       # setup-poetry runs `poetry lock` (to reconcile the lock with the internal
       # JFrog source it injects), which REWRITES tracked poetry.lock / pyproject.toml

.github/workflows/engineer-bot.yml

@@ -80,6 +80,12 @@ jobs:
         uses: ./.github/actions/setup-poetry
         with:
           python-version: '3.11'
+          # Match code-coverage.yml's e2e job: install optional extras (notably
+          # pyarrow, declared optional=true behind the `pyarrow` extra) so the
+          # agent's REQUIRED live E2E repro test runs against the same runtime as
+          # the e2e suite it mirrors. Without this, arrow-touching e2e tests
+          # ModuleNotFoundError/skip instead of failing red-for-the-right-reason.
+          install-args: "--all-extras"
 
       # setup-poetry runs `poetry lock` (to reconcile the lock with the internal
       # JFrog source it injects), which REWRITES tracked poetry.lock / pyproject.toml