message: [Docs] Remove reproducers from the project page.
  Jim pointed out that this was still open on the website.
diff: @@ -291,21 +291,6 @@ state at StopPoint 0, StopPoint 1, etc. These could then be used for testing
  reactions to complex threading problems & the like, and also for simulating
  hard-to-test environments (like bare board debugging).
  -A Bug-Trapper infrastructure
  -----------------------------
  -
  -We very often have bugs that can't be reproduced locally. So having a
  -bug-report-trapper that can gather enough information from the surroundings of
  -a bug so that we can replay the session locally would be a big help tracking
  -down issues in this situation. This is tricky because you can't necessarily
  -require folks to leak information about their code in order to file bug
  -reports. So not only will you have to figure out what state to gather, you're
  -also going to have to anonymize it somehow. But we very often have bugs from
  -people that can't reduce the problem to a simple test case and can't give us
  -our code, and we often just can't help them as things stand now. Note that
  -adding the ProcessMock would be a good first stage towards this, since you
  -could make a ProcessMock creator/serializer from the current lldb state.
  -
  Expression parser needs syntax for "{symbol,type} A in CU B.cpp"
  ----------------------------------------------------------------
  