trajectorylisted

# Trajectory Quality Turn an agent's recorded decisions and actions into an evidence-backed next improvement. Operate the project's existing trajectory capability; do not replace its framework, business data, labels, or judgment criteria. ## Keep the owners separate 1. Treat case-harness or another trajectory framework as infrastructure that quantifies and localizes trajectory problems, then accumulates their evidence through normalization, Dataset and Run artifacts, Findings, Evaluations, Measurements, Worksheets, metrics, and reports. 2. Treat the project as owner of its RecordingSource, Loader, annotations, Detectors, Evaluators, Measurers, report projection, canonical command, and optimization targets. 3. Treat this skill as the operator that discovers those assets, runs them, turns their evidence into one bounded next problem and change surface, and organizes a controlled tuning experiment. The framework answers where a problem appears, with what evidence, magnitude, and trend. This skill uses project context to decide what to change next and how to verify it. Do not call a lower-level framework directly when the project exposes a wrapper. Framework code alone is `no_capability`; require either a usable project entrypoint that can produce trajectory evidence or an existing project-owned artifact sufficient for the requested analysis. A missing specialized Detector or Evaluator alone is not `no_capability`: when normalized trajectories are available, insp