Fix refactor to CI from DEBUG in playwright config

Author: webstackdev

.github/instructions/general.instructions.md

@@ -77,8 +77,8 @@ When a Playwright-native action (e.g., `page.click()`, `page.fill()`, `page.hove
 ## E2E Testing Standards
 
 - **NEVER hard-code content slugs in e2e tests** (e.g., `/articles/typescript-best-practices`, `/services/web-development`). Content can be deleted or renamed. Always dynamically fetch the first available item from listing pages (articles, services, case-studies, etc.) and navigate to it. This prevents test breakage when content changes.
-- **Playwright E2E Tests**: ALWAYS run with `CI=1` environment variable (e.g., `CI=1 npx playwright test`). This prevents the Playwright test runner from launching its own dev server. The user maintains a running dev server for development.
-- **NEVER run the full e2e test suite** unless explicitly requested by the user. The full suite is very resource intensive and takes over 10 minutes to run. Only run specific e2e test files when verification is needed (e.g., `CI=1 npx playwright test test/e2e/specific-file.spec.ts`).
+- **Playwright E2E Tests**: ALWAYS run with `CI=1` and `FORCE_COLOR=1` environment variables (e.g., `CI=1 FORCE_COLOR=1 npx playwright test`). This prevents the Playwright test runner from launching its own dev server. The user maintains a running dev server for development.
+- **NEVER run the full e2e test suite** unless explicitly requested by the user. The full suite is very resource intensive and takes over 10 minutes to run. Only run specific e2e test files when verification is needed (e.g., `CI=1 FORCE_COLOR=1 npx playwright test test/e2e/specific-file.spec.ts`).
 - **NEVER start a dev server yourself**. The user runs their own dev server for development. When you need a dev server running, notify the user instead of starting one.
 
 ### Astro View Transitions Testing

.github/instructions/testing.instructions.md

@@ -14,7 +14,7 @@ applyTo: "**/*.spec.ts"
 ## E2E Testing
 
 - **NEVER hard-code content slugs** - fetch dynamically from listing pages
-- **Always run with `CI=1`** - e.g., `CI=1 npx playwright test test/e2e/file.spec.ts`
+- **Always run with `CI=1` and `FORCE_COLOR=1`** - e.g., `CI=1 FORCE_COLOR=1 npx playwright test test/e2e/file.spec.ts`
 - **NEVER run full e2e suite** unless requested - it takes 10+ minutes
 - **NEVER start dev server** - user maintains running server
 - **Use `BasePage.waitForPageLoad()`** to wait for `astro:page-load` event

playwright.config.ts

@@ -34,15 +34,15 @@ export default defineConfig({
   /* Run tests in files in parallel */
   fullyParallel: true,
   /* Fail the build on CI if you accidentally left test.only in the source code. */
-  forbidOnly: !!process.env['CI'],
+  forbidOnly: !!process.env['GITHUB_ACTIONS'],
   /* Retry on CI only */
-  retries: process.env['CI'] ? 2 : 0,
+  retries: process.env['GITHUB_ACTIONS'] ? 2 : 0,
   /* Opt out of parallel tests on CI. */
-  workers: process.env['CI'] ? 1 : '75%',
+  workers: process.env['GITHUB_ACTIONS'] ? 1 : '75%',
   /* Only run @ready tests in CI, all tests locally */
-  ...(process.env['CI'] ? { grep: /@ready/ } : {}),
+  ...(process.env['GITHUB_ACTIONS'] ? { grep: /@ready/ } : {}),
   /* Reporter to use. See https://playwright.dev/docs/test-reporters */
-  reporter: process.env['CI']
+  reporter: process.env['GITHUB_ACTIONS']
     ? 'github'
     : isCIMode
       ? [