PINKIIILQWQ abd6b85200 fix(state): resolve compression chain tip in resolve_resume_session_id ... After context compression, the parent session holds pre-compression messages and a child (or deeper descendant) holds the continuation. resolve_resume_session_id() short-circuited when the input session already had messages (row is not None -> return session_id), causing REST API endpoints, gateway resume, and CLI resume to serve stale parent messages. Remove the early-return. Walk the full descendant chain, record the deepest node that has messages (best), and return best if not None else the original session_id (preserving the empty-chain fallback). Callers (api_server.py, web_server.py, cli_agent_setup_mixin.py, cli_commands_mixin.py) all use the resolved != input -> redirect pattern and are transparent to this change.		2026-06-25 16:29:09 -07:00
..
test_get_anchored_view.py	feat(session_search): single-shape tool with discovery, scroll, browse — no LLM (#27590)	2026-05-17 23:28:45 -07:00
test_get_messages_around.py	feat(session_search): single-shape tool with discovery, scroll, browse — no LLM (#27590)	2026-05-17 23:28:45 -07:00
test_resolve_resume_session_id.py	fix(state): resolve compression chain tip in resolve_resume_session_id	2026-06-25 16:29:09 -07:00
test_session_archiving.py	fix(sessions): archive compressed conversation lineages	2026-06-11 12:31:10 +05:30