From 6af7e3d30bfab43633b5aef4a0c9671a4ca71e5f Mon Sep 17 00:00:00 2001 From: dave Date: Sat, 4 Apr 2026 11:41:56 +0000 Subject: [PATCH] huskies: done 469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml --- ...t_command_to_show_overall_test_coverage.md | 25 ----------------- .../472_story_discord_chat_transport.md | 24 ---------------- ...ns_and_timezone_in_default_project_toml.md | 28 +++++++++++++++++++ 3 files changed, 28 insertions(+), 49 deletions(-) delete mode 100644 .huskies/work/1_backlog/471_story_bot_command_to_show_overall_test_coverage.md delete mode 100644 .huskies/work/1_backlog/472_story_discord_chat_transport.md create mode 100644 .huskies/work/5_done/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md diff --git a/.huskies/work/1_backlog/471_story_bot_command_to_show_overall_test_coverage.md b/.huskies/work/1_backlog/471_story_bot_command_to_show_overall_test_coverage.md deleted file mode 100644 index 2daa59d6..00000000 --- a/.huskies/work/1_backlog/471_story_bot_command_to_show_overall_test_coverage.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -name: "Bot command to show overall test coverage" ---- - -# Story 471: Bot command to show overall test coverage - -## User Story - -As a user on any chat transport (Matrix, WhatsApp, Slack, or web UI), I want a `coverage` command that runs the test suite with coverage instrumentation and reports the overall coverage percentage, so I can track code quality from any interface. - -## Acceptance Criteria - -- [ ] New bot command `coverage` registered in the command registry -- [ ] Runs test coverage (e.g. cargo llvm-cov or cargo tarpaulin) and parses the overall percentage -- [ ] Reports overall line coverage percentage in chat response -- [ ] Command appears in `help` output -- [ ] Returns a clear error if the coverage tool is not installed -- [ ] Command works across all transports (Matrix, WhatsApp, Slack, web UI) via the shared command registry -- [ ] Available as both a bot command in chat and a slash command in Claude Code -- [ ] By default, reads cached coverage from .coverage_baseline for an instant response without rerunning tests -- [ ] Optional `coverage run` variant reruns script/test_coverage and reports fresh results - -## Out of Scope - -- TBD diff --git a/.huskies/work/1_backlog/472_story_discord_chat_transport.md b/.huskies/work/1_backlog/472_story_discord_chat_transport.md deleted file mode 100644 index 7ba01bea..00000000 --- a/.huskies/work/1_backlog/472_story_discord_chat_transport.md +++ /dev/null @@ -1,24 +0,0 @@ ---- -name: "Discord chat transport" -agent: coder-opus ---- - -# Story 472: Discord chat transport - -## User Story - -As a user who uses Discord, I want to control huskies from a Discord server so I can create stories, check status, start agents, and chat with the bot from Discord like I can from Matrix. - -## Acceptance Criteria - -- [ ] Discord transport implements the ChatTransport trait (send_message, send_typing, etc.) -- [ ] Bot connects via Discord gateway websocket using serenity crate -- [ ] All shared bot commands (status, help, start, unblock, etc.) work from Discord -- [ ] Stage transition and block notifications are posted to configured Discord channel(s) -- [ ] LLM fallthrough works — non-command messages are forwarded to Claude Code -- [ ] Config in bot.toml: discord_token, discord_channel_ids, allowed_users -- [ ] Bot only responds when mentioned or in configured channels - -## Out of Scope - -- TBD diff --git a/.huskies/work/5_done/469_bug_scaffold_missing_rate_limit_notifications_and_timezone_in_default_project_toml.md b/.huskies/work/5_done/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/5_done/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