From 2cf654aa4c90ea11fd6de0473842da6a418c47ee Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 4 Apr 2026 11:04:39 +0000 Subject: [PATCH] huskies: create 469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml --- ...return_current_time_in_project_timezone.md | 20 ------------- ...ns_and_timezone_in_default_project_toml.md | 28 +++++++++++++++++++ 2 files changed, 28 insertions(+), 20 deletions(-) delete mode 100644 .huskies/work/1_backlog/467_story_mcp_tool_to_return_current_time_in_project_timezone.md create mode 100644 .huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md diff --git a/.huskies/work/1_backlog/467_story_mcp_tool_to_return_current_time_in_project_timezone.md b/.huskies/work/1_backlog/467_story_mcp_tool_to_return_current_time_in_project_timezone.md deleted file mode 100644 index baaa36ed..00000000 --- a/.huskies/work/1_backlog/467_story_mcp_tool_to_return_current_time_in_project_timezone.md +++ /dev/null @@ -1,20 +0,0 @@ ---- -name: "MCP tool to return current time in project timezone" ---- - -# Story 467: MCP tool to return current time in project timezone - -## User Story - -As an LLM agent (coder, QA, or top-level bot), I want an MCP tool that returns the current time in the project's configured timezone so I can reason about time without having to read project.toml and convert from container UTC manually. - -## Acceptance Criteria - -- [ ] New MCP tool `get_current_time` returns current date/time in the project's configured timezone -- [ ] Output includes both local time and UTC for clarity -- [ ] Uses the `timezone` field from project.toml, falls back to UTC if not set -- [ ] Includes day of week and timezone abbreviation (e.g. 'Fri 2026-04-03 14:30 BST (13:30 UTC)') - -## Out of Scope - -- TBD diff --git a/.huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md b/.huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md new file mode 100644 index 00000000..88b7bca1 --- /dev/null +++ b/.huskies/work/1_backlog/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md @@ -0,0 +1,28 @@ +--- +name: "Scaffold missing rate_limit_notifications and timezone in default project.toml" +--- + +# Bug 469: Scaffold missing rate_limit_notifications and timezone in default project.toml + +## Description + +The scaffold template for `project.toml` does not include the `rate_limit_notifications` or `timezone` fields. New projects get defaults (notifications on, no timezone), but these settings aren't visible or documented in the generated config file. Users have to discover them manually. + +The 455 rename also stripped these fields from the huskies project's own `project.toml` because it was regenerated from the scaffold. + +## How to Reproduce + +1. Run `huskies init` on a new project +2. Check the generated `.huskies/project.toml` + +## Actual Result + +No `rate_limit_notifications` or `timezone` fields in generated project.toml. + +## Expected Result + +Both fields present with commented defaults so users know they exist. + +## Acceptance Criteria + +- [ ] Bug is fixed and verified