Bug Description

Since PR #17409 / #10619, providers receive session_id on the per-turn write/recall hooks and on_turn_start now fires. They still cannot resolve the human-readable session title — useful for memory backends that render session lists or attribute extracted facts to a named conversation.

Steps to Reproduce

n/a

Expected Behavior

The MemoryProvider sync_turn (or on_turn_start) receives session_title= sourced from self._session_db.get_session_title(session_id). Empty string when no title has been generated yet.

• Related: [Bug]: MemoryProvider doesn't see multiple user identities in shared sessions #7781

Actual Behavior

Session title is unavailable

Affected Component

Agent Core (conversation loop, context compression, memory)

Messaging Platform (if gateway-related)

No response

Operating System

All

Python Version

n/a

Hermes Version

0.8.0

Relevant Logs / Traceback

Root Cause Analysis (optional)

No response

Proposed Fix (optional)

No response

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR