amal66 adds a real pre-merge safety net

This fork now checks that both sides of the product can still build before a pull request lands.

workflowinfrastructure

A fast automated review gate now runs on proposed changes and updates to the main line, complementing the slower full product checks already planned. It is aimed at catching the unglamorous failures that otherwise reach the shared branch: broken server builds, type problems and failing tests.

The legal-AI service is installed, tested when tests exist, and checked for a clean build.
The web application is tested when possible and must complete a production build using safe placeholder settings.
Code-style checks run too, but remain advisory while the existing backlog is cleared.
The evaluation suite runs when present and requires a perfect score.

The result is quicker feedback without making incomplete testing work a blocker for every change.

So what Teams considering amal66's fork should care because it is starting to treat reliability as a release discipline, not a last-minute discovery.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

2 commits from amal66/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA	Subject	Author	Date
`7c1b463b`	ci(chapter-12): add automated checks for pull requests	Amal	2026-05-24	↗ GitHub
commit body Chapter: 12 - Continuous integration. Plain-English map: Add a GitHub Actions pipeline for tests, builds, migration checks, and deploy gating. Why it matters: Reviewers should not have to run every check by hand. CI gives maintainers and contributors a shared, repeatable answer about whether a change is ready. Principle: Make correctness checks part of the merge path. Precedent borrowed: Downstream AGPL disclosures and testing-focused forks that added CI around backend and document-processing behavior. Upstream base: willchen96/mike@d39f580. Original local commit: e3d2728.
`b20109ac`	ci: build and test workflow for backend and frontend	QA Runner	2026-07-20	↗ GitHub
commit body Ported from amal66/mike#46 onto current main, extended for this tree: backend job runs npm ci, tests (--if-present, so it is safe to merge in any order relative to the test-harness PR) and tsc build; frontend job runs tests, eslint as an advisory step (main currently carries 23 lint errors - flip to blocking once burned down), and a production next build with placeholder NEXT_PUBLIC_* env (verified locally that the build succeeds and contacts nothing); evals job runs node evals/run.mjs when present, else skips. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-1341.md from inside the repo you want the changes in.

⬇ Download capture-thread-1341.md