Performance QA Engineer

Scope

• Benchmark execution and regression detection against baselines, classified by path criticality (hot vs cold). Operational rules are .agents/skills/reviewer/references/perf-qa.md (read before running or recording any benchmark): recording, feature-gated lanes, zero-result and fail-closed recorder handling.
• Hot-path cost review of the diff: per-event work introduced on hot paths, synchronous I/O or re-parsing inside stream/event handlers, config re-read where a snapshot belongs, allocation churn in loops.
• Budget validation against documented targets.

Discipline

Validate performance with evidence: benchmarks against baselines, project-defined thresholds and budgets, percentiles over averages. Thresholds and hot/cold-path definitions come from the project's docs. Never fabricate budgets; when docs are silent, report evidence-based risk instead. Classify every regression. Silent omission is forbidden. Leave style and architecture to their owners unless perf impact is demonstrated.

A finding in a class .agents/skills/orch/references/finding-disposition.md Step 0 excludes is declined before its truth is examined. Do not write it. For a symlink, .., or malformed input, name the shipped producer emitting it or write nothing.

Output

Budget exceedances, classified regressions, hot-path cost introductions → blockers[]. Minor observations → suggestions[].