Avoid hardcoding date in TestReviewSummaryTokenEnricher_LoadsCurrentSessionState

[computermode]

https://entire.io/gh/entireio/cli/trails/387

This test started failing because we hit 7 days on the IsStale threshold today and the date was hard coded to May 8th.

---

Note

Low Risk
Test-only change that removes a brittle, time-dependent fixture; low risk aside from potential flakiness if any logic assumes specific wall-clock dates.

Overview
Stops hardcoding a fixed StartedAt timestamp in manifest_test.go and instead uses time.Now().UTC().Truncate(time.Second) in the token hydration/enricher tests.

This prevents the suite from failing as the run becomes stale relative to the current date.

^{Reviewed by Cursor Bugbot for commit dd1ea22. Configure here.}

[Copilot]

Pull request overview

Updates a flaky review manifest test to avoid using a hard-coded timestamp that becomes stale once the session IsStale threshold is exceeded, aligning the test with how session state staleness is enforced in session.StateStore.

Changes:

• Replace hard-coded time.Date(...) timestamps with time.Now().UTC().Truncate(time.Second) in review manifest token-related tests.
• Prevent session state fixtures from being treated as stale (and therefore deleted/ignored) during test execution.