huskies: create 469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml

2026-04-04 11:04:39 +00:00
parent a11900a78f
commit 2cf654aa4c
2 changed files with 28 additions and 20 deletions
@@ -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
@@ -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