Skip to content

Completeness overlays: Google Tasks, GitHub Issues; fixed-read CRUD Causality v2 for Tasks and Calendar - #534

Merged
michielbdejong merged 5 commits into
mainfrom
claude/completeness-overlays-v2
Oct 14, 2026
Merged

michielbdejong merged 5 commits into
mainfrom
claude/completeness-overlays-v2

Conversation

@michielbdejong

Copy link
Copy Markdown
Contributor

Collection completeness overlays: Google Tasks and GitHub Issues, with fixed-read CRUD Causality v2

The completeness declarations were held on branches since 2026-10-08/09, waiting for a syncables consumer of notFound. Main's syncables now reads notFound, gone and parentAbsent, so they are published here. No spec change is needed.

None of these overlays is selected by a catalog yet; a later dated catalog (catalog-0.22, held) selects them.

Google Tasks crud-causality-v2 (fixed read)

  • The tasks collection always sends showCompleted=true and showHidden=true.
  • Its collection envelopes carry emptyWhenAbsent, as Tasks pagination v2 does.
  • The Tasks completeness overlay depends on this file.

Google Calendar app-crud-causality-v2 (fixed read)

  • The events read sends showDeleted=true and singleEvents=false.
  • The event update now declares mode: patch with jsonMergePatch. This fixes v1's missing mode (CRUD Causality rule 5).

Google Tasks completeness

  • Task lists and tasks: absent: removed, notFound: unavailable.
  • Tasks also: parentAbsent: unavailable, and a read tombstone deleted: true.
  • Evidence is the pinned OAD's own descriptions:
    • tasklists.list: "Returns all the authenticated user's task lists";
    • Task.deleted: "Flag indicating whether the task has been deleted".
  • Google doesn't document what a 404 means, so it is declared unavailable. No gone is declared, so a 410 is unavailable as well (Collection Completeness 0.3.0).

GitHub Issues completeness

  • Issues and comments: absent: removed, notFound: unavailable. Comments also: parentAbsent: unavailable.
  • No gone. GitHub's "Get an issue" says a 410 can mean a deletion the caller can see, but every issue answers 410 when the repository's issues are turned off.

Todoist is left out. Its API reference didn't render the task fields or the single-task read, and the pinned OAD is an authored subset with no descriptions.

Tests

  • test_crud_fixed_query_overlays.py
  • test_completeness_overlays.py: composed with Tasks pagination v2, including a 410 case.
  • test_github_issues_completeness.py
  • test_crud_reads_in_catalogs, test_oad_pins and the pin validator (510 overlays) pass.

README: new "Collections with fixed reads" and "Collection completeness" sections.

🤖 Generated with Claude Code

michielbdejong and others added 5 commits October 13, 2026 00:59
…e Tasks, Google Calendar, GitHub Issues)

Held since 2026-10-08/09 for a syncables notFound consumer, which main now
has (notFound, gone, parentAbsent).
- Google Tasks crud-causality v2 (listQuery showCompleted/showHidden,
  collection envelopes with emptyWhenAbsent) and Google Calendar
  app-crud-causality v2 (listQuery showDeleted/singleEvents; the event
  update's mode patch, which v1 lacks against rule 5, with jsonMergePatch).
- Google Tasks completeness (task lists and tasks absent removed, notFound
  unavailable; tasks parentAbsent; read tombstone deleted true), checked
  against Collection Completeness 0.3.0 (no gone, so a 410 is unavailable).
- GitHub Issues completeness (issues and comments absent removed,
  notFound unavailable, no gone, since a 410 can be disabled issues;
  comments parentAbsent).
A drafted Todoist overlay is left out: its reference could not be read
and its pinned OAD has no descriptions. No dated catalog selects them.
Tests: test_crud_fixed_query_overlays.py, test_completeness_overlays.py,
test_github_issues_completeness.py.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The GitHub Issues completeness test tolerates exactly the published
crud-causality v1 findings that #524's validator reports (patchFormat
merge; label writes without a patchFormat), and runs clean against it.
Descriptions: Google Tasks' tasks leave out assigned tasks (showAssigned,
default false, not in the pinned OAD); GitHub's page-number paging can
skip an issue deleted or transferred during a read, which then stays
unconfirmed until its GET; Calendar's events leave out hidden invitations
(showHiddenInvitations, default false). The README rows match.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@michielbdejong
michielbdejong merged commit 6dc3112 into main Oct 14, 2026
22 checks passed
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>
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