697 - Data Sourcing for Sharing Excess

[marcbachan]

Pull Request

Change Summary

FYI: Claude helped quite a bit here in building out a basic CLI component and adding Supabase helper functions. Extra scrutiny on those is welcome.

Addresses #697. Introduces a standalone Python script that is designed to pull down events from a public Google Calendar, such as Sharing Excess, and normalize the retrieved events to be able to store them in the resources table in Supabase.

As the resources table does not have start/end date fields, these are pulled from the site and inserted into the description with some clear delimiters, like:

[[ start: 2026-03-10T15:00:00-04:00 | end: 2026-03-10T17:00:00-04:00 ]]

This allows us to do some post-processing/filtering to determine whether the event is "live" or not.

We can do this scrape periodically by using the LOOK_FORWARD_DAYS property to get all events for a specific window into the future, or just do this monthly in one of the PHLASK sessions or something. Not sure how we want to handle.

Change Reason

Billy summed this up quite nicely on #697. Essentially, we would like to be able to actively maintain "live" food sites posted by Sharing Excess and help them and us get the word out a little easier.

Verification [Optional]

Here is an example of a CSV debug output that we can get by using the basic CLI component that Claude helped write:

 python calendar_to_supabase.py --csv 

events.csv

These records can then be written to the DB either directly with CSV import in Supabase, or enter the credentials in the .env file here and run the script with the helper to write them to the resources table.

Related Issue: #697