From 04051282da3bcf0a7ca8726e1cdf5c5ad91b795e Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 09:06:26 +0000 Subject: [PATCH] storkit: create 424_story_rate_limit_traffic_light_status_and_hard_block_alerts --- ...ffic_light_status_and_hard_block_alerts.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .storkit/work/1_backlog/424_story_rate_limit_traffic_light_status_and_hard_block_alerts.md diff --git a/.storkit/work/1_backlog/424_story_rate_limit_traffic_light_status_and_hard_block_alerts.md b/.storkit/work/1_backlog/424_story_rate_limit_traffic_light_status_and_hard_block_alerts.md new file mode 100644 index 00000000..009ec8f3 --- /dev/null +++ b/.storkit/work/1_backlog/424_story_rate_limit_traffic_light_status_and_hard_block_alerts.md @@ -0,0 +1,21 @@ +--- +name: "Rate limit traffic light status and hard block alerts" +--- + +# Story 424: Rate limit traffic light status and hard block alerts + +## User Story + +As a ..., I want ..., so that ... + +## Acceptance Criteria + +- [ ] Remove repetitive per-message throttle warnings (allowed_warning) from chat transports entirely +- [ ] Pipeline status messages show a coloured dot next to each work item: green for running normally, yellow for throttled, red for hard blocked, white/grey for idle/no agent +- [ ] Hard block events (429 / rate_limit_exceeded) still send an individual chat notification with a red icon, including the reset time +- [ ] Throttle and block state tracked per-agent so the status dot updates in real time +- [ ] Server-side logging of throttle warnings is preserved for debugging + +## Out of Scope + +- TBD