A self-contained guide for fixing an inaccurate streaming percentile estimator in any codebase. If your
project uses an online/streaming quantile estimator (P² / "P-square" / Raatikainen extended-P² / a 2m+3-marker
sketch) and it returns wrong percentiles on real, skewed data, this explains why and how to fix it without
abandoning the streaming property. The goal is "still an estimate, only a good one" — keep it O(1)-memory and
fast; do not replace it with an exact sort, inflate the marker count, or buffer samples.
(This came out of one concrete case; the originating example is in the appendix. The body is deliberately project-agnostic — apply the pattern, not the names.)