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 variables that may be useful during development testing and
  in advanced and use cases.
  
  * *`TEST161_SERVER`*: This variable allows you to set a custom backend server,
  for example:
  
  [source,bash]
  
negative.code: The ops-class sources create symlinks footnote:[`.root` is in your source
  directory and points to your root directory, `.src` is in your root directory
  and points to your source directory] between your OS/161 source and root
  directories in order to infer your environment, which may not always be what
  you want. To support partial environments where either source or root cannot be
  inferred from the other, or you want to use a specific set of `test161`
  configuration files, you can use `test161 config` to set the test161 directory
  