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. Read [Quality concepts](../../CONCEPTS.md) before discovery or interpretation. It defines ownership, subject identity, execution facts, evaluation, comparison, and result states shared by the skills. The project owns recording sources, loaders, annotations, Detectors, Verifiers, Measurers, report projection, and optimization targets. Trajectory and deterministically derived Measurements are inputs to discovery and verification. A Detector discovers patterns; a Verifier checks an explicit criterion. Both can concern cost or effect and use hard or soft rules. Map the project's native component names to these roles without assuming that a specific API or artifact exists. Require either a usable project entrypoint that produces trajectory evidence or existing evidence sufficient for the requested analysis. A missing specialized Detector or Verifier alone does not make the capability absent: inspect representative and counterexample trajectories for candidate problems, clearly recording them as analyst observations rather than fabricated framework results. ## Discover the capability Read the project's AGENTS.md and README first, then locate: - the canonical command for collecting, building, evaluating, or reporting trajectories; - persiste