Fix sleep edits not preserving the wake calendar date

[Creanathan]

Summary

• Fix the Android compilation blocker caused by the trailing comma after dateChosen = true.
• Keep explicit wake-date selection for Allow editing sleep start and end date/time #970 on both platforms.
• Reject inverted, future-ending, and multi-day edited windows at the shared persistence guard.
• Preserve legitimate same-night corrections, including the reported 5-hour endpoint correction.
• Add Android and Swift parity coverage for the 24-hour boundary and the 32-hour Settings: finish the iOS-only scheduled-export dedup + compile-verify #336's Swift legs (#335) #406 regression shape.

Design decision

The wake date is user-selectable to fix #970, but a date change must not silently create an unbounded multi-day sleep. A maximum 24-hour edit window preserves normal long sleep/nap corrections while preventing stages and totals from being re-bucketed across unrelated days, addressing the design conflict raised in review for #406.

Validation

• git diff --check passes.
• Focused diff is based directly on upstream main and contains only the eight sleep editor/guard/test files.
• Android full debug unit tests were attempted, but this Windows environment has no Android SDK configured.
• Swift package tests were attempted, but Swift tooling is not installed on this Windows environment.
• Static parity review confirms Android and Swift guards and tests use the same 24-hour rule.

🤖 Generated with Claude Code

[Creanathan]

CI is currently blocked before any jobs start: Android CI, Swift Packages CI, App build, Source Hygiene, and i18n Coverage all show action_required with zero jobs. This is GitHub's fork-workflow approval gate, not a test failure. Please approve the pending workflows so the full validation suite can run.

The branch is based directly on upstream main and the PR diff is focused to 8 sleep editor/guard/test files (+117/-74).