From 5d84100c41784abcb6d3b66f628215ff9937c81f Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 15:35:14 +0000 Subject: [PATCH] storkit: create 436_refactor_unify_story_stuck_states_into_a_single_status_field --- ...stuck_states_into_a_single_status_field.md | 26 +++++++++++++++++++ 1 file changed, 26 insertions(+) create mode 100644 .storkit/work/1_backlog/436_refactor_unify_story_stuck_states_into_a_single_status_field.md diff --git a/.storkit/work/1_backlog/436_refactor_unify_story_stuck_states_into_a_single_status_field.md b/.storkit/work/1_backlog/436_refactor_unify_story_stuck_states_into_a_single_status_field.md new file mode 100644 index 00000000..5aa45658 --- /dev/null +++ b/.storkit/work/1_backlog/436_refactor_unify_story_stuck_states_into_a_single_status_field.md @@ -0,0 +1,26 @@ +--- +name: "Unify story stuck states into a single status field" +--- + +# Refactor 436: Unify story stuck states into a single status field + +## Current State + +- TBD + +## Desired State + +Replace the separate blocked, merge_failure, and review_hold front matter fields with a single status field (e.g. status: blocked, status: merge_failure, status: review_hold). Simplifies the unblock command, auto-assign checks, and pipeline advance logic. + +## Acceptance Criteria + +- [ ] Replace blocked: true, merge_failure: string, and review_hold: true with a single status: field in story front matter +- [ ] Auto-assign checks a single field instead of three separate ones +- [ ] Pipeline advance and lifecycle code reads/writes the unified status field +- [ ] Unblock command clears the status field regardless of which stuck state it was +- [ ] retry_count remains a separate field (it's a counter, not a state) +- [ ] Migration: existing stories with old fields are handled gracefully on read + +## Out of Scope + +- TBD