huskies: create 491_story_watcher_fires_on_crdt_state_transitions_instead_of_filesystem_events
This commit is contained in:
+25
@@ -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
|
||||||
Reference in New Issue
Block a user