fix: lazy-load Playwright to prevent it leaking into check-trigger bu…

[DeDuckProject]

Problem

check-trigger was pulling in require("@playwright/test") even though it never uses Playwright. The root cause was a barrel file chain:

check.ts
  → @git-glimpse/core (barrel index.ts)
    → pipeline.ts
      → playwright-runner.ts  ← static import { chromium } from '@playwright/test'
    → fallback.ts             ← static import { chromium } from '@playwright/test'

esbuild marks @playwright/test as --external, so dist/check.js ended up with a dangling require("@playwright/test") that fails at runtime when Playwright isn't installed. Consumers hit either a runtime error or (worse) an ERESOLVE peer dependency conflict when trying to install Playwright as a workaround.

Fix

Changed static imports of chromium in playwright-runner.ts and fallback.ts to await import('@playwright/test') inside the function body — matching the existing pattern already used for esbuild in config/loader.ts.

Type-only imports (import type) remain static since TypeScript/esbuild erases them entirely.

Verification

dist/check.js now has zero references to @playwright/test:

grep 'playwright' packages/action/dist/check.js → 0 matches ✅

Why this is the right design

check-trigger's whole purpose is to be a cheap pre-check that skips heavy dependency installation. Requiring Playwright at load time defeats that entirely.

🤖 Generated with Claude Code