Covers the full persistence flow:
- User messages are persisted via ConversationsRepo.addMessage with correct role/content
- Assistant responses are persisted with model, provider, tokens, and toolCalls metadata
- Session resume maps DB messages to ConversationHistoryMessage for context injection
- buildHistoryPromptSection formats history into system prompt (full and summarized paths)
- GET /api/conversations/search returns matching messages via ConversationsController
- End-to-end simulation: create conversation → persist messages → load history on resume
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Verifies conversation persistence, context loading, search, and history summarization. 20 tests covering addMessage, findMessages, buildHistoryPromptSection, search endpoint, and E2E flow.