embabel-chat-store integration

[jasperblues]

Summary

Integrates embabel-chat-store with embabel-agent, establishing agent-api as the source of truth for chat abstractions. This simplifies the dependency graph and enables pluggable conversation storage (in-memory or Neo4j, thus far. More in future).

Changes

Type Hierarchy Simplification

• Deleted MessageAuthor - Conversation methods now use User from agent.api.identity directly
• Added StoredUser (in chat-store) - Interface extending User with Drivine annotations for Neo4j persistence
• Added SimpleStoredUser (in chat-store) - Ready-to-use implementation

New in agent-api

• StoredMessage interface - Storage contract for messages
• ConversationFactory interface - Creates conversations for a store type
• ConversationFactoryProvider interface - Aggregates factories by type
• ConversationStoreType enum - IN_MEMORY or STORED
• Fluent API: context.ai().conversationFactory(type)

Architecture

  agent-api (source of truth)
  ├── User                      ← identity interface
  ├── StoredMessage             ← storage contract
  ├── Conversation              ← uses User for attribution
  ├── ConversationFactory
  └── ConversationFactoryProvider

  chat-store (persistence layer)
  ├── StoredUser                ← User + Drivine annotations
  ├── StoredConversation        ← Neo4j implementation
  └── ChatSessionRepository

[alexheifetz]

looks like needs rebase

[igordayen]

massive change on pom version can be most likely avoided with proper rebase in place.
please share PR with chat-store to assess cross-repos interdependencies , if still any. thanks

[igordayen]

${project.version}

[jasperblues]

Is this comment still relevant after rebase?

[igordayen]

also: please consider preserving history for cross-repos refactoring

[johnsonr]

I think we should at least consider making Message an interface and avoiding the need for StoredMessage.

I'm not sure what the impact of this will be on user code: Probably not too great

[sonarqubecloud]

Quality Gate failed

Failed conditions
67.1% Coverage on New Code (required ≥ 73%)

See analysis details on SonarQube Cloud