M06-L05 challenge — Correct, verify, and hand off

Starting checkpoint: FAULT-fixture, based on CP06. Suggested time: 60–90 minutes.

Submit a failure report and the smallest justified fix. Preserve the original bad run, identify the intended format, propose competing explanations, and make one controlled correction. Run the original scenario again and a nearby stale/recovery scenario. Attempt the recorded target build and preserve its actual result or open dependency.

Your evidence bundle must include checkpoint/source identity, the fixture diff, original diagnostic/exit, corrected normal replay, stale/recovery replay, build record, and a short handoff. Explain why the nonfinite fixture event still represents a successful execution of a FAULT scenario. Include one documentary hardware fact with its primary source and one physical claim that remains unperformed.

Do not weaken the parser, invent a sensor reading, or change policy to make the terminal look normal. Recover by extracting FAULT-fixture into another folder if the working copy becomes confusing. Keep useful previous work instead of overwriting it.

Use the answer key only after your own attempt. A supplied expected log or an agent's assurance is not a receipt from your machine.