From 7aa337d81b594c7d120c3ef4494981bee0c23cb0 Mon Sep 17 00:00:00 2001 From: Dave Date: Fri, 20 Feb 2026 14:55:28 +0000 Subject: [PATCH] Update story 45: accept_story needs MCP tool not just REST Co-Authored-By: Claude Opus 4.6 --- .../current/45_deterministic_story_lifecycle_management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.story_kit/stories/current/45_deterministic_story_lifecycle_management.md b/.story_kit/stories/current/45_deterministic_story_lifecycle_management.md index 914f1c6..30aee6d 100644 --- a/.story_kit/stories/current/45_deterministic_story_lifecycle_management.md +++ b/.story_kit/stories/current/45_deterministic_story_lifecycle_management.md @@ -12,7 +12,7 @@ As a developer running autonomous agents, I want the server to manage story file ## Acceptance Criteria - [ ] `start_agent` automatically moves the story from upcoming/ to current/ if it isn't already there -- [ ] A new `accept_story` MCP/REST endpoint moves a story from current/ to archived/ (human-only action, not available to coder agents) +- [ ] A new `accept_story` MCP tool AND REST endpoint moves a story from current/ to archived/ (available to any caller — the point is the server does the move, not the agent freestyle) - [ ] Agents cannot move story files directly — the server is the single source of truth for story lifecycle - [ ] If a story is already in current/, `start_agent` leaves it there (idempotent) - [ ] If a story doesn't exist in upcoming/ or current/, `start_agent` returns a clear error