openclaw - 💡(How to fix) Fix Compaction quality guard does not verify identifier survival in summaries [1 pull requests]

Problem

The compaction quality guard validates that summaries are well-formed and meet length thresholds, but it does not verify that opaque identifiers from the original transcript survive into the post-compaction summary.

Identifiers like UUIDs, commit SHAs, session keys, file hashes, and run IDs appear throughout tool call arguments, tool results, and message text. When the summarization model drops these identifiers, subsequent tool calls and references in the conversation break silently because the agent loses context about which specific resource was being operated on.

Impact

After compaction, the agent may:

• Reference the wrong resource because a UUID was lost
• Fail tool calls that require an exact identifier (run IDs, session keys)
• Confuse multiple similar resources when their distinguishing identifiers were dropped
• Silently produce incorrect results without any warning that context was lost

Expected behavior

The compaction quality guard should:

1. Extract opaque identifiers from all original messages (including tool call arguments and tool result content)
2. Verify that those identifiers appear in the post-compaction summary
3. When identifiers are lost and policy is strict, trigger a re-summarization retry with the lost identifiers injected as a preservation hint
4. Log identifier loss even when the threshold for retry is not reached

Scope

This covers identifiers in:

• Regular message text content
• Tool call arguments (toolCall, toolUse, functionCall blocks)
• Tool result content (excluding toolResult.details which are stripped for security)