TDD CI — Promote Tests to GitHub Actions (Phase 3)

Once a slice is green locally, make its tests run automatically in CI. This is the enterprise step that turns "passes on my machine" into "the team's main branch is protected by these tests." Keep it a deliberate, separate phase: CI config is infrastructure and deserves its own review.

For the anatomy of a workflow, caching, Playwright-in-CI specifics, and branch-protection guidance, read references/github-actions-guide.md. Ready-to-customise templates are in assets/workflows/.

Confirm exact, current actions/* versions and runner images with find-docs/ctx7 — action major versions move.

Preconditions

• The slice's full suite (unit + e2e) passes locally first. Do not promote red or unrun tests to CI.
• A git remote on GitHub exists (git remote -v). If not, tell the user CI will only take effect once the repo is pushed to GitHub; still write the workflow so it's ready.

Procedure

1. Detect the stack, the project directory, and the test commands. Reuse the detection from red-green-refactor's references/test-strategy.md: the unit runner + command, and whether the outer loop is a Playwright e2e suite (web) or an integration test (CLI / HTTP API / service). Read the plan's Project directory field — if the app lives in a subfolder, the workflow must run there (see step 3). Use the project's own scripts (package.json, Makefile) as the source of truth for how tests are invoked.