80ab7d2b1c
When context-compression rotation fires mid-turn, the current user message was persisted twice into the child session. Root cause: dedup used id()-seeded sets of copies instead of markers on the live objects. Replace with _DB_PERSISTED_MARKER-based dedup as the sole authority: - _ensure_compressed_has_user_turn returns CompressedUserTurnOutcome - After publish_compression_child succeeds, stamp the live anchor-source row (not a drifted index) with _DB_PERSISTED_MARKER - _sync_persisted_markers mirrors stamps from result to live lists by scoped identity (handles direct-path, adoption divergence, _session_messages) - Remove _flushed_db_message_ids from rotation commit path (markers replace it) - Unconditional (loud) imports — no silent fallback Salvage of #94996 by @fedosis, rebased on top of #95433 (stall-fallback, already merged). Both conversation_compression.py and run_agent.py are built from origin/main + #94996's diff applied on top, preserving the force_terminal refactor and _publish_new_fence from #95433. Credit: @fedosis original PR #94996.