[ermos]

Summary

• listEntries keeps the read collection in memory, per site and collection.
• The cache key is the head sha of the site branch, the collection settings and the open drafts (number, branch, updated_at). A list costs two light calls (pulls and branch head) instead of reading every file, which matters most on GitLab and Forgejo / Gitea (one call per entry).
• Any commit (from Sumigo or a direct push) or draft update invalidates it on the next list, no TTL.
• Draft schedules come from the database, so drafts are re-attached to the fresh pulls of each request.
• README, introduction and forges guide describe the cache.

Tests

• TestEntriesAreCachedUntilTheBranchMoves: a second list does not read the forge, a moved branch does.