fix(qa): use requiredChannelDriver instead of execution.channel pin in goal scenarios

steipete · steipete · commit 818dd18ded6e · 2026-07-05T19:37:45.000-07:00
diff --git a/qa/scenarios/goals/goal-context-next-turn.yaml b/qa/scenarios/goals/goal-context-next-turn.yaml
@@ -24,9 +24,9 @@ scenario:
     - extensions/qa-lab/src/providers/mock-openai/server.ts
   execution:
     kind: flow
-    channel: qa-channel
     summary: Start a goal, send an unrelated next turn, and inspect the exact mock-provider request payload.
     config:
+      requiredChannelDriver: qa-channel
       requiredProviderMode: mock-openai
       conversationId: goal-context-next-turn
       senderId: qa-goal-operator
diff --git a/qa/scenarios/goals/goal-context-survives-compaction.yaml b/qa/scenarios/goals/goal-context-survives-compaction.yaml
@@ -32,9 +32,9 @@ scenario:
     - extensions/qa-lab/src/providers/mock-openai/server.ts
   execution:
     kind: flow
-    channel: qa-channel
     summary: Start a goal, compact the session, then inspect the next mock-provider request for active-goal context.
     config:
+      requiredChannelDriver: qa-channel
       requiredProviderMode: mock-openai
       conversationId: goal-context-compaction
       senderId: qa-goal-operator
diff --git a/qa/scenarios/goals/goal-followthrough-live.yaml b/qa/scenarios/goals/goal-followthrough-live.yaml
@@ -27,9 +27,9 @@ scenario:
     - src/agents/tools/goal-tools.ts
   execution:
     kind: flow
-    channel: qa-channel
     summary: Stage a two-step active goal, then require a bare continue turn to write the next artifact without replanning.
     config:
+      requiredChannelDriver: qa-channel
       conversationId: goal-followthrough-live
       senderId: qa-goal-operator
       artifactFilePrefix: goal-continuance-live
