perflisted

# Performance Quality Assess how a deployed system behaves under a declared resource profile and load. Operate the project's existing performance capability; do not replace its load framework, workload semantics, target policy, or service-level objectives. ## Keep the owners separate 1. Treat case-harness or another performance framework as infrastructure for load scheduling, lifecycle, observation, metric reduction, artifacts, reports, and Verdicts. 2. Treat the project as owner of its Workloads, Cases, Experiment/Profile configuration, target adapters, Probes, SLOs, safety limits, canonical command, and comparison baselines. 3. Treat this skill as the operator that discovers those assets, selects and runs the relevant experiment, checks evidence validity, interprets or compares results, and helps evolve bounded project-owned coverage when requested. Do not call a lower-level framework directly when the project exposes a wrapper. Framework code without a project-owned workload and runnable profile is `no_capability`. ## Discover the capability Read the project's AGENTS.md and README first, then locate: - canonical commands and directories for performance, load, capacity, stress, soak, scalability, or regression testing; - the subject boundary and target environment, including whether it is a local process or remote system such as Kubernetes, the deployed revision, where the load runner executes, and how it reaches the application endpoint; - workload