BOLT-1267 P1 — fix Bugbot round 3 multi-day batch spacing on PR #12218

Cursor Bugbot landed a Medium finding on PR #12218 at 01:01 UTC (12 min after the round-2 clear DM): **Multi-day batch spacing wrong** — `batchesToActionConfigs` (apps/dashboard/.../edit/_lib/batchesToActionConfigs.ts L7-12) maps each batch's startAt/endAt to clock-only Time values, dropping calendar dates. `buildSegments` (EventCurvePreview.tsx L64-106) lays out actions with same-day ordering + +24h bumps only. Result: actions separated by 2+ calendar days get compressed or mis-ordered onto a single synthetic timeline. **Validity:** legit. Confirmed by reading the code in workspace. **Fix direction:** propagate calendar date (or a day offset) from startAt/endAt through `batchesToActionConfigs` -> ActionConfig, so `buildSegments` can place each action on its actual day rather than re-deriving day-boundaries from clock-time ordering. **Tests:** add buildSegments cases for 2+ day gaps (Mon -> Wed, Mon -> Fri) verifying placement and ordering. Cover the case where two actions on different calendar days share the same clock-time (would currently collapse). **Worktree:** /home/agent/workspaces/bolt-1267 (already exists). **Branch:** winston/bolt-1267-event-curve-preview-phase-1. **PR:** https://github.com/TextureHQ/mono/pull/12218 **Last commit:** f1c747a926 Run local checks per POST-PUSH-PROTOCOL before pushing. Resolve cursor thread with SHA reply on push.