repair-cases — synthetic before/after repair demonstrations with evidence

Diagnosing failures in code and pipelines requires reproducing the fault, understanding its cause, and showing the fix. This portfolio contains two synthetic before/after cases where faults were intentionally introduced in local code and fixtures. No client system, production data, or commercial website was used.

Case one, silent_pipeline, shows a pipeline completing without an exception but mapping reordered columns by position and misreading changed encoding. Case two, slow_page, contains a local static page with a large hero asset, a blocking script, four font stylesheets, and an injected layout shift; an optimized variant removes the measured bottlenecks.

Each case includes scripts to generate fixtures, run tests, and reproduce the faults and repairs. The PDFs are two-page summaries generated from the same measured evidence. Numbers in the summaries are measurements of these files, not of anyone’s production site. The fixes hold for the fault that was planted here and for the evidence shown alongside it, not as general remedies.

Code: https://www.twine.net/signin