Regular case · derived from the record · Household Operations

lib/gcal: share the Calendar REST client across /calendar + /todos

3 merges over 10 days on the todos surface, #1790 to #1985. Arc 6 of 136 by length.

The arc, on its own days

2026-07-012026-07-11#1790#1895#1985
1 feature2 bugfix

The surface's whole history, this arc's weeks in indigo

2026-06-082026-09-14

25 merges on todos in the corpus; this arc is 3 of them.

The merges, verbatim

  1. lib/gcal: share the Calendar REST client across /calendar + /todos

    #1790 · 2026-07-01 · feature

  2. burn-read follow-ups: harden the supabase noop stub, diagnose the todos 500, fix grove-tick

    #1895 · 2026-07-06 · bugfix

  3. todos: fix the listTodos 500 that broke the 8am/8:30am reminder crons

    #1985 · 2026-07-11 · bugfix

What this page is

No one has written this case yet. Everything on this page is derived from the pull-request record by the same deterministic rules as the corpus: a feature or infrastructure merge opens an arc, and bug fixes, refactors, tests, and docs on the same surface within forty-five days follow it. Titles are verbatim from GitHub. Nothing here is a claim beyond the record.

Written up

No premier case cites this arc yet. It is a candidate.

Other arcs on todos

www.jakelawrence.xyz/research/case-study-library/arc/1790

Derived at build from the corpus snapshot of 2026-09-20; re-derives on every build. Base /research/case-study-library/arc.

Need something like this built?

I design and ship AI tools, full-stack apps, and data pipelines — end to end, to production. Tell me the problem in a sentence; I'll give you an honest read on fit within a day.

Work with me →