Backend Hardening & TDD Guide

Pause feature work to install a test harness and harden the backend before resuming Lesson 12. This guide replaces “go straight to converter resolver UI” with a 6-phase pass that pays for itself across every subsequent feature.

How to use this guide

Phase order

Top-line decisions (locked)

Known bugs the test suite should land on

These are confirmed in the codebase. Don’t fix them out of order — write the failing test first, then fix.

Estimated effort

8–14 working days end-to-end, heavily front-loaded on Phase A. The harness is the single most leveraged piece of work — Phases B–F are mostly mechanical once it’s right.