From 0fa0b60feba9a5b3c952f16653c122618b361ec1 Mon Sep 17 00:00:00 2001 From: dave Date: Wed, 8 Apr 2026 00:55:02 +0000 Subject: [PATCH] huskies: create 491_story_watcher_fires_on_crdt_state_transitions_instead_of_filesystem_events --- ...ransitions_instead_of_filesystem_events.md | 25 +++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 .huskies/work/1_backlog/491_story_watcher_fires_on_crdt_state_transitions_instead_of_filesystem_events.md diff --git a/.huskies/work/1_backlog/491_story_watcher_fires_on_crdt_state_transitions_instead_of_filesystem_events.md b/.huskies/work/1_backlog/491_story_watcher_fires_on_crdt_state_transitions_instead_of_filesystem_events.md new file mode 100644 index 00000000..74e7afd5 --- /dev/null +++ b/.huskies/work/1_backlog/491_story_watcher_fires_on_crdt_state_transitions_instead_of_filesystem_events.md @@ -0,0 +1,25 @@ +--- +name: "Watcher fires on CRDT state transitions instead of filesystem events" +agent: coder-opus +depends_on: [490] +--- + +# Story 491: Watcher fires on CRDT state transitions instead of filesystem events + +## User Story + +As a developer, I want the auto-assign loop, notifications, and WebSocket UI updates to subscribe to CRDT state transitions instead of filesystem directory watches. + +## Acceptance Criteria + +- [ ] Auto-assign triggers on CRDT state change (story entering a stage) instead of filesystem watcher +- [ ] Stage transition notifications fire from CRDT state changes +- [ ] WebSocket UI updates fire from CRDT state changes +- [ ] The filesystem watcher for .huskies/work/ is removed or deprecated +- [ ] Timer tick loop and dependency tick loop read from CRDT state +- [ ] agent: coder-opus +- [ ] depends_on: [490] + +## Out of Scope + +- TBD