The explainer will draw the edit graph behind DiffCraft: how Myers' greedy search walks the diagonals, why the shortest edit script is also the one a reviewer finds readable, and what the engine does when the edit distance passes its budget. It runs on the same library as the diff checker, so the walk-through can never drift from the real behaviour.
The engine itself is shipped: line alignment with an edit-distance budget, intra-line word and character marking, fold counts for long unchanged runs, and a unified patch that the test suite applies with git apply before every deploy. What is missing is only the visual explanation.