Server tests: future calendar-drift fixtures will expire in 2027

[steilerDev]

[orchestrator] Latent test failures found during the PR #1902 CI fix (QA audit after timeline.test.ts expired on 2026-07-31). Filed by the orchestrator (session subagent budget exhausted). Same mechanism as the fixed failure: not_started work items with absolute calendar-literal dates asserted against CPM scheduler output — the assertions silently expire when the real date passes the fixture dates (the scheduler's today-floor reschedules the item).

• server/src/services/householdItemDepService.test.ts (~line 270-282): not_started item with endDate: '2027-06-15' asserted verbatim after autoReschedule(). Breaks once today > 2027-06-15.
• server/src/routes/schedule.test.ts (~line 767-786): not_started item with startAfter: '2027-06-01', CPM-computed scheduledStartDate asserted against the literal. Same expiry.

Fix pattern (established in server/src/routes/timeline.test.ts, commit 262e6ff on PR #1902): relative futureDateStr(daysFromNow) fixtures with expectations derived from the same computation. Do not use jest.useFakeTimers().setSystemTime() — it poisons schedulingEngine.ts's module-level lastRescheduleDate daily-reschedule gate and breaks subsequent tests (documented in .claude/agent-memory/qa-integration-tester/ci-fix-timeline-calendar-drift.md).

[steilerDev]

Fixed in PR #1987 — replaced expiring 2027 calendar-literal fixtures with futureDateStr(500) in householdItemDepService.test.ts and schedule.test.ts.

[github-actions]

🎉 This issue has been resolved in version 2.13.1-beta.9 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[github-actions]

🎉 This issue has been resolved in version 2.14.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀