exeris-benchmarks

Comparative strict-gate review for exeris-benchmarks. Use on every PR making a cross-target comparative claim — verifies 4 gate artefacts present + `claim-status.json = comparison_eligible` + `track_id` consistent.

Fairness + reproducibility review for exeris-benchmarks. Use on every committed result and every cross-target claim — enforces matched scoping, separation axes, and complete metadata.

Publication-mode scrub review for exeris-benchmarks. Use whenever `publish-report.sh` runs, when an artefact crosses to a publishable surface, or when raw `.jfr` / flamegraph appears.

Router/Planner skill for exeris-benchmarks. Produces primary agent, secondary handoffs, execution order, validation gates, and minimal next action for a benchmark task.

Router/Planner triage skill for exeris-benchmarks. Classifies task type (architecture / scenario / driver / JMH / target / verification / docs / publication), scope, severity, and recommends primary agent based on primary risk against fairness / reproducibility / strict gate / confidentiality.

TLS comparator label discipline review for exeris-benchmarks. Use on every TLS JMH benchmark / TLS row / TLS report change.

Guard Exeris cross-tier comparisons so Community vs Enterprise claims stay correctly labeled, protocol-consistent, and inference-safe.

Protect proprietary Enterprise details in benchmark outputs by reviewing traces, symbols, and publication artifacts before public reporting.

Review Exeris benchmark methodology for fairness and evidence quality: warmup, measurement windows, target/payload/concurrency equivalence, and overclaiming risk.

Review Exeris benchmark reproducibility and environment capture: metadata completeness, JDK/toolchain versions, hardware profile, JVM flags, repeatability, and naming consistency.

Review Exeris benchmark result interpretation for honest conclusions, clear tier/protocol labels, and overclaiming prevention.

Build an execution routing plan for Exeris benchmark work: primary agent, handoffs, metadata requirements, and reporting constraints.

Review Exeris benchmark scenario design quality: scenario semantics, naming clarity, workload realism, and separation across benchmark layers.

Classify Exeris benchmark requests by family, target, and comparison axis. Use for benchmark triage before architecture, implementation, or reporting work.