MILES Pipeline

CI monitor the CI monitor bot's analysis of the job, with its confidence (HIGH MEDIUM LOW), when it has posted one. The rest is read from the job logs and the commits each image build recorded: a failing test is walked back to its last pass, and the commits between the two images are searched. Cause changed the failing test, or a function or line on its traceback · Cause? only touched a file on the traceback, or the workflow / Dockerfile · Fix later commit on the branch the image builds from that changes the same code · Fix? open PR that names the test · status on GitHub: open merged