From 6077f74dbdf03b64f938daf75b660c85f844bf56 Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 28 Mar 2026 10:12:53 +0000 Subject: [PATCH] storkit: accept 09_story_remove_scroll_bars --- ...237_bug_work_item_titles_render_too_large_in_expanded_view.md | 1 - .../work/6_archived/254_story_add_refactor_work_item_type.md | 1 - .../255_story_show_agent_logs_in_expanded_story_popup.md | 1 - 3 files changed, 3 deletions(-) diff --git a/.storkit/work/6_archived/237_bug_work_item_titles_render_too_large_in_expanded_view.md b/.storkit/work/6_archived/237_bug_work_item_titles_render_too_large_in_expanded_view.md index 5e10dec7..8e00841f 100644 --- a/.storkit/work/6_archived/237_bug_work_item_titles_render_too_large_in_expanded_view.md +++ b/.storkit/work/6_archived/237_bug_work_item_titles_render_too_large_in_expanded_view.md @@ -1,6 +1,5 @@ --- name: "Work item titles render too large in expanded view" -merge_failure: "Merge pipeline infrastructure failure: squash merge committed successfully on merge-queue branch, but cherry-pick onto master failed with 'fatal: bad revision merge-queue/237_bug_work_item_titles_render_too_large_in_expanded_view'. The merge worktree setup also failed (ENOENT for .story_kit/merge_workspace — pnpm install, pnpm build, cargo check all skipped). The merge-queue branch appears to have been cleaned up before the cherry-pick step could reference it. Master is untouched." --- # Bug 237: Work item titles render too large in expanded view diff --git a/.storkit/work/6_archived/254_story_add_refactor_work_item_type.md b/.storkit/work/6_archived/254_story_add_refactor_work_item_type.md index 7ea9f665..2291b56d 100644 --- a/.storkit/work/6_archived/254_story_add_refactor_work_item_type.md +++ b/.storkit/work/6_archived/254_story_add_refactor_work_item_type.md @@ -1,6 +1,5 @@ --- name: "Add refactor work item type" -merge_failure: "merge_agent_work tool returned empty output on two attempts. The merge-queue branch (merge-queue/254_story_add_refactor_work_item_type) was created with squash merge commit 27d24b2, and the merge workspace worktree exists at .story_kit/merge_workspace, but the pipeline never completed (no success/failure logged after MERGE-DEBUG calls). The stale merge workspace worktree may be blocking completion. Possibly related to bug 250 (merge pipeline cherry-pick fails with bad revision on merge-queue branch). Human intervention needed to: 1) clean up the merge-queue worktree and branch, 2) investigate why the merge pipeline hangs after creating the squash merge commit, 3) retry the merge." --- # Story 254: Add refactor work item type diff --git a/.storkit/work/6_archived/255_story_show_agent_logs_in_expanded_story_popup.md b/.storkit/work/6_archived/255_story_show_agent_logs_in_expanded_story_popup.md index 29e8caf8..08aa547f 100644 --- a/.storkit/work/6_archived/255_story_show_agent_logs_in_expanded_story_popup.md +++ b/.storkit/work/6_archived/255_story_show_agent_logs_in_expanded_story_popup.md @@ -1,6 +1,5 @@ --- name: "Show agent logs in expanded story popup" -merge_failure: "merge_agent_work tool returned empty output. The merge pipeline created the merge-queue branch (merge-queue/255_story_show_agent_logs_in_expanded_story_popup) and merge workspace worktree at .story_kit/merge_workspace, but hung without completing. This is the same issue that affected story 254 — likely related to bug 250 (merge pipeline cherry-pick fails with bad revision on merge-queue branch). The stale merge workspace worktree on the merge-queue branch may be blocking completion. Human intervention needed to: 1) clean up the merge workspace worktree and merge-queue branch, 2) investigate the root cause in the merge pipeline (possibly the cherry-pick/fast-forward step after squash merge), 3) retry the merge." --- # Story 255: Show agent logs in expanded story popup