As we're preparing to ramp up development and onboard new developers, it makes sense to spend some effort improving some development guardrails so that we can move quickly and integrate often while not jeopardizing the stability, correctness, and performance of shadow @ HEAD.

This includes activities such as:

• Ensuring available tests and analyses (e.g. static analysis provided by the compiler in the form of warnings) pass before code is integrated to master
• Improving the coverage, reliability, and speed of such tests and analyses