diff --git a/.story_kit/work/1_upcoming/280_story_long_running_supervisor_agent_with_periodic_pipeline_polling.md b/.story_kit/work/1_upcoming/280_story_long_running_supervisor_agent_with_periodic_pipeline_polling.md
deleted file mode 100644
index 69d06df..0000000
--- a/.story_kit/work/1_upcoming/280_story_long_running_supervisor_agent_with_periodic_pipeline_polling.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-name: "Long-running supervisor agent with periodic pipeline polling"
-agent: coder-opus
----
-
-# Story 280: Long-running supervisor agent with periodic pipeline polling
-
-## User Story
-
-As a project owner, I want a long-running supervisor agent (opus) that automatically monitors the pipeline, assigns agents, resolves stuck items, and handles routine operational tasks, so that I don't have to manually check status, kick agents, or babysit the pipeline in every conversation.
-
-## Acceptance Criteria
-
-- [ ] Server can start a persistent supervisor agent that stays alive across the session (not per-story)
-- [ ] Server prods the supervisor periodically (default 30s, configurable in project.toml) with a pipeline status update
-- [ ] Supervisor auto-assigns agents to unassigned items in current/qa/merge stages
-- [ ] Supervisor detects stuck agents (no progress for configurable timeout) and restarts them
-- [ ] Supervisor detects merge failures and sends stories back to current for rebase when appropriate
-- [ ] Supervisor can be chatted with via Matrix (timmy relays to supervisor) or via the web UI
-- [ ] Supervisor logs its decisions so the human can review what it did and why
-- [ ] Polling interval is configurable in project.toml (e.g. supervisor_poll_interval_secs = 30)
-- [ ] Supervisor logs persistent/recurring problems to `.story_kit/problems.md` with timestamp, description, and frequency — humans review this file periodically to create stories for systemic issues
-
-## Out of Scope
-
-- Supervisor accepting or merging stories to master (human job)
-- Supervisor making architectural decisions
-- Replacing the existing per-story agent spawning — supervisor coordinates on top of it
diff --git a/.story_kit/work/1_upcoming/281_story_matrix_bot_announces_itself_when_it_comes_online.md b/.story_kit/work/1_upcoming/281_story_matrix_bot_announces_itself_when_it_comes_online.md
deleted file mode 100644
index 9af23c0..0000000
--- a/.story_kit/work/1_upcoming/281_story_matrix_bot_announces_itself_when_it_comes_online.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-name: "Matrix bot announces itself when it comes online"
----
-
-# Story 281: Matrix bot announces itself when it comes online
-
-## User Story
-
-As a user in the Matrix room, I want Timmy to post a message when he starts up, so that I know the bot is online and ready to accept commands.
-
-## Acceptance Criteria
-
-- [ ] Bot sends a brief greeting message to each configured room on startup (e.g. 'Timmy is online.')
-- [ ] Message uses the configured display_name, not a hardcoded name
-- [ ] Message is only sent once per startup, not on reconnects or sync resumptions
-- [ ] Bot does not announce if it was already running (e.g. after a brief network blip)
-
-## Out of Scope
-
-- TBD
diff --git a/.story_kit/work/5_done/276_story_detect_and_log_when_root_mcp_json_port_is_modified.md b/.story_kit/work/5_done/276_story_detect_and_log_when_root_mcp_json_port_is_modified.md
new file mode 100644
index 0000000..7125e7b
--- /dev/null
+++ b/.story_kit/work/5_done/276_story_detect_and_log_when_root_mcp_json_port_is_modified.md
@@ -0,0 +1,17 @@
+---
+name: "Detect and log when root .mcp.json port is modified"
+---
+
+# Story 276: Detect and log when root .mcp.json port is modified
+
+## User Story
+
+As a ..., I want ..., so that ...
+
+## Acceptance Criteria
+
+- [ ] TODO
+
+## Out of Scope
+
+- TBD