Skip to content

Release 1.3.0: how the triage agent is graded - #5

Merged
AddisonTech merged 5 commits into
mainfrom
claude/dreamy-mccarthy-9sz67x
Oct 20, 2026
Merged

AddisonTech merged 5 commits into
mainfrom
claude/dreamy-mccarthy-9sz67x

Conversation

@AddisonTech

@AddisonTech AddisonTech commented Oct 20, 2026 •

Copy link
Copy Markdown
Owner
  • Pins the triage agent to its 0.3.0 merge commit, cc5f707f329a20862dbb19318e6d428c8162bcfd.
  • GET /api/triage/grading reads the template writer's eval pass rates from the pinned agent package (bms_triage_service.eval_scorecard()). Nothing is hard-coded; a 503 if the installed agent has no scorecard.
  • A small "How this agent is graded" panel on the Triage tab shows the pass rate per grader and links to the Evals section of the agent's showcase page.
  • The Triage fixtures were rebuilt from the simulator with the new agent by backend/scripts/make_triage_fixtures.py, now in the repository. Apart from the agent version and run timings they match 1.2.2: the utility failure first, five consequences collapsed, the same measured dip.
  • Version 1.3.0, README and a new CHANGELOG.

Backend 85 tests, front end 44 tests, production build.

The Triage tab fixtures are rebuilt from the simulator with the new agent
by backend/scripts/make_triage_fixtures.py, now in the repository. Apart
from the agent version and run timings they match 1.2.2: the utility
failure first, five consequences collapsed, the same measured dip.
GET /api/triage/grading reads the template writer's eval pass rates from
the pinned agent package, and a small panel on the Triage tab shows them
per grader with a link to the Evals section of the agent's showcase.
The fixture script indented by two spaces, which rewrote every line of
both outage fixtures. With the original layout their diff from 1.2.2 is
the agent version and the run timings.
@AddisonTech
AddisonTech merged commit 2575151 into main Oct 20, 2026
2 checks passed
@AddisonTech
AddisonTech deleted the claude/dreamy-mccarthy-9sz67x branch October 20, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant