CI runs only Playwright e2e: unit tests, lint, and typecheck never run in CI

[usmanimamu17-create]

Problem

.github/workflows/e2e-tests.yml is the only PR/push workflow, and it runs a single job: npm ci, npx playwright install, npm run test:e2e. The unit suite (vitest, ~20 test files in tests/ and src/), ESLint, and any typecheck never execute in CI. Consequences:

• Red code merges silently: a failing unit test, a lint error, or a type error in an unused module does not block a PR — the e2e suite (which currently exercises only a few journeys) can pass while the unit suite is red.
• The repo's own gates are unenforced: the project ships npm run lint and npm test scripts; nothing runs them automatically, so their value depends on every contributor remembering.
• The companion infra issues (typecheck script, codegen verification) have no home: any "add X to CI" work is unmoored until the CI pipeline is the place where checks run.

Root cause

The CI workflow was added for e2e coverage only (the unit/lint steps either were never added or were removed with the backend CI cleanup).

Why this is architecturally hard

1. Adding unit + lint + typecheck jobs is straightforward, but the ordering and caching matter: npm ci is shared, Playwright browsers are a heavy install that should not run on every job, and vitest/next build can conflict on cache dirs.
2. The e2e workflow currently assumes a running app+backend (the specs hit real routes); a unit/lint job must NOT depend on the backend, so the workflow needs job separation (unit first, e2e after).
3. Deciding the merge gate (required checks) is a repo-administration step; the workflow must be the artifact that makes it possible.

Proposed design

Add unit-test, lint, and typecheck jobs (or steps) to .github/workflows/e2e-tests.yml (or a new ci.yml), run them on every PR and push to main, and document the required-check expectations. Verify the jobs pass on the current tree.

Acceptance criteria

Service

• PRs run unit tests, lint, and typecheck in CI.
• The e2e job runs only after (or independently of) the fast checks.

Tests

• The new workflow file is valid and the fast jobs pass locally.
• A deliberately failing unit test would fail CI (verified once).

Out of scope

OpenAPI codegen verification (open issue #272) and the backend CI.

Getting started

npm test && npm run lint && npx tsc --noEmit

Good first files to read: .github/workflows/e2e-tests.yml, package.json.

[Teejay2696]

@Teejay2696 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Let ne do this now Asap

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Teejay2696 to this issue.

[Johnsource-hub]

@Johnsource-hub has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, kindly assign task. I’m confident I can take ownership of this task and deliver a well-tested solution that meets your expectations.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Johnsource-hub to this issue.

[Dataguru-tech]

@Dataguru-tech has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, I would like to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Dataguru-tech to this issue.

[drips-wave]

Congratulations, @Dataguru-tech! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @Dataguru-tech: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @Dataguru-tech as part of the Stellar Wave Program's 8th Wave 🥳

😎 @Dataguru-tech: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.