amal66 gives Mike a testing safety net

A small change makes future improvements easier to trust before they reach legal teams.

infrastructureworkflow

amal66 has put the first basic checks around Mike's backend and interface, giving the project a way to catch breakage before a change is merged.

  • Backend checks now verify core server-side behaviour.
  • Frontend checks now verify key interface utilities.

The setup is deliberately modest: it does not yet automate checks on every proposed change, but it gives later work a stable place to add deeper tests. Just as importantly, the checks are kept out of the production build, so the application can still be prepared for release without pulling test material into that process.

So what Anyone considering Mike for serious legal workflows should care because this is the groundwork for safer, more predictable change.

View this fork on GitHub →

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

Commits in this thread

1 commit from amal66/mike, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
4039b949 test: minimal vitest harness for backend and frontend QA Runner 2026-07-20 ↗ GitHub
commit body
Ported from amal66/mike#24 onto current main; lockfiles regenerated against
this tree. Adds vitest as a dev dependency with a `test` script in both
packages, excludes test files from the backend tsc build, and seeds one
suite per package (backend: downloadTokens, 12 tests; frontend: cn() utils,
8 tests). Verified locally: backend 12/12, frontend 8/8 passing.

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-1347.md from inside the repo you want the changes in.

⬇ Download capture-thread-1347.md