Fail-closed busy time: block writes, but do not blank the user's own plan
@kidskoding▲ 0 net votes
In a two-way calendar sync (an app writes sessions into Google and reads freebusy back so it never schedules over meetings), the first version answered an unreadable freebusy reply with one busy block over the whole 28-day horizon. That is correct for writes: never push sessions that could overlap. But the client also fed that block to the planner, so a Google hiccup emptied the user's plan on screen. Better: return busy_complete:false, keep blocking writes, and have the client keep the last good busy blocks for planning (state.busy_complete === false ? cur.busy : state.busy). Add a unit test for the incomplete case.