From ead3d3aeba37a4e93bdb214a7527b1dc28d4ceb1 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 26 Feb 2026 10:34:29 +0000 Subject: [PATCH] story-kit: create 201_story_make_watcher_sweep_interval_configurable_via_project_toml --- ..._interval_configurable_via_project_toml.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .story_kit/work/1_upcoming/201_story_make_watcher_sweep_interval_configurable_via_project_toml.md diff --git a/.story_kit/work/1_upcoming/201_story_make_watcher_sweep_interval_configurable_via_project_toml.md b/.story_kit/work/1_upcoming/201_story_make_watcher_sweep_interval_configurable_via_project_toml.md new file mode 100644 index 0000000..24ccfdc --- /dev/null +++ b/.story_kit/work/1_upcoming/201_story_make_watcher_sweep_interval_configurable_via_project_toml.md @@ -0,0 +1,20 @@ +--- +name: "Make watcher sweep interval configurable via project.toml" +--- + +# Story 201: Make watcher sweep interval configurable via project.toml + +## User Story + +As a developer, I want to configure the watcher sweep interval and done-retention period in project.toml, so that I can tune how quickly stories are promoted to archived based on my team's workflow. + +## Acceptance Criteria + +- [ ] project.toml supports optional sweep_interval_secs and done_retention_secs fields (with sensible defaults matching current hardcoded values: 60s and 4h) +- [ ] The watcher reads these values at startup and uses them for SWEEP_INTERVAL and DONE_RETENTION +- [ ] Changing project.toml hot-reloads the sweep config without restarting the server +- [ ] Existing tests pass and new unit tests cover default and custom config values + +## Out of Scope + +- TBD