Gadoes bolts a cache onto Mike's outside-data calls

Gadoes added a result cache for the calls Mike makes out to external tools and data sources. The trick is a normaliser that recognises when two slightly different requests are really asking the same question, so the answer can be served from the cache instead of going back out over the wire. It's a tight piece of work - barely 230 lines of new code, with tests covering both the normaliser and the cache itself.

Alongside it, the fork looks to have moved its database migrations under Supabase, a hosted Postgres backend that a lot of small teams use to skip running their own infrastructure. The migration files now live in two places, which is a maintenance footgun worth knowing about if you're borrowing this work.