feat: support harper-pro distribution in integration tests

[Ethan-Arrowood]

Summary

• integrationTests/fixture.ts: getHarperBinPath() now reads HARPER_DISTRIBUTION env var — defaults to harper, switches to @harperfast/harper-pro (dist/bin/harper.js) when set to harper-pro
• package.json: new test:integration:harper-pro script sets HARPER_DISTRIBUTION=harper-pro so you can run npm run test:integration:harper-pro (or pass a specific file: npm run test:integration:harper-pro -- integrationTests/next-16.pw.ts)
• .github/workflows/integration-tests.yml: split the single integration-tests job into two named jobs (integration-tests-harper, integration-tests-harper-pro) each with their own node-version matrix — 3 Node versions × 2 distributions = 6 runners running in parallel, keeping each runner focused; added a distribution workflow_dispatch input for targeted manual runs; workflow remains disabled (if: false on generate-matrix) while the broader CI fix is in progress

Local usage

# Run all tests with harper (default)
npm run test:integration

# Run a single test file with harper
npm run test:integration -- integrationTests/next-16.pw.ts

# Run all tests with harper-pro
npm run test:integration:harper-pro

# Run a single test file with harper-pro
npm run test:integration:harper-pro -- integrationTests/next-16.pw.ts

# Or set the env var directly
HARPER_DISTRIBUTION=harper-pro npx playwright test --config integrationTests/playwright.config.ts integrationTests/next-16.pw.ts

Test plan

• npm run test:integration resolves to the harper bin (no env var set)
• npm run test:integration:harper-pro resolves to @harperfast/harper-pro/dist/bin/harper.js
• Single-file invocation works for both scripts
• Workflow matrix produces correct artifact name prefixes (harper-logs-harper-* vs harper-logs-harper-pro-*)

🤖 Generated with Claude Code