From facbf51f056b5c87fe5ef552ec64e07deb733fb3 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 11:18:36 +0000 Subject: [PATCH] storkit: create 426_bug_mergemaster_pipeline_marks_story_done_without_verifying_code_landed_on_master --- ...ffic_light_status_and_hard_block_alerts.md | 23 ------------------- ...without_verifying_code_landed_on_master.md | 7 +++--- 2 files changed, 4 insertions(+), 26 deletions(-) delete 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 deleted file mode 100644 index 7b7ec8d6..00000000 --- a/.storkit/work/1_backlog/424_story_rate_limit_traffic_light_status_and_hard_block_alerts.md +++ /dev/null @@ -1,23 +0,0 @@ ---- -name: "Rate limit traffic light status and hard block alerts" -agent: coder-opus ---- - -# 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 -- [ ] Traffic light dots in status report should be small/compact, not large emoji - -## Out of Scope - -- TBD diff --git a/.storkit/work/1_backlog/426_bug_mergemaster_pipeline_marks_story_done_without_verifying_code_landed_on_master.md b/.storkit/work/1_backlog/426_bug_mergemaster_pipeline_marks_story_done_without_verifying_code_landed_on_master.md index fa96b1c0..a816a34c 100644 --- a/.storkit/work/1_backlog/426_bug_mergemaster_pipeline_marks_story_done_without_verifying_code_landed_on_master.md +++ b/.storkit/work/1_backlog/426_bug_mergemaster_pipeline_marks_story_done_without_verifying_code_landed_on_master.md @@ -33,11 +33,12 @@ Audited all 9 stories in `5_done/` to check whether their code actually landed o | 420 — loc file command | `d6f8239` (5 files, +112/-32) | YES | | 421 — Timer command | `cf5424f` (7 files, +836) | YES | | 422 — Unblock command | `6c6bc35` (4 files, +336) — manual cherry-pick | YES | -| **423 — Auto-schedule timer on rate limit** | **None** | **NO** | -| **424 — Rate limit traffic light** | **None** | **NO** | +| 423 — Auto-schedule timer on rate limit | `b44f3a3` + `8ab2e19` (6 files, +375/-8) — manual cherry-pick | YES | +| **424 — Rate limit traffic light** | **None** | **NO — moved back to backlog for redo** | | 425 — Chat notification on story block | `98b5475` (5 files, +184/-15) | YES | +| **427 — Text normalization for line breaks** | **None** | **NO — phantom done, code never landed** | -**3 out of 9 stories (422, 423, 424) had broken merges.** 422 was fixed manually. 423 and 424 still have code stranded on their feature branches with no merge commit on master. +**4 out of 10 stories (422, 423, 424, 427) had broken merges.** 422 and 423 were fixed via manual cherry-pick. 424 was moved back to backlog for a fresh run. 427 also hit the same bug — marked done without code on master. ## Actual Result