dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: accept 255_story_show_agent_logs_in_expanded_story_popup

Browse Source
This commit is contained in:
Dave
2026-03-17 11:23:36 +00:00
parent 4585537dd8
commit f5524b3ae1
3 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
.story_kit/work/6_archived/254_story_add_refactor_work_item_type.md Normal file
View File

@@ -0,0 +1,23 @@
---
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
## User Story
As a project owner, I want a refactor work item type so that I can track and assign code restructuring tasks separately from features and bugs.
## Acceptance Criteria
- [ ] create_refactor MCP tool creates a refactor file in work/1_upcoming/ with deterministic filename (e.g. 254_refactor_split_agents_rs.md)
- [ ] Refactor files use the naming convention {id}_refactor_{slug}.md
- [ ] Refactor items flow through the same pipeline as stories and bugs (upcoming → current → qa → merge → done → archived)
- [ ] list_refactors MCP tool lists open refactors in upcoming
- [ ] Frontend displays refactor items distinctly from stories and bugs (different label/color)
- [ ] Watcher recognizes refactor files and auto-commits moves like stories and bugs
## Out of Scope
- TBD

16
.story_kit/work/6_archived/255_story_show_agent_logs_in_expanded_story_popup.md Normal file
View File

@@ -0,0 +1,16 @@
---
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
## Description
The expanded story popup has an "Agent Logs" tab that currently shows "No output". Implement the frontend and any necessary API wiring to display agent output in this tab. This is new functionality — agent logs have never been shown here before.
## Acceptance Criteria
- [ ] Agent Logs tab shows real-time output from running agents
- [ ] Agent Logs tab shows historical output from completed/failed agents
- [ ] Logs are associated with the correct story