Skip to content

Release 1.3.1: triage agent 0.3.1, one card per episode - #6

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

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

Conversation

@AddisonTech

@AddisonTech AddisonTech commented Oct 21, 2026 •

Copy link
Copy Markdown
Owner
  • Pins the triage agent to 7eb8aff82eb442ba92ece3d15c18bff7dabe904c, its main branch just after the 0.3.1 merge, with the committed Haiku eval results.
  • Triage cards, consequences and set aside entries are keyed by point and episode start (or point and list position where there is no start), since 0.3.1 can escalate two episodes on one point. New tests render two episodes on one point and check the keys React gets; they fail on the old code.
  • The grading panel reads the new scorecard from the pinned package: template 58 of 58 cases, every grader at 100%.
  • Outage fixtures rebuilt with backend/scripts/make_triage_fixtures.py; they differ from 1.3.0 only in the agent version and run timings.
  • Version 1.3.1, README and CHANGELOG.

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

Pins to 7eb8aff, main just after the 0.3.1 merge, which carries the
committed Haiku eval results. The rebuilt outage fixtures differ only in
the agent version and run timings.
Since agent 0.3.1 one point can have two escalated episodes, so a point
alone no longer makes a unique key for a card, a consequence, or a set
aside entry.
@AddisonTech
AddisonTech merged commit b9ed7fd into main Oct 21, 2026
2 checks passed
@AddisonTech
AddisonTech deleted the claude/dreamy-mccarthy-9sz67x branch October 21, 2026 14:51
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