huskies: create 477_story_crdt_state_backend_replacing_filesystem_pipeline_state

.huskies/work/1_backlog/477_story_crdt_state_backend_replacing_filesystem_pipeline_state.md

@@ -1,5 +1,6 @@
 ---
 name: "CRDT state backend replacing filesystem pipeline state"
+agent: coder-opus
 ---
 
 # Story 477: CRDT state backend replacing filesystem pipeline state

.huskies/work/1_backlog/483_bug_timer_slash_command_not_wired_up_in_web_ui.md

@@ -1,29 +0,0 @@
----
-name: "Timer slash command not wired up in web UI"
----
-
-# Bug 483: Timer slash command not wired up in web UI
-
-## Description
-
-The `/timer` command in the web UI returns "Unknown command" because `bot_command.rs` dispatch_command only has explicit async handlers for `assign`, `start`, `delete`, and `rebuild`. The `timer` command is async (handled by the Matrix transport's message loop) but has no corresponding handler in the web UI's bot command endpoint. It falls through to `dispatch_sync` which calls `try_handle_command`, but the timer registry stub returns `None`.
-
-The fix: add a `"timer" => dispatch_timer(args, project_root).await` branch to `dispatch_command` in `bot_command.rs`, similar to the existing `dispatch_start` and `dispatch_delete` handlers.
-
-## How to Reproduce
-
-1. Open the web UI
-2. Type `/timer list` or `/timer 463 14:00`
-3. See "Unknown command: /timer"
-
-## Actual Result
-
-Unknown command: `/timer`. Type `/help` to see available commands.
-
-## Expected Result
-
-Timer command works in the web UI the same as it does via Matrix.
-
-## Acceptance Criteria
-
-- [ ] Bug is fixed and verified