Skip to main content
Calendar and the integrated Tasks Calendar offer Recurring event in Create. It saves to canonical Tuturuuu Calendar. Daily, weekly, monthly and yearly rules support an interval and no end, an occurrence count, or an inclusive end date. Monthly and yearly rules offer an absolute day or the first, second, third, fourth or last selected weekdays; yearly rules also select a month. Absolute month days can skip missing dates or use the month’s last day. Choose a named time zone: local wall-clock times remain stable across DST. Nonexistent spring-forward slots are skipped; repeated fall-back times use the earlier instant. All-day end dates are exclusive midnight boundaries. Expansion visits at most 36,600 local dates from the anchor, including history needed to preserve counts and exception identities. Uncounted rules reject an oversized effective range before generating occurrences; an inclusive end date caps that range, while count rules may finish earlier and keep the same scan limit. Far-away original exception slots also contribute to the effective range. calendar-recurrence.test.ts covers early rejection and count/end-date behavior. Generated occurrences open a dedicated editor. Only this occurrence, Entire series, and This and following occurrences are explicit choices, defaulting to this occurrence. Requests preserve its immutable original slot and use the loaded series revision. Concurrent changes require an explicit reload. Whole-series editing uses the original anchor; future count rules retain remaining slots. Relative-weekday patterns can be edited, while details-only edits preserve imported week boundaries and month-end behavior. The anchor must remain an actual first occurrence; invalid changes are rejected rather than silently shifting it. Virtual occurrences never use ordinary event CRUD or drag mutation APIs. Dragging and resizing are disabled; use the scoped editor to move an occurrence. Native ranges revalidate in the background, retaining same-actor data through transport, throttling and temporary failures. Definitive access denial clears retained data. Reads and writes use verified actor lifetimes and separate workspace cache keys. Unchanged failed write intents reuse idempotency keys. Reopening or changing the workspace/account resets form state. Native Create defaults to canonical Tuturuuu Calendar. The connected-calendar editor below remains gated by provider admission and verified source capabilities; production admission is disabled until authenticated provider parity is proven. Regression evidence: native-recurrence-model.test.ts covers DST, validation, all-day boundaries, original identities, remaining counts and retry intent IDs; native-recurrence-dialog.test.tsx covers forms, permission and reset behavior; native-recurrence-pattern-model.test.ts and native-recurrence-pattern-fields.test.tsx cover relative weekday, yearly month, month-end and imported-rule preservation against Google and Outlook serializers; use-native-calendar-occurrences.test.tsx covers SWR and actor/permission fences; use-calendar-readonly.test.tsx proves virtual mutations cannot reach ordinary write APIs.

Unsupported provider rules

When the provider recurrence pilot is enabled, a complete, stable Google or Outlook snapshot with an unsupported rule becomes read-only. The exact raw master and exceptions are retained in an actor/source-bound encrypted journal; no approximate native rule is created. Calendar and integrated Tasks Calendar show a read-only badge and direct the user to the original calendar. Ordinary writes and scoped provider writes check authoritative private state, including when a delayed import loses its visible metadata marker. A previously supported canonical series is hidden rather than left visible with outdated dates. A subsequent supported snapshot restores the same series identity and removes verified legacy duplicates atomically. Publication compares both the captured master ETag and observation hash, so separately edited exceptions cannot overwrite a newer observation. Pending canonical or ordinary provider operations defer this transition; database admission rejects new legacy operations after the read-only state is published. Other calendars and unmatched provider identities remain untouched. The provider mutation pilot remains disabled by default. These checks do not establish authenticated Google/Outlook write parity or enable provider editing in the native creation dialog. Rollout still requires provider runtime verification. Regression evidence: calendar-provider-readonly.sql, provider inbound snapshot and service tests, readonly.test.ts, and calendar-provider-readonly.test.ts.

Recoverable connected-calendar editor

The shared Calendar recurrence editor checks actor-scoped provider capabilities before offering Google or Outlook calendars. Admission remains disabled by production default. An offered connection must belong to the current actor, have active credentials and outbound sync, an explicit writable provider role, and an enabled linked workspace calendar. These configuration capabilities do not prove provider access; each mutation still rechecks credentials and the fresh provider master. Imported provider series always use the provider operation API, including this-occurrence, entire-series and future changes. They never fall back to native series writes. Disabled admission, missing ownership or uncertain capabilities makes the imported series read-only. Native Tuturuuu series retain the native API. Pending provider changes keep fields frozen and expose a continue-synchronization action. The actor/workspace-scoped query cache retains the original intent; only its operation UUID is written to tab-scoped session storage before dispatch. No event content, tokens or account details are persisted there. Refreshing or reopening the dialog resumes that same UUID, and only an applied receipt closes the dialog and invalidates Calendar data. Applied provider receipts also revalidate the affected workspace’s database and provider event projections, including a creation resumed after a reload; pending receipts leave those views intact. If session storage is unavailable, new provider writes fail before dispatch. Cross-device operation history is not provided by this editor. Provider write admission still requires authenticated Google and Outlook parity evidence before production enablement. Regression coverage: provider capabilities.test.ts, operation-route tests, native-recurrence-provider-routing.test.tsx and use-provider-recurrence-operation.test.tsx cover source permissions, native fallback exclusion, ambiguous responses, dialog dismissal, tab reload recovery and actor separation.

Fresh conferences on future splits

New Google/Outlook future-update plans create the replacement series before trimming the original. Provider creation is checkpointed only after a fresh conference identity is available. Original join links and Google conference signatures are never cloned into the replacement: Google Meet uses a stable operation-derived createRequest; Outlook selects the original supported meeting provider only when the destination calendar explicitly permits it. Pending or failed conference generation preserves the untrimmed original and remains in the recoverable operation flow. Google regeneration uses at most two additional request identities on the same replacement event; an exhausted budget remains blocked for support, with no original-series trim. The database binds checkpoint roles atomically: the created replacement receipt belongs to the new canonical series, and the trim receipt advances the original binding. Older persisted trim-first plans retain their original order and receipt selection. New unsupported provider metadata, including Outlook attachments, remains rejected before reservation. A copied body or description that embeds the original meeting link is also rejected; generated meeting HTML blobs are not stripped or copied with stale credentials. Preflight detects raw, HTML character-reference and percent-encoded prior join identities; unrelated malformed percent escapes cannot suppress detection. Raw string values and parsed URL comparison also cover browser-normalized control characters, backslashes, protocol-relative links and dot segments. This follows the URL parsing contract. The original body remains unchanged, including benign encoded content; detection rejects the operation rather than sanitizing it. conference.test.ts and future-admission.test.ts cover encoded-link rejection before any plan reservation. Character references follow the HTML syntax contract. Production provider mutation admission stays disabled until authenticated provider and deployment evidence is complete; these tests do not constitute that evidence. Coverage: conference.test.ts, writer.test.ts, plan.test.ts, and apps/database/supabase/tests/calendar-provider-series.sql. Provider contracts: Google conference creation and Outlook calendar online meetings.

Calendar settings workspace identity

Calendar settings resolves route aliases such as personal before mounting integration sync or hours/timezone consumers. These consumers and their caches use the resolved workspace ID; resolution failures do not dispatch alias requests to UUID-only Calendar APIs. This applies to the standalone Calendar settings shell. Regression coverage: apps/calendar/src/components/settings/settings-dialog.test.tsx.

Truthful storage hints

The shared recurrence editor shows its native-storage hint only for canonical native events and native creation. Connected Google/Outlook editing or selected provider creation suppresses that hint, including when provider capabilities are unavailable. This display decision does not change source permissions, admission or the prohibition on native write fallback for provider events. Coverage: native-recurrence-provider-routing.test.tsx renders the actual recurrence fields for native, Google, Outlook and disabled-provider cases.

Outlook attendee privacy on future tails

For a verified organizing source, future splits retain the source’s explicit hideAttendees setting only when the fresh master supplies its attendee list. The encrypted plan carries this field without attendee response statuses. Creation and retained-event recovery both require an authoritative matching privacy receipt before trimming the original series. Non-organizers, malformed privacy settings and unsupported attachments remain blocked. This is source parity, with production admission still disabled; it does not prove invitation delivery or authenticated Outlook behavior. Graph v1 reference attachments expose read/delete metadata without a documented reference-creation/source-URL contract. Tuturuuu therefore does not copy attachment bytes or invent attachment references when splitting an Outlook series. Regression coverage: provider create-metadata.test.ts and writer.test.ts. Contract: Graph event attendee privacy and Graph reference attachments.

Future edit resets

Editing this and following occurrences starts a replacement tail and resets its previous moved, edited and cancelled exceptions. Native and connected-calendar editors show this consequence before Save. Selecting the first occurrence normalizes to a whole-series edit and does not show the tail-reset notice; single-occurrence and whole-series edits also omit it. The existing transaction preserves earlier exceptions. This notice changes no provider admission or write behavior. Regression coverage: native-recurrence-dialog.test.tsx checks notice visibility and preserves the original scope/revision/boundary submission assertions.

Single Calendar settings host

One dashboard-owned host mounts Calendar settings with the verified workspace ID. Responsive account menus forward their query intent without mounting their own settings providers. This prevents stacked inaccessible dialogs and duplicate connection checks while preserving settings from collapsed, expanded and mobile layouts. Settings content mounts only while the dialog is open. Provider accounts, synchronization and mutation admission are unchanged. Coverage: settings-dialog-host.test.tsx checks query intent, shortcut, close cleanup and workspace scoping; existing settings-dialog.test.tsx retains alias resolution.

Provider admission evidence

Production provider editing remains disabled by default. Source capabilities and mocked provider receipts are configuration and regression evidence, not proof that Google or Outlook accepted an operation or delivered invitations. Before admission, record the exact deployed source and migration results, then verify each provider with an authorized account and a dedicated test calendar:
  • Create and reload a series through Tuturuuu and the provider; inspect provider master identity, timezone, all-day boundaries and the recurring dates.
  • Edit and delete this occurrence, the whole series, and future occurrences; verify moved/cancelled original-slot identities, remaining counts, earlier exceptions, and the visible tail-reset warning.
  • Change the provider series externally and reconcile it back without duplicates; verify a richer unsupported rule stays read-only rather than being approximated.
  • Interrupt and resume an operation with the same persisted UUID; verify one provider result, correct source-bound receipt, and refreshed Calendar projections.
  • For supported conference splits, verify a fresh meeting identity and preserved attendee/privacy metadata before the original tail is trimmed. Check organizer and recipient behavior separately; a mutation response does not prove delivery.
  • Verify expired credentials, read-only calendars, revoked access and actor or workspace changes fail closed, with no native-write fallback or cross-actor data.
These checks have not been established by the focused source tests. Admission must not imply unrestricted provider parity: Outlook attachment-bearing future splits and bodies containing the prior conference’s join credentials remain unsupported and rejected before reservation. Tuturuuu neither clones attachment bytes nor strips generated meeting HTML to bypass these limits. Special Google event types and incomplete attendee snapshots also retain their explicit preflight restrictions. Native Tuturuuu recurrence remains independently usable.