Self-repair: let the model fix its own mistakes

Even with a good prompt, the model sometimes writes a slide the compiler rejects: a missing required prop, a card with so much text it overflows at 10pt, a component that doesn't exist. The compiler already describes each problem precisely. That's exactly what a model needs to fix it.

The loop

1. Compile the deck. If there are no problems, you're done.
2. Send the deck and a list of its problems ("Slide 3: <Card> needs a title prop") with repairDeck, written for you.
3. Compile the fixed version.
4. If it has fewer problems, keep it and loop. If not, stop and keep what you had.
5. Never go round more than MAX_REPAIR_ROUNDS times.

Each trip round the loop is a repair round.

Testing it on purpose

A good model often writes a perfect deck, so the repair path might never run while you test. That's why generateDeck accepts an options.compile function. The harness passes one that reports a made-up problem the first time, forcing a repair round. Swapping a dependency like this is a pattern you'll use a lot in module 11.