dave/storkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 7 Wiki Activity

story-kit: start 115_story_hot_reload_project_toml_agent_config_without_server_restart

Browse Source
This commit is contained in:
Dave
2026-02-23 22:41:46 +00:00
parent c60128386d
commit 9d2db2c98d
1 changed files with 9 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
.story_kit/work/2_current/115_story_hot_reload_project_toml_agent_config_without_server_restart.md
View File

@@ -6,12 +6,18 @@ name: "Hot-reload project.toml agent config without server restart"
## User Story ## User Story
As a ..., I want ..., so that ... 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 ## Acceptance Criteria
- [ ] TODO - [ ] 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 ## Out of Scope
- TBD - Hot-reload of server settings other than agent config
- Debounce tuning beyond the existing 300ms window