feat(calendar): opt-in durable UUID recovery for private Google Calendar projections - #2293
Open
martin-forge wants to merge 4 commits into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Google task events can go missing, duplicate, or link to an old path after task files move or the local event index is lost. A damaged or missing task file must not make recovery delete its Calendar event.
Solution
Add an optional Rebuild private task projections setting, off by default. Exported tasks receive a persistent UUID. Startup and the existing recovery loop use it to repair event links, missing events and stale details.
Cleanup requires a readable task with the same UUID and either a retirement marker or an identical surviving event. Missing IDs and unreadable files preserve events. The same check protects queued retries, and deletion refuses a provider revision that changed after verification. Unrelated and invited events remain untouched.
Testing
build:testpass. Live Obsidian checks against disposable Google events confirm that malformed frontmatter and missing task IDs preserve the events.