v1.13.56

Upgrade Notes

• Trajectory evaluation now requires Python 3.11+ and uses ATIF v1.7 models with Detector/Verifier APIs. Consumers of the former Evaluator API must migrate to Verifier and TrajectoryAnalysisRun.
• Rebuild existing trajectory Dataset/Run artifacts from the original sessions and labels. Run weekly_report.py --week <YYYY-Www> to rebuild the selected week and its predecessor; use ccr_trajectory_report.py --no-history when rebuilding a single week. Diagnostic caches use a new schema.
• Routed model calls now share a bounded fallback budget, configured through routing.call_timeout_sec (default: 180 seconds).

New Features

• Build labeled trajectory datasets from local review sessions and GitHub/GitLab annotations, with weekly HTML/Markdown reports for review completion, finding quality, cost, and behavior patterns.
• Diagnose selected trajectories incrementally with resumable caches, explicit call budgets, bounded evidence context, and token-usage reporting. Trace known missing findings to the review stage where delivery stopped.
• Enrich code-search results with bounded symbol context and expose additional import and supertype facts to support evidence gathering.

Bug Fixes

• Constrain investigation tools during wrap-up and preserve explicit incomplete outcomes when an execution cannot finish. Routed fallback no longer stacks hidden SDK retry budgets.
• Keep language-analysis caches separate by backend and reuse parsed facts across queries.
• Correct weekly-report denominators and label-availability handling, surface dataset build failures, and reuse canonical analysis results for reports and diagnostics.
• Preserve label links and resolvable step evidence when adapting CCR exports to ATIF; derive measurements before detection and verification.

Full changelog