anchor.diff:  * 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
  +* More usability cleanup
   ** Usage
   ** Help
   ** Bash completion
  
positive.code: Test files (`*.t`) are located in the `tests/` directory in your test161 root
  directory. This directory can contain subdirectories to help organize tests.
  Each test consists of one or more commands, and each test can have its own
  `sys161` configuration.  Tests are run in their own sandboxed envrionment, 
  but commands within the test are executed within the same `sys161` session.
  Some tests will consist of multiple commands, and such tests are designed to
  stress test your system.
  
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:
  