From 13db4d00f86bebfa1a92ebc6baf734e291bd4d88 Mon Sep 17 00:00:00 2001
From: Step7750 <Step7750@gmail.com>
Date: Mon, 27 Jul 2026 23:33:29 -0600
Subject: [PATCH] Update Handling of `Committed` Trades

Some trades can linger in the `Committed` state without ever reaching `Complete`. Since they are functionally equivalent, we need to report them server-side as well.

Ref CSF-1717
---
 src/lib/alarms/trade_history.ts | 7 ++++++-
 1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/src/lib/alarms/trade_history.ts b/src/lib/alarms/trade_history.ts
index 0e7c9ac7..3ddfd672 100644
--- a/src/lib/alarms/trade_history.ts
+++ b/src/lib/alarms/trade_history.ts
@@ -142,7 +142,12 @@ export async function getTradeHistoryFromAPI(
 
     const data = (await resp.json()) as TradeHistoryAPIResponse;
     return (data.response?.trades || [])
-        .filter((e) => e.status === TradeStatus.Complete || e.status === TradeStatus.TradeProtectionRollback) // Ensure we only count _complete_ trades (k_ETradeStatus_Complete) or rolled back (for reporting)
+        .filter(
+            (e) =>
+                e.status === TradeStatus.Committed ||
+                e.status === TradeStatus.Complete ||
+                e.status === TradeStatus.TradeProtectionRollback
+        ) // Only report exchanged/completed trades or trade-protection rollbacks
         .filter((e) => !e.time_escrow_end || new Date(parseInt(e.time_escrow_end) * 1000).getTime() < Date.now())
         .map((e) => {
             return {