fix(e2e): 50s timeout on TFJS-dependent waitFor (SwiftShader still slow in CI)

Author: stephenliang

e2e/play-again.spec.ts

@@ -19,7 +19,8 @@ test.describe('Play again', () => {
 
   test('completing the last mode shows the play-again screen', async ({page}) => {
     const continueBtn = page.getByRole('button', {name: 'Continue'}).first();
-    await continueBtn.waitFor({state: 'visible'});
+    // TFJS model load in CI (SwiftShader, no GPU) can take 30-40s.
+    await continueBtn.waitFor({state: 'visible', timeout: 50_000});
     await continueBtn.click();
 
     await expect(page.getByTestId('play-again-screen')).toBeVisible();
@@ -28,7 +29,8 @@ test.describe('Play again', () => {
 
   test('play-again resets progress and returns to step 0', async ({page}) => {
     const continueBtn = page.getByRole('button', {name: 'Continue'}).first();
-    await continueBtn.waitFor({state: 'visible'});
+    // TFJS model load in CI (SwiftShader, no GPU) can take 30-40s.
+    await continueBtn.waitFor({state: 'visible', timeout: 50_000});
     await continueBtn.click();
 
     await page.getByTestId('play-again-btn').click();

e2e/progress-bar.spec.ts

@@ -57,7 +57,7 @@ test.describe('Progress bar — onContinue integration', () => {
   test('completing a mode marks it done and advances to the next step', async ({page}) => {
     await page.goto('/');
     const continueBtn = page.getByRole('button', {name: 'Continue'}).first();
-    await continueBtn.waitFor({state: 'visible'});
+    await continueBtn.waitFor({state: 'visible', timeout: 50_000});
     await continueBtn.click();
 
     await expect(page.getByTestId('step-0')).toHaveAttribute('data-state', 'completed');