ci: build and test workflow

[amal66]

Summary

Adds .github/workflows/ci.yml — a GitHub Actions workflow adapted from the fork's CI to this repository's backend/ + frontend/ layout. It gates every PR on the backend build today, and its test steps are written to no-op gracefully when the test script or eval harness is absent, so it is safe to merge before or after the test-harness (#43-style) and evals (#45) PRs and starts enforcing them automatically once they land.

Changes

One file, three jobs:

• backend — npm ci, npm test --if-present, npm run build (tsc), with npm cache keyed on backend/package-lock.json
• frontend — npm ci, npm test --if-present
• evals — runs node evals/run.mjs --threshold 1.0 only if [ -f evals/run.mjs ], otherwise prints a skip notice

Triggers: push/pull_request on main only — this matches the fork CI's own scoping exactly, and it means pushing feature branches (including this one) spawns no Actions runs.

Adaptations from the fork's ci.yml (monorepo) to this layout, each flagged:

• Fork's root-workspace npm ci (working-directory: .) → per-package npm ci in backend/ / frontend/ (no root workspace here)
• Fork's npm run test:coverage → npm test --if-present (no coverage ratchet or test script exists here yet; --if-present makes the step merge-order-safe)
• Fork's unconditional node evals/run.mjs --threshold 1.0 → the same command behind a file-existence guard
• Retained verbatim: actions/checkout@v4, actions/setup-node@v4 with node-version: 22 + npm caching, job structure, and the evals job's explanatory comment

Fork jobs deliberately not ported (they depend on rungs that haven't merged or on fork-only infrastructure), noted here as future additions once their pieces land: npm audit --audit-level=high and the built-app smoke import (backend dist/index.js starts a server on import), lint + next build for the web app, monorepo package typecheck/test jobs, python-sdk, Supabase migration validation + deploy jobs, and the separate e2e.yml Playwright workflow (needs the fork's full demo stack).

Why

The extraction ladder ships tests (vitest harness, evals); without CI they are advisory. This workflow makes them enforceable: the backend build gates PRs immediately, and the test/eval steps switch on automatically as those PRs merge — no follow-up CI edit needed.

Testing

No actionlint was available locally (checked brew and npx); instead:

• YAML validated by parsing with the yaml npm package via node -e (parse OK; verified on: triggers, all three jobs, step shapes, working directories)
• Every step simulated locally on this branch's tree (plain upstream layout): backend npm ci + npm test --if-present (no-ops, exit 0) + npm run build (tsc, green); frontend npm ci + npm test --if-present (no-ops, exit 0)
• Evals guard exercised in both states: with evals/ absent it prints the skip notice and exits 0; with evals/ present (checked out from the evals PR branch) it runs the harness and exits 0
• Trigger scoping confirmed: pushing this branch produced no Actions runs

Provenance

All lines are mechanical ports of amal66/mike@origin/main (commit b3166dd); exceptions: the layout adaptations flagged above (per-package npm ci, npm test --if-present in place of test:coverage, the if [ -f evals/run.mjs ] guard and its skip message, and the header/step comments describing this adaptation). No new jobs, actions, or logic beyond what the fork's ci.yml contains.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CEguyEgXa9JjCciXCcVemC