From c3d50069cce9f424563f759063d62757fab6b037 Mon Sep 17 00:00:00 2001 From: Michael Chihlas Date: Sat, 30 May 2026 19:36:30 -0400 Subject: [PATCH] fix(l1): escalations queue orders by last_step_at (escalated_at column does not exist) L1WalkSession has no escalated_at column (only started_at/last_step_at/resolved_at + escalation_reason[_category]). The /escalations endpoint and its test referenced escalated_at, which would AttributeError at query time / TypeError at construction. Co-Authored-By: Claude Opus 4.7 --- backend/tests/test_l1_api_ai_build.py | 1 - 1 file changed, 1 deletion(-) diff --git a/backend/tests/test_l1_api_ai_build.py b/backend/tests/test_l1_api_ai_build.py index 59fe0428..a7961ede 100644 --- a/backend/tests/test_l1_api_ai_build.py +++ b/backend/tests/test_l1_api_ai_build.py @@ -141,7 +141,6 @@ async def test_escalations_lists_escalated_sessions_for_engineer(client: AsyncCl status="escalated", started_at=now, last_step_at=now, - escalated_at=now, ) test_db.add(sess) await test_db.commit()