fix: resolve Playwright E2E CI failures

Two root causes:

1. FloatingWidget not enqueued in CI: The enqueue_assets() method
   guarded on function_exists('wp_ai_client_prompt'), which failed
   in the wp-env environment before the compat layer could define it.
   The floating widget UI (FAB + panel) does not need the AI client
   to render — remove the guard. Provider availability is enforced
   at message-send time via the REST API.

2. Session management tests timing out: Tests submitted a message
   and waited for the send button to reappear (sending=false), which
   requires the background job to complete. In CI without an AI
   provider, the loopback worker never runs and the job stays in
   'processing' state indefinitely.

   Fix: wait for the stop button (sending=true, immediate) instead
   of the send button (sending=false, requires job completion).
   Also call fetchSessions() immediately after session creation so
   the sidebar reflects the new session even when the job never
   completes.

Author: superdav42

includes/Admin/FloatingWidget.php

@@ -43,10 +43,9 @@ public static function enqueue_assets( string $hook_suffix ): void {
 			return;
 		}
 
-		// Require the AI client.
-		if ( ! function_exists( 'wp_ai_client_prompt' ) ) {
-			return;
-		}
+		// Note: wp_ai_client_prompt() availability is NOT checked here.
+		// The floating widget UI (FAB + panel) renders independently of the AI
+		// client. The REST API handles provider availability at message-send time.
 
 		$asset_file = GRATIS_AI_AGENT_DIR . '/build/floating-widget.asset.php';
 

src/store/index.js

@@ -1230,6 +1230,10 @@ const actions = {
 						select.getCurrentSessionMessages(),
 						[]
 					);
+					// Refresh the sidebar immediately so the new session appears
+					// even if the subsequent run job never completes (e.g. no AI
+					// provider configured in the test environment).
+					dispatch.fetchSessions();
 				} catch {
 					dispatch.appendMessage( {
 						role: 'system',

tests/e2e/admin-page.spec.js

@@ -13,6 +13,7 @@ const {
 	goToAgentPage,
 	getMessageInput,
 	getSendButton,
+	getStopButton,
 	getChatPanel,
 	getMessageList,
 } = require( './utils/wp-admin' );
@@ -107,13 +108,15 @@ test.describe( 'Admin Page - Session Management', () => {
 		await input.fill( 'Test message' );
 		await input.press( 'Enter' );
 
-		// Wait for input to clear (message submitted).
+		// Wait for input to clear (message submitted synchronously).
 		await expect( input ).toHaveValue( '' );
 
-		// Wait for the send/stop cycle to complete before clicking New Chat.
-		// The send button replaces the stop button when sending=false.
-		const sendButton = getSendButton( page );
-		await expect( sendButton ).toBeVisible( { timeout: 15_000 } );
+		// Wait for the stop button to appear — this confirms sending=true and
+		// that the session was created. We do NOT wait for the send button to
+		// reappear because the background job may not complete in CI (no AI
+		// provider configured). New Chat works regardless of sending state.
+		const stopButton = getStopButton( page );
+		await expect( stopButton ).toBeVisible( { timeout: 10_000 } );
 
 		// Click new chat.
 		const newChatButton = page.locator( '.ai-agent-new-chat-btn' );
@@ -131,11 +134,14 @@ test.describe( 'Admin Page - Session Management', () => {
 		await input.fill( 'Create a session' );
 		await input.press( 'Enter' );
 
-		// Wait for the send/stop cycle to complete — the session list refreshes
-		// after the run completes (or errors). The send button reappears when
-		// sending=false, which is when fetchSessions is dispatched.
-		const sendButton = getSendButton( page );
-		await expect( sendButton ).toBeVisible( { timeout: 15_000 } );
+		// Wait for the stop button to appear — this confirms sending=true and
+		// that the session was created via POST /sessions (which happens before
+		// the background job is spawned). The session list is refreshed after
+		// session creation, so the sidebar item should appear shortly after.
+		// We do NOT wait for the send button to reappear because the background
+		// job may not complete in CI (no AI provider configured).
+		const stopButton = getStopButton( page );
+		await expect( stopButton ).toBeVisible( { timeout: 10_000 } );
 
 		// At least one session item should appear in the sidebar.
 		const sessionItems = page.locator( '.ai-agent-session-item' );
@@ -154,10 +160,13 @@ test.describe( 'Admin Page - Keyboard Shortcuts', () => {
 		await input.fill( 'Some text' );
 		await input.press( 'Enter' );
 
-		// Wait for the send/stop cycle to complete before triggering the shortcut.
-		// The send button replaces the stop button when sending=false.
-		const sendButton = getSendButton( page );
-		await expect( sendButton ).toBeVisible( { timeout: 15_000 } );
+		// Wait for the stop button to appear — this confirms sending=true and
+		// that the message was submitted. We do NOT wait for the send button to
+		// reappear because the background job may not complete in CI (no AI
+		// provider configured). The Ctrl+N shortcut works regardless of sending
+		// state.
+		const stopButton = getStopButton( page );
+		await expect( stopButton ).toBeVisible( { timeout: 10_000 } );
 
 		// Trigger new chat shortcut.
 		await page.keyboard.press( 'ControlOrMeta+n' );