From e9f8aafdaac27da73d2ce392bec83ab35b4fd536 Mon Sep 17 00:00:00 2001 From: Dave Date: Tue, 24 Feb 2026 12:59:59 +0000 Subject: [PATCH] story-kit: create 139_story_retry_limit_for_mergemaster_and_pipeline_restarts --- ...t_for_mergemaster_and_pipeline_restarts.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) create mode 100644 .story_kit/work/1_upcoming/139_story_retry_limit_for_mergemaster_and_pipeline_restarts.md diff --git a/.story_kit/work/1_upcoming/139_story_retry_limit_for_mergemaster_and_pipeline_restarts.md b/.story_kit/work/1_upcoming/139_story_retry_limit_for_mergemaster_and_pipeline_restarts.md new file mode 100644 index 0000000..886a6eb --- /dev/null +++ b/.story_kit/work/1_upcoming/139_story_retry_limit_for_mergemaster_and_pipeline_restarts.md @@ -0,0 +1,21 @@ +--- +name: "Retry limit for mergemaster and pipeline restarts" +--- + +# Story 139: Retry limit for mergemaster and pipeline restarts + +## User Story + +As a developer using story-kit, I want pipeline auto-restarts to have a configurable retry limit so that failing agents don't loop infinitely consuming CPU and API credits. + +## Acceptance Criteria + +- [ ] Pipeline auto-restart has a configurable max_retries per agent in project.toml (default 3) +- [ ] After max retries exhausted, agent status is set to Failed and no further restarts occur +- [ ] Server logs clearly indicate attempt number and when max retries are exhausted +- [ ] Retry count resets when a human manually restarts the agent (resume_context is None) +- [ ] Retry limit applies to all pipeline stages: Coder, QA, and Mergemaster restarts + +## Out of Scope + +- TBD