test: make the suites pass wherever they are run, and track the statute service

↗ view on GitHub · Ethan Ward · 2026-08-19 · 46b73752

All three failing backend tests and the whole frontend suite were failing on
the surroundings rather than the code. Run inside the deployed container, the
frontend tests picked up the live server address and React was in its release
build, which leaves out the helper needed to render a component in a test.
The backend tests read a signing key that the deployment happens to set. Each
suite now supplies what it needs instead of trusting whatever is already
there, so a plain test run passes on a laptop and on the server alike.

One backend test also insisted the default model was Gemini. That choice has
already moved once and will move again; it now checks what its own name says,
that each default resolves to a provider at all.

The statute and web lookup service, which runs beside the app rather than
inside it, was in no repository and no backup. A copy now lives here so it can
be restored and its history followed. Its settings, including the token, stay
out of the repository.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PoCRDAPyEq4wwBVFFbDzck
Repository wardethan2000-eng/mike
Author Ethan Ward <ethanward321@hotmail.com>
Authored
Parents 0d4423f5
Stats 6 files changed , +638 , -4
Part of Reliable research runs and statute sources

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-46b73752.md from inside the repo you want the change in.

⬇ Download capture-commit-46b73752.md