refs team#41948

refs team#41943

refs team#41943

refs team#41943

refs team#41943

It feels clearer that way, now we acknowledge the old branch purge
script and clarify when the error can occur. We move that to the end
of the playbook so we have a clearer "what do i do" explanation which
assumes people know what's going on.

We're currently hoping that this alert will not fire very often.

refs team#41948

I *always* have to abort and run lsblk anyways, I'm not omniscient.

this improves i/o significantly for solid state devices

A new alert related to this is being created.

refs: #42050

The `config` file does *not* have the full path, actually.

This introduces garbage in pipelines.

this adds some rough notes of stuff I learned when dealing with
team#42052

I also learned some more about how the entire thing works and I hope to
have some time to add additional notes to the reference/design sections

refs team#41943

refs team#41945