fix(bots): bump engine pin to latest main (d9cb1e6); map Feature/Task ⇒ task

The prior pin (d24ca21) used the `enhancement` flow, but engine main has since
renamed it to `task`. Bump the 4-way engine pin to current main HEAD (d9cb1e6)
and update the Type→flow mapping to match the renamed flow:
  Bug ⇒ bug-fix, Task/Feature ⇒ task (was Feature ⇒ enhancement)
Without this, a Feature-typed issue would pass `--flow enhancement`, which the
engine's `choices` no longer accepts (runtime failure). Also handles Task
(previously fell through to config default). SDK/CLI pins unchanged (0.2.102 /
2.1.61, still matching the engine at d9cb1e6). Header + author-run comments
updated to match.

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

Author: eric-wang-1990

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

@@ -105,7 +105,7 @@ jobs:
           # Pinned engine SHA. DUPLICATED in all four bot workflows
           # (engineer-bot{,-followup}.yml, reviewer-bot{,-followup}.yml) — bump
           # them in LOCKSTEP or the bots silently run different engine versions.
-          engine-ref: d24ca2171d191a652a67f4f43995f0959c9a5791
+          engine-ref: d9cb1e63dc31eed550194a29d1cfd7de9c9c793b
 
       # 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

@@ -2,8 +2,8 @@
 #
 # A maintainer labels an ISSUE with `engineer-bot`; the bot addresses it and opens
 # a PR. The author FLOW is chosen from the issue's TYPE (a GitHub org-level Issue
-# Type): `Bug` ⇒ bug-fix (reproduce with a failing test, then fix); `Feature` ⇒
-# enhancement (smallest correct change); any other type / none ⇒ the repo's
+# Type): `Bug` ⇒ bug-fix (reproduce with a failing test, then fix); `Task`/`Feature`
+# ⇒ task (smallest correct change); any other type / none ⇒ the repo's
 # .bot/config.yaml `flow:` default. Set the Type BEFORE `engineer-bot` — it's read
 # live when the run starts. Driven by the selected flow + this repo's .bot/
 # (config + prompts).
@@ -92,7 +92,7 @@ jobs:
           # Pinned engine SHA. DUPLICATED in all four bot workflows
           # (engineer-bot{,-followup}.yml, reviewer-bot{,-followup}.yml) — bump
           # them in LOCKSTEP or the bots silently run different engine versions.
-          engine-ref: d24ca2171d191a652a67f4f43995f0959c9a5791
+          engine-ref: d9cb1e63dc31eed550194a29d1cfd7de9c9c793b
 
       - name: Resolve issue + gather context
         id: ctx
@@ -134,13 +134,15 @@ jobs:
           # set AFTER this fetch is not seen — set the type BEFORE `engineer-bot`).
           # The type→flow MAPPING is pinned (not "use the type name as the flow")
           # so an arbitrary custom org type can never select an engine flow:
-          #   Bug ⇒ bug-fix (red→green TDD)   Feature ⇒ enhancement (small-change)
-          # Any other type (incl. Task) or no type ⇒ emit nothing ⇒ the author
-          # step omits --flow ⇒ the engine uses .bot/config.yaml `flow:`.
+          #   Bug ⇒ bug-fix (red→green TDD)
+          #   Task/Feature ⇒ task (single-pass, smallest correct change; the engine
+          #     has no separate `enhancement` flow — it was renamed to `task`)
+          # Any other type or no type ⇒ emit nothing ⇒ the author step omits
+          # --flow ⇒ the engine uses .bot/config.yaml `flow:`.
           TYPE="$(jq -r '.type.name // ""' "$RUNNER_TEMP/issue.json")"
           case "$TYPE" in
-            Bug)     echo "flow=bug-fix"     >> "$GITHUB_OUTPUT" ;;
-            Feature) echo "flow=enhancement" >> "$GITHUB_OUTPUT" ;;
+            Bug)          echo "flow=bug-fix" >> "$GITHUB_OUTPUT" ;;
+            Task|Feature) echo "flow=task"    >> "$GITHUB_OUTPUT" ;;
           esac
           DELIM="GHEOF_$(date +%s%N)${RANDOM}"
           if printf '%s' "$TITLE" | grep -qF "$DELIM"; then
@@ -158,7 +160,7 @@ jobs:
         # $GITHUB_ENV (the bot config's author.env_tokens).
         #
         # The author FLOW is chosen from the issue TYPE by the ctx step above
-        # (Bug ⇒ bug-fix, Feature ⇒ enhancement). We pass --flow ONLY when that
+        # (Bug ⇒ bug-fix, Task/Feature ⇒ task). We pass --flow ONLY when that
         # step derived one: an empty --flow would be rejected by the CLI's
         # `choices`, and omitting it lets the engine fall back to the
         # .bot/config.yaml `flow:` default (no/other type, or type-set-late case).

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

@@ -80,7 +80,7 @@ jobs:
           # Pinned engine SHA. DUPLICATED in all four bot workflows
           # (engineer-bot{,-followup}.yml, reviewer-bot{,-followup}.yml) — bump
           # them in LOCKSTEP or the bots silently run different engine versions.
-          engine-ref: d24ca2171d191a652a67f4f43995f0959c9a5791
+          engine-ref: d9cb1e63dc31eed550194a29d1cfd7de9c9c793b
 
       - name: Run reviewer follow-up
         env:

.github/workflows/reviewer-bot.yml

@@ -85,7 +85,7 @@ jobs:
           # Pinned engine SHA. DUPLICATED in all four bot workflows
           # (engineer-bot{,-followup}.yml, reviewer-bot{,-followup}.yml) — bump
           # them in LOCKSTEP or the bots silently run different engine versions.
-          engine-ref: d24ca2171d191a652a67f4f43995f0959c9a5791
+          engine-ref: d9cb1e63dc31eed550194a29d1cfd7de9c9c793b
 
       - name: Resolve trigger inputs
         id: inputs