amal66 gives Mike a testing safety net
A small change makes future improvements easier to trust before they reach legal teams.
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.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?