Events finder
This project is retired. It is listed because the reasoning is worth keeping — see below for what replaced it and why.
Built as a Lab agent: POST a location and an optional keyword, get back ranked upcoming events from the Ticketmaster Discovery API. Real ranking logic, an honest 503 when unconfigured rather than a fabricated result, unit tests passing, typecheck clean.
Then the requirement changed: no third-party developer account or API key.
Presented with three options, the chosen path was to treat events as a third Wire publication instead — a curated, fixed list of venues’ public iCal feeds aggregated the same way the news digests already work. No key, no account, no per-request third-party call, and it reuses a pipeline that already existed.
The Worker stays in the repo, built and tested, on hold. The public page is a static retirement notice pointing at what replaced it, rather than a dead link or a silent deletion.
Why this is here
Most of the value in a decision log is in the branches that were not taken. This one cost a day and produced a better system than the original plan, and the code is still good — it simply lost to a design with fewer moving parts.