story-kit: queue 72_bug_story_creation_does_not_quote_yaml_special_characters_in_name for merge

.story_kit/work/2_current/72_bug_story_creation_does_not_quote_yaml_special_characters_in_name.md

@@ -1,42 +0,0 @@
----
-name: "Work item creation does not quote YAML special characters or include front matter"
-test_plan: pending
----
-
-# Bug 72: Work item creation does not quote YAML special characters or include front matter
-
-## Description
-
-Two related issues in server-side work item creation:
-
-1. **create_story** writes the `name` value into YAML front matter without quoting. If the name contains YAML-special characters like colons, the resulting front matter is invalid YAML and fails to parse.
-
-2. **create_bug** does not write YAML front matter at all (no `---` block with `name` and `test_plan`). The UI/parser expects front matter on all work items in the pipeline, so bug files show parse errors.
-
-## How to Reproduce
-
-### Issue 1 (create_story)
-1. Call create_story with a name containing a colon, e.g. "Server-owned agent completion: remove report_completion dependency"
-2. Open the generated .md file
-3. Observe the front matter parser rejects it: "mapping values are not allowed in this context"
-
-### Issue 2 (create_bug)
-1. Call create_bug with any name
-2. Open the generated .md file
-3. Observe there is no YAML front matter block — just a markdown heading
-
-## Actual Result
-
-- create_story: Invalid front matter when name contains colons
-- create_bug: No front matter at all
-
-## Expected Result
-
-- All work item creation methods should write valid YAML front matter with quoted `name` values
-- create_bug should include `---` front matter block with `name` and `test_plan` fields, consistent with create_story
-
-## Acceptance Criteria
-
-- [ ] create_story quotes name values containing YAML-special characters
-- [ ] create_bug writes YAML front matter with name and test_plan fields
-- [ ] Existing tests updated to cover special character handling

.story_kit/work/2_current/73_story_fade_out_completed_agents.md

@@ -1,25 +0,0 @@
----
-name: Fade Out Completed Agents in Panel
-test_plan: pending
----
-
-# "Story 70: Fade Out Completed Agents in Panel"
-
-## User Story
-
-As a user, I want completed agent entries in the Agents panel to gradually fade out and disappear after about 60 seconds, so that the panel doesn't fill up with stale results.
-
-## Acceptance Criteria
-
-- [ ] When an agent reaches a terminal state (completed or failed), a 60-second countdown begins
-- [ ] During the countdown the entry fades from full opacity to zero using a CSS transition
-- [ ] After the fade completes, the entry is removed from the panel DOM
-- [ ] Running and pending agents are never faded or removed
-- [ ] If the user expands a fading entry (clicks the triangle), the fade pauses so they can read the output
-- [ ] Collapsing the entry resumes the fade from where it left off
-
-## Out of Scope
-
-- Persisting completed agent history across page refreshes
-- A "show all completed" toggle to bring back faded entries
-- Configurable fade duration