ci: add GitHub Actions workflow (build + core tests, FalkorDB smoke)

[Phoenixrr2113]

Adds the repo's first CI workflow.

Hard gate (build-and-test) — builds all 19 packages (tsc, so it typechecks the monorepo) and runs @codegraph/core (149 tests), which is green without secrets or services.

Non-blocking (integration-smoke) — runs graph + plugin-nlp against FalkorDB service containers in offline mode (CODEGRAPH_EMBEDDING_PROVIDER=none). Marked continue-on-error because the suite has pre-existing failures unrelated to this workflow:

• integration tests need an embedding provider + Voyage/LLM credentials
• a few legacy tests call methods that no longer exist (getAboutEdgesForCodeNode, deleteAboutEdge, getEntityByText)
• 6 packages exit 1 on "No test files found" (need --passWithNoTests)

Once those are triaged, drop continue-on-error and fold the filters into the hard gate.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
v0-landing-page-build	Ready	Preview, Comment, Open in v0	May 29, 2026 2:47pm

[augmentcode]

🤖 Augment PR Summary

Summary: Adds the repo’s first GitHub Actions CI workflow.

Hard gate: build-and-test installs deps, runs Turbo build/typecheck across the monorepo, and runs @codegraph/core unit tests in offline mode (CODEGRAPH_EMBEDDING_PROVIDER=none).

Smoke coverage: Adds a non-blocking integration-smoke job that starts FalkorDB service containers and runs @codegraph/graph + @codegraph/plugin-nlp tests.

Triggering: Runs on pushes and PRs targeting main, plus manual dispatch.

CI hygiene: Uses minimal permissions and concurrency cancellation; the smoke job is marked continue-on-error while the integration suite is triaged.

_{🤖 Was this summary useful? React with 👍 or 👎}

[augmentcode]

Review completed. 2 suggestions posted.

Comment augment review to trigger a new review at any time.

[augmentcode]

.github/workflows/ci.yml:65 — Using falkordb/falkordb:latest makes this job non-reproducible and can start failing if the upstream image changes. Pinning to a specific version/digest would make the smoke test more stable.

Severity: medium

Other Locations

• .github/workflows/ci.yml:74

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}

[augmentcode]

.github/workflows/ci.yml:30 — These actions are referenced by floating tags (e.g., @v4), which are mutable and can change behavior without changes in this repo. If supply-chain hardening matters for this CI, consider pinning actions to a commit SHA.

Severity: low

Other Locations

• .github/workflows/ci.yml:33
• .github/workflows/ci.yml:36
• .github/workflows/ci.yml:83
• .github/workflows/ci.yml:86
• .github/workflows/ci.yml:89

_{🤖 Was this useful? React with 👍 or 👎, or 🚀 if it prevented an incident/outage.}