story-kit: done 245_bug_chat_history_persistence_lost_on_page_refresh_story_145_regression

.story_kit/work/5_done/245_bug_chat_history_persistence_lost_on_page_refresh_story_145_regression.md

@@ -0,0 +1,37 @@
+---
+name: "Chat history persistence lost on page refresh (story 145 regression)"
+merge_failure: "Squash-merge resulted in an empty diff — the feature branch has no code changes beyond master. The bug fix commits may have already been merged into master through another path, or the feature branch was never ahead of master."
+---
+
+## Rejection Notes
+
+**2026-03-16:** Previous coder produced zero code changes — feature branch had no diff against master. The coder must actually use `git bisect` to find the breaking commit and produce a surgical fix. Do not submit with no code changes.
+
+# Bug 245: Chat history persistence lost on page refresh (story 145 regression)
+
+## Description
+
+Story 145 implemented localStorage persistence for chat history across page reloads. This is no longer working — refreshing the page loses all conversation context. This is a regression of the feature delivered in story 145.
+
+## How to Reproduce
+
+1. Open the web UI and have a conversation with the agent
+2. Refresh the page (F5 or Cmd+R)
+
+## Actual Result
+
+Chat history is gone after refresh — the UI shows a blank conversation.
+
+## Expected Result
+
+Chat history is restored from localStorage on page load, as implemented in story 145.
+
+## Acceptance Criteria
+
+- [ ] Chat messages survive a full page refresh
+- [ ] Chat messages are restored from localStorage on component mount
+- [ ] Behaviour matches the original acceptance criteria from story 145
+
+## Investigation Notes
+
+**Use `git bisect` to find the commit that broke this.** Story 145 delivered working localStorage persistence — something after that regressed it. Find the breaking commit, understand the root cause, and fix it there. Do NOT layer on a new implementation. Revert or surgically fix the regression.