amal66 puts a fast quality gate in front of changes

A new automated check aims to catch broken releases before they reach the main line of development.

infrastructureworkflow

amal66 has added a quick review-stage gate for proposed changes, complementing a separate, fuller end-to-end check. It runs on proposed changes and updates to the main branch, with the core checks intended to finish in roughly two to three minutes.

Backend checks confirm the service can be built and, where available, run its tests.
Frontend checks confirm the product can be built for release and run available tests.
Code-quality checks are visible but not yet blocking, while the existing backlog is addressed.
Evaluation checks run when the relevant materials are present, testing whether AI outputs meet the repository's stated threshold.

The result is a more reliable baseline: obvious breakage should surface during review rather than after a change lands.

So what Legal teams and product buyers tracking Mike should care because steadier release discipline is a practical signal of whether a fork can be maintained with confidence.

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