Make pipelined reference-only; show unscored profiles as faded column…

[MDA2AV]

…s (#1058)

Per the #1058 resolution, pipelined stays on the board but leaves the composite: HTTP/1.1 pipelining is disabled in modern browsers and unsupported by mainstream proxies, but the profile remains a valuable raw-I/O / middleware-efficiency indicator.

• catalog: pipelined scored/engineScored -> false, blurb marks reference
• board: unscored profiles (pipelined, fortunes) now render in the composite matrix as faded columns — aggregate() no longer skips them and the column filter keeps them; cells carry counts=false so they never enter the sum, headers get a .refcol fade, and reference cells explain themselves on hover (distinct from the engine not-counted tip)
• docs: composite-score tables updated (pipelined No (*), closing note now names both reference profiles, missing echo-ws-limited row added), pipelined pages and README marked reference-only

Verified with a node harness over the real data.js: both columns appear, counts=false on every row, and each score equals the sum of counted cells only.

Description

---

PR Commands — comment on this PR to trigger (requires collaborator approval):

Command	Description
/benchmark -f <framework>	Run every test the framework subscribes to
/benchmark -f <framework> -t <test>	Run one test only
/benchmark -f <framework> --save	Run and save results (updates the leaderboard on merge)
/benchmark -f <framework> -t <test> --save	Run one test and save results
/benchmark -f <framework> --compare <other>	Measure the deltas against another framework instead of this one
/benchmark-multiple -f <fw1>,<fw2>,...	Benchmark several frameworks in one run — takes -t and --save too; saved results land in a single commit
/benchmark-multiple --save	No -f needed: benchmark and save every framework the PR touches
/benchmark-test -t <test>	Benchmark all enabled frameworks subscribed to <test> and save the results

For /benchmark, always specify -f <framework>; the flags combine in any order. Results come back as a comment with a per-profile table of RPS, p99, CPU and memory — one table per framework on multi runs. A new benchmark comment while a run is in flight queues behind it (one deep) instead of cancelling it. For multi-framework PRs (dependency bumps, same-language refactors) prefer /benchmark-multiple, which runs everything in a single job and commits all saved results together, so no run overwrites another. --compare works on single-framework runs only.

What the deltas are measured against. By default, this framework's own results published on main - answering "did this change help?". When you are tuning a variant or a successor entry, --compare re-bases them on another entry instead:

/benchmark -f genhttp-11 --compare genhttp

The reply states which baseline it used, and profiles the other framework does not run show n/a rather than a delta.

---

Run benchmarks locally

You can validate and benchmark your framework locally with the lite script — no CPU pinning, fixed connection counts, all load generators run in Docker.

./scripts/validate.sh <framework>
./scripts/benchmark-lite.sh <framework> baseline
./scripts/benchmark-lite.sh --load-threads 4 <framework>

Requirements: Docker Engine on Linux. Load generators (gcannon, h2load, h2load-h3, wrk, ghz) are built as self-contained Docker images on first run.