anchor.diff:  ....
   $ /bin/true
   ....
  +
  +=== [tags]Test Tags
  +Optionally, tests can have one or more tags. `test161` can be invoked to run these tests
  +as a group with `test161 run <tag>`.
   
   === Progress Tracking Using `stat161` Output
   
  
positive.code: also checks to ensure that there are no user cycles generated when we are
  running in kernel mode, which could be caused by a hung progress.
  
  == TODOs
  
  === Nits
  
negative.code:     progress: 60
  ....
  
  == Commands, Tests, and Targets
  
  === [[commands]]Commands
  
  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
   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.
  
  === [[tests]]Tests
  
  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.
  
  === [[targets]]Targets
  
  Target files (*.tt) are located in the `targets/` directory in your test161 root
  directory. Targets specify which tests are run for each assignment, and
  how the scoring is distributed. When you `test161 submit` your assignments, you will
  specify which target to submit to.
  
  == Features
  
  === Testfile Syntactic Sugar
  