anchor.diff:  <moveThreadCount>4</moveThreadCount>
   ----
   +
  -This can be `1` to enforce running the multithreaded code with only 1 move thread.
  +This can be `1` to enforce running the multithreaded code with only 1 move thread
  +(which is less efficient than `NONE`).
   * JavaScript formula: Formula for the number of move threads to run in parallel. It can use the variable ``availableProcessorCount``. For example:
   +
   [source,xml,options="nowrap"]
  
positive.code: </solver>
  ----
  
  The following ``moveThreadCount``s are supported:
  
  * `NONE` (default): Don't run any move threads. Use the single threaded code.
  * ``AUTO``: Let Planner decide how many move threads to run in parallel.
  On machines or containers with little or no CPUs, this can fall back to the single threaded code.
  * Static number: The number of move threads to run in parallel.
  +
  [source,xml,options="nowrap"]
  
negative.code: is still reproducible, unless the `moveThreadCount` is set to `AUTO` or a function of `availableProcessorCount`.
  ====
  
  The `moveThreadBufferSize` power tweaks the number of moves that are selected but won't be foraged.
  Setting it too low reduces performance, but setting it too high too.
  Unless you're deeply familiar with the inner workings of multithreaded solving, don't configure this parameter.
  
  To run in an environment that doesn't like arbitrary thread creation,
  