Skip to content

Google Calendar events completeness overlay; why not Todoist or Discord - #586

Merged
michielbdejong merged 6 commits into
mainfrom
claude/calendar-events-completeness
Oct 15, 2026
Merged

michielbdejong merged 6 commits into
mainfrom
claude/calendar-events-completeness

Conversation

@michielbdejong

@michielbdejong michielbdejong commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

Google Calendar events completeness overlay; why not Todoist or Discord

overlays/APIs/googleapis.com/calendar/v3/completeness-32237fa5…-overlay.yaml declares, on the events collection:

  • notFound: unavailable. A deleted event stays readable: the pinned OAD says of cancelled events "The get method always returns them", and the read-tombstone overlays turn that 2xx into a deletion. The Calendar errors guide gives "has never existed" and "a calendar that the user can not access" as causes of a 404. Today a consumer takes that 404 as a deletion (the default).
  • absent: removed. An event can leave a calendar's list without being deleted, for example when moved with events.move or when the user's access changes. With showDeleted=true, a deletion shows up as a cancelled item, not as an absence.

Not declared

  • gone: the guide's 410s are about sync tokens and repeated deletes, not reads. A 410 on a read is classified like a 404, as unavailable.
  • parentAbsent.

Not verified: whether cancelled events are ever purged, and what their read answers then.

Test: overlays/tests/test_calendar_events_completeness.py.

  • It composes the overlay with the catalog's Calendar overlays, read-tombstone-v2 and each crud overlay on main, in either order, and runs both validators.
  • It classifies reads: a 2xx cancelled answer is deleted, a 2xx confirmed answer is present, and 404 and 410 are unavailable.
  • It checks the pinned wording, that only x-completeness is added, and that no catalog selects the overlay.

Why not Todoist or Discord (recorded in overlays/README.md)

  • Discord: the only catalog collection, /users/@me/guilds, has no item read in the crud overlay, so an absent guild could never be settled.
  • Todoist: the evidence is too thin. The pinned OAD is an authored subset, and the docs don't say which tasks the lists return, or what a read answers for a deleted, completed or archived item.

🤖 Generated with Claude Code

michielbdejong and others added 3 commits October 14, 2026 12:02
…ilable)

A deleted event stays readable (get answers status cancelled, the read
tombstone), and the errors guide gives "never existed" and an inaccessible
calendar as a 404's causes, so notFound is unavailable; an event can leave
a calendar's list without being deleted, so absence is removed. No gone,
no parentAbsent. Tested with each Calendar crud overlay and read-tombstone
v2. The README also records why Todoist and Discord get no completeness
overlay. Not selected by a dated catalog.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…eview wording

The test decides a 2xx answer with Deletion Feeds' read_tombstone, which
honours except: a cancelled exception is present under read-tombstone-v2
and deleted under the superseded, unselected v1. It composes with the list
tombstones and the deletion feed and runs the Deletion Feeds validator.

Overlay and README: a move can leave a cancelled remnant behind, which
reads as a deletion from the source calendar where a tombstone overlay is
selected and as an absence under the catalogs' read; removed stays safe.
Deleted events "will eventually disappear"; only their read afterwards is
unverified. The Todoist note says only the 404/410 meaning and the
deleted, completed or archived reads are undocumented.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
michielbdejong and others added 2 commits October 15, 2026 17:22
…s-completeness

# Conflicts:
#	overlays/README.md
- The README's conflict with main resolved: #617's Todoist row joins the
  table (four overlays), the old Todoist paragraph goes, the Discord
  sentence stays, and the test list adds the Calendar and Todoist tests.
- "An event can leave the list without being deleted (access changed)"
  had no source: overlay and README now call it assumed, not documented.
- The overlay says the dated catalogs select neither tombstone overlay, so
  there a deletion or a move is an absence.
- The errors guide's two 404 examples are list items; the overlay quotes
  them separately instead of joining them with a semicolon.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
michielbdejong added a commit that referenced this pull request Oct 15, 2026
- Merged main: #617's Todoist row joins the table (four overlays with
  this one; five once #586 lands), and the test list names both.
- The "Issues" quote is verbatim now (double quotes, as the docs).
- "Issues are disabled for this repo" is in neither the docs nor the
  pinned OAD: the overlay cites Create an issue's "If issues are disabled
  in the repository, the API returns a 410 Gone status." and marks a read's
  410 and its body as not verified; the test relies on no body text. The
  README notes that #534's published GitHub Issues overlay makes the same
  claim (declaration unaffected: a 410 is unavailable either way).
- Cites Using pagination in the REST API for page-number paging.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michielbdejong
michielbdejong merged commit 18e4251 into main Oct 15, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant