From c9ac9cd8a6b2b12de1f9a6d2068c5afc247d30f7 Mon Sep 17 00:00:00 2001 From: Dave Date: Mon, 23 Feb 2026 12:53:14 +0000 Subject: [PATCH] story-kit: create 68_story_frontend_pipeline_state_stale_after_server_restart --- ...peline_state_stale_after_server_restart.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .story_kit/work/1_upcoming/68_story_frontend_pipeline_state_stale_after_server_restart.md diff --git a/.story_kit/work/1_upcoming/68_story_frontend_pipeline_state_stale_after_server_restart.md b/.story_kit/work/1_upcoming/68_story_frontend_pipeline_state_stale_after_server_restart.md new file mode 100644 index 0000000..dd47d7e --- /dev/null +++ b/.story_kit/work/1_upcoming/68_story_frontend_pipeline_state_stale_after_server_restart.md @@ -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