You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit b7cb7d5
Browse filesBrowse the repository at this point in the historyBrowse files
Companion gap to the reasoning_steps fix above: run_agentic_items never
copied any per-kind diagnostic info into ItemReport.best_detail, so every
agentic result's "detail" field was always {} -- undiagnosable, unlike
the single-shot path which gets this for free from ItemEvaluation.detail.
AgenticEvalOutcome gains a `detail: dict` field, populated by each
evaluate_agentic_* function from whatever its own Result/Evaluation class
already tracks (no new capture needed) -- e.g. actual_maql for
metric_skill, the full visualization per-check breakdown (now shared via
evaluation_result_detail() between the single-shot and agentic paths so
both report the identical shape), judge_reasoning/actual_output for the
LLM-judge kinds (guardrail, general_question). Same *AssertionError
idiom as reasoning_steps: attached as .detail on failure, returned on
the AgenticEvalOutcome on success. cli/agentic_runner.py copies it onto
item_report.best_detail in both branches.
0 commit comments