story-kit: create 87_story_update_agent_lozenge_colour_scheme_across_panels

.story_kit/work/5_archived/87_story_update_agent_lozenge_colour_scheme_across_panels.md

@@ -1,23 +0,0 @@
----
-name: "Update agent lozenge colour scheme across panels"
-test_plan: pending
----
-
-# Story 87: Update agent lozenge colour scheme across panels
-
-## User Story
-
-As a user, I want a consistent and meaningful colour scheme for agent lozenges, so I can quickly distinguish between idle, pending, and running agents across both the Agents roster panel and the stage panel.
-
-## Acceptance Criteria
-
-- [ ] Idle agents in the Agents roster panel are grey with a green dot on the left (ready but not working)
-- [ ] Pending agents in stage panel slots remain amber #e3b341
-- [ ] Running agents in stage panel slots use green #3fb950 for the whole lozenge (matching the current idle roster style)
-- [ ] Active agents in the roster panel (if still shown) use green #3fb950 for the whole lozenge
-- [ ] The semi-transparent pattern is maintained (color+18 bg, color+44 border, full color text)
-- [ ] Roster badges keep borderRadius 6px, slot lozenges keep 999px pills
-
-## Out of Scope
-
-- TBD

.story_kit/work/5_archived/88_story_auto_assign_agents_to_available_work_on_server_startup.md

@@ -1,26 +0,0 @@
----
-name: "Auto-assign agents to available work"
-test_plan: pending
----
-
-# Story 88: Auto-assign agents to available work
-
-## User Story
-
-As a user, I want the server to automatically assign free agents to queued work items, both on startup and whenever an agent finishes its current task, so that work progresses continuously without manual intervention.
-
-## Acceptance Criteria
-
-- [ ] On server startup, scan work/2_current/ for stories with no running coder agent and auto-assign available coders
-- [ ] On server startup, scan work/3_qa/ for items with no running QA agent and auto-start the QA agent
-- [ ] On server startup, scan work/4_merge/ for items with no running mergemaster agent and auto-start the mergemaster agent
-- [ ] When a coder agent completes (moves story to QA), check work/2_current/ for unassigned stories and assign the now-free coder to the next one
-- [ ] When a QA or mergemaster agent completes, similarly check their respective queues for more work
-- [ ] Auto-assignment respects the agent roster limits from project.toml (don't exceed max concurrent agents per role)
-- [ ] Items in work/1_upcoming/ are NOT auto-started (they require explicit user action)
-- [ ] Auto-assignment logs clearly which stories are being picked up and which agents are assigned
-
-## Out of Scope
-
-- Automatic promotion of items from upcoming to current (that remains a user decision)
-- Priority ordering of queued work items (FIFO by filename is fine)