fix: increase CI step timeout to 1800s, trim cross-browser test set

- Step timeout 900→1800s to accommodate 34 tests across 5 projects
- Remove test 06 (dashboard pages) from cross-browser specs — each
  subtest creates a wallet context, making 4× browser runs too slow
- Cross-browser now runs 03 (GraphQL verification) + 07 (landing pages)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

.woodpecker/e2e.yml

@@ -405,7 +405,7 @@ steps:
     image: mcr.microsoft.com/playwright:v1.55.1-jammy
     depends_on:
       - wait-for-stack
-    timeout: 900
+    timeout: 1800
     environment:
       STACK_BASE_URL: http://caddy:8081
       STACK_RPC_URL: http://caddy:8081/api/rpc

playwright.config.ts

@@ -9,8 +9,10 @@ import { defineConfig, devices } from '@playwright/test';
  *   and only run read-only / UI-rendering specs (03, 06, 07).
  */
 
-// Read-only specs safe to run in every browser/viewport after chain state exists.
-const CROSS_BROWSER_SPECS = '0[367]-*.spec.ts';
+// Lightweight read-only specs for cross-browser/viewport validation.
+// Test 06 (dashboard pages) is excluded because each subtest creates a wallet
+// context, making it too slow for 4× additional browser runs in CI.
+const CROSS_BROWSER_SPECS = '0[37]-*.spec.ts';
 
 // Chromium-specific launch flags (not valid for Firefox/WebKit).
 const CHROMIUM_ARGS = ['--disable-dev-shm-usage', '--no-sandbox'];