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

story-kit: create 85_story_agent_lozenges_move_between_roster_and_work_items_instead_of_duplicating

Browse Source
This commit is contained in:
Dave
2026-02-23 18:55:54 +00:00
parent 1539e52b19
commit 520c1a0990
2 changed files with 0 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
.story_kit/work/5_archived/85_story_agent_lozenges_move_between_roster_and_work_items_instead_of_duplicating.md
View File

@@ -1,23 +0,0 @@
---
name: "Agent lozenges move between roster and work items instead of duplicating"
test_plan: pending
---
# Story 85: Agent lozenges move between roster and work items instead of duplicating
## User Story
As a user, I want agent lozenges to physically move from the Agents roster to their assigned work item and back, so the UI conveys that the agent has left the idle pool rather than duplicating it in both places.
## Acceptance Criteria
- [ ] When an agent is assigned to a work item, its lozenge animates out of the roster and flies to the work item card
- [ ] The roster gap closes up smoothly as remaining idle agents slide together
- [ ] While an agent is working, its lozenge only appears on the work item card, not in the roster
- [ ] When an agent completes, the lozenge animates back from the work item to the roster
- [ ] The roster opens up to receive the returning lozenge
- [ ] No duplicate lozenges appear at any point during the animation or while working
## Out of Scope
- TBD

22
.story_kit/work/5_archived/89_story_persistent_per_session_agent_logs.md
View File

@@ -1,22 +0,0 @@
---
name: "Persistent per-session agent logs"
test_plan: pending
---
# Story 89: Persistent per-session agent logs
## User Story
As a user, I want each agent session to write its output to a persistent log file so I can inspect what an agent did after it completes, even across server restarts.
## Acceptance Criteria
- [ ] Each agent session writes output to a log file at .story_kit/logs/{story_id}/{agent_name}-{session_id}.log
- [ ] Log files persist across server restarts and agent completions
- [ ] The get_agent_output MCP tool falls back to reading the log file when the in-memory stream is empty or the agent has completed
- [ ] Log files include timestamps, tool calls, text output, and status events
- [ ] Different sessions for the same agent on the same story produce separate log files (no mixing)
## Out of Scope
- TBD