story-kit: queue 115_story_hot_reload_project_toml_agent_config_without_server_restart for QA
This commit is contained in:
@@ -0,0 +1,23 @@
|
||||
---
|
||||
name: "Hot-reload project.toml agent config without server restart"
|
||||
---
|
||||
|
||||
# Story 115: Hot-reload project.toml agent config without server restart
|
||||
|
||||
## User Story
|
||||
|
||||
As a developer, I want changes to `.story_kit/project.toml` to be reflected in the AgentPanel without restarting the server, so that I can update agent configurations and see them immediately in the UI.
|
||||
|
||||
## Acceptance Criteria
|
||||
|
||||
- [ ] The filesystem watcher detects modifications to `.story_kit/project.toml` at the project root
|
||||
- [ ] A `WatcherEvent::ConfigChanged` is broadcast to all WebSocket clients when `project.toml` changes
|
||||
- [ ] Worktree copies of `project.toml` (paths containing `worktrees/`) are ignored
|
||||
- [ ] The WebSocket layer forwards an `agent_config_changed` message to the frontend
|
||||
- [ ] Pipeline state is NOT refreshed on config changes (only work-item changes trigger pipeline refresh)
|
||||
- [ ] The frontend `AgentPanel` re-fetches the agent roster when it receives `agent_config_changed`
|
||||
|
||||
## Out of Scope
|
||||
|
||||
- Hot-reload of server settings other than agent config
|
||||
- Debounce tuning beyond the existing 300ms window
|
||||
Reference in New Issue
Block a user