fix(bots): move adapter debugger to configuration

skills/scripts/e2e/bot-event-routing-product-flow.mjs

@@ -233,7 +233,12 @@ try {
     .click();
   await page.getByRole("dialog").waitFor({ state: "hidden" });
 
-  await page
+  const adapterConfigCard = page.locator('[data-slot="card"]').filter({
+    has: page.getByText(/Adapter Configuration|适配器配置|アダプター設定/, {
+      exact: true,
+    }),
+  });
+  await adapterConfigCard
     .getByRole("button", {
       name: /Listen for platform events|监听平台事件|プラットフォームイベントを監視/,
     })

skills/skills/langbot-testing/cases/bot-event-routing-product-flow.yaml

@@ -33,14 +33,14 @@ steps:
   - "Confirm the adapter capability summary, friendly event name, target, and route status are visible."
   - "Confirm overlapping routes and unmatched-event fallback behavior are explained before save."
   - "Open Test event route and run a dry-run against the current form."
-  - "Open Platform event debugging and send a real inbound event through the HTTP Bot adapter."
+  - "Open Platform event debugging from Adapter Configuration and send a real inbound event through the HTTP Bot adapter."
   - "Confirm the normalized event, raw event code, payload, and latest discarded route status are visible."
 checks:
   - "UI: A user can choose a channel and add a scenario-labeled behavior during initial Bot creation."
   - "UI: Event routing uses user-facing labels and does not require the raw event name in the primary route card."
   - "UI: Definite route shadowing and unmatched-event fallback behavior are visible without opening raw logs."
   - "UI: Dry-run visibly reports that the route matched the discard processor."
-  - "UI: Adapter event debugging is clearly separate from route preview and starts listening only after the dialog opens."
+  - "UI: Adapter event debugging lives under Adapter Configuration, remains separate from route preview, and starts listening only after the dialog opens."
   - "UI: A real adapter event shows its friendly name, raw code, and normalized event data."
   - "UI: The route card updates to discarded after the real inbound event is handled."
   - "Console: No unexpected frontend errors appear during the flow."