[ci] CI/CD Pipeline with GitHub Actions

[josueazc]

DESCRIPTION

There is no automated CI/CD pipeline. Every PR is currently merged without automated lint, type-check, or build verification. As external contributors start landing PRs, broken code can reach main undetected. This task adds a GitHub Actions workflow that runs on every PR and push to main across the full monorepo (frontend, backend, and Rust contracts).

GOAL

Every PR triggers an automated workflow that lints, type-checks, and builds all apps. Failing checks block merges, preventing broken code from reaching main and giving external contributors fast feedback.

REQUIREMENTS

• .github/workflows/ci.yml triggered on push to main and pull_request to main
• Jobs: lint (ESLint), typecheck (tsc --noEmit), build (Next.js + NestJS)
• Rust job: cargo check + cargo test inside contracts/velar-bond/
• Node 22 required (Supabase client fails on Node 20 — documented in README)
• Cache node_modules (via actions/setup-node cache) and the cargo registry between runs
• Workflow status badge added to the README

ACCEPTANCE CRITERIA

• Opening a PR triggers the CI workflow
• A PR with a TypeScript error fails the typecheck job
• A PR with a Rust error fails the cargo check job
• CI passes on a clean checkout of main
• README shows the workflow status badge
• Work follows Velar monorepo structure
• Can be reviewed by the team via a clean PR with description

NOTES

Relevant files: .github/workflows/ (new), package.json (lint/build scripts), contracts/velar-bond/Cargo.toml. Use actions/setup-node@v4 with node-version: 22 and actions-rs/toolchain for Rust. Good starting point: GitHub's starter workflow for Node.js monorepos.

---

Difficulty: Intermediate
Priority: High

[Musab1258]

I have strong experience building CI/CD pipelines with GitHub Actions for
complex monorepos that combine TypeScript and Rust environments. To tackle this,
I will create a workflow triggered on PRs and pushes to main that enforces the
strict Node 22 requirement using actions/setup-node@v4 and caches dependencies
for the Next.js and NestJS apps. Concurrently, I will configure
actions-rs/toolchain with cargo caching to reliably execute cargo check and test
specifically within the contracts/velar-bond/ directory. Finally, I will ensure
these checks block broken merges and update the README with the new workflow
status badge. I am ready to submit a clean, well-documented PR to provide your
contributors with fast and reliable feedback.