benchmarks: the PyneCore harness is kept outside this repository; its leg is optional - #383

…-out private strategies (BIZ-11)

Where the PyneCore speedup is stated (README.md, benchmarks/README.md, results/speed.md and the aggregate that writes it), the
200 strategies are now described as 100 corpus probes and 100 held-out private strategies. The population paragraph of
benchmarks/README.md says the same, with the market and timeframe facts kept. The provenance claims follow the new sentences
exactly: the closed-half claim matches the new wording, and the speedup claim now also reads the two counts and checks them
against the timed slot names (100 corpus probes, 100 closed), so it is stricter, not weaker. No number changes.

Reworded sentences, named for the doc-revert gate:
* the market and timeframe that both the bench feed and the TradingView tapes cover.
* strategies both engines time (p5 15×, p95 131×), and 4.2× over vectorbt across its 13 ports.
* strategies both engines time, measured at engine on an AWS c7a.8xlarge with PyneCore timed as a subprocess.
* across the 200 strategies both engines time (p5 15×, p95 131×).
* (across 200 commonly-timed strategies): 36× (p5 15×, p95 131×)

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>

…enerator carries the new wording, and a run without it never rewrites the committed speed table (BIZ-11)

A read of the change found the following; all are fixed here.

* The generator still emitted the old sentence naming the private runner and its command line, so regenerating speed.md would
  have put the path back into a public file. The harness-present branch of speed/aggregate.py now emits exactly the text of
  the committed speed.md, and a new test, tests/test_aggregate.py, runs the real aggregate with and without --pynecore and
  checks that block against both its own output and the committed file.
* A run without timings from PyneCore wrote its (different) table over the committed results/speed.md. It now writes
  _workdir/speed.md and says so; the committed file is not touched. Tested with an aggregate stand-in that writes to the
  path it is given: the committed file stays byte-identical in the absent cases and is the output in the present case.
* SKIP_PYNE=1 now means what it meant before: it skips only the PyneCore strategy runs and the canonical indicator run, not
  the .ohlcv conversion and not the PyneCore timing. The "harness not present" line is printed only when the harness really
  is absent. A run without the harness leaves the committed PyneCore trade lists and canonical output as they are.
* test_run_all.py: every case now starts from a clean slate (markers, outputs and committed PyneCore files re-seeded), so a
  result of one case cannot satisfy another; a new test runs with the harness present, with an absolute and a relative
  harness path, and checks that the runner sees PINEFORGE_REPO_ROOT, that the timings reach the aggregate as --pynecore and
  that the table goes to its usual place; a recording stand-in for pyne proves it is never called without the harness; the
  argument check also rejects --pynecore=... and any path ending pc_speed.json.
* check_provenance.py: the 100/100 split in the speedup claim comes from the selection manifest (source == closed, the
  replacement slot included) instead of a slug suffix; probes + held must equal n. The claim pattern is unchanged. A test
  covers names that disagree with their manifest source.
* README: the added pointer sentence no longer says "set PYNECORE_HARNESS_DIR to reproduce"; it says the harness is not
  distributed, when the leg runs, and that the published PyneCore figures are dated and not re-measured here. The manual
  timing command sets PINEFORGE_REPO_ROOT.

Reworded base sentences, named for the doc-revert gate:
* SKIP_BUILD, SKIP_PINEFORGE, SKIP_PYNE, SKIP_PINETS, SKIP_VECTORBT, SKIP_INDICATORS, SKIP_SPEED and SKIP_REPORTS each skip one step.
* skip PyneCore strategy + indicator runs and timing

Co-Authored-By: Claude Sonnet 5.5 <[email protected]>