Add provider-neutral verified zara-calendar service #500

Open
nsaspy wants to merge 0 commits from rage/10-calendar into main
Owner

Implements #10.

Recovered the existing RED contract onto canonical main after #63, then implemented a provider-neutral calendar domain with timezone-aware bounded search, free/busy, conflict explanations, read-only scheduling suggestions, recurrence/attendee/reminder preservation, and explicit expected-version mutations.

Create/update/delete require provider acknowledgement plus fresh observed state; rejected or stale mutations never claim success. Attendee changes are explicit patches only. Without a configured provider the plugin reports calendar-backend-not-configured instead of fabricating events.

Published through plugins.json, so the generated pinned-Zara compatibility, registry, package, runtime-layout, plugin test, and Nix gates cover it. Tests use only a fake backend and require no network/account/credentials.

Zara Core remains authoritative for normal authorization/approval.

Implements #10. Recovered the existing RED contract onto canonical `main` after #63, then implemented a provider-neutral calendar domain with timezone-aware bounded search, free/busy, conflict explanations, read-only scheduling suggestions, recurrence/attendee/reminder preservation, and explicit expected-version mutations. Create/update/delete require provider acknowledgement plus fresh observed state; rejected or stale mutations never claim success. Attendee changes are explicit patches only. Without a configured provider the plugin reports `calendar-backend-not-configured` instead of fabricating events. Published through `plugins.json`, so the generated pinned-Zara compatibility, registry, package, runtime-layout, plugin test, and Nix gates cover it. Tests use only a fake backend and require no network/account/credentials. Zara Core remains authoritative for normal authorization/approval.
Some checks failed
CI / test (pull_request) Failing after 19s
This branch is already included in the target branch. There is nothing to merge.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin rage/10-calendar:rage/10-calendar
git switch rage/10-calendar

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff rage/10-calendar
git switch rage/10-calendar
git rebase main
git switch main
git merge --ff-only rage/10-calendar
git switch rage/10-calendar
git rebase main
git switch main
git merge --no-ff rage/10-calendar
git switch main
git merge --squash rage/10-calendar
git switch main
git merge --ff-only rage/10-calendar
git switch main
git merge rage/10-calendar
git push origin main
Sign in to join this conversation.
No description provided.