amal66 puts Mike's riskiest parts under test

This fork is treating an automated test suite as a shippable feature, not an afterthought.

infrastructuresecurity

amal66 has built up a growing battery of automated checks - past 118 of them - aimed squarely at the places where a legal-AI tool quietly goes wrong. The coverage targets the sensitive edges: encrypted user keys, the tokens that gate secure file downloads, and the routing that decides which AI provider handles a given request, including making sure an unrecognised model fails safely instead of guessing.

The team also reworked how the app starts up so the whole thing can be exercised end-to-end, not just in pieces. The practical payoff is that these tests double as documentation - they pin down how the trickiest helpers are actually meant to behave, so future changes don't silently break them.

So what Anyone weighing a Mike fork for real client work should care: this is the kind of groundwork that separates a demo from something you'd trust in production.

View this fork on GitHub →

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

Commits in this thread

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

SHA	Subject	Author	Date
`16de3244`	test(chapter-11): cover token storage and API-key helpers	Amal	2026-05-24	↗ GitHub
commit body Chapter: 11 - First regression tests. Plain-English map: Add Vitest tests for download tokens, storage-path helpers, and user API-key encryption behavior. Why it matters: These helpers sit near sensitive boundaries. If they regress, users can lose access, leak secrets, or store files in the wrong place. Principle: Test the sharp edges first. Precedent borrowed: The fork report highlighted several forks with meaningful test suites. This starts that same protection around core helper behavior. Upstream base: willchen96/mike@d39f580. Original local commit: 4fdc779.
`e7a09761`	test(chapter-28): add HTTP integration tests around the Express app	Amal	2026-05-24	↗ GitHub
commit body Chapter: 28 - Request-level testing. Plain-English map: Extract an app factory from process startup and add Supertest integration tests that exercise the API through HTTP-style requests. Why it matters: Unit tests protect small functions. Integration tests catch mistakes in route wiring, middleware order, and app startup assumptions. Principle: Test important boundaries at the level where users and clients hit them. Precedent borrowed: The fork report's testing leaders and downstream backend test coverage. Upstream base: willchen96/mike@d39f580. Original local commit: 9549258.
`d2406f43`	test(chapter-36): cover model routing and safe fallbacks	Amal	2026-05-24	↗ GitHub
commit body Chapter: 36 - Provider contract tests. Plain-English map: Add tests that verify known model IDs route to the right provider and unknown model preferences fall back safely. Why it matters: Provider routing mistakes are hard for users to diagnose. They show up only when a chat request hits the wrong external API or an unknown model string. Principle: Provider abstraction needs tests that define its contract. Precedent borrowed: The fork report's alternative-provider cluster. Upstream base: willchen96/mike@d39f580. Original local commit: a706a79.

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

⬇ Download capture-thread-595.md