Full Code Review

DO

1. List all files, by line count and all files by bytes.
2. To figure out what's really going on, visit every single code and test file 1 at the time.
3. READ. REVIEW. CRITICISE. THINK.
4. Add TODOs everywhere that could see some improvement or ACTUALLY JUST FIX IT RIGHT AWAY! Be super nitpicky!
5. MAKE SURE TO VALUE TYPE-SAFETY VERY HIGHLY!

Architect Checklist

For the full checklist of questions to ask per file, load ./references/architect-checklist.md.

Planning Phase

1. Before you start, make sure our repo/git is clean. Run git status, then commit any pending work with a very detailed message.