- resolveAnchorTimestamp returns endTimestamp + 1 instead of Infinity
- Validate timestamps are finite before creating blocks
- Skip corrupted blocks in overlap checks and compression application
- Include block timestamp range in overlap error messages
- Filter out corrupted blocks on session restore
- Fix prompt tag name: dcp-message-id → dcp-id to match injected tags
- Remove duplicate test, keep corrupted-block resilience test
The root cause of the compression spiral (101 failures, 2 hours):
resolveAnchorTimestamp returned Infinity when no message followed the
compression range. Infinity corrupted JSON serialization (became null),
and null timestamps in JS overlap checks coerced to 0, making every
range appear to overlap the ghost block b7.
Fixes:
- resolveAnchorTimestamp returns endTimestamp + 1 instead of Infinity
- Validate all timestamps are finite before creating a block (fail fast)
- Skip blocks with non-finite timestamps in overlap checks and compression
- Include existing block range in overlap error messages (diagnostic)
- Filter out corrupted blocks on session restore
- Guard synthetic message timestamp creation against non-finite values
- Add regression tests for Infinity anchor and null-timestamp blocks
Backward and forward expansion now skip PI-internal passthrough roles
(compaction, branch_summary, custom_message) when scanning for paired
assistant↔toolResult messages, ensuring atomic removal. Added a
post-compression repair safety net and deep-cloning to prevent content
mutation across context events.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
wassname