story-kit: create 68_story_frontend_pipeline_state_stale_after_server_restart
This commit is contained in:
@@ -0,0 +1,20 @@
|
|||||||
|
---
|
||||||
|
name: Frontend Pipeline State Stale After Server Restart
|
||||||
|
test_plan: pending
|
||||||
|
---
|
||||||
|
|
||||||
|
# Story 68: Frontend Pipeline State Stale After Server Restart
|
||||||
|
|
||||||
|
## User Story
|
||||||
|
|
||||||
|
As a user viewing the web UI, I want the pipeline panel to show the correct state after a server restart, so that I am not looking at stale stage data from before the restart.
|
||||||
|
|
||||||
|
## Acceptance Criteria
|
||||||
|
|
||||||
|
- [ ] Server scans .story_kit/work/ directories on startup and loads current pipeline state from the filesystem
|
||||||
|
- [ ] Frontend re-fetches full pipeline state on WebSocket reconnect
|
||||||
|
- [ ] Pipeline panel accurately reflects filesystem state even if file moves happened while the server was down
|
||||||
|
|
||||||
|
## Out of Scope
|
||||||
|
|
||||||
|
- TBD
|
||||||
Reference in New Issue
Block a user