story-kit: accept 74_story_agent_lozenges_float_across_ui_during_assignment

.story_kit/work/5_archived/70_story_server_owned_agent_completion_remove_report_completion_dependency.md

@@ -0,0 +1,27 @@
+---
+name: "Server-owned agent completion: remove report_completion dependency"
+test_plan: approved
+---
+
+# Story 70: Server-owned agent completion: remove report_completion dependency
+
+## User Story
+
+As a developer using story-kit, I want the server to automatically run acceptance
+gates and advance the pipeline when an agent process exits, so that the pipeline
+does not stall when an agent forgets or fails to call `report_completion`.
+
+## Acceptance Criteria
+
+- [ ] When an agent process exits normally, the server automatically runs acceptance gates (uncommitted changes check + cargo clippy + tests)
+- [ ] When acceptance gates pass on natural process exit, the agent status is set to `Completed` and the pipeline advances
+- [ ] When acceptance gates fail on natural process exit, the agent status is set to `Failed` and the pipeline handles the failure appropriately
+- [ ] `report_completion` is removed from the MCP tools list (agents no longer see or call it)
+- [ ] The default agent prompt no longer instructs agents to call `report_completion`
+- [ ] If a completion was already recorded before the process exits (legacy path), the server does not run gates a second time
+
+## Out of Scope
+
+- Removing the concept of a `CompletionReport` struct (still used internally)
+- Changing the pipeline advancement logic itself
+- Frontend changes

.story_kit/work/5_archived/74_story_agent_lozenges_float_across_ui_during_assignment.md

@@ -0,0 +1,23 @@
+---
+name: Agent lozenges float across UI during assignment
+test_plan: approved
+---
+
+# Story 74: Agent lozenges float across UI during assignment
+
+## User Story
+
+As a user, I want to see cool animations, so that I get a great visual representation of agent activity.
+
+## Acceptance Criteria
+
+- [ ] Agent lozenges animate as floating overlays (absolute/fixed positioned) that fly across the screen from the agents panel to the target work item panel
+- [ ] The floating animation travels over top of all other UI elements, not within the layout flow
+- [ ] Agent lozenges maintain a fixed intrinsic width at all times - they do not stretch or expand to fill the width of the panel they dock into
+- [ ] When an agent completes or is reassigned, the lozenge floats back to the agents panel (or to the next work item) using the same overlay animation
+- [ ] The animation uses FLIP-style transitions (or equivalent) to smoothly interpolate between start and end positions
+- [ ] Idle and active lozenge states remain visually distinct (pulse/shimmer for active) as implemented in story 59
+
+## Out of Scope
+
+- TBD