Update story 45: accept_story needs MCP tool not just REST

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Dave
2026-02-20 14:55:28 +00:00
parent 8003a98a35
commit 7aa337d81b

View File

@@ -12,7 +12,7 @@ As a developer running autonomous agents, I want the server to manage story file
## Acceptance Criteria ## Acceptance Criteria
- [ ] `start_agent` automatically moves the story from upcoming/ to current/ if it isn't already there - [ ] `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 - [ ] 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 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 - [ ] If a story doesn't exist in upcoming/ or current/, `start_agent` returns a clear error