Failure-layer isolation

Always isolate one failure layer at a time before changing code. Broad refactors look efficient but conflate causes and weaken evidence; directly exercise intermediate artifacts—for example, spawn the .download binary to distinguish delta-patch output failure from spawn or replacement failure—then fix only the proven layer.