Validate post recovery state - Github Codespaces Tutorial

Recovery isn't real unless you can prove it worked. We've rolled the system back to a known good state. That's necessary, but it's not sufficient. In production, nobody cares that you ran a recovery. They care whether the system is actually safe and usable afterward. So, let's get to it. Go to validate.py. Its job is to answer one question clearly. Are we ready to move forward or not? There are three steps to confirm whether or not we're ready to move forward. The first is schema integrity. We confirm the recovered output still matches the structure the rest of the system expects. Recovery that breaks contracts just creates a new failure downstream. Your first task is to add the necessary integrity checks for the schema. And let's find your very first to-do. And here it is starting on line 65, Integrity Checks. And to validate the schema, we'll need to add required top-level fields. And these top-level fields need to map back to this agent summary output base model. So we'll start…