Open a task and read the benchmark as evidence, not just as a rank table.

Browse the task catalogue by the revised L1 → L2 taxonomy, then inspect benchmark metadata, per-pipeline rankings, split-level spread, and neighbouring tasks that may share biological or operational constraints.