fix squash e2e test

[gtrrz-victor]

No description provided.

[cursor]

PR Summary

Low Risk
E2E test-only change that adjusts expectations and messaging checks without modifying production logic.

Overview
Updates TestResumeSquashMergeMultipleCheckpoints to reflect new entire resume behavior when a squash-merge commit contains multiple Entire-Checkpoint trailers: it should restore only the most recent checkpoint (by CreatedAt) and report that older checkpoints were skipped.

The test assertions for both GitHub and git merge --squash message formats are changed from expecting “Restored 2 sessions” to checking for the “older checkpoints skipped” output, and the test description/comments are aligned accordingly.

^{Written by Cursor Bugbot for commit 4927cb3. Configure here.}

[Copilot]

Pull request overview

This PR fixes the TestResumeSquashMergeMultipleCheckpoints e2e test to match the current behavior of entire resume when encountering squash-merged commits with multiple checkpoint trailers. The production code (resume.go) was updated (in a prior change) to restore only the latest checkpoint (by CreatedAt timestamp) instead of all checkpoints, but the e2e test expectations still asserted the old "Restored 2 sessions" output.

Changes:

• Updated the TestResumeSquashMergeMultipleCheckpoints function doc comment to reflect the new behavior (restore only the latest checkpoint).
• Updated both squash merge format assertions to check for "older checkpoints skipped" instead of "Restored 2 sessions".