From a68f07dd29a0aeb7b35b1182264ec056e136dda9 Mon Sep 17 00:00:00 2001 From: Dave Date: Thu, 26 Feb 2026 10:34:31 +0000 Subject: [PATCH] story-kit: create 202_story_make_agent_watchdog_interval_configurable_via_project_toml --- ..._interval_configurable_via_project_toml.md | 19 +++++++++++++++++++ 1 file changed, 19 insertions(+) create mode 100644 .story_kit/work/1_upcoming/202_story_make_agent_watchdog_interval_configurable_via_project_toml.md diff --git a/.story_kit/work/1_upcoming/202_story_make_agent_watchdog_interval_configurable_via_project_toml.md b/.story_kit/work/1_upcoming/202_story_make_agent_watchdog_interval_configurable_via_project_toml.md new file mode 100644 index 0000000..a7c725f --- /dev/null +++ b/.story_kit/work/1_upcoming/202_story_make_agent_watchdog_interval_configurable_via_project_toml.md @@ -0,0 +1,19 @@ +--- +name: "Make agent watchdog interval configurable via project.toml" +--- + +# Story 202: Make agent watchdog interval configurable via project.toml + +## User Story + +As a developer, I want to configure the agent watchdog polling interval in project.toml, so that I can tune the orphan-detection frequency for my environment. + +## Acceptance Criteria + +- [ ] project.toml supports an optional watchdog_interval_secs field (default 30s matching current hardcoded value) +- [ ] AgentPool::spawn_watchdog reads the configured interval instead of using a hardcoded constant +- [ ] Existing tests pass and new unit tests cover default and custom config values + +## Out of Scope + +- TBD