Four hundred lines in thirty seconds

At the bottom of every plan is a line like Plan: 6 to add, 9 to change, 6 to destroy. It is the only aggregate the tool gives you, it is genuinely useful, and it does not tell you what you need to know.

A replacement counts as one add and one destroy. So does a resource you deliberately removed and a resource you deliberately added. 6 to add, 6 to destroy is consistent with six replacements, six deliberate swaps, or any mixture — and the difference between those is the difference between a routine deploy and an outage.

What the summary does do is tell you whether to slow down. Any non-zero destroy count is a reason to read the blocks.

The gutter is three characters wide and every line has one. Scanning it is a fundamentally different operation from reading the plan: you are looking for a shape, not parsing a sentence, and it works at a speed reading does not.

-/+ and +/- are the only shapes that matter on the first pass. + on its own is a resource being added, which is usually what you asked for. ~ is the majority of the document and can be ignored entirely until the second pass.

The obvious improvement to this exercise is a button that shows only the replacements. It would take an afternoon and it would destroy the skill it appears to support, because the skill is finding them in a document that does not help you.

Your terminal has no such button. Neither does your pull request. The plan a colleague pastes into a chat window has no such button. If the only place you can find a replacement quickly is a website that marks them for you, you have learnt the website.

So: no filter, no count above the fold, no jump-to-next, nothing highlighted. The plans here are long and dull on purpose, and the drills are graded on what you find in them.