anchor.diff:  
   The basic unit in `test161` is a command. such as `lt1` for running Lock Test 1,
   or `sp1` to run the whalemating test.  Information about what to
  -expect when running these commands, as well as what input/ouput they expect
  +expect when running these commands, as well as what input/output they expect
    is specified in the `commands/` directory in your test161 root directory.
   All .tc (test command) file in this directory will be loaded and commands must
   only be specified once.
  
positive.code: * Environment inference with environment variable overrides, similar to the test161 client
  ** `test161-server config` to both show the configuration and modify it
  * Log the configuration on startup
  * More usablility cleanup
  ** Usage
  ** Help
  ** Bash completion
  
negative.code: * Order the test output in some meaningful way, probably by depth in the
  dependency graph. (That way all skipped tests should be shown last.)
  ** Not necessarily true. You could have a long, unrelated branch that
  succeeds (even leaf nodes), but some unrelated dependency fails early. I made the
  default print order topological sort, but it's still confusing. I added the
  reason a test is skipped, which helps. Maybe a nice ASCII art tree would work here...
  * Check for repository problems:
  