From ca3d5ee7a6b06273e68bd192bce81fb5a3ddb5f0 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 19 Mar 2026 15:49:38 +0000 Subject: [PATCH] story-kit: create 312_bug_auto_assign_assigns_mergemaster_to_coding_stage_stories --- ..._assigns_mergemaster_to_coding_stage_stories.md | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-) diff --git a/.story_kit/work/1_backlog/312_bug_auto_assign_assigns_mergemaster_to_coding_stage_stories.md b/.story_kit/work/1_backlog/312_bug_auto_assign_assigns_mergemaster_to_coding_stage_stories.md index 714e69b..3598d63 100644 --- a/.story_kit/work/1_backlog/312_bug_auto_assign_assigns_mergemaster_to_coding_stage_stories.md +++ b/.story_kit/work/1_backlog/312_bug_auto_assign_assigns_mergemaster_to_coding_stage_stories.md @@ -6,17 +6,23 @@ name: "Auto-assign assigns mergemaster to coding-stage stories" ## Description -Auto-assign picked mergemaster for story 310 which was in 2_current/. Mergemaster should only work on stories in 4_merge/. The auto_assign_available_work function doesn't enforce that the agent's configured stage matches the pipeline stage of the story it's being assigned to. Story 279 (auto-assign respects agent stage from front matter) was supposed to fix stage matching, but the check may only apply to front-matter preferences, not the fallback assignment path. This was observed on 2026-03-19 when story 310 was moved back to backlog and restarted — mergemaster was assigned instead of a coder. +Auto-assign picks agents whose configured stage doesn't match the pipeline stage of the story. Observed multiple mismatch types: + +- **Mergemaster assigned to coding-stage stories**: Story 310 was in `2_current/` but got mergemaster instead of a coder (2026-03-19) +- **Coders assigned to QA-stage stories**: Coders (stage=coder) have been observed running on stories in `3_qa/` +- **QA agents assigned to merge-stage stories**: QA agents (stage=qa) have been observed running on stories in `4_merge/` + +The `auto_assign_available_work` function doesn't enforce that the agent's configured stage matches the pipeline stage of the story it's being assigned to. Story 279 (auto-assign respects agent stage from front matter) was supposed to fix stage matching, but the check may only apply to front-matter preferences, not the fallback assignment path. ## How to Reproduce -1. Move a story to 2_current/ with no agent front matter preference +1. Move a story to any pipeline stage with no agent front matter preference 2. Wait for auto_assign_available_work to run -3. Observe that mergemaster gets assigned instead of a coder agent +3. Observe that agents from the wrong stage get assigned (e.g. mergemaster to coding, coder to QA) ## Actual Result -Mergemaster was assigned to story 310 in 2_current/. +Agents are assigned to stories in pipeline stages that don't match their configured stage. Mergemaster codes, coders do QA, QA agents attempt merges. ## Expected Result